Share a reviewable result without assuming source-link access

A working link for the author is not enough

Plan the handoff through an approved access route so a reviewable workbook does not become a collection of inaccessible references.

ParseMill exports reviewed invoices to Excel with separate summaries, line items, sources and review status. You can import an XLSX or CSV template and save a client setup. Run a real invoice through to the final workbook and check it in the application that receives your work.

Separate data access from evidence access. Permission to receive an extracted register does not automatically imply permission to receive every source document. Agree an appropriate review path with the source owner when those permissions differ.

Use a recipient-access card

These examples describe access outcomes, not instructions to broaden permissions. Keep unrelated documents out of the package. If access cannot be provided, state the limitation and the specific review activity the recipient can still perform.

W3C: Data on the Web Best Practices discusses access and versioning in data publication. A resolvable reference should identify the intended version, not merely a mutable location with the right filename.

Test the complete evidence path

1. List the source documents required to review the shared records. Confirm the recipient’s authorized scope and the applicable sharing method.
2. Open representative references using the intended recipient access context. Check document identity, revision, physical page and observation.
3. Replace nonportable paths with a documented manifest or authorized shared location. Preserve stable record keys so the references remain attached to the data.
4. Include an access note with the deliverable: available evidence, known limitations, owner contact and the process for requesting permitted clarification.

W3C: Provenance model primer separates source entities from derived outputs. The handoff should preserve that relationship even when the source and register have different access arrangements.

Avoid access fixes that obscure evidence

Uploading a new copy with an unchanged filename can lose version history. A broad folder link can expose unrelated material or make the correct report hard to find. Use the narrow authorized package and record exactly which source version supports the shared rows.

Do not call a source reference verified merely because a login page opens. The recipient must reach the actual document and observation required by the review. Record denied or unavailable access as a separate handoff issue.

Confirm a reviewable delivery

For the fixture, only the authorized shared source is immediately reviewable. The other cases require a documented access resolution or an explicit limitation. The recipient should know which evidence they can inspect and how to pursue the rest.

When sharing ParseMill output, include a recipient-access check alongside value review. It helps turn source references into usable evidence rather than links that work only for the person who created the export.