The Case: The Voice Note That Became a Contract Dispute

The Ambiguity of 2:14 PM

The Consultant received a voice note on WhatsApp. It was three minutes long. The client was driving. There was background noise.

“Hey, on the landing page, let’s just flip the color scheme… make it pop more… and maybe add that video we talked about to the header? Okay thanks.”

The Consultant heard “flip the color scheme” and inverted the black and white palette. They spent six hours redesigning the header to accommodate a video.

They presented the work. The client was confused. “Why is the page black? I meant flip the button colors. And I meant the video should go in the footer, like we discussed last week.”

The Consultant played back the voice note. “Flip the color scheme” was indeed vague. “Add that video… to the header” was clearer, but the client claimed they misspoke and meant footer.

The work was rejected. The time was billable, but the client refused to pay for “work I didn’t want.”

The Dispute: Audio Is Not Data

Voice notes carry tone, which is useful for sentiment, but they are imprecise for logic. They allow the speaker to be lazy with their vocabulary.

The enemy is Interpretive Listening.

1. Lack of Precision: “Make it pop” is not a specification.
2. No Searchability: You cannot CTRL+F a voice note to find the word “footer.”
3. Ephemeral Context: The “video we talked about” relies on a shared memory that may not exist.

Consequently, building a project based on a voice note is building on sand.

The Proof: The Transcription Protocol

To protect the firm, we must treat a voice note as a draft of instructions, not the instructions themselves.

The protocol is simple: Transcribe and Verify.

Upon receiving the voice note, the Consultant must pause. Do not start working. Instead, send a text or email reply:

“I received your note. To ensure I have this right before I start billing:

1. Invert button colors (Green to Blue).
2. Insert ‘Promo_Video_v2’ into the Header. Please confirm.”

This action converts the vague audio into a rigid text specification.

If the client replies: “No! Video in the footer. And invert the whole background, not the buttons.”

You have just saved six hours of rework. You have caught the error in the specification phase, not the delivery phase.

If the client replies: “Confirmed.”

You now have a Ledger entry.

Scope Confirmation: Item 1: Invert Buttons Item 2: Video in Header Status: CLIENT_APPROVED

If they later argue “I meant footer,” you present the text. “You confirmed the Header in writing. I executed the confirmed plan.”

Voice is for feeling. Text is for scope. Do not confuse the two.

FAQs

Should we refuse voice notes?

You cannot control how a client communicates. You can only control how you record it. Accept the note, but do not act on it until it is transcribed.

Is a voice note not a record?

It is a poor record. Finding a specific instruction at minute 2:14 of a ten-minute file during a legal argument is inefficient and prone to error.

Who is responsible for the misunderstanding?

The professional is responsible. It is our duty to clarify ambiguity before expending resources.