Quick answer: A useful construction check-in asks seven things: what is complete, what remains, what evidence exists, what is blocking progress, which people or materials are needed, whether the planned date is realistic, and who owns the next action. The questions should be tied to a specific task and recorded as reported information, not treated as an automatic inspection, safety clearance or approval.
A construction milestone rarely fails without warning. More often, the warning lives in a subcontractor’s unanswered text, an unconfirmed inspection booking or a delivery date nobody has reconfirmed. A superintendent may know that the drywall crew is scheduled for Thursday, yet not know whether the rough-in work has actually been accepted. A project board can show every task as assigned and still leave the next trade unable to start.
Why milestone check-ins need more than a percentage complete
Imagine a tenant-improvement project with a ceiling-close milestone on Friday. Electrical reports “90% done”; mechanical reports “ready”; inspection is pencilled in. Neither answer says whether an inspection was passed, whether final tests are documented, or whether someone must return to correct an issue. A progress percentage may be useful for planning, but it is not evidence that a predecessor has been released to the next trade.
A better process starts with the dependency: Which authorised decision or deliverable must exist before work proceeds? For one task, that might mean a material delivery. For another, it might mean an inspector’s approval or a site manager’s documented sign-off. The check-in collects current facts so the responsible person can make that decision.
OSHA’s construction communication guidance emphasises coordination among employers and contractors when work and hazards overlap. A scheduled call can support that communication, but it cannot replace required job briefings, stop-work processes or competent-person inspections.
The seven questions to include in a construction check-in
1. What work has actually been finished since the last update?
Ask for a named activity, location and outcome: “Which of the Level 2 corridor rough-in sections were completed today?” An answer such as “we made progress” should not turn a status green. If the subcontractor can report a completed scope clearly, the manager can compare it with the acceptance criteria. Distinguish work reported complete from work verified and approved.
2. What specific work remains before this milestone?
Ask about remaining quantities, trade interfaces and punch items. “One firestop location outstanding” is actionable; “nearly there” is not. Where the task covers multiple areas, use separate tasks or subitems to avoid hiding a single unresolved portion beneath a parent completion label. The question should refer to the board item the recipient actually owns.
3. What proof or confirmation is available?
Depending on the project, the answer may identify a photo, test sheet, delivery note, inspection request or document reference. The AI call should capture where that evidence can be found, not invent it or certify its adequacy. If an inspection is required, record “requested”, “scheduled”, “passed” and “not confirmed” as different states. An authorised person should evaluate the evidence against the contract and governing requirements. Our pre-inspection follow-up guide goes deeper on this step.
4. What is blocking you right now?
Give the participant options to describe the obstacle in their words: access, predecessor trade, materials, drawings, decision, labour availability or another constraint. Then ask who can remove it. “Waiting on revised shop drawing from the design lead” is better than “blocked”. Blockers should create a human action where necessary instead of triggering speculative edits to unrelated project data.
5. Which crew, material or permit must be ready next?
Milestone confidence depends on handoffs. Ask whether the next crew has access, the material is on site, the equipment is booked and any required permits or approvals are confirmed. For electrical and mechanical interfaces, avoid treating one trade’s verbal assurance as authorisation for another trade to start. A missed handoff should reach the superintendent or appropriate coordinator.
6. Is the target date still realistic, and why?
Collect an estimated completion date and the assumptions behind it. “Thursday if the lift arrives before noon” is not the same as a firm Thursday commitment. If the date changes, the response can be logged for management review; whether it changes the contractual schedule, client commitment or milestone baseline is a separate authorised decision.
7. Who owns the next action, and by when?
End with one accountable owner and a concrete next checkpoint. For example: “The mechanical foreman will provide the revised test record by 3 p.m. tomorrow.” If the person cannot name an owner, record “ownership unresolved”. A useful call ends with a responsibility and a deadline, not simply a call summary.
Build a milestone-ready monday.com board
Use a parent item for the milestone and individual items or subitems for its prerequisites: trade close-out, inspection request, inspection outcome, evidence review, handover to the next crew. Define separate owners and dates where people actually differ. monday.com’s subitem guidance explains that subitems may have their own column structure, so confirm the supported data mapping before configuring an external calling workflow.
A practical board might track: named task, responsible person, next call date, reported status, blocker category, promised next step, evidence reference and human verification status. Those field names are a suggested board design, not a claim that a specific Autoza setup creates them automatically. Never map an ambiguous “all done” answer directly to “inspection approved”.
Autoza AI for monday.com publicly describes scheduled start-of-day and status calls, configured questions, board updates, retries and call summaries. Its published description mentions status fields, notes and timestamps. Teams should confirm any detailed subitem mapping and exception rules in their own configuration before relying on them. For a full walkthrough, see how to automate subcontractor progress check-in calls in monday.com.
When to call, retry and escalate
Milestone-critical dependencies deserve a more precise schedule than ordinary daily updates. Call a trade lead at an agreed time that allows an intervention before the next shift. For a Friday ceiling close, the project manager might review blocking items on Tuesday and Thursday. A missed call is not proof that the work is late; it means the information is missing.
Set reasonable business-hour windows and make participation arrangements clear. Retry only within approved limits. Escalate to a human when the answer describes a safety concern, an unresolved inspection, a disputed completion claim, missing access, or a change that affects another trade. An AI status call should never become the emergency reporting channel for an active hazard. To decide when a call is the right channel at all, read phone calls vs monday.com notifications for subcontractor updates.
Sample check-in dialogue for a ceiling-close milestone
AI caller: “This is the automated project follow-up caller for the Level 2 ceiling-close work. Is this a good time for a short status update?”
Foreman: “Yes. All cable pulls are done, but we have one test report to upload.”
AI caller: “Which report is missing, who will provide it, and when do you expect it?”
Foreman: “Circuit verification. Our lead electrician will send it by 2 p.m.”
AI caller: “Has the required inspection been confirmed as passed by the authorised inspector?”
Foreman: “Not yet. We are waiting for confirmation.”
The correct record is not “milestone complete”. It is “work reported complete; document pending; inspection not confirmed; human review needed”. This is an illustrative script for planning, not a transcript from a customer.
Measure whether the questions improve coordination
Review answer completeness, number of actionable blockers identified before a deadline, overdue ownership gaps, and corrections needed after human verification. Also ask foremen whether questions are short and relevant. A call that gathers ten fields nobody uses is less valuable than a focused call that reveals one blocking dependency early.
For crews who already respond promptly to monday.com notifications, the board may not need another call. Use calling when the phone is the practical route to reliable information, and preserve human judgment for technical approvals. Crews that report every day may find our guide to daily progress updates from field crews useful.
Frequently asked questions
Can an AI check-in confirm that a construction inspection has passed?
No. The caller can record what a participant reports and where supporting evidence may exist. Only the authorised inspector or responsible approver can establish the inspection outcome. Keep reported and verified states separate.
Should every construction task receive the same seven questions?
No. Use the seven as a question bank. A materials delivery needs fewer questions than a multi-trade close-out. Choose the smallest set that produces a usable next action for that role and milestone.
Can construction subitems be followed up separately in monday.com?
monday.com supports subitems with their own columns. Whether an AI calling integration can call and map every desired subitem field depends on the implementation and permissions. Verify support and test a sample board before rollout.
What happens when the subcontractor does not answer?
Mark the attempt as unanswered, retry within the approved calling schedule, and notify the assigned human owner if the deadline warrants it. Do not infer absent, late or incomplete solely from a missed call.
How often should milestone check-ins happen?
Base timing on dependency risk and the time remaining to intervene. High-impact handoffs may justify several planned checkpoints; low-risk tasks may only need an update near the due date. Agree on calling hours and avoid unnecessary contact.
Turn milestone uncertainty into a controlled workflow
The point of a construction check-in is not to replace a superintendent. It is to give the superintendent a consistent stream of specific, attributable, reviewable information before handoffs become expensive. If your team manages construction tasks in monday.com, explore Autoza’s scheduled call workflow or request a guided workflow review to discuss questions, ownership and approval boundaries.
Related reading
- Phone Calls vs monday.com Notifications for Subcontractor Updates
- Pre-Inspection Follow-Up: Which Construction Tasks Need a Phone Call?
- Construction Daily Progress Updates: A Better Way to Hear From Field Crews
- How to Automate Subcontractor Progress Check-In Calls in monday.com
- Autoza AI for monday.com: scheduled status calls
- Workflow automation services
- Daily Check-in Agent