What you will learn
- Keep shipment, receiving, movement, placement, and review records distinct but connected.
- Identify duplicate records and unresolved quantity or lot relationships.
- Prepare a material-document handoff that supports assigned review without implying acceptance.
05.01
Build a record chain rather than a folder of attachments
Material traceability depends on relationships. A delivery ticket, receiving note, product label, submission, supporting material document, and placement record may describe different events or different levels of detail. Give the receiving entry a stable identifier and connect each relevant record to it. Make clear which document supports identity, quantity, location, or review status; do not rely on attachment count as proof of completeness.
RE-019 connects DT-448, DR-019, MR-008, MD-031, and S-014. Fictional SP-DR-01 supplies documentation fields, not acceptance criteria. The packet cannot determine material suitability. Real projects use their applicable specifications, procedures, and assigned reviewers.
05.02
Reconcile quantities by event and unit
Start with the event each number represents. DT-448 states eight components in a shipment at 08:35. Iris observes six at B during the later visit. MR-008 records two moved from B to C at 08:50. These references provide a documentary explanation for the difference, but they should remain distinguishable in the receiving record. The explanation is not an installation quantity or an independent count at C.
Preserve units exactly. If records use different units or descriptions, identify a reconciliation task rather than adding unlike quantities. Do not infer a conversion from a product name or memory. When a calculation is required, retain its inputs, units, assumptions, and review reference in the appropriate project record. This course uses counts of components only; it provides no pay-quantity or measurement method.
A scanned duplicate of DT-448 should not create another eight-component delivery. Compare ticket identifiers, supplier, date, and source relationship before summarizing. Preserve the files according to project rules, but count events rather than files. If two tickets share an identifier and the relationship is unclear, flag it instead of deleting evidence or choosing the more convenient total.
05.03
Trace identifiers across supporting documents
The ticket identifies lot L-72; MD-031 identifies L-27. Preserve both references and state the mismatch. The existence of a material submission or review cover does not establish that MD-031 applies to this delivery. Link the available submission identifier and reviewer-stated status without converting an ambiguous cover into an approval.
A useful check asks whether the document actually identifies the material, lot, item, or other project-required reference being reviewed. Confirm readability and missing pages before handoff. If a supporting document covers several lots or several products, record the relevant portion and any unresolved relationship. The learner's role here is to expose the connection or gap; the assigned reviewer determines whether the supplied evidence meets the project's requirements.
05.04
Record a replacement without declaring the issue accepted
On 20 October at 11:30, fictional supplier transmittal MT-006 supplies MD-041 identifying lot L-72 and states that it replaces MD-031 for DT-448. Keep that transmittal as the source of the claimed relationship. Update RE-019 with the new document and receipt time, while retaining the earlier mismatch and the history required by the project.
This resolves a missing documentary link at the supplier-statement level; it does not supply the materials reviewer's disposition. A precise status is 'replacement supporting document received and referred for review.' Avoid 'material approved' or 'all certificates complete' unless an applicable, authorized source supports that statement. Different checks can have different outcomes: quantity reconciliation may be documented while material review remains pending.
05.05
Prepare a receiving handoff that can be acted on
The handoff should identify the delivery, current location information, quantity bases, document relationships, and outstanding review. Include the original sources needed to check the summary. NCDOT's weight-ticket guidance illustrates agency-specific identification and placement fields; Caltrans describes digital ticketing as a way to organize delivery information. Neither source supplies a universal procedure for this fictional case.
Use a precise issue and owner: 'RE-019: MT-006 links replacement MD-041 to DT-448/L-72; reviewer disposition not supplied. Refer to the materials reviewer before the next record review.' Do not invent a stop-work direction or installation release. Follow actual project procedures for required action and record their source.
Worked example · Fictional project
Worked example: RE-019 evidence summary
RE-019 summary: 'DT-448 lists eight components, L-72, destination B. DR-019 records six observed at B during the morning visit. MR-008 records two moved to C before the visit and provides the documentary reconciliation. Installation is not documented. MD-031 identifies L-27; supplier MT-006 later supplies MD-041/L-72 as its replacement for this ticket.'
Status: 'Quantity relationship documented from cited records; no independent observation at C. Replacement material document received and referred to the designated reviewer; disposition pending.' This separates the physical-event account, supporting-document receipt, and technical review instead of rolling them into one green completion label.
Try it yourself · Fictional scenario
Put the module into practice
A summary imports two scans of DT-448 as separate deliveries and reports 16 accepted components. It treats MT-006's replacement statement as the materials reviewer's approval. The packet contains no installation record and no reviewer disposition.
Your task
- Identify the duplicate-count and authority errors.
- Write a corrected quantity statement and a separate material-review status.
- List the source relationships that a reviewer should be able to open.
Write your response in your own notes before opening the sample. This exercise is for practice and does not record a score or course completion.
Reveal a sample response
The scans represent one ticket in this scenario, so they cannot support 16 delivered components. Attribute eight to DT-448, six observed at B to DR-019, and the two-component movement to MR-008. State that installation is not documented. Do not describe the documentary reconciliation as a new physical inspection.
Record MD-041 as a replacement supplied under MT-006, with reviewer disposition pending. The reviewer should be able to open DT-448, DR-019, MR-008, MD-031, MT-006, MD-041, and the relevant S-014 reference from RE-019. This supports review without claiming that receipt of an attachment completes it.
Keep in mind
Trace each quantity and identifier to the event or document it represents, and keep receipt of evidence separate from its review disposition.
Further reading
These primary references provide context. Follow the edition and requirements applicable to your project.
- NCDOT: Construction Manual — Weight Tickets as a Basis of Payments
An agency-specific example of material-ticket identifiers, quantities, and placement information. No payment procedure or acceptance requirement is imported into the fictional case.
- Caltrans: e-Ticketing
Background on electronic collection and organization of material-delivery information. The reconciliation exercise is original REC&I content.
General education for civil engineering, construction, and inspection teams. Project requirements and assigned professional responsibilities govern.
Course RECI-CE-001 · Module 5 of 6 · Review edition