The one idea
A document is not a picture of a page. It is a set of instructions, which the receiving computer follows using whatever it has available.
If it does not have your font, it substitutes one. If its printer has different margins, the text reflows. Every manual adjustment you made — extra blank lines, hand-placed spacing, a page break in exactly the right spot — was tuned to a layout that no longer exists.
The fix is to give instructions that survive translation instead of instructions that depend on your specific machine.
Other computers do not have your fonts and settings, so they rebuild your document and things move. Use built-in features instead of manual spacing.
Use styles rather than direct formatting, use real page breaks rather than repeated returns, keep table headers repeating, and send a PDF whenever the layout matters.
Word-processor files store content plus layout instructions resolved at render time against locally available fonts and page metrics. PDF stores the resolved layout with fonts embedded, which is why it is stable across machines.
The four things that break
Fonts
If a font is not installed on the reader's machine, it is replaced. The replacement is a different width, so everything after it shifts.
Stick to fonts that ship with the operating system or the office suite — Calibri, Arial, Times New Roman, Georgia, Verdana, Cambria. Fonts you downloaded for free from a font site exist on your computer and almost nowhere else.
This matters most for anything you send outside your organisation. Inside a company that installs a corporate font on every machine, you can use it safely — that is exactly why companies do that.
Manual spacing instead of real spacing
The most common cause of documents falling apart.
Pressing Enter four times to push a heading onto a new page works perfectly until one sentence above it gets shorter. Then the heading has four blank lines in the middle of a page.
| Instead of | Use |
|---|---|
| Pressing Enter repeatedly | Insert a page break (Ctrl+Enter / Cmd+Enter) |
| Spaces to indent | Tab, or paragraph indent settings |
| Blank lines between paragraphs | Space before/after in the paragraph settings |
| Manually aligning with spaces | Tab stops or a table |
| Enter at the end of every line | Nothing. Let text wrap. |
The principle: if you are pressing a key repeatedly to move something, there is a setting that does it properly. Manual adjustments are anchored to a layout that will change.
Tables
Tables break in two ways, and both have a setting that prevents them.
The header row disappears. A table crosses a page boundary and page two shows columns of numbers with no idea what they mean. Fix: select the header row and turn on the option to repeat it on every page — in Word, table properties, row, "Repeat as header row at the top of each page".
A row splits across pages. Half a row on one page, half on the next. Fix: turn off "Allow row to break across pages" in the same settings.
Also set column widths deliberately rather than dragging until it looks right. Dragged widths are tuned to your window, and tables set to auto-fit to content will resize when the content or the font changes.
Images
An image inserted with text wrapping set to "in front of text" is floating over the page, anchored loosely. Add a paragraph above and it can drift to another page entirely, or sit on top of your text.
Use "in line with text" as the default. The image behaves like a very large character, staying in its place in the flow. It is less flexible for design work and far more predictable, which is what you want in a report.
You are sending a proposal to a client. Before it goes:
- Fonts: Calibri and Cambria only, both standard.
- Page breaks: real breaks, no rows of empty paragraphs.
- Table on page three: header row repeats, rows do not split.
- Logo: in line with text, not floating.
- Exported to PDF, then opened and checked in a PDF reader — not just exported and attached.
That last step takes forty seconds and is the one people skip. The export is where problems become visible, and it is the last moment they are free to fix.
Send a PDF when the layout matters
PDF stores the finished layout with the fonts embedded. It looks the same everywhere, which is exactly what you want for anything final.
Send a PDF for: proposals, reports, invoices, anything going to a client, anything printed, anything where you would be embarrassed if it moved, and CVs.
Send an editable file for: anything someone needs to edit or comment on, drafts, templates, collaborative documents.
The most common failure is sending a Word file for a job application. It opens differently on the recruiter's machine, and if the layout has broken, that is what they judge. Unless the posting asks for a specific format, send a PDF.
Making a document travel safely
1 of 7Use standard fonts, and no more than two. One for headings, one for body. If you must use a brand font, confirm the recipient has it — or send a PDF.
Try this
A colleague sends you a document to check before it goes to a client. You notice:
- The body font is one called "Proxima Nova Soft".
- Section 3 starts on a new page because there are five empty paragraphs above it.
- The pricing table crosses pages two and three; page three has no header row.
- The logo sits slightly over the first line of text.
- The contents page lists section 4 on page 6; it is actually on page 8.
She says: "It looks fine on my screen." What do you tell her?
Your challenge
Level 3 · IndependentTake a document you have sent to someone. Check it against six things: standard fonts only, no manual spacing hacks, tables with repeating headers and unbroken rows, in-line images, updated contents page, no leftover comments or tracked changes.
Fix everything that fails, export to PDF, and open the PDF.
You have succeeded when you have found at least one problem you did not know was there. Almost every document has one, and this is how you learn to see them before sending rather than after.
What people usually get wrong
- Downloaded fonts in documents that leave your machine. They will be substituted, and everything after them moves.
- Empty paragraphs instead of page breaks. The most common structural failure in documents.
- Tables without repeating header rows. Page two of a table becomes unreadable, and unreadable numbers get misread.
- Floating images. They drift, and they drift onto text.
- Sending a Word file for a job application. It opens differently, and the broken version is the one that gets judged.
- Not opening the exported PDF. Export is when problems become visible. It takes forty seconds.
- Leaving tracked changes and comments in. Internal commentary reaching a client is a real and recurring incident.
- Formatting each heading by hand. Forty manual edits that drift apart, instead of one style change.
How someone experienced does it
Experienced people build from a template rather than a blank page. The styles, fonts, margins and table formats are already correct, so consistency is the default rather than something to maintain. If your organisation has one, use it; if not, make one from your best document and reuse it.
They also modify the style rather than the text. When headings need to be smaller, they change the Heading 2 style once and every heading updates. Anyone selecting headings individually is doing something the software was built to do for them, and introducing inconsistency with every manual edit.
The habit that separates them completely is checking the output rather than the source. They open the PDF, they scroll every page, and on anything important they open it on a different device or send it to themselves first. It is the same instinct as testing a backup — you do not have a working document until you have seen the version the reader will get.
When not to use this
None of this applies to collaborative working documents. A shared file that a team is actively editing does not need PDF export, and locking it down defeats the point.
Cloud-native documents — Google Docs, or Word files kept in a shared workspace — also sidestep some of these problems, because everyone opens the same file with the same rendering. The font problem largely disappears; the manual-spacing and table problems do not, because they still break the moment content changes or someone exports it.
The rules matter at the point a document leaves the environment it was made in. That is the moment to apply them, and it is why the export check is the step that catches everything.
Why the same file looks different in Word, Google Docs and LibreOffice
Opening a .docx in something other than the version of Word that made it can shift the layout, and the reason is worth understanding.
The file stores content, structure and formatting instructions. It does not store a fixed picture of the pages. When a program opens it, it re-renders the document using its own layout engine, its own font availability, and its own interpretation of the formatting instructions.
Different programs implement those instructions with small differences — line-height rounding, how tables distribute width, how floating objects anchor. Each difference is tiny; accumulated over forty pages, they move page breaks.
This is why converting between formats degrades a complex document, and why a document that has been round-tripped Word to Google Docs and back is often subtly damaged. Pick one tool for a given document and stay in it. If it must cross tools, keep the formatting simple and check the result — and if the layout genuinely matters, send the PDF, which is the only format that stores the resolved result rather than the instructions.
Prove it
Take an important document, apply every check in this lesson, export to PDF, and open it on a different device — a phone counts.
Write down what moved. That list is your personal set of habits to fix, and it is usually shorter and more specific than you expect.
Keep learning this
Paste this into any AI assistant. It turns the assistant into a tutor that tests you instead of just answering you.
Act as an experienced practitioner who is good at teaching. I have just learned document formatting that does not break on other computers. Assume I am intelligent but relatively new to this — treat me as beginner level. Work through this in order, and wait for my reply at each step: 1. Ask me 5 questions that test whether I actually understood document formatting that does not break on other computers. Do not reveal the answers yet. 2. After I answer, tell me which parts I got right, which I got wrong, and which I only half-understand. Explain only what I misunderstood — do not re-teach what I already know. 3. Give me one practical challenge based on something I could genuinely encounter at work or in daily life. Do not solve it for me. 4. Evaluate my solution the way an experienced person would judge it, including what a professional would have done differently. 5. Tell me what to learn next, and why that comes next. 6. Give me trustworthy sources for deeper study — prefer official documentation, primary research or standards bodies over blogs and videos. Rules for you: no buzzwords. No motivational filler. Say "I'm not certain" when you are not certain, and tell me which parts of your answer I should verify myself. Clearly separate facts from your recommendations and your opinions.
Become independent at this
Use this when you want a path from where you are to actually good, with checkpoints you can test yourself against.
I want to become independently capable at producing documents that survive being sent to other people — not permanently dependent on AI, tutorials or step-by-step guides. Design a progression for me with five stages: Beginner, Guided practice, Independent practice, Real-world application, Professional level. For each stage tell me: - what I must know - what I must be able to do without help - the mistakes people make at this stage - one practical challenge - one real project that would prove I reached this stage - one way I can test myself honestly Then tell me the signals that I am ready to move to the next stage, and the signals that I have skipped ahead too early. Keep the theory to the minimum I actually need. Focus on ability I can transfer to situations you and I have not discussed.