The real cost of a no-show on a data center fit-out.
When an engineer does not arrive, the day rate you save is the smallest number in the story. The real cost is everything that was scheduled around them.
Consider a rack and stack team of six on a fit-out with a booked access window. One person is missing. The team’s output drops by more than a sixth, because the work was sequenced for six pairs of hands and the pallets do not rearrange themselves. The window closes with cabinets unfinished. The next window is in four days.
Nobody on that project would describe it as a staffing problem. It shows up as a slipped milestone, a tense call with the landlord and a commissioning team rebooked for the following week. The missing engineer’s day rate never appears in any of it.
This article sets out where the cost actually sits, why no-shows keep happening and what you can do before the next one.
Count what is actually lost.
Start with the day rate of everyone waiting, then add the value of the access window itself, then the knock-on to the teams scheduled after you. Each layer is usually larger than the one before.
The people waiting. Five engineers cannot do the work of six in the same time. Some tasks need two people. Others wait on a step the missing person owned. You pay the whole team for the day and get part of a day’s output.
The window. On a live estate or a shared campus, access is booked. It may need escorts, a security desk and a change approval. When the window closes, the remaining work does not carry over to tomorrow. It waits for the next approved slot, and the next slot may be days away.
The trades behind you. Fit-out sits in a sequence. Power and cooling come before it. Cabling, network, testing and commissioning come after it. When one stage slips, every booking behind it moves. Some of those teams charge for the day they were booked whether they work or not.
The date that matters. At the end of the sequence is a handover date someone has promised. A customer’s go-live, a lease start, a migration. Contracts often price delay against that date. A single missed shift can move it.
Add those layers and the day rate you did not pay is a rounding error. That is the figure your finance team needs to see, and the one most suppliers never mention.
Why replacements are harder to find now.
A no-show used to be fixable with a phone call. That is less true in 2026.
The 2026 AGC and NCCER workforce survey found that 28% of construction firms had worked on a data center project in the past year. Of those firms, 58% said data center work had increased competition for skilled workers. Across all respondents, 42% said worker shortages had delayed projects (AGC and NCCER, 2026).
The wider pipeline is tight too. Associated Builders and Contractors estimated that US construction needed about 349,000 net new workers in 2026 to meet demand (ABC, 2026).
In a market like that, the replacement you find at short notice may not hold the same certifications. They may not have site access cleared. They may not have worked to your standards. A no-show often costs you a second day while the replacement gets through the gate.
Why it keeps happening.
Most agencies fill a role by finding a CV that matches and a person who says yes. Neither of those predicts attendance. A CV lists skills. A yes on the phone is a statement of intent made before the schedule is known.
Reliability is a behavior, and behaviors can be assessed. Vio scores it directly, from evidence of previous engagements and from scenario questions that show how an engineer handles a clash between a personal commitment and an access window.
There are other causes worth naming, because they sit on the client side:
- Late detail. Shift times, site addresses and access rules that arrive the night before invite last-minute drop-outs.
- Overlapping offers. Engineers in demand hold more than one offer. The one that confirms first, with clear terms, usually wins.
- Unclear conditions. Night work or long drives that were not in the brief are a common reason to walk away on day two.
None of these excuse a no-show. All of them make one more likely.
What to do about it.
Ask your supplier how they assess reliability as well as skills. Ask what happens on the day if someone does not arrive, and whether the replacement has been vetted to the same standard. Build the answer into the brief.
Then make your own plan less fragile:
- Confirm in writing, early. Send the shift schedule, site address, access steps and contacts at least three working days ahead. Ask for a reply.
- Clear access for a backup. If security checks take a week, clear one more person than you need.
- Sequence for loss. Plan the window so that losing one person delays the least critical task first.
- Call the day before. A short call surfaces most problems while there is still time to fix them.
- Agree replacement terms. Put the replacement time and standard in the contract, not only in a sales conversation.
None of this costs much. Most of it is a habit a project manager can adopt this week.
Put a number on your own project.
The figures that matter are yours: your team size, your window, your trades and your handover date. The cost of a no-show calculator on this site turns your own project numbers into the figure your finance team will recognize.
Run it once at the start of a project. Keep the result next to the schedule. It makes the case for paying for reliability in terms everyone on the project already uses.