A scope-change note identifies what changed in the proposed context and which selected records may be affected. The product identity can stay the same while its counterpart or applicable source changes. Name the previous and proposed context, then list the sources that need another review. Do not hide the relationship by replacing the product label.
A changed shortlist is different from a changed source issue. Record additions, removals and ordering choices separately from a provider’s product revision. The specification desk lets a buyer reorganize identities without approving their relation. In its fictional revision example, a local source note becomes stale when the issue changes.
Before preparing a real inquiry, identify the difference, affected references and responsible reviewer. Ask which current sources cover the proposal rather than assuming an older sample or document still applies. The local brief preserves open questions and list order only. It does not decide suitability, substitution, configuration or an accepted project scope.
Keep these fields together
- Previous context
- Proposed difference
- Affected identities
- Sources to reopen
- Review responsibility
Use the blank source worksheet to record actual information from the responsible provider. Fields are intentionally empty; the fictional collection does not supply a decision, current document or real project record.
Download a blank source register (CSV)