An AI assistant can summarize supplier emails in seconds. The useful question for a project manager is whether those messages establish that the right materials are available for the next operation. Keep an estimated arrival, a shipment notice, and a checked delivery separate before treating any of them as a reason to send a crew.

Procore’s supply-chain guide describes procurement through installation and recommends close order tracking, communication, and checking paperwork for omissions. Anthropic’s guide to agent tools recommends realistic tasks with verifiable outcomes. These are established sources, not fresh product announcements. Datum’s application is a small materials-readiness review that tests whether an assistant can preserve the distinctions your scheduler depends on.

One order can have several different answers

Consider a hypothetical bathroom remodel. A supplier email says the trim package should arrive Friday. A later shipment notice covers the shower head, but the valve trim remains on backorder. The receiving record shows one carton at the warehouse. A summary that says “plumbing fixtures delivered” would conceal the missing part and the delivery location.

The proposed review should instead show the relevant order lines, the latest evidence for each, and the unresolved requirement for the planned installation. It can draft a question about the valve trim. The project manager still decides whether the crew can perform useful work and whether the schedule should change.

Build a readiness record around the work

For a first pilot, choose one completed material package. Supply its approved product list, purchase order, supplier messages, shipping records, receiving checks, and the team’s requirements for the associated work. Have the responsible person identify which items must be available together. A model should not invent that dependency from a generic installation description.

  • Identity: project, purchase-order line, product model, finish, required quantity, and delivery destination.
  • Supplier expectation: the stated date or range, what event it describes, who supplied it, and when it was last confirmed.
  • Movement: which items and quantities shipped, with the shipment evidence and any remaining balance.
  • Receipt: what was received, where it is stored, and whether quantity and condition have been checked.
  • Decision: the missing evidence or material, a named follow-up owner, and the project manager’s readiness verdict.

These are suggested operating fields, not claims about a software feature. Preserve the supplier’s wording when dates are tentative. Do not turn “expected to ship” into “arrives on site,” or treat a warehouse receipt as a jobsite delivery. Where records conflict, show the disagreement beside the source links.

Ask for changes that need attention

A daily review can become noise if it repeats every open order. Datum would ask the assistant to show changed dates, partial quantities, mismatched destinations, and missing confirmations against the previous accepted record. Keep unchanged items available for inspection without making the project manager reread them all.

Agree on when a status needs reconfirmation based on the upcoming work and the supplier relationship. A date that has passed without a receiving record should trigger a check, not an automatic “delivered” status. If a supplier portal cannot be reached, retain the previous evidence and mark the failed refresh. Do not quietly replace it with a guess.

Practice on the costly false green light

Anthropic recommends pairing realistic evaluation tasks with outcomes that can be checked. For this pilot, prepare historical examples with answers marked by the person who handles procurement. Include a split shipment, damaged goods, a changed finish, a warehouse delivery, and an old email quoted inside a newer message. Include a fully received package too.

Test whether the assistant attaches each update to the correct order line and preserves every missing prerequisite. Count incorrect readiness signals, missed changes, unnecessary follow-ups, and minutes spent reviewing. Require zero unsupported readiness claims in the practice set before trying the workflow alongside live operations; passing that set does not remove human review.

The first deliverable is a checked readiness list and a short queue of questions for your purchasing team. Keep substitutions, supplier messages, and crew commitments in the existing approval process. Bring the record that once fooled your team into thinking everything had arrived: it gives an AI training session a concrete problem to solve.

Sources Read

Next step, if this note maps to a problem on your desk: book a conversation with Adam. Thirty minutes, weekday evenings, Eastern time.

Related Field Notes