Contracted work
The agreed priorities.
From the proposal baseline, EXHIBIT-PROPOSAL.
Each line names the agreement behind it: the contracted priorities, and the extra work you approved separately.
Contracted work
From the proposal baseline, EXHIBIT-PROPOSAL.
Approved addition
Approved before it began, with the scope and acceptance references recorded.
Fictional example. Not issued and not for payment.
Each line cites its scope reference. Amounts are privately agreed and withheld from this public example.
EXHIBIT-INVOICE
Fictional example business with 20+ employees, improving its existing service-request software.
Not issued
Not for payment
| Line | Scope reference | Amount |
|---|---|---|
| Contracted service | EXHIBIT-PROPOSAL / agreed request-workflow priorities | Not shown in public exhibit |
| Approved extra work | EXHIBIT-CHANGE / weekly workload summary | Not shown in public exhibit |
What if it does not match?
AI may flag a missing or inconsistent reference. It cannot create an approval.
AI flags a possible mismatch between work, approval and billing references.
Your delivery lead compares the records with the authorized client approver.
People resolve the discrepancy together. Accepted work is not permission for a new charge.
AI cannot create authorization for an extra charge.
These fictional references do not establish a debt.
One improvement to existing software, with people making each decision along the way.
Priorities agreed first.
EXHIBIT-PROPOSAL
Extra work approved before it began.
EXHIBIT-APPROVAL
Delivered work accepted by the client.
EXHIBIT-ACCEPTANCE
Each line cites its source.
EXHIBIT-INVOICE
Source, approval, acceptance and billing stay distinct records, each with a person accountable.
Return to all documents →