A container-relation note names the actual bin or tray and the counterpart relevant to the question. The counterpart might have a separate source and issue history. Start with those identities so a reader knows what relationship is being proposed. A matching colour or neighbouring photograph is not evidence that one object fits another.
Ask the responsible provider what current records cover the relation and what remains outside their scope. Record supplied facts separately from unanswered attributes. If the proposed counterpart changes, preserve its prior identifier as history and reopen the correspondence. An individual container source should not silently become a complete answer for another storage object.
Use the blank scope worksheet to carry the relationship into a real request. The register keeps independent source states and lets a discussion include a bin without including the bay. Its layout animation makes records easier to follow but tests no containment, stackability or contents suitability. Actual applicability decisions belong to the appropriate real-world review.
Keep these fields together
- Container ID
- Counterpart ID
- Sources per subject
- Proposed relation
- Open applicability question
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)