Skip to content

The handover record

Loaded by the handover subagent, and the stop & refer subagent  ·  Not loaded by section subagents

What the fleet produces at the end of a call, and the checks that run before it is handed to the coach. Only the closing subagents load this page — a section subagent that had it would be tempted to summarise, and its job is to ask.

What to record

Store answers against field IDs, never as a transcript summary. For each: the field ID, the normalised value matching the declared answer type, and the client's own words where the wording carries information the option label loses.

Mark each field as one of:

Status Means
answered The client gave an answer and it was normalised to the field's type
declined The client was offered the question and chose not to answer
skipped — not triggered A conditional whose trigger never fired. Correct behaviour, not a gap
skipped — section omitted The client opted out of a whole section, or the call ended first

These are four different things and collapsing them into "blank" destroys the record. A coach reading declined knows not to raise it; a coach reading blank will ask again.

The handover

At the end, produce a record for the coach containing:

  • Every red flag found, with the field that triggered it
  • Every declined question
  • The triage outcome from Screening red flags — Clear, Proceed with caution, Clearance required, or Refer & stop
  • Anything the client said that doesn't fit a field but a coach should read
  • Which sections completed, and which subagent was holding the call if it ended early
  • The questionnaire version the client answered (form_version)

The agent proposes a triage outcome, it doesn't decide one

A human confirms it before anyone trains. Present it as a suggestion with its reasoning visible.

Before finishing

  • Every non-conditional required field is answered or explicitly declined
  • No conditional question was asked without its trigger firing
  • No triggered conditional was missed
  • Consents in section 11 were each answered separately, and No was as easy to give as Yes
  • Every red flag is in the handover
  • Nothing declined was asked twice — including across a subagent handoff
  • Every section's handoff state was merged, none dropped
  • The client was told what happens next and when

Partial calls

A call that ends early still produces a record. Sixty answered fields are worth having; discarding them because the call dropped at section 7 wastes the client's time and guarantees they answer sections 1–6 twice.

Mark the remaining sections skipped — section omitted, note where the call ended, and flag whether a callback is needed. Where a stop condition ended the call, the record is complete as it stands — the outstanding sections are not a gap to fill, and nobody should call back to fill them without the coach saying so.