Sharing and execution

A reviewed packet can carry a sharing expiry, content hash and revision. The Sharing Manager checks those details against the approved decision before the packet is marked Shared. The packet status expresses the business outcome. The operation record explains what was attempted, which revision was used and what evidence came back from an external destination.

An operation run holds an operation key, source revision and input hash. Its ordered steps hold input and output references and can retain an external receipt identifier, receipt date and attachment. An execution attempt records its own start, finish, provider reference and failure reason. These records help the team distinguish a completed share from a request that was queued, failed or left uncertain.

• Scope. Check the parcel, document type and expiry on the packet before sending a scoped document set.
• Run. Record the exact source revision and steps so the result can be traced to the reviewed material.
• Receipt. Compare the external reference and receipt evidence with the operation before confirming the packet outcome.

Choose the external document delivery destination and agree what its receipt means. Decide where receipt attachments are stored, how provider references are reconciled and who can retry an uncertain attempt. The team should establish how the same operation key prevents duplicate delivery. It should also decide how long a sharing scope remains valid and who can archive a packet after the business work is finished.

A failed attempt needs a reason the operator can investigate. An uncertain attempt should leave its run at reconciliation required while the manager checks the original operation key and provider reference. A repeated request with that key must not cause a second delivery. Keeping the run and attempt records separate makes it possible to see the intended operation and each attempt to carry it out.

The Sharing Manager opens a reviewed packet for a property closing. They confirm that the decision is Approved for the current revision and that the expiry still covers the intended share. They record the run and its steps, then inspect the delivery receipt. If the provider confirms receipt, the packet can move to Shared with the evidence linked to the operation. If the provider times out, the attempt remains uncertain; the manager checks the original provider reference before trying again. The team can explain why the packet was or was not shared without relying on a message in someone’s inbox.

• Reviewed Packets for Sharing — Packets at reviewed status waiting for a scope and receipt check.
• Runs Needing Reconciliation — Operations whose external outcome needs investigation.
• Shared Packets — Packets with a recorded shared status and expiry.

See review and sharing and archive and history.