What to do if a builder rejects a snag

Rejection is common, especially when descriptions are vague or evidence is unclear. The best response is calm, specific, and documented.

Step 1: get a clear rejection reason

Ask for the reason in writing for each rejected item. A one-line reason is enough. This avoids misunderstandings and gives you a concrete basis for follow-up.

Examples of useful reasons:

Step 2: improve the evidence, not the emotion

Before resubmitting, upgrade each item with stronger evidence:

Step 3: re-submit in one grouped update

Do not send five separate messages. Send one concise update with a short cover note and all revised items together. It is easier to review and harder to misplace.

Suggested wording you can copy

Thanks for reviewing the original report. Please find attached an updated list with clearer photos and room references for the items marked as rejected. Could you please re-review these items and confirm next steps for each one.

When someone says "within tolerance"

Ask for the standard or tolerance reference being used, and request it against the specific location/item. Keep the discussion factual. Avoid arguments in chat threads.

Keep a simple status trail

Use status labels so everyone can see what is open, under review, and fixed. This makes follow-up visits more productive and avoids repeated debate about what was agreed.

What not to do

Practical outcome

Most rejected items are resolved faster when the second submission is cleaner than the first. Better structure often matters as much as the defect itself.

Use FixList to keep rejected items organised

Track what is open, what was challenged, and what is fixed, all in one list with clear photos and references.

Download FixList or read the FAQ.

Back to all guides