What to Say When a Client Asks for Revisions After Final Files Are Delivered

A client may treat final delivery as another chance to revise because the files are still fresh in their mind. For the freelancer, final delivery usually means the agreed review window, included rounds, final payment step, and handoff process are complete. Those expectations need to be reset before more work starts.

The reply should stay helpful without quietly reopening the project for free. Acknowledge the note, check whether the request is a correction, support item, or new revision, and name the next approval step before touching the files again.

Try: "Hi [Name], thanks for sending this over. Since the final files were delivered on [date] and the included revision window is now complete, I can review these as a post-delivery change request. If you want to move forward, I will confirm the scope, timing, and fee before making the updates."

If the request might be a small fix, add: "If any item is a file issue from the approved final version, I will flag that separately. New preferences, added formats, copy changes, or direction changes would be handled as paid updates."

Not every post-delivery message is the same. A broken export, missing agreed file, typo you introduced, or issue with the approved deliverable may deserve a quick correction. A new stakeholder opinion, new format, updated copy, different creative direction, or extra implementation request is new work.

Spell out the difference in plain language. For example: "I can correct the missing PDF export from the final package. The new social sizes and rewritten intro copy are outside the delivered scope, so I can quote those as an update." That makes the boundary concrete instead of emotional.

Dates make the reply easier to understand. Mention when final files were delivered, when approval happened, or when the review window closed. This is not about shaming the client. It is about pointing back to the agreed project admin trail.

A useful line is: "The review window closed on [date], and final files were delivered after approval on [date]. I can still help with updates, but they need to go through a new approval and payment step."

A boundary works better when it includes a next step. Offer to estimate the added work, send a payment link, book a paid support block, or create a new mini-project. Avoid debating whether the request is small before you have named the process.

For a simple response, write: "Send me the exact list of changes, and I will reply with the update fee and earliest delivery date before starting." That keeps the relationship service-oriented while protecting your unpaid time.

Future project links should define the final review window, what counts as final approval, which files are included in handoff, how long small corrections are accepted, and how post-delivery updates are priced. Clients are less surprised by boundaries when they saw them before the project ended.

MicroFreelanceHub helps freelancers draft safer client replies and create client-ready project links with revision limits, handoff rules, deposits, milestone payments, signatures, and payment links. It is software for clearer freelance communication and project admin, not legal advice or a guarantee of payment.