Communication During Quality Review

Quality review is a conversation between two parties who will likely work together again, conducted about work that has already been paid for in part. How findings are raised affects whether they get fixed considerably more than whether they are justified.

This is not about being agreeable. It is about the practical observation that a review framed as a shared comparison against an agreed standard gets punch items addressed quickly, and one framed as an accusation gets a defensive counterparty and a slow remedy.

Before the Review

• Establish the standard in advance, so review is a comparison rather than an assertion. Almost everything else follows from this.
• Agree that findings will be reviewed jointly. Findings raised in absentia get contested.
• Agree the timing, so nobody is being asked to inspect at 4 AM or to defend work a week after new soiling has arrived.
• Agree the punch item process — how items are recorded, what completion date applies, and how reinspection works.

Framing a Finding

A finding communicated well contains four things: what, where, what was expected, and what would resolve it.

The last row is worth noting. Asking a question rather than making an allegation is more effective when there is any chance the answer is a reasonable one — and there frequently is.

Sequencing the Conversation

1. Start with what passed. Not as a courtesy — as a calibration. It establishes that the review is against a standard rather than a search for faults.
2. Raise punch items next, individually, with location and expectation.
3. Separate scope questions and mark them for later. Do not attempt to resolve them on site.
4. Agree completion dates per item rather than for the list as a whole.
5. Confirm the reinspection arrangement before parting.

Handling Disagreement

Where a contractor disagrees that something is a deficiency, the productive question is which of three things is in dispute: whether the condition exists, whether it was in scope, or whether it meets the standard. Each has a different resolution.

• Whether it exists — resolved by looking at it together, in daylight, on a dry surface.
• Whether it was in scope — resolved by the written scope, not by argument. If the scope is silent, that is a scope failure to fix next time rather than a contest to win now.
• Whether it meets the standard — resolved by the approved test area. This is what the test area is for.

A dispute that cannot be placed in one of those three categories is usually a disagreement about expectations that were never written down, which is diagnostic in itself.

Communicating Upward and Outward

Property managers frequently have to report quality outcomes to owners, asset managers, or boards, and that reporting benefits from the same discipline. What was scoped, what was delivered, what was accepted, what remains open with dates, and what it cost relative to plan — stated plainly, with photographs, and without either overselling a routine clean or dramatizing a punch list.

On multi-tenant property, communicating outward to tenants after the work — briefly, with photographs — converts a CAM line item that looks like cost into one that looks like stewardship. See tenant appearance planning.

When a Relationship Is Not Working

Communication cannot fix a structural problem. Where punch items recur across engagements, where documentation has to be chased every time, or where quality drifts and does not correct after being raised, the issue is not how findings are communicated. See vendor evaluation for the signals that justify a change.