A request bundle should help the recipient locate the proposed machine, current issue and sources needed to answer the question. Separate whole-object identity, counterpart relationship and supplied scope when they require different references. Preserve the discussion order as a reading aid, without implying an equipment sequence, purchase decision or supplied combination.
Include the source identifiers you actually have and label those still requested. Older issues can remain useful context when their relation to the current proposal is explicit. If a source is missing or its applicability is unresolved, keep that question beside its object rather than assigning one reviewed label to the entire bundle.
The local export is a NOT SENT preparation file. It has no upload or messaging endpoint and does not create an inquiry. Before using a real provider channel, replace the fictional identifiers with actual proposal records and name the next responsible reader. The bundle organizes unanswered questions; it does not authorize a machine configuration or operation.
Keep these fields together
- Ordered proposals
- Current issues
- Available references
- Requested sources
- 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)