---
title: "Material receiving and delivery log drafting"
role: superintendent
slug: material-receiving
status: ready today
updated: 2026-09-11
canonical: https://aiagents.construction/roles/superintendent/material-receiving/
---

## The job

The superintendent on a US general-contractor job in the $5–10M-a-year shop — often the owner wearing a hard hat, or one field person who also walks inspections, texts the PM, and still has to meet the truck at the gate. There is no dedicated receiving clerk. When a delivery arrives, someone has to match the packing ticket to the purchase order (or the sub’s PO), count what came off the truck, check condition and required certs / mill tags / SDS if the project asks for them, decide accept / note / reject, write where it is stored, and sign the ticket before the driver leaves. If that log is a sticky note that never reaches AP, you pay for material that never arrived. If a fluent AI draft invents a PO match, invents quantities, or invents a cert number the truck never carried, you have worse than a missing log — you have a record that looks official and is wrong.

This job is **use an agent**, not build a model. The super already has a desk: the open PO / commitment list the PM or controller keeps, the packing ticket and BOL the driver hands over, a phone for photos of the ticket and any damage, Excel/Word/PDF for the receiving log, and email or a shared folder to the PM / AP. The agent sits in the **assemble-and-draft** step only. It does not own the count. It does not accept or reject. It does not decide storage. It does not become the signature on the ticket. An unsigned AI receiving log is not a gate record, and it is not proof of delivery for pay.

Without an agent the work is still the same: stop the truck, open the ticket, walk the load, count units, note damage or shortage, check that required paperwork arrived, write the log, sign the ticket, tell the supplier if you reject or short-accept, park the material where it will not get ruined before install.

**What Division 01 expects on delivery and storage (numbering + example specs — not invented clause text).** [CSI MasterFormat 2026](https://www.csiresources.org/standards/masterformat2026) is the current North American shared language for organizing project requirements; Division 01 (General Requirements) received maintenance updates. A published MasterFormat 2018 numbers listing used by industry references **01 65 00 – Product Delivery Requirements** (packing, shipping, delivery, and acceptance of products, in general), **01 66 00 – Product Storage and Handling Requirements** (storage and handling of products, in general), and **01 32 43 – Purchase Order Tracking** under Construction Progress Documentation ([AGC Austin MasterFormat 2018 PDF](https://www.agcaustin.org/uploads/1/2/2/9/122909896/masterformat_2018_web.pdf)). MasterFormat is numbering language, not a receiving form. Your project manual and your contract name who inspects deliveries, who may reject, and what paperwork must travel with the load. Draft **into that** format when Division 01 already names one.

Example project language (cite as example specs, **not** AIA statute). South Davis Water District Section **01 65 00 Product Delivery and Handling** ([PDF](https://www.southdaviswater.gov/_files/ugd/c285cb_a8ffa73a68fa4a579ed6a53e9448c17b.pdf)): deliver products in undamaged condition in original containers or packaging with identifying labels intact and legible; immediately upon delivery, inspect shipment to determine (1) product complies with requirements of Contract Document reviewed submittals, (2) quantities are correct, (3) containers and packages are intact and labels are legible, and (4) products are properly protected and undamaged; discard damaged products. University of Houston master spec Section **01 60 00 Product Requirements** ([PDF](https://www.uh.edu/facilities-planning-construction/vendor-resources/owners-design-criteria/master-specs/pdf/01-60-00-fl---product-requirements.pdf)): deliver, store, and handle products using means and methods that will prevent damage, deterioration, and loss; deliver in undamaged condition in manufacturer’s original sealed container or other packaging system complete with labels and instructions; inspect products on delivery to determine compliance with the Contract Documents and that products are undamaged and properly protected; store to allow inspection and measurement of quantity or counting of units. Those are **example** Division 01 texts. Your job’s Division 01 wins.

**What A201 says about materials and warranties (official summary only — do not invent clause text).** Official [A201–2017 summary](https://help.aiacontracts.com/hc/en-us/articles/1500010259162-summary-a201-2017-general-conditions-of-the-contract-for-construction): under Article 3 (Contractor), § **3.5.2** is described as requiring that material, equipment, and other special warranties (e.g. a twenty-year roof warranty) must be written in the name of the Owner or be transferable to the Owner and will commence in accordance with Section 9.8.4. Practical point for this job: receiving is where special warranties, mill certs, and manufacturer paperwork either arrive with the load or get flagged as missing — the agent may list paperwork **present in the upload** or marked missing by the human; it does not invent a warranty number. Official preview: [A201–2017 PDF](https://contractdocs.aia.org/PreviewFiles/Preview_A201-2017.pdf) — Article 3 Contractor / warranty context (cite via AIA materials; do not invent clause text not read). Receiving does **not** rewrite Contract Sum, does **not** approve a pay application, and does **not** become a Change Order.

**This job is not a daily, not a safety note, not a look-ahead, not AP coding, and not a submittal review.**

- **Not a superintendent daily.** A construction daily is a contemporaneous day narrative — manpower, weather, work in place, delays, visitors, a signature by the person who was there. Sister job: [superintendent daily field report](https://aiagents.construction/roles/superintendent/daily-report/). A receiving log may be **mentioned** in the daily (“received AHU-2, ticket 4481, staged Laydown B”); it is not the day narrative.
- **Not a safety observation.** Sister job: [safety observation and near-miss logging](https://aiagents.construction/roles/superintendent/safety-observation/). A crushed pallet or leaking drum may spawn a safety note **and** a receiving reject; the hazard / near-miss seat is different from the gate log.
- **Not a look-ahead.** Sister job: [weekly look-ahead schedule drafting](https://aiagents.construction/roles/superintendent/look-ahead/). Look-ahead plans near-term work; receiving records what physically arrived. Material that never cleared the gate may become a look-ahead constraint — still two seats.
- **Not controller AP invoice coding.** Sister job: [AP invoice coding and matching](https://aiagents.construction/roles/controller/invoices/). AP matches an invoice to a commitment after the fact. This seat writes the **field** receiving record the invoice later needs. Do not let the model invent a three-way match.
- **Not PM submittal review.** Sister job: [first-pass submittal review](https://aiagents.construction/roles/project-manager/submittal/). Submittals are reviewed **before** fabrication / shipment. Receiving checks whether the delivered product appears to match reviewed submittals and the ticket — the superintendent still owns that field call; the agent does not “approve” a submittal at the gate.

**Why a $5–10M GC still does this.** A missed short, a signed ticket for damaged goods, or a cert that never made the job file shows up later as an AP fight, a failed inspection, or material installed that should have been rejected. On this size GC the gate log is usually the **superintendent / owner-super** with a phone and a shared spreadsheet — not a warehouse WMS. That is why the **first-pass structured draft from real ticket text, notes, and photos** is the job — and why the human still owns every count, every disposition, storage location, signature, and supplier call. Do **not** claim AI can accept material or replace the signature on the ticket.

## Use

This is a use workflow. You do not train a model. You do not ask it to invent quantities, invent a PO match, invent a cert / heat / mill number, or invent “accepted — no damage.” You give it what you already saw and wrote down, you get a structured receiving-log draft, you edit and keep only what you would defend when AP asks “did this load clear the gate?”

1. **Confirm the instrument.** Are you drafting a one-load receiving log / delivery ticket attachment for the job file (your Excel columns or Word headings), or does Division 01 / the Owner already name a receiving or stored-material form under 01 65 00 / 01 66 00 / 01 32 43? Draft **into that**. Do not fork a competing “official” WMS. Do not treat the draft as a pay approval or a Change Order.
2. **Gather only this load’s inputs.** Packing ticket / BOL / delivery ticket (photo or OCR text you provide); the open PO / commitment line you believe this load belongs to (number + description only if in the upload); your voice or scratch notes (qty counted, condition, shortage/overage, certs present/missing, storage location, accept/note/reject); phone photos of damage or illegible labels if any; reviewed-submittal ID **only if** you already have it and put it in the upload. Do not feed “the whole job folder” and hope.
3. **Separate facts the files show from calls only a human may make.** Ticket number, carrier, ship-from, line descriptions printed on the ticket, and OCR text can be drafted from the upload. **Physical count, whether the product matches the reviewed submittal, accept / note / reject, storage location, what may be installed, signature on the ticket, and calling the supplier** are the superintendent’s call — pulled from the truck and the Contract Documents, not from model memory. If you did not count a line, write **unknown — super to confirm**, do not invent “24 of 24.”
4. **OCR and photos are inputs, not truth.** Paste ticket OCR or attach the photo. The agent may structure fields from that text. It does not “see” a quantity you never counted. A 2026 field evaluation of general-purpose multimodal assistants on live-site photos found stronger performance on descriptive tasks than on judgment-intensive ones; models can emit confident narratives that go past the picture (*Smart Cities* 2026, 9(7), 114, [doi:10.3390/smartcities9070114](https://doi.org/10.3390/smartcities9070114)). Do not put model-inferred “qty received = ticket qty” from a photo onto a log you will sign.
5. **Feed the agent those files plus your template.** Your Excel columns or Word headings (date/time, project, PO / commitment #, ticket / BOL #, carrier, line item, ticket qty, counted qty, condition, certs / tags / SDS, storage location, disposition accept/note/reject, notes, photos attached, signed by). Prompt shape: draft one receiving log for this Project and this load only; use only the uploaded ticket text/photos, PO line the human named, and the human’s count / condition / disposition notes; do not invent quantities, PO matches, cert numbers, or “undamaged”; flag mismatches the human already noted; leave count and disposition as **super to confirm** unless the notes name them; do not approve pay; do not claim three-way match; footer: “Draft only — superintendent owns count, disposition, storage, ticket signature, and supplier notification; not a pay approval.”
6. **Human edit before anyone else sees it.** Walk the draft against the ticket and your count. Strike invented PO numbers and phantom certs. Confirm counted qty is what you counted. Confirm disposition matches what you told the driver. Confirm storage location is real. Confirm photos of damage are attached when you noted damage. Confirm you did not “solve” a shortage by inventing a partial accept the ticket never recorded.
7. **Sign the ticket and notify — human only.** Sign (or initial) the carrier ticket the way you already do. Call or email the supplier / PM yourself on reject, shortage, or damage. File the **edited** log with the ticket photo set where AP and the PM can find it. The agent does not auto-email the supplier a raw model draft as “we accepted this load.” Sister seats stay separate: day narrative is [daily-report](https://aiagents.construction/roles/superintendent/daily-report/); near-term plan is [look-ahead](https://aiagents.construction/roles/superintendent/look-ahead/); hazard notes are [safety-observation](https://aiagents.construction/roles/superintendent/safety-observation/); invoice coding is [invoices](https://aiagents.construction/roles/controller/invoices/); product approval before shipment is [submittal](https://aiagents.construction/roles/project-manager/submittal/).
8. **Log the way you already do.** Keep the edited receiving log with the ticket PDF/photos and the PO reference. When stored material later supports a pay app or invoice match, that is the PM / controller seat — not a silent rewrite inside the gate log.

Expected shape of the gain: less time turning ticket text, count notes, and damage photos into a readable first-pass receiving log the superintendent can edit before the driver leaves or before AP asks. That is not “the model received the truck.” There is no published, independent hours-saved or accuracy number for a $5–10M GC first-pass receiving-log draft that this page will invent. Time one of *your* deliveries (draft + your edit vs writing cold) before you change anything you pay for.

## Build

A general-purpose model that can read ticket OCR text, short voice/note transcripts, and (carefully) photo captions can draft a structured receiving log from those inputs. Physical count, accept/reject, storage location, cert authenticity, and ticket signature need a person. Do not treat the draft as proof of delivery for pay, and do not build from invented quantities or phantom PO matches.

> A workable v1: a prompt template that returns one receiving-log package — header (project, date/time, PO # from human upload only, ticket/BOL # from ticket text, carrier), line table (description from ticket, ticket qty, counted qty defaulting to **super to confirm** unless named in notes, condition, certs/tags present or **not in upload**, storage location from notes only), disposition (accept / note / reject from human notes only), flags (**qty mismatch noted by human / damage photo attached / cert missing per notes / draft — not pay approval / not three-way match**), attached-photo checklist, and a “superintendent owns count, disposition, storage, signature, supplier notification” footer. Keep the source ticket and photos with the log. Require “not in the uploaded files” instead of filling a gap.

Do not build a custom warehouse system this quarter. Do not fine-tune. Do not connect a model to auto-email suppliers or auto-approve invoices. This load’s ticket and notes are the only corpus that matters.

## Deploy

1. Pick five recent deliveries you still stand behind — one clean full accept, one shortage, one damaged/partial reject, one load where a required cert was missing, one quiet small-tools / consumables drop that still needed a ticket on file.
2. Run the agent on the **same** ticket text/photos + PO line + your count/condition/disposition notes only (no later AP emails that reveal outcomes unless you are testing edit, not prophecy). Time upload, draft, and your edit.
3. Diff the draft against what you actually filed / what the ticket shows. Record invented quantities, invented PO matches, invented cert numbers, missed damage notes, dispositions the model flipped, and any draft that claimed pay approval or three-way match.
4. Decide using a rule set in advance: no log is filed unedited; every quantity and PO number must exist in the ticket upload or a super-supplied cell; if the model invents five fluent “24 received — mill cert M-4419” lines the ticket never showed, it is not ready.

Use your real tickets and your real photos, not a vendor demo. Keep the workflow only if the log you would file is still something you would put your name on when AP or the inspector asks.

## Manage

**What “good” looks like**

- A named human **edits every draft**, owns the count, disposition, storage location, ticket signature, and supplier notification.
- Raw model text is never emailed to the supplier, Owner, or Architect as “proof of delivery.”
- The upload includes the ticket text/photos, the PO line used, and the count/condition notes actually taken — not a memory of “typical lumber drop.”
- Receiving vs daily vs safety note vs look-ahead vs AP invoice coding vs submittal review stay distinct. Sister seats stay those jobs.
- Quantities and cert numbers appear only when a person counted them or the source ticket states them. Blank / **super to confirm** is honest; a confident fake count is not.
- Pay applications and invoice matches are not silently “approved” inside a receiving PDF.
- If you already have a receiving / stored-material template or app, the agent drafts **into that**. This page does not sell a new one.

**Who owns the seat**

The superintendent / owner-super owns the gate log, physical count, accept/reject, storage, what gets installed, signature on the ticket, and supplier notification. On a $5–10M GC that is one person and the phone/laptop they already use. The PM owns submittal status before shipment. The controller owns invoice coding and match after the fact. An agent does not become any of those seats.

**When to skip the agent (what not to automate)**

- You have no ticket and no count notes. Do not ask a model to remember the truck.
- You expected the model to invent quantities, invent a PO match, or invent mill/cert numbers. Wrong seat.
- Life-safety or hazmat unload with an active spill / unstable load — handle the scene first; write the log yourself; at most let the agent format headers from known ticket fields after the area is safe. Sister [safety-observation](https://aiagents.construction/roles/superintendent/safety-observation/) if a near-miss applies.
- You need a formal stored-material pay-app backup package with notarized bills of sale. That is the PM / controller / contract path — not a gate-log paraphrase.
- The receiving habit is already a clean Excel sheet and typing is not the bottleneck. Leave it.

**How to stand it up this quarter**

Use the model you already have access to. Drop in this load’s ticket photo/OCR, the PO line, your count and condition notes, and your receiving headings. Edit every line, sign the ticket, file the log, notify the supplier if needed. Keep the workflow only if the package is still something you would put your name on. Do not buy a warehouse or field-material product to complete this job.

## Citations

Tools are citations, not new brand pages. Do not invent vendor homepages. This page does not create a Procore, Autodesk, BuildingConnected, STACK, Primavera, or other vendor listing.

- **[CSI MasterFormat 2026](https://www.csiresources.org/standards/masterformat2026)** / **[MasterFormat 2018 numbers PDF](https://www.agcaustin.org/uploads/1/2/2/9/122909896/masterformat_2018_web.pdf)** — Division 01; **01 65 00** Product Delivery Requirements; **01 66 00** Product Storage and Handling Requirements; **01 32 43** Purchase Order Tracking. Numbering language; your Division 01 wins.
- **[South Davis Water 01 65 00](https://www.southdaviswater.gov/_files/ugd/c285cb_a8ffa73a68fa4a579ed6a53e9448c17b.pdf)** — example project spec: inspect on delivery for reviewed-submittal compliance, correct quantities, intact packages/labels, undamaged products (example language, not AIA statute).
- **[UH 01 60 00 Product Requirements](https://www.uh.edu/facilities-planning-construction/vendor-resources/owners-design-criteria/master-specs/pdf/01-60-00-fl---product-requirements.pdf)** — example owner master spec: deliver/store/handle to prevent damage; inspect on delivery for Contract Document compliance and undamaged, properly protected products.
- **[AIA A201–2017 summary](https://help.aiacontracts.com/hc/en-us/articles/1500010259162-summary-a201-2017-general-conditions-of-the-contract-for-construction)** — Article 3 / § 3.5.2 material, equipment, and other special warranties in the name of the Owner or transferable to the Owner; commence per § 9.8.4. Cite summary language only; do not invent clause text.
- **[AIA A201–2017 official preview](https://contractdocs.aia.org/PreviewFiles/Preview_A201-2017.pdf)** — Article 3 Contractor / warranty context (cite via AIA materials, not invented clause text).
- **Excel, Word, PDF, email** (+ phone photos of ticket/damage) — draft log, ticket attachment, issue to PM/AP. If they already have a receiving / stored-material app, the agent drafts into that. No new vendor page on this site. Sister seats: [daily report](https://aiagents.construction/roles/superintendent/daily-report/), [look-ahead](https://aiagents.construction/roles/superintendent/look-ahead/), [safety observation](https://aiagents.construction/roles/superintendent/safety-observation/), [AP invoices](https://aiagents.construction/roles/controller/invoices/), [submittal](https://aiagents.construction/roles/project-manager/submittal/).

## Watch-outs

- **Invented quantities, PO matches, and cert numbers.** Models write fluent “PO 10422 — 24 received — mill cert M-4419 — accepted undamaged” lines that are not on the ticket or in your notes. Same failure mode as legal citation hallucination: Dahl, Magesh, Suzgun & Ho, *Large Legal Fictions*, 16 *J. Legal Analysis* 64 (2024) ([arXiv:2401.01301](https://arxiv.org/abs/2401.01301), [doi:10.1093/jla/laae003](https://doi.org/10.1093/jla/laae003)) — public LLMs, asked verifiable questions about federal cases, hallucinated often and often could not tell. Those percentages are **legal-case questions, not receiving-log accuracy**; do not import them as a construction performance rate. Do import the habit: every quantity, PO number, and cert ID in the draft is unverified until you open the ticket and your count notes. Blank / **super to confirm** is honest; a confident fake accept is not.
- **Treating an AI receiving log as proof of delivery for pay or as a three-way match.** Field receiving feeds AP and the PM; it does not approve an invoice or a pay application. Sister [invoices](https://aiagents.construction/roles/controller/invoices/) owns coding/match after the fact.
- **Photo theater as quantity or condition.** Do not let a model declare “full pallet, no damage” from a picture you did not walk. Multimodal assistants can narrate past the frame ([Smart Cities 2026](https://doi.org/10.3390/smartcities9070114)).
- **Skipping reviewed-submittal / cert checks the project requires.** Example Division 01 language (South Davis / UH) expects inspection against Contract Documents / reviewed submittals and undamaged goods. Flag missing paperwork the human noted; do not invent clearance.
- **Mixing seats.** Receiving ≠ [daily](https://aiagents.construction/roles/superintendent/daily-report/) ≠ [look-ahead](https://aiagents.construction/roles/superintendent/look-ahead/) ≠ [safety observation](https://aiagents.construction/roles/superintendent/safety-observation/) ≠ [AP invoices](https://aiagents.construction/roles/controller/invoices/) ≠ [submittal review](https://aiagents.construction/roles/project-manager/submittal/).
- **Unsigned AI to the supplier or AP.** Fluent, late, and wrong is worse than a short human log. Do not let the model send.
- **Do not replace the superintendent.** The agent drafts from ticket text, notes, and photos the human provides. The super still owns count, disposition, storage, signature, and supplier notification.

## Verdict

**Yes** — a $5–10M US GC should run this job this quarter if material receiving already starts as a ticket, a physical count, condition notes, and a place to file the log; the bottleneck is turning that stack into a readable first-pass gate record before the driver leaves or before AP asks; and a person will still own every count, every accept/note/reject, storage location, ticket signature, and supplier call. Use an agent to **draft the structured material-receiving / delivery log from voice notes, photos, and ticket OCR text the human provides**; the superintendent owns count, disposition, and signature. Skip this quarter if you expected the model to invent quantities or PO matches, to accept material, to invent cert numbers, to auto-email suppliers, to replace the ticket signature, or to buy a warehouse product you do not already have. Do not publish this page as a vendor listing.

## Tools cited

1. [CSI MasterFormat 2026](https://www.csiresources.org/standards/masterformat2026) — Shared North American numbering; Division 01 General Requirements received maintenance updates Last verified 2026-09-11.
2. [MasterFormat 2018 numbers (Division 01 delivery / storage / PO tracking)](https://www.agcaustin.org/uploads/1/2/2/9/122909896/masterformat_2018_web.pdf) — Published listing — 01 65 00 Product Delivery Requirements; 01 66 00 Product Storage and Handling Requirements; 01 32 43 Purchase Order Tracking (numbering language only) Last verified 2026-09-11.
3. [Example Division 01 — South Davis Water 01 65 00 Product Delivery and Handling](https://www.southdaviswater.gov/_files/ugd/c285cb_a8ffa73a68fa4a579ed6a53e9448c17b.pdf) — Example project spec (not AIA statute) — inspect on delivery for compliance with reviewed submittals, correct quantities, intact packages/labels, undamaged products Last verified 2026-09-11.
4. [Example Division 01 — UH 01 60 00 Product Requirements](https://www.uh.edu/facilities-planning-construction/vendor-resources/owners-design-criteria/master-specs/pdf/01-60-00-fl---product-requirements.pdf) — Example owner master spec — deliver/store/handle to prevent damage; inspect on delivery for Contract Document compliance and undamaged, properly protected products Last verified 2026-09-11.
5. [AIA A201–2017 summary (§ 3.5 material / special warranties)](https://help.aiacontracts.com/hc/en-us/articles/1500010259162-summary-a201-2017-general-conditions-of-the-contract-for-construction) — Official summary — § 3.5.2 material, equipment, and other special warranties written in the name of the Owner or transferable to the Owner; commence per § 9.8.4; Contractor Work/warranty context under Article 3 Last verified 2026-09-11.
6. [AIA A201–2017 (official preview)](https://contractdocs.aia.org/PreviewFiles/Preview_A201-2017.pdf) — Official preview PDF — Article 3 Contractor / warranty context (cite via AIA materials, not invented clause text) Last verified 2026-09-11.
7. [Excel / Word / PDF / email](https://www.microsoft.com/microsoft-365) — Receiving log draft, ticket attachment, damage photo set, PDF/email to PM / AP (desk tools they already have) Last verified 2026-09-11.

## Changelog

- 2026-09-11 — Published from Scout’s Friday catch-up job playbook.