Record the previous proposal, the proposed change and the actual object it affects. A configuration issue may concern an assembly, a member or a separately supplied option. Ask which current source describes the difference and what earlier relationships need another answer. Preserve the old reference with its date and represented scope.
Do not mark an entire collection as newly reviewed when only one object changes. The reference lens demonstrates independent state: a changed fictional issue makes that object’s noted source stale while another object retains its own state. This is local preparation behavior, not engineering change approval or evidence that a new source has been received.
Before assembling a request, list the specific source and counterpart relationships to reopen. An updated picture alone cannot settle a changed supplied scope. Use document review to assign the open questions to appropriate readers, and retain their responses with the actual issue. The website performs no configuration validation or authorization to operate.
Keep these fields together
- Previous issue
- Affected object
- Proposed difference
- Source to reopen
- Responsible next reader
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)