Keep Commitments Clear in AI Client Updates.

A supplier says a fixture is expected next week. A project manager notes that installation depends on receipt and crew availability. By the time an AI draft reaches the client, those qualifications can disappear into a confident sentence: “We will install your fixture next week.”

That hypothetical mistake is a useful test for an AI writing assistant. Datum’s proposed starting point is a weekly client update that preserves the status of every date and commitment. The project manager reviews the draft alongside its source records before sending it.

Start with the reporting period and the last message

Procore’s progress-report guide includes the reporting period, completed work, current activity, issues, planned actions, and upcoming dependencies. Those categories help separate what happened from what the team expects to happen. The guide is established construction guidance, not a new AI product announcement.

For a client-facing draft, assemble the current approved schedule, relevant field notes, open client decisions, and the last update actually sent. Label the project and reporting cutoff. Include older unresolved items when they still affect the client; a weekly date filter alone can hide an unanswered question.

Anthropic’s context-engineering guidance recommends selecting the relevant information a model needs and using clear instructions and representative examples. Applied here, that means giving the assistant a focused set of project records and a sample of an approved update. A large folder of messages still needs rules for which records govern a statement.

The last sent update matters because the client may be planning around it. Ask the assistant to flag anything that now differs: a forecast date, an outstanding choice, or a promised follow-up. A polished description of this week’s work can still leave last week’s question unanswered.

Keep uncertainty attached to the sentence

In the fixture example, an internal review note might read: “Supplier expects delivery next week; receipt and crew availability remain unconfirmed.” The project manager can then approve wording that explains the situation without choosing an installation date the team has not committed to.

A client draft could say: “The supplier currently expects your fixture next week. We will confirm the installation date after receipt and crew availability are checked.” That follow-up is itself a commitment. Use it only when the project manager accepts responsibility for it. The assistant should flag a missing follow-up owner rather than create one.

• Completed work: state what the record supports, with a source the reviewer can open. Keep inspection acceptance separate when it has not been recorded.
• Upcoming work: preserve the schedule’s status and any condition that affects the date. Identify conflicts for the project manager to resolve.
• Client decisions: name the choice, the person responsible, and an existing due date. Flag a missing date for review.
• Changes since the last update: identify what moved and the recorded explanation. Do not invent a cause or assign blame.
• Follow-up: carry forward an agreed action and owner, or mark the action as proposed for the project manager’s approval.

Give the reviewer evidence without exposing the whole job file

Keep an internal review copy with links beside factual claims. Prepare a separate client draft using only information approved for that audience. Internal supplier discussions, personal contact details, and commercial notes should not appear simply because the assistant could read them.

If a source is missing, stale, or contradictory, put the issue in the review copy. Avoid reassuring phrases such as “everything is on track” when the records do not establish that. If new information arrives after review, check the affected statements again before sending. Save the approved message so next week’s draft starts from what the client actually received.

Compare the draft with the update your team would send

Try the process on past reporting periods using only records available at each cutoff. Include an unresolved client choice, a conditional delivery date, a changed schedule, and an inaccessible source. Have the project manager prepare the expected facts and open questions before reviewing the AI draft.

Count unsupported commitments, omitted follow-ups, incorrect status changes, and details that should have stayed internal. Compare total preparation and correction time with the current process. This is a proposed trial; no time savings are assumed.

Keep sending manual during the trial. If checking the draft takes longer than writing it, narrow the assignment to a single section, such as completed work. Expand only when the project manager can verify the evidence and wording with less effort.

• Keep unknowns visible in an AI daily report
• Preserve client approval when tracking selections
• Explore practical AI training for your team

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