| name | delivery-commitment-control |
| description | Record delivery decisions and dependency handoffs with acceptance verification and escalation guidance. |
Delivery Commitment Control
Use this skill when formalizing a delivery-affecting decision, opening or closing a cross-party dependency handoff, or escalating one of those records.
Record delivery decisions
For each delivery-affecting decision, record:
- Decision: the agreed outcome.
- Decision owner: the accountable party making or approving the decision.
- Effective date: when the decision takes effect. If unknown, mark it unresolved; do not infer it.
- Affected commitments: commitments changed or confirmed, including accountable owners and due dates where known.
- Impact: the delivery, scope, schedule, risk, or acceptance impact.
- Follow-up actions: actions required to implement or verify the decision.
- Linked control record: the relevant plan, action tracker, change request, or dependency record.
Define dependency handoffs
Use a handoff record whenever one party supplies work, information, access, a decision, or a service that another party needs to continue delivery.
For each handoff, record:
- Provider: the accountable party supplying the dependency.
- Receiver: the accountable party consuming or verifying it.
- Deliverable: the specific item or service to be supplied.
- Acceptance criteria: observable conditions the receiver will use to assess the deliverable.
- Needed-by date: the date by which acceptance is required to protect the dependent plan.
- Verification status:
pending until assessment, accepted when every criterion is met, or rejected with unmet criteria recorded.
- Linked plan or change record: the control record that owns the handoff.
Do not treat a handoff as committed when any required field is missing. Record unresolved ownership, acceptance criteria, or timing as a planning risk.
Set verification status to pending until the receiver assesses the deliverable. Set it to accepted only when every acceptance criterion is met; otherwise set it to rejected and record the unmet criteria.
Before marking a handoff complete, confirm that its verification status is accepted.
Escalate unresolved decisions or handoffs
Raise a critical-path escalation when an unresolved decision or unaccepted handoff threatens an affected commitment. Include the decision or handoff record, unresolved fields or unmet acceptance criteria, accountable decision owner or provider and receiver, effective or needed-by date, latest safe resolution date, and immediate next action.
Minimum decision record
Complete one record per delivery-affecting decision. Fill every field; mark an unknown value as unresolved.
| Field | Record |
|---|
| Decision | |
| Decision owner | |
| Effective date | |
| Affected commitments | |
| Impact | |
| Follow-up actions | |
| Linked control record | |
Minimum dependency handoff record
Complete one record per dependency handoff. Fill every field and update verification status as the receiver assesses the deliverable.
| Field | Record |
|---|
| Provider | |
| Receiver | |
| Deliverable | |
| Acceptance criteria | |
| Needed-by date | |
| Verification status | |
| Linked plan or change record | |
