A source issue is useful when the reader knows which actual identity and subject it covers. Record the document or configuration reference, issue, date and responsible source. A new file name does not by itself establish that a proposed interface is covered. Ask what changed and what remains outside the source scope.
Keep older issues visible as history instead of replacing their labels without explanation. The cart configuration and receiving counterpart may have separate issue histories. Note their correspondence independently. The route board illustrates one small distinction: a selected fictional issue change reopens that record’s noted source, while other product notes remain attached to their own identities.
Before preparing a bundle, list sources that need another answer and the party responsible for each. Noted in this website means only a local preparation state; no actual document has been uploaded, reviewed or approved. The source worksheet leaves the real issue fields blank so that actual provider information can be recorded outside the demonstration.
Keep these fields together
- Source identifier
- Represented subject
- Issue/date
- Previous correspondence
- Question to reopen
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)