Advertisement
Advertisement

Who is responsible for the InDesign file still opening after delivery?

2025-09-16 08:00:46

The team that builds and delivers the InDesign file is responsible for handing over a package that opens, with the links and the fonts the file needs, and for saying which version of the software it was built in. The client is responsible for opening it in a compatible setup and for keeping the fonts and the images that the package already named. A file that opens on the production machine and fails on the client’s machine is not finished, unless the failure is a setup the quote never included.

A packaged book opened on the production desk, links green, fonts listed. On the client’s machine it stopped and asked for a missing font and for two images that had been linked from a local folder and never copied into the package. The client mailed a screenshot and asked who owned the fix. The package had been sent as a lone .indd. The images had stayed on the production disk. That failure belonged to the delivery. A package that still depends on a folder the client does not have is not a delivery.

What “opens” means in the handoff

It means the client can open the file, see the text, see the images, and not face a surprise font substitution that reflows the pages. It means the instructions named the InDesign version. It means fonts the client is allowed to receive are in the package, or the handoff says which fonts the client must already have and what to do if they do not. It means links point inside the package, not at a path on someone else’s computer.

Test this on a second machine, or in a clean folder, before you send it. Opening the file from the folder where it was created hides broken links, because the links still find the originals. The client’s machine is the test that counts. Do that test, and the screenshot in the mail does not happen.

What the client still owns

The client owns the decision to use a much older InDesign than the file was built in, after they were told the version. They own a request, made after delivery, to switch to a font that was never in the job. They own images they insisted on linking from their own library and refused to place in the package. Those are real responsibilities. They should be written in the delivery note so they are not discovered as a dispute.

If the quote said “we deliver a PDF only,” the open InDesign file is not the promise. Responsibility follows the promise. This question is about the job that promised an editable InDesign file.

How to write the line so it survives the handoff

The delivery note should list: the .indd or the package folder, the font names, the links folder, the version, and a sentence that says the file was opened from a clean copy of that package. The client replies that it opened, or sends the screenshot while the job is still warm. A month later, nobody remembers whether the images were in the zip.

The responsibility is concrete. The producer owes a package that stands on its own. The client owes a compatible install and a check on receipt. Between those two, the file still opening is a tested package, not a hope that their machine looks like yours.

What if a font licence does not allow the font to be sent?

Say so before delivery, name the font, and agree a substitute or a path where the client supplies the font on their side, and a package that silently substitutes a font will reflow, and the reflow looks like a translation error. The licence limit is a planning item, and it is not a surprise dialog on the client’s screen.

Who fixes a file that opened, and then broke after the client edited it?

Once the client has changed the file, further fixes are new work, and the original package remains what was delivered. Keep that zip, because later edits belong to the person who made them and the packaged file belongs to the team that sent it.

The related service page is desktop publishing.

Quick FAQ: AI Translation Accuracy

  • How accurate are AI translators? Accuracy is often high for repetitive or general content, while domain-sensitive content still needs expert review.
  • How to improve AI translation quality? Use glossary control, domain prompts, QA checks, and human post-editing in one workflow.
  • Where does human translation still win? Legal, medical, and high-stakes brand content usually requires human nuance and accountability.