Weekly look-ahead schedule drafting

The job

The superintendent on a US general-contractor job in the $5–10M-a-year shop — often the owner wearing a hard hat, or one field person who also orders material, walks inspections, and texts the owner at 5 p.m. There is no dedicated scheduler whose only job is the three-week look-ahead. Every Monday (or Sunday night) someone has to turn the master schedule snapshot, last week’s dailies, the open RFI / submittal log, the weather forecast for the site ZIP, and a scratch manpower note into a readable this week / next week / week after plan the foremen and subs can run. If the first pass is a vague “continue interior work,” nobody shows up with the right crew. If a fluent draft invents finish dates, invents headcounts, or rewrites the critical path the Contract Documents already bound, you have worse than a late look-ahead — you have a schedule that looks official and is wrong.

This job is use an agent, not build a model. The super already has a desk: the current master / baseline schedule export or PDF the PM keeps, last week’s signed dailies, open RFI and submittal lists, weather.gov for the job city or ZIP, a notepad of who is coming / who is short, and Excel/Word/PDF for the look-ahead sheet. The agent sits in the assemble-and-draft step only. It does not own sequencing. It does not call crews. It does not become the CPM master schedule. An unsigned AI draft is not a look-ahead, and it is not a Contract Time change.

Without an agent the work is still the same: pull what the master says is planned, reconcile what last week’s dailies actually did, flag open items that block work, check weather that will stop exterior or pours, write the three-week grid, call the trades, issue the sheet.

What the Contract Documents expect on schedule (official AIA — not the look-ahead form). Official A201–2017 summary § 3.10.1: the Contractor’s schedule must contain detail appropriate to the Project, including (1) the date of commencement, interim milestone dates, and the date of Substantial Completion; (2) an apportionment of the Work by trade or building system; and (3) the time required for completion of each portion of the Work. Official AIA learn on construction schedule & Substantial Completion: Article 8 is the general-conditions home for schedule language; § 8.1.1 defines Contract Time as the period of time, including authorized adjustments, allotted in the Contract Documents for Substantial Completion of the Work; § 8.2.1 — by executing the Agreement, the Contractor confirms that the Contract Time is a reasonable period for performing the Work; § 9.8.1 defines Substantial Completion. Official AIA learn on managing delays: after award the contractor must submit a construction schedule that includes commencement, interim milestones, and Substantial Completion; an apportionment of the Work by construction activity; and the time required to complete each portion; the schedule should show sequence and progressions and be revised appropriately as project conditions change; missing a notice deadline can impact the right to seek additional time or compensation. Official preview: A201–2017 PDF — Article 3 / § 3.10 Contractor’s Schedules and Article 8 Time (cite via AIA materials; do not invent clause text not read).

What a field look-ahead is (and is not). A short-interval look-ahead (often called a weekly look-ahead, 2-week, or 3-week look-ahead) is a field coordination instrument: day-by-day or week-by-week work planned for the near term, by trade/location, with constraints called out (open RFI, missing submittal, weather, manpower). It is not the CPM / network master schedule under § 3.10. It does not change Contract Time. It does not replace a Change Order when scope, sum, or time must move. It is the sheet the super issues so Monday’s crew matches Monday’s work.

Where Division 01 parks the language. CSI MasterFormat 2026 is the current North American shared language for organizing project requirements; Division 01 (General Requirements) received maintenance updates. A published MasterFormat 2018 numbers listing used by industry references 01 31 00 – Project Management and Coordination (management and coordination of subcontractors; project meetings), 01 32 00 – Construction Progress Documentation (administrative/procedural requirements for scheduling, recording, and reporting progress), 01 32 13 – Scheduling of Work, and 01 32 16 – Construction Progress Schedule (AGC Austin MasterFormat 2018 PDF). MasterFormat is numbering language, not a look-ahead form. Your project manual and your contract name who maintains the Contractor’s Construction Schedule, who updates it, and what short-interval reporting the Owner or Architect expects. Draft into that format when Division 01 already names one.

This job is not a daily, not a safety note, not a company pipeline digest, and not the CPM.

• Not a superintendent daily. A construction daily is a contemporaneous, dated, jobsite-level record — manpower, weather, work in place, delays, visitors, a signature by the person who was there. Sister job: superintendent daily field report. Dailies feed the look-ahead (what actually happened last week); they are not the forward plan.
• Not a safety observation. Sister job: safety observation and near-miss logging. A look-ahead may note “fall-protection required on Level 3 deck” as a constraint; the hazard/near-miss log is a different seat.
• Not the president’s pipeline / backlog digest. Sister job: pipeline and backlog digest. That seat is company forward work and cash runway across bids and backlog — not one job’s three-week field plan.
• Not the president’s weekly risk digest. Sister job: weekly project-risk digest. That seat reads exceptions across jobs; this seat writes one job’s short-interval look-ahead.
• Not OAC meeting minutes. Sister job: first-pass OAC meeting-minutes drafting. Minutes may review “schedule for next period”; they are not the crew-call sheet.
• Not the CPM master schedule itself. § 3.10 / 01 32 16 is the Contractor’s Construction Schedule. The look-ahead is a short-interval extract and field plan derived from it — not a replacement for updating logic, float, or Contract Time.

Why a $5–10M GC still does this. A late or sloppy look-ahead is the wrong trade on site, a pour in the rain, a deck waiting on an unanswered RFI, and a Monday morning spent on the phone instead of the building. On this size GC the short-interval plan is usually the superintendent / owner-super with the PM’s master-schedule export — not a separate scheduler. That is why the first-pass draft from real inputs is the job — and why the human still owns every sequence call, every crew count, weather go/no-go, and the issue to the team. Do not claim AI can update Contract Time or replace the master schedule.

Use

This is a use workflow. You do not train a model. You do not ask it to invent crew counts, finish dates, float, or a weather delay. You give it what the files and the site already show, you get a draft three-week grid, you edit and issue only what you would defend when the foreman asks “who is on the slab Thursday?”

1. Confirm the instrument. Are you drafting a weekly / 2-week / 3-week field look-ahead for issue to trades (your Excel columns or Word headings), or does Division 01 / the Owner already name a short-interval format under 01 32 00? Draft into that. Do not fork a competing “official” CPM. Do not treat the look-ahead as a Modification of Contract Time.
2. Gather only this look-ahead cycle’s inputs. Current master / baseline schedule snapshot (PDF, export, or marked print) for activities that fall in the next 1–3 weeks; last week’s signed dailies (what actually started, finished, or slipped); open RFI and submittal items that block near-term Work (number + subject only if in the upload); weather.gov forecast for the job city or ZIP covering the look-ahead window; your manpower / crew-availability notes (who confirmed, who is short); prior look-ahead if this is a revision. Do not feed “the whole job folder” and hope.
3. Separate facts the files show from calls only a human may make. Activity names, locations, and open-item numbers can be drafted from the upload. Sequence, crew size, which day a trade actually runs, whether weather stops the pour, and whether an open RFI is a hard stop are the superintendent’s call — pulled from the site and the Contract Documents, not from model memory. If last week’s daily does not show headcount, write unknown — super to confirm, do not invent “8 carpenters.”
4. Look up weather; do not invent it. Pull the multi-day forecast for the job’s city or ZIP from the National Weather Service (about / forecasts). Paste the forecast line into the upload. The agent does not replace NWS. A model paragraph that says “clear all week — pour Friday” without an NWS source is theater.
5. Feed the agent those files plus your template. Your Excel columns or Word headings (week / day, activity, location or grid, trade, crew note, constraints / open items, weather flag, status). Prompt shape: draft one short-interval look-ahead for this Project only covering this week and the next two; use only the uploaded master-schedule slice, dailies, open-item list, weather.gov line, and manpower notes; do not invent activities, dates, crew counts, or percent complete; flag open RFIs/submittals that appear in the upload as constraints; leave crew and sequence cells as super to confirm unless the notes name them; do not change Contract Time; do not claim this is the CPM master schedule; footer: “Draft only — superintendent owns sequencing, crew calls, and issue; not a schedule update under A201 § 3.10 / not a Contract Time change.”
6. Human edit before anyone else sees it. Walk the draft against the master slice and last week’s dailies. Strike invented activities and phantom finish dates. Confirm every open RFI/submittal constraint is real. Confirm weather flags match NWS, not folklore. Confirm crew notes match who you actually called. Confirm you did not “solve” a delay by inventing recovery logic that belongs in a real schedule update or a Change Order / claim path.
7. Issue to the team — human only. Text/email/PDF the edited look-ahead to foremen and subs the way you already do. Call the crews yourself. The agent does not auto-text the drywall sub a raw model draft as “next week’s plan.” If Division 01 or the Owner expects the short-interval sheet posted at the trailer, post the human-issued version.
8. Log the way you already do. Keep the issued look-ahead with the week’s dailies. When the near-term plan forces a real master-schedule update (logic, duration, milestone), that update is the PM/scheduler seat under § 3.10 / 01 32 16 — not a silent rewrite inside the look-ahead. Sister seats stay separate: yesterday’s record is daily-report; hazard notes are safety-observation; company backlog is pipeline-digest.

Expected shape of the gain: less time turning the master slice, dailies, open items, weather, and manpower notes into a readable first-pass three-week grid the superintendent can edit before crew calls. That is not “the model ran the schedule.” There is no published, independent hours-saved or accuracy number for a $5–10M GC first-pass look-ahead draft that this page will invent. Time one of your Monday cycles (draft + your edit vs writing cold) before you change anything you pay for.

Build

A general-purpose model that can read a schedule PDF/export, daily-report text, open-item lists, and a weather.gov paste can draft a three-week grid from those inputs. Sequencing, crew calls, weather go/no-go, and whether an open RFI is a hard stop need a person. Do not treat the draft as a § 3.10 schedule update, and do not build from invented activities or phantom finish dates.

A workable v1: a prompt template that returns one look-ahead package — week/day columns, activity and location sourced only from uploads, trade column, crew column defaulting to super to confirm unless named in notes, constraints column (open RFI/submittal numbers only if in the upload), weather flag sourced from the NWS paste, flags (not in uploads / possible hard stop / weather conflict / draft — not CPM / not Contract Time change), and a “superintendent owns sequencing, crew calls, issue” footer. Keep the source files with the look-ahead. Require “not in the uploaded files” instead of filling a gap.

Do not build a custom scheduler this quarter. Do not fine-tune. Do not connect a model to auto-email subs or auto-update the master CPM. This week’s inputs are the only corpus that matters.

Deploy

1. Pick five recent look-aheads you still stand behind — one clean interior week, one weather-sensitive exterior/pour week, one week blocked by open RFIs, one week where last week’s dailies showed a slip, one quiet week that was mostly carry-forward.
2. Run the agent on the same master-slice + dailies + open-item list + weather.gov paste + manpower notes only (no later “what we actually did” emails that reveal outcomes unless you are testing edit, not prophecy). Time upload, draft, and your edit.
3. Diff the draft against what you actually issued / what the crews ran. Record invented activities or finish dates, invented crew counts, missed open-item constraints, weather calls that ignored NWS, and any draft that claimed to update Contract Time or replace the CPM.
4. Decide using a rule set in advance: no draft goes to trades unedited; every activity and date must exist in the master slice or a super-supplied cell; if the model invents five fluent “complete Level 2 framing by Thursday” lines the master never showed, it is not ready.

Use your real schedule export and your real dailies, not a vendor demo. Keep the workflow only if the sheet you would issue is still something you would put your name on when the drywall foreman shows up.

Manage

What “good” looks like

• A named human edits every draft, owns sequencing and crew calls, and issues to the team.
• Raw model text is never emailed or texted to subs, the Owner, or the Architect as “the schedule.”
• The upload includes the master slice, dailies, open items, weather.gov paste, and manpower notes actually used — not a memory of “typical week.”
• Look-ahead vs daily vs safety note vs pipeline digest vs CPM master schedule stay distinct. Sister seats stay those jobs.
• Weather is copied from NWS for the look-ahead window, not generated.
• Crew counts and finish dates appear only when a person confirmed them or the source file states them. Blank / super to confirm is honest; a confident fake headcount is not.
• Contract Time and § 3.10 schedule updates are not silently rewritten inside a look-ahead PDF.
• If you already have a look-ahead / field-schedule template or app, the agent drafts into that. This page does not sell a new one.

Who owns the seat

The superintendent / owner-super owns the short-interval look-ahead, sequencing, crew calls, and issue to the team. On a $5–10M GC that is one person and the phone/laptop they already use. The PM (if you have one) owns the Contractor’s Construction Schedule under § 3.10 / Division 01 and Contract Time conversations with the Architect/Owner. An agent does not become either seat.

When to skip the agent (what not to automate)

• You have no master-schedule slice and no recent dailies. Do not ask a model to remember the job.
• You expected the model to invent crew sizes, finish dates, or recovery logic. Wrong seat.
• You need a formal schedule update, time-extension analysis, or Claim under Article 8 / 15. Use the contract path and counsel — not a look-ahead paraphrase. Official A201 summary: Notice of Claims may not be electronic.
• Weather will decide a pour or exterior work and you have not looked at weather.gov. Look it up first; do not let the model guess.
• Life-safety stop-work or an active incident — write the plan yourself; at most let the agent format headers from known constraints.
• The Monday look-ahead habit is already a clean Excel sheet and typing is not the bottleneck. Leave it.

How to stand it up this quarter

Use the model you already have access to. Drop in this week’s master slice plus last week’s dailies plus open RFIs/submittals plus the weather.gov paste plus your manpower notes plus your look-ahead headings. Edit every line, call the crews, issue the sheet. Keep the workflow only if the package is still something you would put your name on. Do not buy a scheduling product to complete this job.

Citations

Tools are citations, not new brand pages. Do not invent vendor homepages. This page does not create a Procore, Autodesk, Primavera, Microsoft Project, Buildertrend, or other schedule-app vendor listing.

• AIA A201–2017 summary — § 3.10.1 Contractor’s schedule detail (commencement, interim milestones, Substantial Completion; apportionment by trade/system; time per portion); Article 8 Time / weather and claim-notice context in the same summary.
• AIA construction schedule & Substantial Completion — Contract Time § 8.1.1; Contractor confirms Contract Time reasonable § 8.2.1; Substantial Completion § 9.8.1.
• AIA manage construction delays — post-award schedule contents; revise as conditions change; extensions and notice discipline.
• AIA A201–2017 official preview — Article 3 / § 3.10; Article 8 (cite via AIA materials, not invented clause text).
• National Weather Service / About — official US weather and forecasts for the look-ahead window. Look up the job; do not let the model guess the high.
• CSI MasterFormat 2026 / MasterFormat 2018 numbers PDF — Division 01; 01 31 00 Project Management and Coordination; 01 32 00 Construction Progress Documentation; 01 32 13 Scheduling of Work; 01 32 16 Construction Progress Schedule. Numbering language; your Division 01 wins.
• Excel, Word, PDF, email — draft grid, crew-call sheet, issue package. If they already have a look-ahead / field-schedule app, the agent drafts into that. No new vendor page on this site. Sister seats: daily report, safety observation, pipeline digest, risk digest, RFI, submittal, meeting-minutes.

Watch-outs

• Invented activities, finish dates, and crew counts. Models write fluent “Level 2 framing complete Thursday — 6 carpenters” lines that are not in the master slice or your manpower notes. Same failure mode as legal citation hallucination: Dahl, Magesh, Suzgun & Ho, Large Legal Fictions, 16 J. Legal Analysis 64 (2024) (arXiv:2401.01301, doi:10.1093/jla/laae003) — public LLMs, asked verifiable questions about federal cases, hallucinated often and often could not tell. Those percentages are legal-case questions, not look-ahead accuracy; do not import them as a construction performance rate. Do import the habit: every activity, date, and headcount in the draft is unverified until you open the sources. Blank / super to confirm is honest; a confident fake crew is not.
• Treating an AI look-ahead as the CPM master schedule or a Contract Time change. Official path for the Contractor’s Construction Schedule is § 3.10 / Division 01 progress documentation. Contract Time moves by the Contract Documents (Change Order / claim path), not by a three-week PDF. AI does not update float and does not grant time.
• Weather theater. Copy NWS for the look-ahead window. A model paragraph that schedules a slab pour under a forecast the upload never contained is not a plan.
• Ignoring open RFIs / submittals that block Work. If the upload shows an open item on the activity you planned, flag it. Do not invent clearance.
• Mixing seats. Look-ahead ≠ daily ≠ safety observation ≠ pipeline digest ≠ risk digest ≠ OAC minutes ≠ formal § 3.10 schedule update.
• Photo / progress theater as percent complete. A 2026 field evaluation of general-purpose multimodal assistants on 1,186 photos from 17 live sites found stronger performance on descriptive tasks than on judgment-intensive ones; models can emit confident narratives that go past the picture (Smart Cities 2026, 9(7), 114, doi:10.3390/smartcities9070114). Do not put model-inferred “% complete” from photos onto a look-ahead that trades will run.
• Unsigned AI to the team. Fluent, late, and wrong is worse than a short human grid. Do not let the model send.
• Do not replace the superintendent. The agent drafts from the master slice, dailies, open items, weather, and manpower notes. The super still owns sequencing, crew calls, and issue.

Verdict

Yes — a $5–10M US GC should run this job this quarter if the short-interval look-ahead already starts as a master-schedule slice, last week’s dailies, open RFIs/submittals, weather.gov, and manpower notes; the bottleneck is turning that stack into a readable first-pass this-week / next-two grid; and a person will still own every sequence call, every crew count, weather go/no-go, and the issue to the team. Use an agent to draft the 1–3 week field look-ahead from those inputs; the superintendent owns sequencing, crew calls, and issue. Skip this quarter if you expected the model to invent crews or finish dates, to replace the CPM master schedule or change Contract Time, to skip weather.gov, to auto-text subs, or to buy a scheduling product you do not already have. Do not publish this page as a vendor listing.