# Use the client change request log

The blank and worked CSVs share 12 columns. They are plain UTF-8 value files, with no formulas, dropdowns, alerts, approvals, evidence storage, access controls or automatic updates. Office/Sheets opening, display and date handling have not been tested.

## Start with your own copy

1. Copy `client-change-request-log-blank.csv`; keep the worked file as a separate reference. Import as UTF-8 if prompted. Check columns, dates, currency and references in a copied file before live use.
2. Enter one row per independently decided request. Replace example IDs, scope/source references, people, dates and amounts with verified information. Store correspondence separately and reference it from the row.
3. Keep impact assessment, the actual client decision and implementation separate. On a reply, match the request/proposal, check shared assumptions, and update the next action, owner and review.
4. Before production, check the decision evidence, inputs and agreed delivery arrangements. Recording or quoting is not approval. Investigate work started while Pending; do not relabel it Approved to hide the missing basis.

## Read the fictional snapshot correctly

The three worked rows are fixed at **10 Nov 2026, 16:00; timezone not asserted**. All people, references, events, dates, hours and fees are invented teaching data, not live reminders or market rates. Future delivery/review dates are labelled plans, not completed events.

- **CR-01: Assessed / Approved / Blocked.** AUD 400 is approved; final copy is missing. The conditional 19 Nov proposal needs copy by 10 Nov. Client lead supplies it; Designer rechecks timing if that condition is missed.
- **CR-02: Recheck required / Pending / Not started.** AUD 300 remains a proposal. Its standalone 18 Nov date excluded CR-01. Designer reassesses combined delivery; Client lead then decides. Combined date stays To recheck. The 11 Nov review is an internal example, not a client deadline.
- **CR-03: Assessed / Declined / Not applicable.** The limited feasibility screen found that inputs/review cannot fit requested 13 Nov. The fee independently stays Not assessed / no quote; no detailed effort or fee estimate exists. Client lead declined in E-CR03-10NOV. Create no production task.

Assessment describes the impact check, not its price: Not assessed means unchecked; Assessed means checked to the recorded extent; Recheck required means assumptions changed.

Blank is unentered; an explicit unknown identifies missing information. AUD 0 means zero fee and needs an agreement and conditions. No free work is agreed here. AUD 700 is not the approved amount. Approval is distinct from completion, project acceptance, invoicing and payment.

Keep the article's later 11/12/20 Nov confirmation, start and completion out of this snapshot. Preserve relevant sources when updating your live copy; CSV does not implement version history.

## Treat imported text as data

Review imported text. Cells beginning with `=`, `+`, `-` or `@` may be interpreted as formulas even when quoted. Use text-import controls or neutralise the text, then check the result. Supplied cells do not begin with formula initiators; future edits are not automatically sanitised.

Preserve the 12 headers and three separate states when adapting. The log organises records; it does not determine an agreement's legal effect.