The point at which the engagement becomes a thing in the firm's systems rather than a prospect. The engagement code is created here and is the key everything downstream joins on — time, cost, bills and documents.
Until this exists there is nowhere legitimate to book time, which is why work starting before setup is a control failure rather than an efficiency.
Boundary
Trigger (in)
A signed engagement letter.
Output (out)
An engagement open for time and cost, with a code, a budget and a team shell.
Requires
terms-agreed
Produces
engagement-opened
Floor: can this run itself
Position
unattended
Manual because
n/a
Basis
Fully automated from the signed letter: code generation, budget creation and the team shell. The model's clearest example of what straight-through looks like.
Confirmed by
nobody named
Behaviour: what runs it
Systems
Engagement register, General ledger, Access provisioning
Data
Dataset
Authoritative source
Also in
State
Owner
Engagement
Engagement register
General ledger, Pipeline
settled
Engagement Lead
Engagement budget
Engagement register
S, Y, S, -, E, R, P, -, G, L
settled
Engagement Lead
Access grant
Access provisioning
S, Y, S, -, I, A, M, -, D, I, R
settled
IT Service Owner
Rules: what is decided here
ID
Rule
State
Enforced by
Basis
Owner
RUL-29
Every engagement has a unique code before work starts
defined
Engagement register
Generated at setup. The join key everything downstream uses.
Engagement Lead
RUL-30
An engagement opens with a budget
defined
Engagement register
Mandatory at creation.
Engagement Lead
RUL-31
Time cannot be booked to a closed or unopened engagement
defined
Time capture
Enforced by the time module. Work before setup is a control failure, not an efficiency.