The source file has asked to speak to a lawyer

The job is finished. Someone asks for “all the files.” A designer stares into a folder that has quietly become an archaeological site.

Source-file delivery should be discussed while the scope is being agreed. Specify what is included, what the recipient needs to use it, and which assets have separate permissions or licensing conditions. Do not assume that paying for a design automatically answers every question about its components.

A practical handoff includes clear filenames and a short explanation of the structure. Remove abandoned experiments that could be mistaken for approved work. Flag linked assets rather than hoping the next person enjoys a missing-file dialogue.

If the client requests material outside the agreed handoff, pause and clarify the request. That is a conversation about scope, not a reason to start a feud over a folder icon.

Terms vary, and a contract-specific disagreement needs appropriate professional advice. A blog joke cannot interpret your agreement.

The file named USE_THIS_ONE_REAL_FINAL deserves particular scrutiny. It has lied before.