At a glance
Use this workflow when a new project needs a clear internal brief. It prepares a handoff for review; it does not create tasks, update a CRM, or send the client an email.
Start with the agreement and the latest conversation
A project handoff should tell the delivery team what was agreed and what still needs a decision. Use the current agreement or scope document in Drive and the relevant kickoff conversation in Gmail. Name the client and reporting cutoff so an older proposal does not become the source of truth.
Connect Gmail and Google Drive separately in a private Geniusly Slack DM. Give the exact document title and enough thread details to distinguish the intended client. If a document cannot be read, provide an accessible text export and record its version. Start with the Gmail connection guide if email is not connected.
- Current agreement and any approved scope changes.
- Kickoff email conversation and named client approver.
- Source dates and the point through which the brief should be current.
- Your rule for resolving conflicting sources, if one exists.
Ask for a delivery handoff in Slack
Prepare the Northstar project handoff using the current Northstar agreement in Drive and the October kickoff email conversation in Gmail. Separate agreed deliverables, exclusions, client inputs, dependencies, recorded owners and dates, and open questions. Link each factual item to its source. Flag disagreements. Label missing information as unknown and suggested next steps as proposals. Return the brief in this Slack conversation and prepare a Markdown file.
This is an illustrative instruction. It is not a completed customer task.
Ask for exclusions as well as deliverables. A polished summary that leaves out an explicit exclusion can cause a delivery team to assume work was sold when it was not. If the sources disagree about scope, keep both statements visible for review.
A handoff format your team can review
Agreed scope
Homepage refresh and onboarding email copy. Paid media production is excluded. [D1: sample agreement]
Client inputs
Brand assets and one named approver are required before delivery planning. The kickoff email names Alex as approver; no asset delivery date is recorded. [D1, G1: sample kickoff thread]
Dependencies and unknowns
The email requests a November launch, but the agreement does not establish a launch date. Treat the date as a request requiring confirmation. Internal delivery owner: unknown. [G1, D1]
Proposed next step
Confirm the asset date and internal owner before promising a launch window. This is a suggestion, not an agreed commitment.
All facts above are invented sample content. In your own task, source references should point to actual accessible material. The useful distinction is between a recorded commitment, a missing detail, and a suggested action.
Review the handoff before your team uses it
- Check the source version. Confirm that the agreement and kickoff thread belong to the intended project and include any approved changes.
- Check scope and exclusions. Compare every deliverable and exclusion with the agreement. Resolve conflicts with the account owner.
- Confirm owners and dates. Keep unrecorded values marked unknown. Confirm proposed assignments with your team.
- Share through your normal process. Review the brief, then copy it or use the prepared file where your team manages delivery.
This workflow reads connected context and prepares work. It does not create project records, edit documents, send Gmail messages, or complete a sales-to-delivery automation. If your process requires those actions, assess that requirement separately.
Choose the next workflow for the account
Use the weekly client brief once the account is in delivery, or the client follow-up workflow when you need reply text for a missing input. For a cross-project internal report, use the weekly operations brief.
Questions & answers
What should an AI project handoff include?
Agreed scope and exclusions, client inputs, dependencies, recorded owners and dates, unresolved questions, and references to the source material. Keep suggestions separate from agreed commitments.
Can Geniusly use my CRM directly?
This guide uses Gmail and Drive. Do not assume a native CRM connection. If your source lives elsewhere, provide an accessible supported export and include its date.
Will Geniusly create tasks or update the agreement?
No. This workflow prepares the handoff in Slack and can prepare a file. Connected-app record writes are not enabled in the current release.
Are these measured customer results?
No. The request and output are illustrative examples. No customer result, time saving, or comparative accuracy is established here.