What happens to your design work after the client opens it in Word
There's a specific kind of email that design studios dread.
It comes from the client, a few weeks after handover. The subject line is something like "quick question about the template" and the body contains a screenshot. In the screenshot, the layout that took three rounds of feedback and two weeks of refinement looks nothing like what left the studio. The logo is stretched. The font has changed to Calibri. The carefully considered spacing between the heading and the body text is gone, replaced by whatever Word decided to do when the client hit enter twice instead of using paragraph spacing.
The studio didn't make that document. But their name is on the relationship, and the client doesn't have a clear sense of whose fault this is.
This is the gap that most design handovers don't fully close.
Why the gap exists
Design and document production are two different disciplines, and the tools they use don't share the same logic.
In InDesign or Figma, a designer has precise control over every element on the page. Spacing is exact. Fonts render consistently. Layouts hold because the software is built to hold them. The design looks right because the environment it was created in is built for looking right.
Word is built for something different. It's built for people to type in, edit, and share. The features that make it useful for that — the ability to paste content from other sources, to adjust formatting on the fly, to work across different machines with different software versions — are exactly the features that make it hostile to precise, designed layouts.
When a design file is handed over to a client and they open it in Word, they're opening it in an environment that was never designed to preserve the things a designer cares most about. The font substitution happens because the client's machine doesn't have the brand typeface installed. The spacing shifts because the paragraph spacing rules weren't built into the styles. The logo stretches because it was placed in a text box rather than anchored correctly, and the client clicked on it and dragged a corner.
None of this is the client's fault. They're using the software the way it was designed to be used.
What the handover usually looks like
Most design handovers involve handing over files. The designer exports a Word document from their layout, or hands over a file that was built to look like the design, and assumes that's sufficient. Sometimes it is. More often, it holds together for a few weeks until the client starts editing it properly, and then the accumulated weight of the software's defaults starts to assert itself.
The font changes when someone opens the document on a machine where the brand typeface isn't installed. The heading that was visually defined by direct formatting reverts to the base paragraph style when a user applies a new style on top of it. The table that was sized to the millimetre shifts when the content inside it changes. The footer that looked right on every page in the design starts doing something unexpected on pages with different amounts of content.
Each of these is a predictable consequence of the gap between design software and Word. They're not edge cases or bad luck. They're what happens when a design is handed over without being engineered for the environment it's going to live in.
What a properly built template prevents
The work of making a design survive in Word isn't complicated, but it requires knowing what Word actually does and building around it rather than against it.
Fonts need to be specified using system fonts for editable text styles, with the brand typeface reserved for static elements that won't be typed over. That way the document looks on brand regardless of what's installed on the client's machine.
Heading and paragraph styles need to be defined in the document's style sheet rather than applied as direct formatting. When styles are properly built, a user applying a heading gets the right font, size, weight, spacing, and colour automatically. When they're applied as direct formatting, each of those properties can be independently overridden without the user realising, and the document drifts.
Layout elements that are meant to be static need to be anchored correctly or built as background elements that don't respond to editing. Elements that are meant to be editable need to sit in native Word placeholders, not in floating boxes that shift unpredictably when clicked.
Spacing needs to be built into the paragraph styles, not achieved by pressing enter. The difference is that paragraph style spacing holds when content changes, and manually entered line breaks don't.
The part that rarely gets said
The design doesn't stop being the studio's design when it leaves the studio. The client's version of it, produced six months later, is what people see when they receive it. If that version looks like something went wrong, the studio's work is what it's being compared to.
This isn't an argument for studios to take on Word builds. It's an argument for having a clear handover process that includes the template build, so the design that took months of careful work can actually hold up in the environment where it's going to be used.
We work with design studios to bridge that gap. We take the design files and build templates that work: the fonts hold, the styles apply correctly, the layout survives contact with real users in a real organisation. The studio's work looks like the studio's work, not like whatever the client's version of it became.
If you have a client project approaching handover and the template side hasn't been resolved, it's worth a conversation before the files are transferred.