The skill and its purpose
A useful record can change while its history remains important. Organisation contacts, capability, evidence, capacity and profile permissions can become stale at different times. Maintaining the record means updating the affected facts with current support and preserving what the earlier version actually said. A fresh website visit does not automatically reverify every field or make an old review apply to a new scope.
Work through the decision
Identify fields with an actual owner and review trigger. Record the source, observation date and verification scope. On change, create the appropriate revision and examine dependent listings, enquiries or claims. Keep unavailable or disputed information clearly labelled. Remove access that no longer serves an authorised role through the actual system, while retaining permitted organisation history. Do not change an evidence expiry date simply to keep a profile looking complete.
Practical exercise — fictional
A fictional provider changes its service area and supplies a new product sheet. Prepare two revisions: the dated capability declaration and the variant-specific evidence update. Identify old enquiries or public descriptions that may need review. Explain why the new product sheet does not reverify every previous project or extend another document’s validity.
Take it to the next job
- Name field owners and review triggers.
- Retain sources and actual observation dates.
- Create revisions instead of rewriting history.
- Review dependent descriptions and permissions.
Try the decision
The exercise stays in this session unless you choose to save it.
