Note
The Snag Check Before the Stage Claim
Most stage rejections arrive as a surprise. The contractor submits, the QS sends back a list, and what follows is several weeks of back-and-forth over snags that were fixable in a day. The cost is not the repair. It is the payment delay while the rejection cycle runs.
A pre-submission snag check is an informal zone walkthrough conducted before the formal stage claim is submitted. It catches most rejections before they start.
Why a Stage Rejection Costs More Than a Pre-Check
When a billing stage is formally rejected, the submission timeline resets. The contractor fixes the snag, resubmits, and the main contractor has another full review cycle. Depending on the main contractor’s billing cut-off dates, a single rejection can push a stage by an entire month.
A pre-submission walkthrough takes 30 minutes. The cost is 30 minutes of a site engineer’s attention and a line in a notebook. The saving is the payment delay a late rejection would cause.
There is a second cost to a formal rejection: the relationship with the QS. A QS who has rejected a stage once scrutinises the resubmission more carefully. A contractor who arrives at the formal submission with zones already pre-cleared arrives in a better position.
What a Pre-Submission Snag Check Actually Involves
A pre-check is not a formal inspection. No certificate is issued, no sign-off is recorded, and nothing is sent in writing to the main contractor. It is a working conversation between the contractor’s site supervisor and the main contractor’s site engineer, conducted in the zone, before the stage claim goes in.
The purpose is practical: are there visible issues that would fail a formal QS check? The site engineer walks the zone and says what they see. The contractor takes notes. Anything fixable before submission gets fixed. Anything that is not actually a defect gets noted so it does not reappear as a rejection later.
The key distinction from a formal inspection is that nothing is binding. The site engineer’s observations during a pre-check are professional comments, not acceptance or rejection. Formal acceptance only happens after the stage is submitted and the QS has reviewed it.
Who to Walk With and How to Record It
The right person to invite is the main contractor’s site engineer or works supervisor, not the QS. The QS does not generally walk sites before a formal submission. The site engineer knows what the work looks like and understands what will and will not stop the QS.
Record the walkthrough in your site diary or project log: the date, the zone, who attended, what was discussed, any issues noted, and their status (fixed before submission, or noted for mutual information). Do not send this record to the main contractor unless they ask for it. It is your internal evidence of the conversation.
If the site engineer flags an item that is not a defect, for example a material that matches the approved sample but conflicts with an outdated drawing on the QS’s desk, write down the issue and the resolution: “Drawing revision discrepancy, confirmed Rev5 is the current instruction.” That note matters if the same item reappears as a formal rejection.
A Worked Example: How One Walk Prevented a Three-Week Delay
A fit-out contractor is approaching the billing stage for three zones on a commercial interior project. Each zone covers ceiling, partitioning, and floor finishes. Seven working days before the planned submission, the site supervisor walks the three zones with the main contractor’s site engineer.
In zone two, the engineer points out two ceiling tiles with chipped edges. In zone three, the silicone bead along the top of a glass partition has not been completed. Both repairs take one afternoon.
At the formal submission a week later, those two items do not appear on any rejection list. The stage is reviewed and accepted within five working days.
Without the pre-check, both items would have appeared on a formal rejection notice. The contractor would have fixed them and resubmitted. At this project’s billing cycle, a resubmission after the cut-off date would have pushed the stage to the following month. The 30-minute walk and one afternoon of repairs saved a full billing cycle.
What does a pre-submission walkthrough do to your formal claim?
It separates your submission from the batch that arrives with unknown defects. A QS reviewing a submission from a contractor who regularly pre-clears zones approaches the package differently from one who is seeing the zone for the first time. The submission itself does not change, but the pre-check means the QS already knows the most visible issues were addressed. Most snag-based rejections are caught before submission. What remains are technical or documentation questions, which resolve faster.
How far in advance of the submission should you do it?
Seven to ten working days is the practical target. That window gives time to fix anything found and still submit within the planned billing cycle. Fewer than five working days and a repair may not be completable before the cut-off date. For zones with specialist finishes or third-party sign-offs, build in more time. A pre-check that finds a problem you cannot fix in time changes your submission date, which is better learned a week early than from a rejection notice.
What if the main contractor will not join the walkthrough?
Most site engineers will join; it saves them a second review round and is part of their role. If the main contractor operates a formal-inspection-only policy, conduct a self-inspection instead: walk the zone against the acceptance criteria, record what you find, and photograph anything borderline. Attach the completed checklist to the formal submission. If a rejection comes back on a pre-checked item, you have a dated record of when it was examined.
If you want to see how a pre-submission snag check fits into a billing stage timeline where each stage is tracked against the actual work and its acceptance paperwork, a 45-minute call is the fastest way to look at one project together.