Use connected records, team mentions and assigned actions to make service reviews easier to continue across locations. For remote teams, check record mentions, action owners, due dates and documented review outcomes. Use current source information rather than an assumed value.

Which information should remote teams collect for a review?

Start with an inventory of the services and operational assets relevant to your work. The scenario on this page concerns a distributed colleague handing off a renewal review through a record mention. The person responsible for that work should confirm the details with the appropriate workspace owner.

How should remote teams separate operating ownership from approval?

Record who can verify information, approve a decision and complete the next action. Missing information about record mentions, action owners, due dates and documented review outcomes should be corrected in the relevant source section before relying on a result.

Which source records should remote teams keep connected?

Connect upcoming renewals and commitments to a visible review workflow. Keep the outcome of a distributed colleague handing off a renewal review through a record mention attached to its source record, with the responsible person and the completed action.

How should remote teams distinguish estimated and confirmed costs?

Maintain the context behind a record so another teammate can continue without rebuilding it. Remote teams focuses on use connected records, team mentions and assigned actions to make service reviews easier to continue across locations. The page links to the sections relevant to that purpose.