Every Late RFI Answer Is an Idle Field Labor Bill

The Money Leaves When the Crew Stops, Not When the Question Arrives

Six days. Two trades on standby. One question about a sleeve location that the model already answered.

That is the shape of the problem. An RFI gets written, logged, routed, answered, closed, and archived, and somewhere in that paperwork chain a crew stands on a deck with nothing to do. The person who wrote the RFI did their job. The person who answered it did their job in 20 minutes. The gap between that answer and the field is where the money goes.

Most firms track RFIs as a documentation metric. Open count, average response time, overdue list. Useful for the log, worthless for the payroll. The cost is not in the document. It is in the hours a crew burns standing next to material they cannot install because nobody told them which way the sleeve goes. That number never shows up next to the RFI because it lives in a different system, on a different report, owned by a different person.

Every late RFI answer is an idle field labor bill. Once you start reading it that way, the fix stops looking like a document management problem and starts looking like a cost-control problem. And cost-control problems are the ones you can actually solve.

When I talk to superintendents about this, they do not describe it as an RFI problem. They describe it as a Tuesday problem. Two guys in the wrong place, a foreman on the phone, a crane window sliding. They already know the math. They just do not get to write it down where the coordinator will see it.

What Six Days of Standby Actually Costs You

Take a two-trade standby on a commercial job. Two crews, four to six people between them, a lift and a foreman. Run that out for six days and you are not talking about a rounding error. An unresolved conflict behind a crew can burn $15K to $50K a week in idle field labour, and a clash that sat 47 days burned $28,000.

And you pay it whether or not you see it. Payroll runs Tuesday. The lift sits on rent. The general conditions keep ticking. None of those line items say the word RFI on them, so nobody connects the cost back to the question that sat in a queue for a week. The expense gets absorbed into labor variance and everybody shrugs at the end of the month.

The worse version is the compounding one. When the answer finally lands, the crew is already on another floor or another job. Now you have a remobilization cost stacked on top of the standby, plus a schedule float hit you may not recover. One sleeve location, answered late, can walk a sequence backward by two weeks.

Here is the part that stings. Your sub answered it in 20 minutes. The knowledge existed, was written down, and was correct. The six days were pure transit time. You paid for a question moving through people, not for a question being solved.

If cost control is the goal, this is the kind of cost it has to see. Not just the concrete and the conduit, but the idle time your coordination gaps created. Those hours are as real as the rebar.

The Answer Was Already in the Model

The sleeve location lives in the model. It has coordinates, a host wall, an elevation, a size, and a revision number. When the fabricator asks where it goes, the model answers. It always did. The issue was never a knowledge gap, it was a routing gap. The question went into a system that had no contact with the geometry.

BidLight keeps one live record of the project inside Revit and Navisworks. That means the answer and the question live in the same place. Every issue gets pinned to the element it concerns, and it carries the sheet and revision that raised it. When you open the sleeve detail you see the note, the trade, the status, and the person who owns it. Not a PDF attachment in a thread. Not a screenshot in an email. The geometry and the decision, together, current as of the last publish.

When the design moves, the record moves with it. Change the sleeve location, publish, and the comparison shows the element as modified, with the issue still attached. You do not need a tracker to tell you something changed. The model tells you, because every export is a versioned snapshot and any two revisions compare element by element.

That is the useful version of coordination. Not a chatbot guessing at the situation. It is a system where the object, the revision, the open question, and the owner all resolve to the same geometry. BidLight does not run automated clash detection. It tracks the changes and the clashes and issues between revisions, pinned to the elements, and an issue closes only with a screenshot, a tagged user, and the model commit that fixed it.

So the next time a foreman asks which way the sleeve goes, the answer is not a document to be chased. It is a location in the model that someone can open, with the closed issue and its proof sitting right next to it.

Why the 6am Digest Beats the Inbox

Inboxes are where answers go to wait. The person who owns the sleeve question is not refreshing a portal. They are walking a job, running a crew, or on the phone with a supplier. If the answer requires them to log in somewhere, it waits. That waiting is the bill.

The 6am digest puts the open items in front of the person who owns them, before the shift starts. Not a notification that something happened. A short list of what is blocking work today, what changed overnight, and what needs a decision before the crew mobilizes. By the time the foreman is on site, the list is already in their hand.

This is the difference between a documentation system and a cost-control system. A documentation system is satisfied when the RFI is closed. A cost-control system is satisfied when the field knows the answer before the standby starts. Same question, different finish line, and the second one is the one that shows up in your labor variance.

Pair that with a live model and the loop closes fast. Someone answers at 4pm. The digest carries it at 6am. The crew starts with the current geometry and the answer attached. That is a short turnaround on a question that used to take six days, and nobody had to chase a single email to make it happen.

You do not need a culture change to get there. You need the answer to land in the same place the work lives. For most firms that is Revit and Navisworks, not a third-party log. The shorter the distance between the decision and the geometry, the fewer hours you pay for nothing.

What This Changes About Your Schedule

Once RFI answers attach to the geometry, your record stops being a snapshot. The project view shows every issue against its owner, so you see who is behind while there is still schedule left to move work. Change the sleeve, and you see which trades are touched before anyone orders material.

Many answers ARE design changes. The sub does not just answer the question, they resolve it, and resolution moves elements. If your record is a file on someone's desktop, that movement is invisible until the field finds it. If your record is riding the model, it is visible at 6am with the rest of the digest. A change you see in the model costs about $50. The same one found in the field costs $5,000 to $50,000.

This is also where the numbers add up across a programme. On the hyperscale case study, the record produced 18,000+ hours saved and 8,900+ issues resolved, with $12.3M in cost saved. Not by replacing anyone's judgment, but by keeping the history current while the design churned. Your coordinator spends their time on the calls that need a human, not on hunting for the current version, which many lose about 11 hours a week to.

And it makes early review a service you can offer. When a client asks what a layout change touches, you can answer in the meeting, in about 15 minutes instead of a 90-minute session. You are not selling software, you are selling the ability to say what a change means out loud and defend it. That is a service line you can offer, and it is the same model you already built.

Plans run from Basics at $260 per licence per year to Max at $590, with custom Enterprise terms, and every plan includes unlimited projects. If you would rather not run it yourself, BidLight does done-for-you BIM work, including execution plans, 4D sequencing, and fabrication detailing and spooling. Either way, the field stops waiting on paper.

If you have been hoping a spreadsheet template would close the gap, this is the honest version. The gap was never the log. It was the distance between the answer and the crew. Close that distance and the standby hours come back to you as margin.