Manual Contract
Definition
The fully structured, no-AI capture path where the Lead fills a form stating exactly who must do what by when. The "I am asking [Knight] to [objective] by [date]" Mad-Libs form.
Avoid: manual entry, direct entry, task creation.
Role
Manual Contract is the purest expression of consent-first capture. No AI, no URL parsing, no ambiguity — the Lead specifies every field directly. The assignee picker is part of the form, so the Knight is identified before the Draft row is created, unlike Smart Paste (where the Squire suggests an assignee that the Lead may change).
The resulting row has source = manual_contract. A Manual Contract cannot be assigned to the Lead themselves — self-handshake is disallowed at the resolver; the Knight must be a distinct user.
Lifecycle
Not a stateful concept — Manual Contract is a capture path, not an entity. It produces a Draft row and exits.
- Lead fills the structured form (assignee, objective, deadline).
Draftrow created withsource = manual_contract; assignee is pre-set from the picker.- Lead promotes to
Pending_Handshakefrom the Detail Sheet when ready.
Related guides
Last updated: 22 June 2026