Keep referring dentists in the loop.
Referral updates get buried between systems.
Est. deploy 4–6 weeksSee the walkthrough
Client Communication · Construction
Turn field voice notes into a reviewed daily log.
Superintendents rewrite the same facts after hours.
For: Superintendents and the team responsible for client communication in construction.
01 · The outcome
What good looks like.
The team has a superintendent-approved daily report, with source evidence and an explicit approval before any external action. Track minutes to complete an approved daily log against a baseline; do not assume automation improves it.
A connected workflow that uses voice notes, job date, crew counts, and approved daily-log template to draft a factual daily log and mark unclear quantities or names for confirmation. It produces a superintendent-approved daily report.
Where AI helps, and where a person decides.
AI can draft a factual daily log and mark unclear quantities or names for confirmation. It drafts and organizes; it does not authorize spending, commitments, clinical decisions or customer communication. The superintendent verifies the source facts and approves the final action.
Superintendent is accountable. People approve customer-facing, sensitive, financial, and legally binding actions.
- Superintendent: Capture the source and scope
- Superintendent: Review the proposed outcome
- Superintendent: Release only the approved version
- Superintendent: Check the result and exceptions
A named person approves customer-facing messages, spending, record changes and binding commitments before release. Pre-approved scripts are versioned; exceptions stop for review.
02 · The handoffs
How the work moves.
Every handoff has an owner. Select a step to open or close its detail.
Start when: A superintendent submits consented end-of-day voice notes. Connect only voice notes, job date, crew counts, and approved daily-log template. The superintendent confirms the request is authorized and in scope.
Ready when: The source reference, permissions and accountable owner are recorded.
Use the authorized records to draft a factual daily log and mark unclear quantities or names for confirmation. Preserve the original language alongside the draft and label uncertain fields.
Ready when: Each proposed fact links back to a source, and missing information is visible.
Check a superintendent-approved daily report against the original records and current policy. Correct errors and escalate exceptions to the qualified specialist; do not auto-approve.
Ready when: Superintendent has recorded approval or a reason to hold the item.
After explicit approval, save a superintendent-approved daily report in the system of record. Send only approved messages to verified recipients. Record the version and prevent duplicate delivery.
Ready when: The approved record is saved; any delivery is confirmed or placed in the retry queue.
Review minutes to complete an approved daily log each week, sample completed records for quality, and resolve held items. Change the rules only after reviewing actual errors and staff feedback.
Ready when: Exceptions have owners, the metric has a baseline, and corrective actions are assigned.
Sample record.
$ david run --workflow=construction-voice-daily-log
ILLUSTRATIVE RECORD / NOT LIVE CUSTOMER DATA
- Example
- Illustrative only — not a real client record
- Reference
- CONSTRUCTION-VOICE-DAILY-DEMO-001
- Trigger
- A superintendent submits consented end-of-day voice notes.
- Owner
- Superintendent
- Prepared output
- a superintendent-approved daily report
- Review status
- Awaiting human approval — no external action taken
- Missing information
- Owner to verify source completeness
- Measure
- Minutes to complete an approved daily log
Start with your tools.
Connect Procore, QuickBooks, Microsoft 365 through approved APIs or controlled exports. Map record identifiers first; test permissions and field updates in a sandbox. Vendor names describe possible connections, not a guarantee of an available integration or license.
When things go wrong.
- A named person approves customer-facing messages, spending, record changes and binding commitments before release. Pre-approved scripts are versioned; exceptions stop for review.
- Use only authorized sources and role-based access. Keep an audit trail of source records, drafts, approvals and delivery status; deduplicate retries.
- If an integration fails, a source is missing or confidence is low, pause the action and assign the original request to the accountable owner.
Try this week / no DAVID required
A useful first step.
This week, have your superintendent time five examples of this work. Use redacted copies of voice notes, job date, crew counts, and approved daily-log template to make a superintendent-approved daily report manually, then list which fields required judgment.
What to measure.
- Minutes to complete an approved daily log
- Minutes of human handling per completed item
- Drafts needing substantive correction
- Exceptions unresolved beyond the agreed review window
Estimate your time back.
20.8
$11,232
03 · More workflows to consider
Related workflows.
Route post-visit questions to the right person.
Clinical questions get mixed with billing requests.
Est. deploy 4–6 weeksSee the walkthrough
Send the right approved visit instructions.
Patients receive instructions for the wrong visit type.
Est. deploy 4–6 weeksSee the walkthrough
Want this running in your business in 2–4 weeks?
Free 30-minute call. We'll tell you honestly whether AI fits, and where.