Skip to main content

​
The handoff problem

Real teams change shape:
  • A recruiter goes on leave mid-pipeline.
  • An agent handles screening; a human takes over for negotiation.
  • You shift from an all-human team to a hybrid human + AI setup.
Spreadsheets and static SOPs break here. The new person opens a folder of notes and guesses what happened. Context lives in someone’s head — or scattered across email. Tracks are built so any overseer can gather enough context to continue without starting over.

​
What continuity means in practice

When someone new opens an instance, they should immediately see:
  1. History — everything that happened, in order (Events tab).
  2. Current position — which checkpoints were visited and which milestones are done.
  3. Pending tasks — work assigned to them or their role.
  4. What they can do — actions available at the current checkpoint for their role.
  5. What is left — required milestones still open before the track completes.
That bundle is the continuity brief — not a separate report, but the instance page itself when used as intended.
Screenshot placeholder Split or stacked view: Events timeline on one side, Checkpoints & Progress on the other — same instance, showing history + current state together.

​
History that includes everyone

The Events timeline records actions from all overseer types consistently:
  • Team members
  • Contacts
  • Agents
When an agent achieves a milestone or fulfills a task, it appears the same way a human’s action would — name (or agent label), timestamp, event type. The next overseer does not need to know how the system stored it; they just read the story.
Screenshot placeholder Events list mixing human and agent actors: “Agent Review Bot fulfilled task,” “Sarah visited checkpoint Interview,” etc.
Video placeholder (Screen Studio) 60-second narrative: open instance as new overseer → scan Events → read Notes → see pending task assigned to you → fulfill task → achieve next milestone. No voiceover required — on-screen flow tells the story.

​
Handoff scenario walkthrough

Here is a end-to-end example on a contact hiring track:

​
Step 1 — Human creates work

Recruiter Sarah moves the candidate to Technical Interview and creates a task: “Summarize GitHub activity” — assigned to screening agent Repo Scout.

​
Step 2 — Agent fulfills

Repo Scout reads instance context (prior notes, resume tab if configured), fulfills the task, and leaves a summary in the task completion record. Events show the fulfillment.

​
Step 3 — Human picks up

Engineering manager Mike opens the instance for the first time. He:
  • Reads Events to see Sarah’s moves and Repo Scout’s summary.
  • Checks Checkpoints & Progress — candidate is at Technical Interview; Portfolio reviewed milestone still open.
  • Achieves Portfolio reviewed after his call.
  • Creates a task for Sarah to schedule the onsite.
Mike never spoke to Sarah live. The instance was the handoff.
Diagram placeholder Simple three-step illustration: Human → Agent → Human with arrows through a shared “Instance timeline” box. User-facing labels only.

​
Notes are part of continuity

Structured milestones capture what was done. Notes capture why and how it felt — subjective context automation misses. Encourage overseers to note:
  • Interview impressions before handoff
  • Deal risks during negotiation
  • Exceptions to normal process (“approved despite missing reference — VP sign-off in email”)
Notes appear in Events and stay with the instance permanently. For entity context history (how knowledge about a person or record evolved), see the Intelligence Timeline in Intelligent Registries — separate from track instance events but equally important for handoff.
In Active Tracks, notes support replies and sometimes audio recording — useful for field teams capturing voice memos that become part of the handoff record.

​
Best practices for teams

​
When continuity breaks (and how to fix it)

​
Dynamic operating procedures, not dead documents

Continuity is the payoff of treating Tracks as living systems rather than PDF playbooks. Checkpoints flex; milestones record truth; events preserve memory; tasks coordinate people and agents. That is the difference between an SOP on a shelf and a dynamic operating procedure your organization actually runs on. Next: Track Data — aggregate views for managers and ops leads.