Get it in writing: end the 'I never approved that' fight

The same Geneca study found that 80% of respondents admit they spend at least half their time on rework (Geneca). Half. Redoing things that were not clearly agreed the first time. Asana's Anatomy of Work research, drawn from more than 10,000 knowledge workers, puts a matching number on it from another angle: 60% of a person's time at work goes to "work about work" rather than skilled work, and the average worker loses 209 hours a year just to duplicated effort (Asana).

For a freelancer, rework has a sharper edge than it does for a salaried employee, because you are almost never paid for it. Every revision round that exists only because approval was vague is time billed to nobody. You quoted the job once. You are doing it one and a half times. The client is not evil for asking; they genuinely do not remember agreeing, because there was nothing to agree to. This is the same root as scope creep, and it has the same fix: pin the decision down when it happens, not when it is disputed.

When there is no record, you lose

Sooner or later the ambiguity reaches the invoice, and that is where it stops being annoying and starts being expensive.

Late and missing payment is already the norm. In Remote's 2025 contractor report, 85% of freelancers said their invoices are paid late at least some of the time (Remote). A slice of that is cash-flow, but a real part is dispute: the client is not paying because they are arguing about what they got. Freelancers Union's coalition survey found that 62% of freelancers in New York had lost wages at least once, and 53% had lost up to $10,000 to nonpayment on completed work (Freelancers Union). Completed work, unpaid, in part because "completed" was one person's opinion.

And here is the quiet reason freelancers keep losing these: most of them have nothing to stand on. Freelancers Union found that only 28% of freelancers use a contract for any given gig (Freelancers Union). If fewer than a third even have a signed agreement, far fewer have a documented sign-off on the deliverable itself. When it is your word against theirs, the person holding the money wins by default.

The chargeback nobody plans for

If the client paid by card, the fight does not even end when the money arrives. It can be reversed.

Chargebacks911's 2024 field report found that 72% of merchants reported an increase in friendly-fraud chargebacks in 2024 (Chargebacks911). Friendly fraud is the polite name for a customer who received what they paid for and disputes the charge anyway, sometimes because they genuinely misremember, sometimes because they changed their mind. For a freelancer, a chargeback that says "I didn't get what I paid for" is very hard to fight with a vague email trail and a verbal approval. It is much easier to fight when you can show a signed contract and a timestamped record of the client approving the exact deliverable they later disputed. Documentation is not bureaucracy here. It is your evidence.

Make the sign-off a recorded event

The fix is to turn approval from a passing comment into a recorded action. Not a heavier process, just a clear one: a specific point where the client accepts a specific version, and that acceptance is written down somewhere neither of you can later rewrite.

This is built into how Delivvo works, and it is worth describing plainly.

In Delivvo, the client reviews and approves work inside their portal, and the approval is captured as an event, tied to that deliverable, with a timestamp on it. The contract is signed there too, with real e-signature, so the agreement itself is on the record before the work even starts. When you later send the invoice, it points back to work the client already accepted in the same place, not to a claim you are asking them to take on faith. "Which version did you approve, and when?" stops being an argument and becomes something you both just look at. The invoice runs through your own payment gateway, because Delivvo takes 0% of client payments and never sits in the money path.

To be honest about the limits: no system makes a determined bad-faith client behave, and a timestamp will not force someone who never intends to pay to pay. What documented sign-off removes is the far more common problem, the honest dispute that only exists because nobody wrote the decision down. Most "I never approved that" fights are not fraud. They are two reasonable people remembering a vague moment differently, and that is exactly the fight a record ends. If asking for approval is the part you find awkward, we put together email templates for getting clients to approve work to make the request feel routine.

How to get clean sign-off starting now

You can tighten this today, with or without any particular tool, in rough order of payback:

• Sign something before you start. Even a short agreement beats none, and it puts you in the 28% who have anything to stand on. It sets the frame for every approval that follows.
• Make approval an action, not a vibe. "Looks good" in passing is not sign-off. Ask for an explicit yes on a specific version, and make it easy for the client to give.
• Timestamp the yes. Whatever the client approves, capture when and which version. A dated record is the whole difference between proving it and hoping they remember it.
• Tie the invoice to the approval. Bill for work the client accepted, and reference that acceptance. It shortens the argument and strengthens you if it ever reaches a chargeback.
• Keep it all in one place. Approvals scattered across email and chat are the same as no approvals when you need to find them. One record beats five threads.

None of this makes you harder to work with. Done well, it makes you easier, because the client always knows exactly where things stand and what they said yes to.

Delivvo records client approvals as timestamped events tied to the exact deliverable, alongside e-signed contracts and invoices, all in one branded portal, with payments running through your own gateway at a 0% platform cut. The next "I never approved that" is answered by looking, not arguing. See how it works.

The bottom line

The fights that drain freelancers, the endless revisions, the scope arguments, the invoice that sits unpaid, usually come down to a missing record of a single yes. Only about a fifth of projects end with both sides sure they are done, most of the work-week goes to rework, and barely a quarter of freelancers even use a contract. Ambiguity is not neutral. It is a cost, and the person without the record pays it. Get the sign-off in writing, tie it to the exact work, and keep it somewhere you both can see. "I never approved that" only wins when nobody wrote down that they did.