Skip to content
GoodCompany
Get started

GUIDE 09 / CLIENTS AND DELIVERY

Hand over the context, not just the task.

A good handoff lets someone start without reconstructing the conversation. Put the outcome, the supporting material and the decision they need in the same place.

By GoodCompany2 min readClients · Projects · Tasks

WHAT YOU’LL TAKE AWAY

A useful next step,
not another open tab.

  • One person owns the next action.
  • The expected result is written down.
  • The source conversation and files stay findable.

Prepare the workspace

The next owner must be a member with access to the task and relevant sources. Check sharing on mailboxes, calendars, Sidekick conversations and Vault items separately.

Example: North Studio

Maya hands Willow Bakery’s website handover to Leo. She attaches the approved copy, names the outstanding client decision and sets a task deadline.

Write the result before assigning the work

  1. Open the client’s project and find the task, or create one in Tasks linked to that client and project.
  2. Use Edit task to set the responsible person and due date. Write a title that describes the action: ‘Send the revised proposal’, not ‘Proposal’.
  3. Add a short definition of done in the description and put smaller checks in the checklist. Mention any decision the next owner must get before proceeding.

Keep the evidence beside the action

  1. Open the task’s Documents area and upload the files the next owner needs. Use linked emails to return to the original request when a link is already present.
  2. Add a comment with what has changed, what is still uncertain and who should review the outcome.
  3. For a delivery checkpoint, open the project milestone and review its owner, linked tasks and acceptance requirements separately. A finished task does not automatically mean the client has accepted the milestone.

Make room for one clarifying question

Ask the next owner to review the handoff and leave a comment if something is missing. Assigning work tells the app who owns it; it does not prove that person has read or accepted the brief.

Keep the handoff in the project rather than spreading revised instructions across unrelated messages. When the brief changes, update the task and leave a comment explaining the change.

Check the outcome

Have Leo open the task and each required source in his own account. Record any missing access and fix only the necessary sharing or role setting.

Avoid a common mistake

Assigning a task does not share every linked resource or prove its assignee has read it. Do not paste a password into the handoff; use a deliberately shared Vault entry.

A handoff you can copy

Adapt this starter in a project note or document. Copying it does not change your workspace. 

Outcome needed:

Next owner:

Due date and why it matters:

Done means:
- 

Context / source conversation:

Supporting files:

Open question or blocker:

Who should review it:

Ready to put it into practice?

A quick checklist for this visit. Your company records stay unchanged.

0 of 7 steps reviewed

Further reading

Need help with a specific screen? These articles explain where to click, which fields to fill in and what happens next.

NEXT GUIDE

Make the next file easy to find.

You should not need to remember who uploaded a file to find it again. A consistent name and the right project context do more than another deeply nested folder.

Continue

GOOD QUESTIONS

A few specifics.

Does assigning a task grant someone access to all project files?

No. Their role and access rules still apply. Check their access before relying on a linked record or file in a handoff.

Can I follow this guide on a phone?

Yes. Use More to reach Tasks, Clients or Documents. The same records and permissions apply; folders and extra filters may be inside expandable controls on smaller screens.