How to Document a Recommendation That Was Declined
Why this matters
Almost every shop writes something down when a customer says no. Almost none of it works when it is needed, because it is needed on a day nobody planned for: a year later, after the thing you warned about happened, in front of a customer who genuinely does not remember the conversation. A decline record is not a note. It is a piece of evidence with a service life, and it is worth exactly what it can still prove on the day of the failure. Judge every field in it by that test and the shape of the record changes: it has to be dated, it has to have been delivered, and it has to come back in front of the customer on its own without anyone remembering to look for it.
Siblings cover the conversation and the hazard case. See related: Documenting a Customer Refusal the Right Way, and Documenting a Refused Hazard Repair to Protect Everyone. This one is about what makes the artifact survive.
Step 1: Settle any hazard before you write anything
If what you found is a live hazard rather than a deferred repair, the record is not the first move. For a fuel gas odor: everyone leaves the building immediately, no switches are operated, no lights, no phone used inside, and the call goes to the gas supplier emergency line and the fire department from outside and clear of the structure. For a live conductor in a wet location or an energized part exposed to occupants, keep people clear and isolate at the source; for your own crew, de-energize, lock and tag, and prove dead before contact under 29 CFR 1910.333(b)(2). Write the record after the condition is controlled, and write it that day. A decline record does not close out a hazard the customer cannot safely keep in service, and whether continued operation is also unlawful is a question for the code your jurisdiction has adopted and for your authority having jurisdiction rather than something you decide on the driveway; that is a different article and a different duty.
Step 2: Write the finding so a stranger could go and check it
The finding needs three parts: what you observed, where, and how you know. "Worn component" fails all three. "Drive belt on the rotating assembly, upper access panel, showing glazing on the working face and roughly a third of its width cracked through" can be verified by the next tech on site, and that is the whole point. A finding a stranger cannot re-check is an opinion, and an opinion a year old carries no weight.
Attach the evidence reference in the same field: photo file name or record ID, meter reading, pressure or temperature value with its unit. You will not remember which photo it was.
Step 3: State the consequence, not just the condition
This is the field that decides whether the record is worth anything, and it is the one shops leave out. A customer who declines a recommendation is not declining a condition. They are declining a consequence they were never told about. "Recommend replacing" describes work. "If it fails in service it will take the downstream assembly with it, turning a planned replacement into an unplanned repair with the equipment down" describes what they are choosing.
Say the consequence in the customer's terms: downtime, damage to something else, a bigger repair, a safety issue, or an efficiency loss. If you cannot name the consequence, you may not actually have a recommendation - you may have a preference, and it is worth being honest about which one you are documenting.
Step 4: Put a number on both sides of the choice
State the recommended work in hours and the expected condition if it is deferred. Hours, not currency, because the record has to still make sense in three years and because hours are what the customer is comparing anyway. If you have a real interval - "components of this type on this duty typically go another season, not another year" - say it with its basis. If you do not, say the timing is unknown and say why, which is itself information.
Step 5: Name who declined and how
Full name, role, and the channel: on site verbally, by phone, by email reply. If the person declining is not the person who will live with the consequence - a property manager deciding for a tenant, a facilities contact deciding for a department - the record says so in the same line. That single clause is what stops your record from being read later as evidence that the affected party was informed, which it is not.
Do not ask for a signature on a hazard the customer intends to keep in service and treat that as the end of it. A signature records their decision. It does not make an unsafe condition acceptable. See related: What You Owe When You Find Something Dangerous.
Step 6: Deliver it, and keep proof of the delivery
A record in your system that the customer never received is a note to yourself. Send it: the finding, the consequence, the recommendation, the decline, in the customer's own copy, the same day. Email or the customer portal both leave a timestamp. Reading it aloud does not.
Set the standard as same day, before end of business, and hold it. A record delivered three weeks later is arguable in a way one delivered that afternoon is not.
Step 7: Give it a re-surfacing trigger
This is the step that separates a filing system from a record that works, and it is the one almost nobody does. Put the declined item on an open-recommendations list attached to the equipment or the property, not to the job. Then set two defaults and tune them to your book:
- Re-surface on every subsequent visit to that equipment. The tech sees the open item on dispatch, mentions it, and the visit note records whether it was raised and what was said. Silence is a valid outcome; not knowing is not.
- Re-send the open list annually, tied to the account anniversary or a maintenance renewal, whichever you already run.
Two things come out of this. The customer's memory stops being the system of record. And a declined item that is raised at three consecutive visits and declined at all three is a genuinely informed decision in a way one raised once, fourteen months ago, is not.
Step 8: Store it where the next dispute will look
The record lives on the equipment or property history, not buried inside one job. When the failure comes, the person pulling the file is looking up the address or the unit, not the invoice number of a visit nobody remembers. If your system only lets you attach it to a job, put the finding in the equipment notes as well and cross-reference. Duplication is cheap; an unfindable record is not.
A record put to the test
A shop recommends replacing a worn drive component on a customer's rotating assembly: 3.5 hours, parts and labor, scheduled at the customer's convenience. The customer declines, citing budget. The tech writes it up and moves on.
Fourteen months later the component fails in service and damages the downstream assembly. The recovery runs 11.0 hours. That is 3.1 times the hours of the declined repair, and the two figures compare cleanly because both are hours billed to the customer. The customer says they were never told.
The shop pulls the record. It has the date, the finding with a location, a photo reference, the recommended hours, the customer's name, and an emailed copy with a timestamp from the afternoon of the visit. That settles the first question completely: they were told.
Then the customer reads it and asks a fair question. The record says "recommend replacing worn drive component, 3.5 hours." It does not say the component failing would damage anything else. And on that point the shop has nothing, because the tech knew the consequence and did not write it. The customer's position is now narrow but real: they declined a maintenance item, not a risk to the larger assembly, and had they understood the second one they would have scheduled it.
The shop's outcome was a split on the recovery invoice. What is worth carrying is which field failed. Every field in that record was present and correct except one, and the missing one was the consequence, which is the only field that describes what the customer was actually choosing between. The rest prove the conversation happened. That one proves what the conversation was about. Worth noting alongside it: nothing re-surfaced the item across fourteen months and several visits, so the customer's memory was the only system holding it.
The fix costs one sentence. The record should have read: "Recommend replacing drive component, 3.5 hours. Advised that failure in service is likely to damage the downstream assembly and turn a planned 3.5-hour job into an unplanned repair several times that size, with the equipment out of service while it is done."
Note what that sentence does not do. It does not predict a date, which the shop could not know, and it does not put a figure on the eventual repair, which it also could not know. It states the mechanism and the shape of the outcome, both of which the tech genuinely knew standing in front of the equipment.
What changes if the customer is a business rather than a consumer
The fields do not change. The routing does. In a commercial account, the person declining is usually spending someone else's budget and may lack authority to accept the risk they are accepting. Address the record to your contact, name their role, and where the consequence reaches beyond their area - production downtime, a tenant's premises, another trade's work - say so plainly in the record so it can be escalated by whoever reads it. Whether a decline by that contact binds their employer is a legal question that turns on authority and on the contract, and it belongs with your attorney rather than with a work order.
Verifying the record before you close the job
Read your own record as if you were the customer's advocate a year from now, and check five things:
- Could a different tech find the condition from the location you wrote?
- Does a consequence appear, in words the customer would use, not just a condition?
- Is there a date and a delivery timestamp to a named person?
- Is the item on the open-recommendations list for that equipment, not only in the job history?
- If it fails tomorrow, does the record tell you what you promised and what you did not?
If a record passes all five, it will answer the questions a dispute actually asks. If it fails number two, it will prove a conversation happened and nothing about what was said, which is where most decline records land.
References
- 29 CFR 1910.333(b)(2), safety-related work practices for work on or near energized electrical parts, general industry; the construction counterpart for lockout and tagging of circuits is 29 CFR 1926.417
- See related: Documenting a Customer Refusal the Right Way; Documenting a Refused Hazard Repair to Protect Everyone; The Repair You Were Told to Do and Would Not Recommend; What a Partial Fix Obliges You to Say