# Change after approval record

Use this record in your existing tracker or shared document. Adapt decision authority,
commercial handling and review arrangements to the project's agreed process.

## Blank record

### Earlier approval or acceptance

- Approved scope revision and stable reference:
- Decision type and scope covered:
- Decision maker and recorded date:
- Accepted build and evidence, if applicable:
- Current development, review and deployment state:

### New request

- Request ID, revision, requester and received date:
- Original message and stated purpose:
- Requested behaviour:
- Baseline comparison and supporting references:
- Classification: correction / addition / unresolved:
- Open questions, owners and next response:
- Affected work to continue or pause; authorised owner confirmation:

### Assessment and decision

- Changed data and behaviour:
- Roles allowed and denied; responsible access owner:
- Dependencies and downstream consumers:
- Revised criteria and exclusions:
- Implementation, testing and documentation work:
- Cost and timing impact; estimate assumptions:
- Feasible options and recommendation:
- Decision maker and authority:
- Decision, exact request revision and date:
- Agreed scope revision and delivery commitment:
- People notified and next action:

### Replacement delivery

- Submitted build, source reference and review environment:
- Changed behaviour and relevant regression checks:
- Evidence reference, producer, build and result per criterion:
- Failed, blocked or untested checks and next owner:
- Acceptance decision, exact build, scope, decision maker and date:
- Deployment instruction and authorised owner, recorded separately:
- Earlier records retained at:

## Fictional worked example: CR-015

These invented records illustrate a workflow. They are not customer evidence or
ProjectHubs screenshots. Build and scope labels are teaching references.

### Earlier record

- Scope S4, from CR-014 revision 2: selected organisation's orders, date and status
  filters, order ID / order date / status / total, maximum 5,000 rows.
- Customer contact details excluded; saved filter presets removed from this release.
- Operations lead reviewed B18 after a date-filter correction to B17.
- Client owner accepted B18 against S4. Retain the recorded decision and evidence.
- B18 deployment state: establish separately with the release owner.

### Request and assessment

- Operations lead requests billing email for Finance reconciliation.
- Record CR-015 separately and link to the earlier acceptance.
- Classification: addition, because S4 explicitly excludes contact details.
- Resolve primary-contact selection, current versus historical values, missing values,
  export permissions and the downstream import's compatibility.
- Delivery lead coordinates assessment; access owner confirms intended role rules;
  Finance import owner checks compatibility.
- Confirm assessment response timing with those owners before promising a date.
- Keep timing and cost proposals provisional until the assessment is complete.

### Illustrative authorised revision

- Assume the client owner authorises CR-015 revision 2 after assessment.
- Proposed S5 becomes the agreed revision: current primary billing email, an empty
  field when missing, and export limited to the agreed role.
- Record assessed effort, commercial treatment and delivery impact through the
  project's agreed process. This teaching example assigns no prices or dates.
- Keep S4 and the B18 decision available; notify affected delivery and review owners.

### Replacement review

- B19 is submitted against S5.
- Check correct email selection and the agreed empty value.
- Check allowed and denied export roles and organisation isolation.
- Assess regression coverage for filters, existing columns and the 5,000-row limit.
- Record Finance import compatibility against the revised CSV.
- Link actual results to B19; preserve B18 results as earlier evidence.
- Acceptance: pending. Submission does not establish a new acceptance decision.
- Deployment: pending separate release-owner instruction.

## Client reply from the article

Thanks for explaining the reconciliation need. B18 was accepted against scope S4,
which exports order ID, order date, status and total. Billing email is excluded
from that scope.

We've recorded the addition as CR-015. Before proposing the change, we need to
confirm the billing-contact rule, export permissions and compatibility with
Finance's CSV import.

The delivery lead will coordinate that assessment and confirm when we can provide
options. The client owner will then decide whether to proceed with the proposed
scope and delivery impact.

The B18 acceptance record remains available. A changed export will have its own
build reference, review evidence and acceptance decision.