Creating Professional Documents

A professional document communicates clearly before anyone reads a single word. Structure and formatting signal competence — a well-formatted page tells the reader you are organized, detail-oriented, and take your work seriously. Here is the anatomy of every professional document:

• Every document needs a title, clearly labeled sections, and a logical flow from top to bottom — readers should never have to hunt for what they are looking for
• Use heading styles (Heading 1, Heading 2) from the Styles panel — not just bold text — so the document is scannable and navigable
• Professional fonts only: stick to Calibri, Arial, or Georgia. Use one font for headings and a different complementary font for body text
• Standard 1-inch margins on all four sides and 1.15 to 1.5 line spacing for optimal readability and professional white space
• Never mix more than two fonts in a single document — inconsistent typography is one of the most common signals of an amateur document
• Always start from structure: set your title and section headers first, then fill in body content — never start with a wall of text

Two file formats serve two distinct purposes in professional document work. Knowing when to use each is a non-negotiable workplace skill:

• .docx / .gdoc — The Working File: Save in this format while you are drafting and editing. It remains fully editable and is what you keep in your files.
• .pdf — The Presentation File: Always export to PDF before sharing a document externally. This locks the layout and preserves your deliberate formatting exactly as designed, no matter what software the recipient uses.
• Never send a raw .docx to a client unless they specifically request an editable version — an editable file exposes your drafting process and can be accidentally modified.

Professionalism extends to the file directory. A consistent naming convention gives every document instant context — who made it, what it is, and which version — without opening the file:

• Use the format: Date_DocumentName_Version — for example, 2025-04_ClientSummary_v1
• Use YYYY-MM date format so files sort chronologically in any folder view
• Increment version numbers when making significant revisions (v1 → v2 → v3)
• Never use spaces in file names — use underscores or hyphens instead, which prevents errors when files are shared across systems