Skip to main content
Ambiguous

is a copy edit right before launch out of scope?

It depends — a last-minute copy tweak can be a covered revision if you still have rounds left, or new work if you're past them or the change is substantive. Urgency alone doesn't make it owed, but it doesn't make it billable either.

Why this answer

Last-minute copy changes are ambiguous because two different things hide under the same urgent message. One is a small correction or a final polish — fixing a date, tightening a headline — that's a normal part of landing a piece of writing and often sits comfortably inside your remaining revision rounds. The other is a substantive rewrite dressed in launch-day urgency: a new value proposition, a different structure, a fresh set of messages that happens to arrive at the worst possible moment. The timing tempts everyone to skip the scope question entirely, because the launch is looming and saying 'let me check the contract' feels obstructive. But urgency cuts both ways. It doesn't obligate you to do substantive new writing for free just because the clock is short, and it doesn't entitle you to bill for a one-word fix just because it's tense. The real determinants are the same as any revision question — how many rounds remain, how big the change actually is — with a timing overlay that can justify a rush premium when the compression is genuine, separate from whether the change itself is in scope.

When the answer flips

It reads as In Scope when you still have revision rounds left and the change is the kind of refinement those rounds exist for — even at the last minute, a covered round is a covered round. It tilts toward Out of Scope on two axes. First, size: a request that rewrites the message, restructures the piece, or adds new copy isn't a tweak, it's new writing, regardless of when it lands. Second, exhaustion: if you're already past the included rounds, even a small change is extra work. The timing adds a third, independent dimension — if a genuine last-minute change forces you to drop everything, work off-hours, or reorder your week to hit the launch, a rush premium can apply even when the change itself would otherwise have been a routine in-scope revision.

What to do next

Move fast on the read so you're not the reason the launch slips, then respond on two separate tracks. Track one is scope: check your remaining rounds and size the change honestly — is this a polish or a rewrite? Track two is timing: is the urgency forcing real disruption, or can you slot it in normally? Then answer accordingly. A small change inside your rounds, you just make — speed reads as trust right before a launch. A substantive rewrite, or anything past your rounds, you name as new work, and if it's also genuinely disruptive you note a rush element: 'This is a new round and it's same-day, so here's the quick price — want me to push it through?' Keep the message short and decisive; nobody at launch wants a paragraph. And afterward, if last-minute changes are a pattern with this client, add a copy-freeze date to your next contract so the final edits have a deadline.

Settled reads your contract and gives you the exact verdict for this situation — try it free →

Frequently asked questions

It's literally one word before we go live. Do I have to make an issue of it?+

No — a one-word fix right before launch is exactly when not to invoke the contract. Make the change, hit the launch, and bank the goodwill of being the calm professional in a tense moment. Scope discipline is for substantive requests and exhausted rounds, not for a single word that takes seconds. The freelancer who pauses a launch to debate a trivial edit looks rigid, not principled. Save your boundary-setting for changes that actually cost you time, and let the tiny ones go without a second thought.

The client is calling it a tweak, but it's basically a rewrite. How do I respond?+

Name the gap plainly, in their terms. Describe what the change actually involves: 'Reworking the headline and the first two sections to lead with a different message is a rewrite, not a tweak — a tweak would be swapping a phrase or fixing a line.' Then offer the path: it's new writing, here's the quick price, and given the timing you can turn it around fast. Clients often call substantive changes 'tweaks' honestly, not manipulatively — they don't see the work underneath. Showing them the work, calmly, usually resets the framing.

Can I charge a rush fee on a copy change even if it's technically an included revision?+

Yes, because scope and timing are two different questions. Whether the change is covered by a remaining round addresses the work itself; whether the urgency forces you to disrupt your schedule addresses the cost of doing it now. A revision that would have been routine on a normal timeline can still carry a rush premium if it makes you drop other work or work off-hours to hit a launch. Be explicit that the premium is for the compression, not the change: 'The edit's covered, but same-day turnaround on launch day is a rush — here's that piece.'

We're out of revision rounds, but it's launch day and the change is tiny. What's fair?+

Fair is acknowledging both truths and choosing relationship over a few dollars. You're technically out of rounds, so the change is strictly extra work — but it's tiny and it's launch day, which is the worst moment to send an invoice for a word. The graceful move is usually to make the small change, mention lightly that you're past the included rounds so the precedent is set, and let it go this once. Save the firm 'that's a paid round' for the next substantive ask, not the launch-day comma.

How do I stop last-minute copy changes from becoming every project's pattern?+

Put a copy-freeze date in the contract — a point before launch after which the text is locked and further changes are billable rush work. A freeze date does for copy what a sign-off does for design: it creates a clean moment when the words are final. State it explicitly, remind the client as it approaches, and the frantic launch-eve rewrites tend to migrate earlier into the process where they belong. When a change does come after the freeze, the clause gives you a calm, pre-agreed basis for pricing it rather than an awkward judgment call.

The client says the launch can't wait, so I have no choice but to do it free. Is that true?+

Their deadline pressure is real, but it isn't your obligation to absorb. A launch that can't wait is a reason for them to decide quickly and pay for speed, not a reason for you to do substantive new work unpaid. Hold the two facts together: you can absolutely turn the change around in time, and it's new work with a price. Framed that way, the urgency becomes leverage for a fast yes rather than a lever to make the work free. If the change is trivial, give it freely — but don't let 'we can't wait' convert a real rewrite into a freebie.

Related reading

Answer scope creep from your actual contract — not a template.

Settled reads your contract and the client's request, gives you a verdict (In Scope / Out of Scope / Ambiguous), and drafts the email grounded in your specific clause.

Try it free →Read the scope creep guide