Relationship Activities

The Relationship Owner logs each call, meeting, email or task against its parent opportunity. A due date records promised follow-up, a completion date records that work happened, and the outcome explains what changed. Line number and revision help distinguish successive entries. The activity log gives the Sales Manager a way to inspect how the opportunity moved without turning a phone call into a new client account or a new matter intake.

An activity belongs to an opportunity, so a call about one proposed engagement does not become a general note on the client account. A due date marks promised follow-up; a completion date and outcome show what the owner actually did.

• Prepare. Relationship Owner establishes the record and checks the links to the relevant firm, person or opportunity.
• Work. The assigned team member records the event or decision where it belongs, using the available status, date and evidence fields.
• Review. Sales Manager and Auditor inspect the record in context, including the parent opportunity and any earlier decision or exception.

The team should use one parent opportunity for one prospective engagement. Related activities, intake requests, review decisions, attachments and operation receipts refer to that parent. This makes a later handoff easier to follow: the recipient can open the opportunity and then inspect the specific record that explains the next action.

Agree which conversations need a dated follow-up, what a useful outcome note contains, and who closes an overdue task. Pick a real prospective engagement for the first rehearsal. Decide who may make routine corrections, who records a review result and how the team handles a returned or rejected item. Keep those decisions in the operating procedure so an owner does not have to infer them from a status label.

Also decide how the team names records and documents. A short, descriptive subject or title should identify the matter without relying on a private message thread. Confirm which organization the record belongs to before the first import, then test access with the same user accounts the team will use in daily work.

After a meeting about a proposed engagement, the owner records the meeting and its outcome. A task due the following week can capture the promised follow-up. Once the follow-up is complete, its completion date and outcome become part of the same opportunity history. If the proposal changes, the owner updates the opportunity separately so the activity record remains a trace of the conversation.

Ask the receiving teammate to find the current state from the record itself. They should be able to identify the owner, the next decision and the history behind it. If an attachment, intake or receipt changes the interpretation, open that child record rather than summarizing it from memory. This rehearsal exposes ambiguous ownership and missing operating conventions before the team expands to more matters.

• Due relationship activities — Calls, meetings, emails and tasks due for follow-up.
• My opportunities — Assigned prospects whose conversations need an owner’s next action.

Start with Opportunity Pipeline, then use the engagement process to rehearse activity and pipeline. The data model shows the exact record links, and roles identifies the team members who work at each step.