Operation Evidence

An Operation Receipt belongs to an opportunity and identifies a guarded action by operation key. It records the action, expected revision, occurrence date and result state. Pending, Completed, Failed and needs review make different outcomes visible. External and effect references can connect a receipt to an observed result, while a failure reason explains a discrepancy. A reviewer can use that trail to check whether an action actually had the local effect it claimed.

An attachment is a separate evidence record with a title, file, upload date, evidence type, visibility and uploader. Internal or Shared visibility helps the team choose who should see supporting material. Attachments can hold the proposal or customer acceptance evidence that a Sales Manager needs when assessing a decision. The file stays linked to its parent opportunity, so a closed pursuit retains the material behind its outcome.

• Action receipt. Each guarded action carries an operation key and expected revision for comparison with its recorded effect.
• Result state. A receipt’s state distinguishes pending work, confirmed completion, a failure and a case needing review.
• Supporting file. Attachments identify their uploader, evidence type and visibility beside the opportunity they support.

Imagine an owner submits a proposal after a customer call. The call outcome is recorded as activity, and the proposal file is attached with the right visibility. The guarded action has a receipt with the expected opportunity revision. A Sales Manager can inspect the decision and receipt together. If the local effect does not match the declared revision, the discrepancy belongs in the receipt history rather than being hidden by a completed label.

Decide which evidence types the team uses and when a file is Shared. Establish who checks a receipt in needs review and how the failure reason should describe the mismatch. Agree how external references are captured when another system confirms an action. The operation key should be stable for a retried request so the same action is not counted as a separate decision. Managers should agree what local evidence is enough to mark a receipt Completed.

Keep the opportunity as the anchor for both kinds of evidence. An Auditor reading an outcome should be able to reach the activity, attachments, review decision and receipts from the same parent. Where another system performs downstream work, the connection should provide an actual reference before anyone interprets the receipt as confirmation of that work.

Attach a proposal file to an open opportunity and choose Internal or Shared visibility deliberately. Record a guarded action and inspect its receipt for operation key, expected revision and result state. Have a Sales Manager compare the receipt with the parent opportunity and decision. Rehearse a mismatch: the manager should see the discrepancy in needs review with a useful reason. Ask an Auditor to follow the record back to the supporting attachment and activity.

• Receipts Needing Review — Guarded actions whose recorded effect needs a manager’s inspection.
• Review Decision Log — The reviewer and source revision behind the related decision.

See evidence reconciliation and integrations.