Activities and evidence

A manufacturing sales record needs to explain what the customer asked for and what the owner actually confirmed. The activity log captures a Call, Meeting, Email or Task with its outcome, due date and completion date against the opportunity. The activity line number orders the entries, while the revision identifies the opportunity version associated with the activity. An empty outcome does not explain a qualification or customer decision.

Each supporting file carries a title and evidence type with its upload date and uploader. Classify its visibility as Internal or Shared. Relationship Owner can then point a reviewer to the acceptance evidence, drawing correspondence or proposal scope relevant to the case. Enforce the visibility classification during configuration and agree who may access Shared files before making them available.

• Customer activity. Relationship Owner logs an actual conversation or task outcome. Configure the activity action to use the next activity line number and current revision, and reject an empty outcome or a closed opportunity.
• Evidence context. Attach files to the intended linked opportunity and choose an evidence type that explains their purpose. Retain the uploader identity so Auditor can distinguish the supporting evidence from the later review decision.
• Follow-up review. Use due date and completion date together when discussing outstanding work. Inspect the recorded completion and outcome before treating a past-due entry as unfinished work.

Agree when a call is complete enough to log, how an email outcome is summarized and which evidence types the team will use. Decide who can read Internal and Shared files within organization scope. File access must follow the caller’s actual permission and opportunity scope even when someone knows an attachment identifier.

Log activity while the opportunity remains open. Rehearse the refusal of new entries after a deal is marked Won or Lost. Keep the original conversation available to the reviewer when later evidence changes the working scope. Decide how the owner summarizes a customer email and which file supports the summary, so the next person can distinguish the customer’s answer from the owner’s interpretation.

Relationship Owner logs a procurement call confirming the required material and the date of the next discussion. A later email provides a different drawing revision. The owner attaches the file to the opportunity, identifies its evidence type and records an outcome that explains the changed scope rather than editing the earlier call into a different conversation.

Sales Manager reviews the submitted inquiry using the applicable evidence and the current revision. Auditor can read the earlier call and the later attachment within authorized scope. During rehearsal, try to create an activity with no outcome, repeat the same qualification operation and attempt to fetch an Internal file from an unrelated organization. The first action must be refused, the replay must avoid a duplicate effect and the out-of-scope access must be denied.

• Activities due — Review dated activity entries alongside completion date and outcome to determine the actual follow-up position.
• My uploaded evidence — Inspect files linked by the signed-in uploader, with evidence classification and visibility shown.

Opportunity qualification consumes qualification evidence. Proposal to customer outcome uses verified acceptance or loss evidence. Review permissions before making files available to the pilot team.