The Co-Pilot Structure

Four tools. One system. Real workflows at a high-net-worth insurance advisory practice.

This is what Mollick's framework looks like when you actually build it. Every concept on the previous page has a concrete implementation here.

Scroll

The real work already lives somewhere else

Client conversations live in Gmail. Documents live in Google Drive. The system doesn't try to replace or duplicate any of that. Instead, it creates a lightweight coordination layer that answers two questions:

1

What exists?

The Task — a routing slip that points to where the work lives across email, documents, and other systems.

2

What should we do about it?

The Work Unit — an advisory calculation about priority and timing that runs independently of human judgment.

Each tool does exactly one job

No custom software. No expensive platforms. Four tools that most knowledge workers already have access to, wired together through a structured methodology.

Airtable

The brain

Two linked tables — Tasks and Work Units — form the coordination layer. Tasks are routing slips pointing to where work lives. Work Units are the flight computer: date-driven formulas that compute priority independently of human judgment. No external scripts, no code — just native Airtable formulas running the escalation ladder, activation checks, and data hygiene enforcement.

What it holds
Tasks (routing slips) Work Units (priority engine) Effective Priority formula Activation Step formula Data Hygiene Flag Action Briefings Filtered queue views

Gmail

The context

Client conversations, carrier correspondence, internal threads — the actual substance of every engagement lives in email. The system doesn't replicate it. Every Task carries a unique Task Number that works as a search key: paste it into Gmail and land on the exact thread. Email is the source of truth for what happened. The system tells you what to do about it.

How it connects
Task Number = Gmail search key Thread history preserved No email forwarding or copying

Google Drive

The documents

Quotes, proposals, policy documents, comparison spreadsheets — everything that isn't a conversation lives in a shared Drive organized by client last name. When a Task says "review the renewal options," the documents are one click away in a predictable location. No digging, no asking where things are filed. File naming convention: date ~ last name ~ description.

Organization
Active Client Drive (shared) Filed by last name Consistent naming convention

Claude

The co-pilot

An AI assistant that operates across all three systems during structured work sessions. Pulls Airtable records, reads Gmail threads, searches Google Drive for documents, cross-checks human priorities against computed priorities, drafts Action Briefings, and updates fields. Claude is the Flow Manager — air traffic control that sees the full queue and surfaces conflicts. The human always has final authority.

What it does in a session
Reads Airtable queue Searches Gmail threads Finds Drive documents Cross-checks priorities Drafts Action Briefings Updates records

How a task review actually works

Every work session follows the same loop. Claude reads the queue, pulls the relevant records and threads, and the human makes the decisions.

The review loop

Claude
Reads the queue, identifies what needs attention
Airtable
Pulls Task + Work Unit, checks the cross-check
Gmail
Reads the latest thread for context
Drive
Reviews documents if needed
Airtable
Updates priority, Action Briefing, review date

A typical task review: 5–15 minutes. The system pre-sorts the queue so the human spends time on judgment, not triage.

1

Start with the queue

Filtered Airtable views surface what needs attention: Must Do items first (deadline pressure), then Should Do (review dates due), then parked items whose review date has arrived, then hygiene flags.

2

Check the cross-check

Does the Task's human-set priority agree with the Work Unit's computed priority? If they disagree, investigate. The disagreement is the signal.

3

Read the context

Use the Task Number to search Gmail for the latest thread. Read what happened since the last review. Check Drive for any documents referenced.

4

Update and brief

Update the Task's Next Action and Review Date. Update the Work Unit's Action Briefing — the structured handoff note that tells anyone picking up the work exactly what to do next and why.

Mollick's six questions — answered by the system

Every component of the system maps back to Mollick's delegation framework. The system doesn't replace management judgment — it gives that judgment a consistent structure.

What are we trying to accomplish?
Task record: Client name, task type, details, and account link tell you what the client needs and why it matters.
Where are the limits of authority?
Work Unit is advisory only. The pilot (Task Owner) has final authority over priority and action. The system recommends but never overrides.
What does "done" look like?
Task Status moves to Closed. Work Unit Lifecycle moves to Closed. The client need is resolved.
What specific outputs do I need?
Next Action on the Task and the Action Briefing on the Work Unit define exactly what happens next in concrete terms.
How do I follow progress?
Lookup fields on the Task: Recommended Priority, Activation Step, Action Briefing — a window into the flight computer without leaving the routing slip.
What should you check before finishing?
Data Hygiene Flag. If it says "Missing required fields," the record is incomplete — you haven't documented why work is parked or who you're waiting on.

None of these concepts require understanding Airtable, formulas, or AI. They require understanding delegation, oversight, and quality control — management fundamentals. The tools are interchangeable. The thinking is not.