Follow the work, not only the partner name
P-12 can fulfill several work orders for several sites. A folder under the partner name is not enough to establish which receipt belongs to W-8. Carry the work reference through each contribution.
Where lots, assets or service episodes matter, include those references too. Use only the granularity your decision needs, but document it. One daily site total may not answer a question about a specific work order.
Keep the contributor separate from the organization or site represented. Staff changes should not sever the record or automatically preserve inappropriate access.
Represent partial and corrected events honestly
A partial receipt is not necessarily an error. Record which part arrived, when and whether the remaining amount is expected. Do not overwrite it with a later total if the timing matters to service performance.
For a correction, preserve the original, changed value, reason and reviewer. A new event should have its own record rather than appearing as a correction to a previous event.
Keep dispatch, receipt, inspection and acceptance dates distinct. The latest upload may contain evidence about an earlier event; it should not reset the operational timeline.
Test traceability in both directions
Start at a site confirmation and trace back to its partner and work order. Then start at W-8 and find all confirmations and unresolved exceptions. Both directions should make sense to someone outside the original team.
Test a duplicate import and an unknown work reference. Retain unresolved records for review rather than forcing an incorrect match. A connected but mistaken relationship can be harder to detect than a visibly unmatched record.
A useful handover includes the reference rules, field definitions, correction process and source links. The next operator should not need the original analyst to explain why two apparently similar rows are different.
Work through the Relay example
This is a fictional teaching example. Adapt the fields and rules to the question your own workflow needs to answer.
| Entity or event | Reference | Keep visible |
|---|---|---|
| Partner | P-12 | Organization and contributor roles |
| Work order | W-8 | Scope and expected handoffs |
| Receiving site | T-6 | Partial receipts and acceptance |
| Correction | Original record reference | Reason, date and reviewer |
Build this part of your plan in more detail
These lessons address the next practical questions in this module. Choose the detail your workflow needs, then return to complete the exercise.
- How to Build a Relationship Record
Prepare a source-linked relationship handoff without confusing people, organizations and interactions.
Add this part to your plan
On workbook page 4, map a partial receipt followed by a corrected confirmation. Show how a reviewer traces both to W-8.
Download workbook (fillable PDF)Compare with a suggested answer
The partial event remains in the timeline. The correction points to its original and explains the change. All records link to the appropriate work order and site without being counted twice.
Self-check: Can someone reconstruct what happened in order, including what changed later?
Questions you may have
Can a partner folder serve as the whole record?
It may store files, but reviewing individual work requires the relevant work, event and source relationships.
Should duplicate-looking records always be merged?
No. They may represent partial events or different periods. Check the relationship before merging.
Apply the method to your work
Use the five-part plan to assess the sources, analysis and permissions your team needs. The solution page shows where a connected platform can support that workflow.
Explore the partners & suppliers solution →