The client wants the editable source files. Were they included in my price?

You priced a logo, video, website or other creative project. The client has approved the final result and now asks for the editable project file, working drafts or “everything used to make it”. You are not sure whether those were part of the quote.

Start with the scope and handover wording. “Final artwork” or “website design” may not say whether you promised exported files, a native project, drafts, reusable tools or a transfer of copyright. Separate those questions before you agree to send a package.

Make a file and rights inventory

Write down the exact items the client means, rather than treating “source files” as one thing.

For a website, “handover” can also mean domain, hosting and administrator access, backups, licences or account ownership. Those are separate practical tasks; a folder of source files might not contain them. The website agency handover checklist covers the buyer-side list.

Keep the file question separate from copyright

Possession of a file and ownership of copyright are different matters. A client can have a copy without owning all copyright in it; copyright terms can also give rights to use work without requiring you to hand over every working file.

In the UK, the Intellectual Property Office says the creator is usually the first copyright owner of artistic work, and a freelancer working under a contract for services will usually retain copyright unless the contract says otherwise. For commissioned work, the creator is usually first owner unless ownership is agreed in writing; the commissioner might instead have an implied licence for the purpose of the commission. An assignment of copyright has a separate written-and-signed requirement under section 90 of the Copyright, Designs and Patents Act 1988. These are UK-specific pointers, and the agreement and circumstances still matter.

None of that automatically answers which files your scope requires you to deliver. Check both the delivery clause and the rights clause. Also avoid promising ownership or unrestricted transfer of fonts, stock assets, software, music or code you do not control.

Decide what a useful handover includes

Before you quote or reply, work through these questions:

• Which exact project files can the client open and edit with tools they have?
• Do those files contain licensed assets or plugins that cannot be transferred?
• Would packaging, cleaning, naming or documenting the project require extra time?
• Are unused concepts, rejected drafts and reusable components in or out of scope?
• Does the current price include future edits or only the stated handover?
• What does the contract say about payment and when any agreed rights take effect?

If no term settles the request, do not present an extra fee as an existing contractual entitlement. Explain the scope you understood and propose a separate, specific addition that the client can accept or decline.

Reply with a concrete choice

You might say:

The agreed delivery is [list final exports/formats]. The request for the editable [Figma/video/project] file is not listed in that scope. I can provide [specific editable items] for [price or revised scope], subject to the included fonts, plugins and stock assets remaining governed by their own licences. The handover would include [files, version and notes], with [excluded drafts/tools] retained. If that works, I’ll add the agreed handover and timing to the project scope before preparing it.

If you did agree to provide editable files, name the formats, versions, included materials and handover date in the confirmation. If the request changes the work, apply the extra-work reply guide to agree the added task before doing it.

For the next project, state both the delivery format and any copyright or licence transfer in the quote. Mention editable files explicitly, even when they are included. The freelance contract guide has a broader scope-to-payment checklist; this question is one item to settle before the project starts.