# Material Delivery Ticket

> The receiving record that documents what material actually arrived on site, in what quantity and condition, and when — the field's proof of delivery and the front line of the three-way match.

- Source: https://briq.ai/acu/object/material-delivery-ticket
- Department: Field Operations & Project Controls (https://briq.ai/acu/department/field)
- Catalog code: FLD 110 · Level: Foundation · Track: Operations · 9 min read
- Also known as: Delivery Ticket, Packing Slip, Bill of Lading, Receiving Ticket, Proof of Delivery

## Definition

A material delivery ticket is the document accompanying a shipment of materials to a construction site that records what was delivered, the quantity, the date and time, and the receiving party's acknowledgement of the material and its condition. It is the field's evidence that a specific quantity of a specific material actually arrived, distinct from the purchase order that ordered it and the invoice that bills for it. Its verification at the point of receipt — confirming that what arrived matches what was ordered and is undamaged and conforming — is the first leg of the three-way match that protects a contractor from paying for material it never received or received defective. For time-sensitive and consumable materials such as ready-mix concrete, the ticket also carries the data that governs acceptance and payment. A material delivery ticket is not a purchase order and not an invoice; it documents physical receipt, and treating an unchecked signed ticket as sufficient to pay against is exactly how over-billing and payment for short or damaged shipments slip through.

## Why it matters

It is the front line of the three-way match that protects payment integrity. The purchase order says what was ordered, the invoice says what is billed, and the delivery ticket says what actually arrived; paying only when all three agree is what prevents a contractor from paying for quantities never delivered, materials substituted downward, or shipments that arrived damaged. A delivery ticket that is signed without being checked, or never captured at all, defeats the entire control.

It carries acceptance data that governs payment and quality for time-critical materials. A ready-mix concrete ticket records the mix design, the batch time, water added, and admixtures, and the elapsed time from batching bears directly on whether the load may be placed; accepting concrete past its time limit or with unauthorized water added is a quality failure the ticket is the record of. For such materials the ticket is not just proof of quantity but the acceptance document itself.

It establishes when material was available to install, which matters for the schedule and for delay claims. The delivery ticket dates when a material reached the site, so a claim that work was delayed awaiting material can be proven or refuted against the receiving record. A gap between when a delivery was needed and when the ticket shows it arrived is direct evidence in a schedule dispute.

It is the basis for reconciling quantities, backcharges, and shortages. When installed quantities do not match ordered quantities, when a shipment is short, or when material arrives damaged and must be rejected, the delivery ticket is the record that supports the shortage claim, the backcharge to the supplier, or the return. Without a disciplined receiving record, quantity and damage disputes devolve into unwinnable arguments after the material is consumed.

## Lifecycle

1. **Order and expected-delivery setup** — A purchase order or release sets what is expected and when, ideally tied to the schedule activity needing the material. Receiving against nothing — no record of what was expected — makes verification at the dock impossible.
2. **Arrival and unloading** — The truck arrives and material is unloaded, with the delivery ticket presented by the driver. For time-critical materials the clock on batch or mix time is already running, so verification cannot be deferred.
3. **Verification against the order** — The receiver checks the delivered material, quantity, and specification against the purchase order and, for products, the approved submittal. Signing without checking is the single most common receiving failure and the one that lets over-billing through.
4. **Condition and acceptance inspection** — Material is inspected for damage, conformance, and, for consumables like concrete, the time and mix parameters that govern acceptance. Damaged or out-of-spec material is rejected or noted at receipt, not discovered after it is placed.
5. **Signature and annotation** — The receiver signs, annotating any shortage, damage, or discrepancy directly on the ticket. A clean signature over a short or damaged load forfeits the claim; the annotation is what preserves it.
6. **Capture and linkage** — The ticket is captured — increasingly photographed at the dock — and linked to the purchase order, the daily report, and the schedule activity. A ticket that stays on a clipboard and never reaches the system cannot support the three-way match or the schedule record.
7. **Three-way match and payment** — At invoicing, the delivery ticket is matched against the purchase order and the invoice, and payment proceeds only on agreement. Discrepancies are resolved before payment, not written off after.
8. **Reconciliation and retention** — Delivered quantities are reconciled against installed and billed quantities, shortages and backcharges are pursued, and tickets are retained for cost, quality, and dispute records.

## Anatomy

- **Ticket number and date/time** — The unique identifier and the arrival timestamp, which for time-critical materials is the acceptance clock and for all materials anchors the schedule and match records.
- **Supplier and delivery source** — Who supplied and shipped the material, tying the ticket to the vendor for the match and any backcharge.
- **Purchase order / release reference** — The order the delivery fulfills. The link that makes verification against what was ordered possible rather than guesswork.
- **Material description and specification** — What was delivered, including grade or product, checked against the approved submittal. A substitution caught here is a substitution not installed.
- **Quantity delivered** — The amount received, in the unit of measure. The figure the three-way match turns on and the basis for detecting shortages.
- **Unit of measure** — Tons, cubic yards, each, linear feet. Mismatched units between ticket, PO, and invoice are a common source of false or missed discrepancies.
- **Condition and acceptance notes** — Damage, shortage, or non-conformance annotated at receipt. The annotation that preserves a rejection or shortage claim.
- **Mix / batch data (for concrete)** — Mix design, batch time, water and admixtures, and elapsed time — the acceptance parameters for ready-mix that govern whether the load may be placed.
- **Receiver signature** — Acknowledgement of receipt by the site. Signing without inspecting is what turns acknowledgement into an unintended waiver of claims.
- **Delivery location / area** — Where on site the material was received or placed, relevant for staging, quantity reconciliation, and installed-location records.
- **Photograph** — An image of the ticket and often the delivered material and its condition, capturing the record before the paper is lost and documenting damage.
- **Linked records** — The purchase order, the supplier invoice, the daily report, the schedule activity, and any NCR or backcharge the delivery generates.

## Failure modes

- **Signed without verification** — The receiver signs the driver's ticket to move the truck along without checking quantity, specification, or condition against the order. A short, substituted, or damaged load is accepted as delivered, the invoice matches the signed ticket, and the contractor pays for material it did not actually receive or received defective.
- **Ticket never captured** — The paper ticket stays on a clipboard in a truck cab or a trailer and never reaches the system. There is no record to support the three-way match, no proof of when the material arrived for the schedule, and no basis to reconcile quantities, so the delivery effectively did not happen on paper.
- **Damage or shortage not annotated** — Material arrives short or damaged, the receiver notices but signs a clean ticket anyway, and the discrepancy is only raised later. Without the annotation at receipt, the supplier disputes it, and the claim for the shortage or the damaged material is difficult to sustain.
- **Concrete accepted past its time limit or with added water** — A ready-mix load is placed despite the ticket showing elapsed time beyond the acceptance limit, or with water added on site beyond what is authorized. The acceptance data on the ticket documented a quality problem that was placed into the structure anyway.
- **Substitution accepted at the dock** — A product different from the approved submittal is delivered, and the receiver, not checking against the submittal, accepts and the crew installs it. The non-conforming material is in the work before anyone compares it to what was actually approved.
- **Unit-of-measure mismatch across documents** — The ticket, purchase order, and invoice express quantity in different units, so the three-way match either flags false discrepancies or, worse, misses a real one because the conversion was done wrong. Payment proceeds on a quantity that does not actually reconcile.
- **Delivered-versus-installed quantities never reconciled** — Material is received and paid for but never reconciled against what was actually installed, so overages, waste, and theft go undetected. The cost variance surfaces later with no way to attribute it to a delivery, a shortage, or a loss.

## Metrics

- **Verification rate at receipt** — Share of deliveries checked against the order for quantity, spec, and condition before signing. The core control metric protecting payment integrity.
- **Ticket capture rate** — Share of deliveries with the ticket actually captured into the system. Measures whether the receiving record exists to support the match at all.
- **Three-way match exception rate** — Share of invoices where the ticket, PO, and invoice do not agree. Reveals how often billed quantities diverge from what was received.
- **Damage / shortage annotation rate** — Share of discrepant deliveries annotated at receipt. Measures whether claims are being preserved or waived at the dock.
- **Concrete acceptance compliance** — Share of ready-mix loads placed within time and mix parameters. A quality-control metric for time-critical materials tied directly to the ticket.
- **Delivered-to-installed reconciliation** — Agreement between received and installed quantities. Detects waste, overage, and loss before it becomes an unexplained cost variance.
- **On-time delivery rate** — Deliveries arriving by the need date tied to the schedule activity. Links receiving to schedule performance and delay exposure.

## The AI shift

- **Conversational** — The receiving record becomes queryable rather than a stack of tickets. You ask which deliveries this week were signed without verification, which invoices have no matching delivery ticket, which concrete loads were placed near or past their time limit, or whether the material for an upcoming activity has actually arrived, cited to the tickets and the linked records.
- **Generative** — Capture shifts from filing paper to a structured digital record: a photographed ticket is read into its fields — supplier, PO reference, material, quantity, unit, and for concrete the batch and time data — a receiving record is drafted and matched against the purchase order, and any discrepancy or missing annotation is surfaced for the receiver to confirm at the dock.
- **Orchestrated** — The delivery ticket stops being an isolated slip. It is matched automatically against the purchase order and the approved submittal to catch shortages and substitutions, tied to the schedule activity that needed the material so arrival is confirmed against the need date, recorded on the daily report, and staged into the three-way match so the invoice cannot be paid without an agreeing ticket.
- **Autonomous** — The routine motion runs continuously: photographed tickets are captured and read, matched against POs and submittals with quantity, spec, and unit discrepancies flagged, concrete time and mix parameters checked against acceptance limits, arrivals confirmed against schedule need dates, and invoices held from payment until the three-way match agrees, while acceptance or rejection of a delivery, placement of time-critical material, and resolution of any discrepancy remain human decisions made at the dock.

## Prompts

### Conversational — Finding receiving control gaps before invoices are paid.

```text
Review this week's material deliveries and surface the control gaps before we pay any invoices against them. Tell me which deliveries were signed but show no evidence of verification against the purchase order; which supplier invoices have arrived with no matching delivery ticket captured; which delivered quantities or specifications do not match what the PO ordered; and which deliveries arrived with damage or shortage annotated but no follow-up. For any concrete deliveries, flag loads where the ticket shows elapsed time near or past the acceptance limit or water added on site. Rank by dollar exposure and tell me which invoices I should hold.
```

**Expected output:** A ranked list of receiving control gaps — unverified signings, missing tickets, quantity and spec mismatches, and concrete acceptance flags — with the invoices to hold identified, cited to the tickets and POs.

**Follow-ups:**

- Draft the discrepancy notes to the suppliers for the short and substituted loads.
- Which invoices should be held from the next pay run until the match is resolved?
- Which concrete loads warrant a follow-up on strength testing given their time data?

### Generative — Turning a photographed ticket into a matched receiving record at the dock.

```text
Read the attached photo of this delivery ticket and create a receiving record. Extract the supplier, the purchase order or release reference, the material description and grade, the quantity and unit of measure, the date and time, and, if this is a concrete ticket, the mix design, batch time, elapsed time, and any water or admixtures added. Match it against the referenced purchase order and the approved submittal, and tell me clearly whether the quantity, specification, and product agree or diverge. Flag any discrepancy, any missing condition annotation, and, for concrete, whether the elapsed time is within the acceptance limit. Tell me exactly what to check physically and annotate before I sign.
```

**Expected output:** A structured receiving record matched against the PO and submittal, with discrepancies, missing annotations, and concrete time limits flagged, and a physical-check list for the receiver before signing, not a passive transcription.

**Follow-ups:**

- If the product differs from the approved submittal, draft the rejection note.
- Link this ticket to the schedule activity that needed this material and today's daily report.
- Stage this into the three-way match against the supplier's invoice.

### Orchestrated — Wiring receiving into the match, the schedule, and the cost record.

```text
Reconcile our delivery tickets against the surrounding records for this month and surface every disconnect. Match each ticket to its purchase order and the corresponding supplier invoice for the three-way match, flagging any invoice being paid without an agreeing ticket and any ticket with no invoice yet; confirm each delivery's material and quantity against the approved submittal; tie each delivery to the schedule activity that needed it and flag any material for an upcoming activity that has not arrived; and reconcile delivered quantities against installed quantities to surface overage, waste, or shortage. Return the reconciliation tied to each ticket and record, and tell me where a supplier backcharge or a schedule risk exists.
```

**Expected output:** A reconciliation joining tickets to POs, invoices, submittals, the schedule, and installed quantities, exposing match exceptions, undelivered materials, and quantity variances, each tied to its record and flagged for backcharge or schedule action.

**Follow-ups:**

- Draft the backcharges for the short deliveries with annotated shortages.
- Which upcoming activities are at risk because their material has not arrived?
- Where does delivered exceed installed enough to warrant a waste or theft investigation?

### Autonomous — Standing policy for running material receiving.

```text
Operate our material receiving continuously under these rules. Capture and read every delivery ticket, match it against its purchase order and the approved submittal, and flag quantity, specification, and unit-of-measure discrepancies at the point of receipt. For concrete and other time-critical materials, check the batch and elapsed time against the acceptance limits and flag any load at risk before placement. Confirm each delivery against the schedule need date and flag late or missing materials. Hold every supplier invoice from payment until the ticket, PO, and invoice agree, and route exceptions with the discrepancy identified. Reconcile delivered against installed quantities and surface variances. Never accept or reject a delivery, never authorize placement of a time-critical load, never approve payment on an exception, and never sign a ticket on our behalf; route all of those to the receiver or project manager with the discrepancy and the supporting records.
```

**Expected output:** Continuous ticket capture, matching, and invoice holds with concrete and schedule flags, where acceptance, rejection, placement of time-critical material, and payment on exceptions always remain human, fully audited.

**Follow-ups:**

- Show me today's match exceptions, concrete time flags, and undelivered scheduled materials.
- Which invoices are held pending resolution and what is the total value?

## Maturity ladder

- **Level 0 — Level 0 — Clipboard signatures** — Tickets are signed at the dock and left on paper, rarely verified against orders and often never captured. Payment proceeds on invoices with no reliable receiving record.
- **Level 1 — Level 1 — Captured** — Tickets are collected and filed digitally, sometimes photographed, but matching against POs and submittals and reconciliation are manual and inconsistent.
- **Level 2 — Level 2 — Matched and linked** — Tickets are verified against POs and submittals at receipt, discrepancies are annotated, tickets feed a three-way match and the schedule, and quantities are reconciled.
- **Level 3 — Level 3 — Assisted** — Photographed tickets are read and matched automatically, quantity, spec, and concrete-time discrepancies are surfaced, and invoices with no agreeing ticket are flagged for review.
- **Level 4 — Level 4 — Operated** — Capture, matching, concrete and schedule checks, and invoice holds run within guardrails, while acceptance, rejection, placement of time-critical material, and payment exceptions stay human.

## FAQ

### What is the three-way match and where does the delivery ticket fit?

The three-way match is the control of paying a supplier only when three documents agree: the purchase order for what was ordered, the delivery ticket or receiving record for what actually arrived, and the invoice for what is billed. The delivery ticket is the middle leg — the physical evidence of receipt — and it is what prevents paying for quantities never delivered, materials substituted downward, or damaged shipments. If the ticket is never captured or is signed without verification, the match has no reliable middle term, and the invoice effectively gets paid against itself, which is exactly how over-billing slips through.

### Why does a concrete delivery ticket matter more than an ordinary packing slip?

Because for ready-mix concrete the ticket is not just proof of quantity but the acceptance document. It records the mix design, the batch time, the water and admixtures, and the elapsed time from batching, and those parameters govern whether the load may legitimately be placed — concrete has a limited window from batching before it must be placed, and adding water on site beyond the authorized amount compromises strength. Placing a load past its time limit or with unauthorized water is a quality failure that the ticket is the contemporaneous record of, which is why receivers must check the time and mix data before the truck discharges, not after.

### What happens if a receiver signs a ticket without checking the delivery?

The signature acknowledges receipt of what the ticket states, so signing a clean ticket over a short, substituted, or damaged load can waive or badly weaken the ability to dispute it later. The supplier will point to the signed ticket, the invoice will match it, and the contractor is left arguing about material that may already be consumed. The correct practice is to verify quantity, specification, and condition against the order before signing and to annotate any shortage, damage, or discrepancy directly on the ticket at receipt — the annotation is what preserves the claim.

### Why reconcile delivered quantities against installed quantities?

Because material can be received and paid for and then disappear into waste, overage, or loss without ever being installed, and if the two are never reconciled that gap surfaces only as an unexplained cost variance with no way to attribute it. Reconciling what was delivered against what was actually installed detects excessive waste, ordering errors, and theft while they can still be investigated and addressed, and it supports shortage claims and backcharges. On material-intensive scopes the delivered-to-installed reconciliation is one of the more revealing cost controls, turning the delivery ticket from a receiving formality into a quantity-management tool.

## Related objects

- [Three-Way Match](https://briq.ai/acu/object/three-way-match)
- [Purchase Order](https://briq.ai/acu/object/purchase-order)
- [Submittal](https://briq.ai/acu/object/submittal)
- [Daily Report (Daily Log)](https://briq.ai/acu/object/daily-report)
- [Accounts Payable Invoice](https://briq.ai/acu/object/ap-invoice)
- [Backcharge](https://briq.ai/acu/object/backcharge)