The Review Landed And The Job Is Not Finished

The framing is up, the kitchen is a hole in the floor, and there is a tarp where the back wall used to be.

Week three of six. The part where it looks worse than it did before anybody started, which every builder knows and no homeowner is ever quite prepared for. The phone buzzes on the way to the truck and it is a review notification with your business name on it.

Somebody has filed a report on a job that is a third of the way done.

Both versions are a problem

If it is a good one, the first feeling is relief. Five stars, warm words about how responsive you have been, how clean the crew keeps the site. You read it twice.

Then it settles in that you are now holding a public verdict on the easy third. The demolition went fine. The framing went fine. What is left is the part where the schedule gets tight, the cabinet delivery slips, and a decision the homeowner has been avoiding finally has to get made in front of them. If any of that goes sideways, that review is the standard you get measured against, by them and by you. And the person who wrote it can go back and change it, which cuts both ways and mostly cuts one.

If it is a bad one, it is worse, and it is usually not even about the work. It is about the dust, or the portable toilet, or a subcontractor who parked across the neighbor's driveway. Often it is about a week where nobody showed up, because you were waiting on an inspection and nobody thought to tell them that was why. All of it is true and none of it is the finished job.

This is the opposite of a complaint arriving about work from two years ago that nobody on your crew remembers. That one is too late to do anything about. This one is too early for anybody to be right about, including you.

Why replying is the trap

Your reflex is to answer, and answering is where owners lose this.

A public reply accepts the premise. It agrees that the job is a thing that can be evaluated right now, in the middle, and it puts you in the position of defending unfinished work in writing. There is no version of that paragraph that reads well. Explain the dust and you sound like you are managing the customer. Say anything about the schedule and you have published your own delay. And if you promise how it will turn out, you have written a guarantee on a page you do not control, about a job with three weeks of unknowns left in it.

The timing problem is sharper than that. Whatever you write today gets read a year from now by somebody comparing you to two other builders, long after the facts changed. A reply that made sense in week three will be sitting under a review from a customer whose kitchen turned out beautifully, and it will still be arguing.

Stay out of writing for now. The conversation this review is asking for is not a public one.

What the review is actually telling you

Go find out what happened on site.

Not what the review says happened. What happened. Call whoever was there, in order, and get the week straight before you talk to the customer. Almost every mid job review traces back to one of a small number of things: a day with no visible progress and no explanation, a person on site who said something they should not have, a change nobody confirmed in writing, or a stretch where the customer did not know what was coming next.

That last one is the usual answer. A customer who posts in the middle of a job is almost always a customer who has nobody to tell. They are living inside a construction site with a tarp for a wall, they have been given a schedule they cannot read, and the only channel that reliably gets a response from a business is a public review. That is not malice. It is a person using the one lever they are sure works.

Which makes the review a report on your communication, not your carpentry.

The call, then maybe a line

Call them the same day. Open by saying you read it, and then stop talking and let them say the whole thing, including the parts that are not fair.

Then do the thing that actually fixes it, which is telling them what happens next and when. Not an apology tour. A sequence with dates in it and the name of the person who will be there. If a date is genuinely unknown, say it is unknown and say when you will know. People can hold an unknown. They cannot hold silence.

If you do post a public reply after that, keep it to a couple of lines. You read it, you spoke with them, the work is ongoing. No defense, no timeline, no promise about the outcome, and nothing that reads as a bid to have the review taken down.

When the job is finished and the walkthrough has gone well, that is when you raise it, and you do not ask them to delete anything. Ask them to add to it. Tell them plainly that the review was written in the middle and the middle was the hard part, and ask them to say how it ended. Most people will, because most people would rather their public word be accurate than be right about week three.

The sentence that prevents all of it

On a long job, say this in the first meeting: at the end of this, I am going to ask you to leave us a review.

One sentence, said early, when nothing has gone wrong yet. It tells the customer a review is expected and it puts that review at the end, so the impulse to file one in week three has somewhere to go. It also says you intend the ending to be worth writing about, which gives you a reason to keep checking in. You have tied your reputation out loud to how they feel on the last day rather than how they feel on any given Tuesday.

Then earn it with a weekly update they did not have to ask for. A long job with a weekly update almost never produces a mid job review, because the lever they would have reached for is already in their hand.

Do this

1. 1Do not reply in public today, whether the review is good or bad.
2. 2Call everybody who was on site and get the actual sequence of the last two weeks.
3. 3Call the customer the same day, say you read it, then let them talk.
4. 4Give them the next steps with dates and names, and name what is still unknown.
5. 5Keep any public reply to two lines, with no defense and no promise about the outcome.
6. 6Do not ask anybody to take a review down.
7. 7At the walkthrough, ask them to add how it ended rather than to change what they wrote.
8. 8On every long job from now on, say in the first meeting that you will ask at the end.
9. 9Send a short weekly update on long jobs without being asked for one.

Where the card fits

A review that arrives mid job is a review that happened at a moment you did not choose.

A tap card lets you choose the moment, because it turns the walkthrough into the review moment. The work is done, you are standing in the finished room with the customer, and the page opens on their phone right there. That is the review you want on your profile, written from the end of the job by somebody looking at the result. Cards and stands are at shop.optechsol.llc.

The short version

A review posted in the middle of a job is a verdict on an unfinished thing, and replying in public makes you defend work that is not done yet. Find out what happened on site, call the customer the same day, give them dates and names, and keep any public reply to two lines. At the walkthrough, ask them to add how it ended. And on every long job, say in the first meeting that you will ask for a review at the end, because a customer who knows the ask is coming stops reaching for the public lever in week three.