Boutique consulting and design agencies keep client work in Notion docs and Asana tasks. The partner question is not "where is the doc," it is "who approved the version the client sees, and what did the drafting agent decide on the way there." A Notion page does not answer that. A Dock row does.
This pattern sits inside our consulting and agencies pillar next to the research and design rails.
Notion and Asana stay the system of record for the raw data. Dock is the system of record for what the AGENT INTERPRETS. Each Dock row carries a pointer back to the platform record, agent identity, decision, reviewer, and timestamp. The agent re-fetches platform data via fresh API reads when it needs current state.
The Client Deliverables surface
| Engagement | Notion doc | Asana task | Agent draft summary | Agent identity | Partner reviewer | Sign-off | Timestamp |
|---|---|---|---|---|---|---|---|
| Acme market entry | notion.so/.../acme-phase-1 | asana #4711 | Recommends EU-first launch; 3 risk flags on regulatory | strategy-agent@firm | partner.lee | Approved with edits | 2026-05-28 14:02 |
| Northwind brand refresh | notion.so/.../northwind-brand | asana #4722 | Final color system + 12 token decisions logged | brand-agent@firm | partner.ortiz | Approved | 2026-05-29 09:11 |
| Globex ops audit | notion.so/.../globex-audit | asana #4730 | 7 findings; 2 marked client-sensitive, pulled from exec summary | audit-agent@firm | partner.lee | Returned for revision | 2026-05-29 16:40 |
The Notion URL is the pointer. The summary, identity, and sign-off are the interpretation. If the partner asks "why did we soften finding 4," the row links to the agent draft, the redline, and the named reviewer who accepted it. We cover the identity column in detail in agent identity.
One worked workflow: draft to partner sign-off
A senior associate asks strategy-agent to assemble the Acme phase-1 deliverable. The agent reads the Notion working doc, pulls the linked Asana subtasks, and writes a one-paragraph interpretation into the Dock row: thesis, three risks, two open questions. It does not edit the Notion doc. Partner Lee opens the row, leaves a comment on the second risk, and flips Sign-off to Approved with edits. The Asana task advances to "client review." Two weeks later, when the client disputes a recommendation, the row still shows who interpreted what, and when. Same cycle as the marketing rail.
Why it matters
Agencies bill on judgment. Notion proves a document exists. Asana proves a task moved. Neither proves a partner read the agent's interpretation before it left the building. The Dock row is what partners defend in a client review, and what a junior consultant points to when asked "why this version." Credential rotation when an associate leaves is handled by the agent identity lifecycle.
Notion positions itself as the AI workspace where docs, wikis, and projects live together 1. That is the right place for the artifact, not for the decision log. Source Global Research tracks how consulting firms absorb AI into delivery, and the consistent finding is that partner-level accountability is what clients pay for 2.
Try the pattern
Spin up a Client Deliverables surface in Dock, point each row at one Notion doc and one Asana task, and require a partner sign-off column before the engagement closes.
FAQ
Does the agent edit the Notion doc directly? No. The agent reads Notion via fresh API calls and writes its interpretation into the Dock row. The Notion doc stays human-authored.
What if Asana is the source of record instead of Notion? Same pattern. The row carries an Asana pointer in addition to or instead of the Notion link. The interpretation column is unchanged.
How is this different from a Notion database of approvals? A Notion approval database is still a doc. It does not enforce agent identity or separate "what the agent decided" from "what the human wrote." Dock does both.
Can the client see the Dock row? No. The client sees the Notion deliverable. The row is internal evidence for partner review and post-engagement audit.
