Why Verbal Approval Is Worth Less Than It Feels

Why this matters

A verbal yes feels like a closed loop. Someone stood in front of your tech, heard the number, and said go. Everybody was honest. The work got done. Then the invoice goes to a person who was not in that conversation and had never agreed to anything, and the shop discovers that the yes it collected was not the yes it needed. This is not mainly a memory problem or a dishonesty problem, though both exist. The condition that voids the most invoices is authority: the speaker was not able to bind the party who pays. That failure is invisible at the moment of approval and permanent afterward.

Three conditions a verbal approval has to survive

A verbal approval has to clear all three of these to be worth what the tech thought it was worth. They are independent, and they fail for different reasons.

• Authority. Could the person speaking commit the party who receives the invoice? A tenant cannot usually commit a landlord. An adult child cannot usually commit a parent who owns the house. An on-site engineer often holds a capped authority they themselves may not have read recently. A spouse usually can, but not always, and not on a commercial account.
• Specificity. Was the approval attached to a defined scope and a stated number? "Go ahead and take care of it" is assent to a direction, not to a quantity. Six weeks later it will be read as approval of whatever the reader thinks was reasonable.
• Recall. Can either party still describe the same conversation? Memory does not decay randomly; it decays toward each party's interest, and it does it to honest people. Two people can be truthful and still hold incompatible accounts by the time an invoice is disputed.

Recall gets all the attention because it is the one that produces the argument. Authority is the one that produces the write-off, because a specificity or recall problem is negotiable and an authority problem is not. If the payer never granted the speaker power to commit them, there is nothing to negotiate about, only a claim against a person who has no budget.

The call that was approved by someone who could not approve it

A small commercial building, a failed unit, a call at 11:40 at night. The shop's after-hours tech meets the building engineer on site. The engineer walks him to the equipment, hears the tech's read on what it needs, hears an estimate of five to six labor hours at the after-hours rate plus a replacement component, and says go ahead, we need it running before tenants arrive.

The tech runs 5.5 labor hours and installs the component. It is running at 5:10 in the morning. The engineer signs the ticket at the door. Nobody involved does anything dishonest at any point in this story.

The invoice goes to the management company that administers the building. It sits. At day 43 it comes back partly rejected. The engineer's written authority, set in a management agreement he had signed two years earlier, allows him to authorize up to 2.0 labor hours per incident without a purchase order number issued by the management company. Above that, the property owner's approval is required and the management company will not process the invoice without the number. The engineer had never once hit that cap before.

So 2.0 of the 5.5 labor hours are approved and 3.5 are disputed, which is about 64% of the labor on the ticket. The component is already installed and cannot be returned, so the material is fully exposed too. The shop's leverage is thin: the work is done, the building is comfortable, and the party who agreed is not the party who pays.

It settles at week 11. The management company pays the 2.0 authorized hours and 2.0 of the disputed 3.5 as a goodwill split, so the shop recovers 4.0 of 5.5 labor hours, about 73%, and writes off 1.5 hours, about 27%. The settled amount is paid 77 days after the invoice date against net-30 terms, roughly 2.6 times the agreed term, which means the shop also financed the job for two and a half extra months.

Notice what would not have fixed this. A better written scope would not have. A signature would not have, and there was one, on the ticket, from the engineer. A recording of the conversation would not have, because the conversation happened exactly as everyone remembers it. The only thing that would have fixed it is one question asked at 11:45 at night: how much can you approve without a purchase order number, and who issues it after hours?

What a verbal approval is actually worth

It is not worth nothing, and treating it as worthless produces its own failure, which is a tech who stops collecting verbals because they "do not count" and ends up with neither a verbal nor a written record.

A verbal approval is evidence of assent. Its value in a dispute is set by how well you can prove three things: that the conversation happened, what was said, and that the speaker had power to say it. A contemporaneous note written the same hour is real evidence. A signed ticket is stronger. A text thread stating the number, sent before the work, and answered, is stronger again, because it fixes the specificity and the timing and does not depend on either memory.

What none of them fix is authority. Authority is a fact about the relationship between the speaker and the payer, and no amount of documentation of the conversation creates it. That is why it belongs at the front of the conversation and not in the paperwork afterward.

The thirty seconds that changes what a verbal is worth

Ask these, in this order, before the work rather than after:

1. "Are you the one who approves the cost, or does it go to someone else?" Plain, not suspicious. Most people answer honestly and instantly, and roughly a third of the time on commercial and managed property the answer is somebody else.
2. "Is there a limit on what you can approve without a purchase order or a manager's sign-off?" This is the question that catches the capped authority. Ask it even when the person clearly runs the site.
3. State a number and a scope out loud, then repeat it back. "So that is up to about five and a half hours plus the component, tonight." A number said twice survives ten weeks better than a number said once.
4. Send it to a channel that timestamps. A text or an email with the scope and the number, before you start, addressed to the person who approves. Their one-word reply is now the record. If the approver is not on site, the on-site person's role is witness, not approver.
5. Get the name and role in writing, not just the signature. A signature that cannot be read and a role nobody recorded is a document that cannot answer the authority question later.

None of that slows a call down by more than a minute, and it is the only part of the exchange that addresses the condition most likely to void the invoice. For the mechanics of writing the request so it can be answered in one tap, see the sibling article on getting a decision in writing without slowing the job.

When verbal is the only thing available, and where approval is not the question at all

Sometimes there is no one to text at two in the morning and the work genuinely cannot wait. Do it, then document within the hour: what you found, what you did, who authorized it, their role, the time, and the number you quoted. A same-day record of a forced decision holds up far better than a reconstruction written when the invoice bounces. Your shop's rules for acting ahead of approval belong in a standing policy, not in a tech's judgment at two in the morning.

Separately, and this is not an approval question at all: a life-safety condition is acted on regardless of who approves anything. A gas odor means everyone leaves the area immediately, no switches or lights are touched, no phone is used inside, and the utility is called from outside. Standing water at energized equipment means people are kept back and the circuit is de-energized at its disconnect and proved dead with a tester checked on a known live source before and after the reading, following NFPA 70E-2021 section 120.5 for the proving sequence and 29 CFR 1910.333(b)(2) for the safe work practice on electric utilization equipment. Whether anyone will pay for the corrective work is a separate conversation held afterward, and a dangerous finding is stated plainly and in writing the same day rather than held as leverage.

How to find your own exposure before it finds you

• Sort last year's write-offs by reason, not by size. Count how many trace to a person who could not commit the payer. Shops that have never counted this are usually surprised by the ratio.
• List your managed-property and commercial accounts and write the approval limit next to each. If you cannot fill in more than half from memory or from your file, you are running those accounts on the hope that nobody ever exceeds a cap you have not read.
• Check whether your after-hours process has an approver path at all. A cap with no way to reach the approver at night is a cap that will be broken.
• Read one of your own signed tickets as an outsider. If it does not carry a printed name, a role, and a stated number, it proves a person was present, not that a payer agreed.

References

• Whether one person can bind another to pay for services is a question of agency and contract law, which is set by state law and often differs for consumer and commercial customers; have your own attorney review how your approval and authorization forms are worded
• NFPA 70E-2021, section 120.5, for the live-dead-live proving sequence, which binds through your employer's electrical safety program and through 29 CFR 1910.333(b)(2)
• See related: The Approval Limit That Is Really a Liability Limit, How to Set Approval Limits With a Property Manager, The Emergency Mitigation Window: Acting Before Approval, How to Get a Decision in Writing Without Slowing the Job