# 9. Keep it current

**Start here:** Run the filled price-change practice below. Find the old price in each affected answer, prepare the replacement and compare a fresh answer with v2. A drafted update is not an updated file.

Start from an approved change. Find where the old fact appears, update the master and working copy, then ask an affected question again.

**Monthly:** check programs, costs, dates, contacts, policy changes and open gaps against real source owners. **Immediately:** update a known consequential change rather than waiting for the monthly reminder.

```
Change log
Date | section | source change | approving role | working copy updated
| affected question rechecked | staff informed

Gaps list
Question | what is missing or wrong | source/section | responsible role
| next action | result after correction
```

Keep the lists nonpersonal and readable. A source is not current merely because an AI says it is. Confirm that the master can be found and recovered through school-approved storage.

### Filled change to practice

```
Help prepare a fictional reference update from these notes:
Current P3 v1: tuition $1,000; required kit $90; other charges unknown.
Approved P3 v2, effective December 1, 2026: tuition remains $1,000;
required kit becomes $110; other charges remain unknown.
Affected answers: Section 03 cost summary and FAQ 'Is $1,000 the
full cost?' Today, for this exercise, is December 2, 2026.
Draft replacement wording, list old phrases to find, and write the
question I should ask after replacing the active copy. Do not edit
files or claim the price is the complete program cost.
```

**Filled change-log entry:** December 2, 2026; Section 03 and cost FAQ; P3 v2 effective December 1; kit $90 → $110; reviewing role still to be named; active-copy replacement and fresh-question check pending. Do not mark those last actions done merely because the draft wording exists. New known subtotal: $1,110; complete cost still unknown.

### Update the answer people use

Trace a changed fact into the reference, FAQ and working copy instead of updating only the chat. The same habit works when a personal-project date changes. Keep the prior approved version recoverable and check a fresh answer against the new source. A reminder to review is not the completed update.