The project execution cockpit: RFIs, look-aheads and field issues in one queue

Thursday, 6:40 a.m. The superintendent opens the three-week look-ahead that was supposed to be locked last night. Half the commitments still say “confirm with MEP.” Two trades have already asked, in a WhatsApp thread that started with a photo of a wet slab and ended with twelve people arguing about who owns the blockage. The Excel RFI log shows forty-three open rows; the ones that matter are buried under status colors nobody trusts. The PM is driving to site with a half-written response on a laptop that will not sync until coffee.

This is day-to-day execution for a lot of mid-market general contractors — three to fifteen active jobs, real money on the floor, and coordination still living in spreadsheets, chat threads and emailed PDFs. People do not need another nine-hour construction management course. They do not need a mega ERP that promises to replace every habit at once. They need the practice of running the job — RFIs, submittals, look-ahead commitments and field issues — to be operational in one place, with clocks they can see and a human who still owns the send.

When the look-ahead is a wish list

A rolling three-week look-ahead only works if it is a commitment register, not a slideshow. Each near-term item needs an owner, the blockers that will kill it, and done criteria someone can check without a meeting. The Thursday ritual is where that register gets honest: what moved, what slipped, what is blocked by design, procurement or another trade, and who owes the next move.

On too many jobs the look-ahead is rebuilt from memory every week. The superintendent knows the floor. The coordinator knows the design queue. The PM knows the owner conversation. None of them share one list that ages in public. By Monday the “plan” is already fiction, and the week is spent chasing people instead of clearing the path.

The fix is not more columns in Excel. It is treating the look-ahead the same way you treat an RFI backlog: as a living queue of coordination objects with owners and clocks — reviewed on a fixed cadence, not reinvented under pressure.

WhatsApp is not a field log

A photo arrives at 11:17. Crack at the interface. Someone tags three people. Someone else forwards it to the architect’s personal number. By afternoon the thread has forty messages, two contradictory instructions, and no single record of who dispositioned the issue. When the PM rotates off or the superintendent goes on leave, the handoff pack is a screenshot folder and a prayer.

Field photos should become issues: structured, owned, severity-visible, linked to the same triage queue as RFIs and submittal actions. Safety-class issues need an authorised clearer — not whoever happened to reply last in the group chat. The daily question should be boring and ruthless: what is blocked, who owes, what changed. If answering that requires scrolling twelve chats, the job is running on archaeology, not coordination.

Excel and PDF export still matter. Teams will not abandon the habit of printing a log or emailing a pack overnight. First-class export is the bridge — not a consolation prize — while the live queue becomes the place work actually moves.

The unit of record is the coordination object

RFIs are contractual instruments. Submittal actions have review clocks. Look-ahead commitments bind trades to near-term work. Field issues either clear before they become change events or they do not. Those are the units of record for day-to-day execution — not a dashboard tile, not a course certificate, and not a chat message that evaporates.

Anything that drafts language against those objects has to respect the same rule the job already knows in its bones: nothing leaves without a named human gate. An AI draft that cites provenance from project knowledge — drawings, specs, prior RFIs, meeting notes held in a governed store such as Contextkeep — can cut the blank-page time. It cannot file the RFI, release the submittal response, or close a safety-class issue on its own. The disposition is named. The clock stays visible. The audit shows who approved what against which sources.

Contractual clocks matter because trades plan crews against them. An RFI that sat nine days in a pink Excel cell while everyone assumed someone else owned it is how you burn a pour window. A submittal that looked “in review” in three places and was expired in none of them is how you discover the shop drawing fight after the material is on a truck. Visibility is not vanity; it is how the superintendent decides whether to remobilize.

That is the difference between “we use AI on site” and a cockpit an Ops Director will actually trust: triage in, draft with citations, human disposition out.

One queue instead of three silos

What Ops Directors and PMs actually need on a mid-market GC book of work is a single coordination cockpit:

RFI and submittal triage — backlog with status, owner and contractual due dates visible, not color-coded folklore in a workbook tab.

AI draft with provenance — first-pass language and routing notes grounded in cited project context, held as draft until a named person issues or rejects.

Named human disposition — clear who closed, deferred, escalated or routed; safety-class items require an authorised clearer.

Rolling three-week look-ahead as commitment register — owner, blockers, done criteria; Thursday ritual to keep it honest beside the open coordination items.

Field photo → issue triage — capture becomes a structured object in the same queue, not a forever-thread.

Daily blocked / owes / changed — a short operational cut of the queue, not another status meeting that restates WhatsApp.

Handoff packs — when a PM leaves for a week or supers rotate, the next person inherits the open objects, clocks and dispositions — not a scavenger hunt.

Rotation is where Excel-and-chat jobs bleed. The outgoing PM dumps a folder. The incoming super inherits half-answered RFIs and a look-ahead that still names people who left last month. A handoff pack that is just the live queue — open items, ages, owners, draft history, blockers — is how you stop paying a tax every time someone takes leave.

That cockpit is what Crewspan is built to be: Atlas’s project execution application for the live coordination loop between office and field. It is not earned-value month-end — that is Baselinecast’s lane. It is not commercial change and payment instruments — Awardbind links out when an issue becomes a commercial event. Crewspan’s job is to keep RFIs, submittals, look-ahead commitments and field issues moving without replacing every other system on day one.

What the PM opens before 07:30 is a daily coordination board — blockers, aging contractual clocks, what changed since yesterday — and a gate queue of AI drafts waiting for a named human. RFI and submittal detail screens hold the draft with provenance citations; issue and disposition stay blocked until approve. The superintendent runs a look-ahead board where open RFIs and issues appear as blockers on commitments, then marks done or missed with a reason so planned-vs-done is a hit-rate, not a whiteboard photo. Field raises an issue from a phone photo and gets a triage suggestion (RFI vs chase vs safety vs commercial); safety clearance stays open until a safety officer clears or refuses with a recorded reason. When someone rotates off the job, a handoff pack snapshots open RFIs, critical submittals, commitments and issues with owners — not a dump folder. Excel export of the old log columns stays first-class so sceptical PMs keep a comfort copy during transition.

What “better” looks like on the ground

Value shows up in measures supers and PMs already argue about in the trailer:

• RFI cycle time — days from open to dispositioned response, with clocks visible while the item is hot.
• Look-ahead hit-rate — share of Thursday commitments that actually clear on their done criteria, not that looked good on a slide.
• Issues closed before change events — field and coordination noise cleared early enough that it never becomes a variation fight.
• Time out of WhatsApp archaeology — hours not spent reconstructing who said what, when the queue already holds the object, the draft history and the named disposition.

Those are operational outcomes. They do not require a platform rip-and-replace story. They require the backlog, the look-ahead and the field intake to stop living in three places that never meet.

What this is not

It is not a Procore feature-parity pitch. Jobs already on a CDE keep that system of record where it belongs; the cockpit is the coordination practice sitting on top of how people actually work today.

It is not Baselinecast. No CPI/SPI theatre, no month-end optimism pack. Progress evidence for earned value stays in controls.

It is not Awardbind. When coordination turns into commercial change, you link out — you do not pretend the RFI queue is the contract instrument.

It is not a training LMS. Nobody on a live job is asking for another curriculum. They are asking for Thursday’s look-ahead to be true and for the RFI that is burning a trade to leave with a human signature and a clock that did not silently expire.

First cut for a mid-market GC

Start narrow. Pick a slice across a few live jobs — not the whole company — where Excel RFI logs and WhatsApp photo threads are already the pain:

1. Stand up RFI and submittal triage with AI draft and mandatory human gate before anything files or emails.
2. Put the rolling three-week look-ahead beside that backlog as a commitment register, with a Thursday ritual and visible blockers.
3. Route field photo and short-note intake into structured issues in the same queue, with authorised clearers for safety-class items.
4. Keep Excel and PDF export first-class so the habit bridge does not become a reason to stall.
5. Leave EVM in Baselinecast and commercial instruments in Awardbind; measure cycle time, look-ahead hit-rate and archaeology hours on the Crewspan slice alone.

Scope that cut in a Solution Definition Sprint: which jobs, which object types, which approvers, which clocks, which exports. Mid-market GCs with roughly three to fifteen active jobs are the natural fit — enough concurrent coordination to hurt, not enough bureaucracy to absorb another mega-system project.

See AEC and built environment, explore Crewspan on the Atlas, or bring us the jobs still running from Excel and WhatsApp.