Board

Formatting Basics

Formatting basics come down to one principle: the format has to match the medium, the audience, and the tolerance for error in that setting. A résumé, a workplace dress code, a spreadsheet, and a remote-work arrangement each carry their own rules, and most formatting failures are not aesthetic — they are mismatches. The document that looks clean on your laptop but breaks in the applicant tracking system, the dress code that reads as neutral but screens out a religious practice, the spreadsheet that nobody can audit after you leave: these are formatting problems with real costs. Get the format right and nobody notices. Get it wrong and the reader stops reading the content entirely.

9 articles
Formatting Basics

Formatting Basics

9 articles

Formatting basics come down to one principle: the format has to match the medium, the audience, and the tolerance for error in that setting. A résumé, a workplace dress code, a spreadsheet, and a remote-work arrangement each carry their own rules, and most formatting failures are not aesthetic — they are mismatches. The document that looks clean on your laptop but breaks in the applicant tracking system, the dress code that reads as neutral but screens out a religious practice, the spreadsheet that nobody can audit after you leave: these are formatting problems with real costs. Get the format right and nobody notices. Get it wrong and the reader stops reading the content entirely.

Résumé formatting: the machine reads first

Format your résumé for the parser before you format it for the human. Most mid-size and large employers run applications through an applicant tracking system that converts your file into plain text, and anything that survives that conversion badly — tables, text boxes, columns, headers and footers, graphics, icons standing in for words — is what the recruiter gets to see. A two-column layout that looks sharp in Word can parse as interleaved fragments, with your job titles landing next to the wrong dates. You find out never, because rejection letters don't explain themselves.

The reliable format is a single-column document in a standard font, with contact details in the body of the page rather than a header, section headings in plain capital letters or bold rather than as designed graphics, and a chronological or skills-based structure the parser can follow top to bottom. Submit a .docx or a text-based PDF, not a scanned PDF or an image export. If the posting gives a file format, use it exactly. Dates in a consistent month-year form, job titles on their own line above the employer, bullets that start with a verb: none of this is decoration. It is what lets a human skim in six seconds and what lets a machine extract the right fields.

The cost is visual. A single-column, plain-font résumé will never look like the designed templates sold on career sites, and for creative fields — design, advertising, some marketing roles — a portfolio or a deliberately styled document may be the right call. The judgment is about who screens first. If a human with taste opens the file, style earns you something. If software opens it, style earns you nothing and can cost you the interview. When you can't tell, default to the parseable version and put your personality in the cover letter.

Cover letters, email, and the formatting of first contact

Match the format of the channel the employer used. If they asked for a cover letter as an attachment, attach a document formatted like a business letter: your contact block, the date, the recipient's details, a salutation, body paragraphs, a close. If they asked you to apply through a portal with a text box, paste plain text with no formatting at all, because smart quotes, bullet characters, and tab indents often arrive as garbled symbols on the other end. If a recruiter emailed you directly, reply in email with a short, well-paragraphed message and no attachment unless asked.

Email formatting has its own failure modes worth naming. A subject line that states the role and your name gets opened; one that says "Application" gets sorted with everything else. Keep paragraphs short enough to read on a phone, because that is where a large share of first reads happen. Avoid colored text, unusual fonts, and signature images with embedded contact details that a mobile client strips out. Attach files with names a stranger can interpret — your name and the document type — rather than a string of numbers from your downloads folder.

The trade-off here is warmth versus safety. Plain-text email feels less polished than a designed PDF, and some candidates worry it reads as casual. In practice the opposite risk is larger: a beautifully designed attachment that the recipient can't open on their phone, or one that trips a spam filter because of an unusual file type, never gets read at all. Format for the device in the reader's hand, not the one on your desk.

Workplace dress codes: where formatting becomes policy

A dress code is an employer's policy specifying how employees are expected to dress at work, and under U.S. Equal Employment Opportunity Commission guidance such codes must not treat employees less favorably because of protected characteristics and may need to be modified as a reasonable accommodation for religious practices or disabilities. That single sentence is the whole formatting problem in miniature: the document has to be specific enough to be enforceable and neutral enough to be lawful. Codes that ban head coverings, require a clean-shaven face, or prohibit certain hairstyles can violate those rules even when the intent was a tidy workplace, because the effect falls unevenly on religious and protected groups.

The format that holds up is a written policy with a clear purpose statement, categories by situation rather than by person — client-facing, warehouse floor, casual Friday — and an explicit accommodation process with a named contact. Describe the standard rather than the garment: "closed-toe shoes" travels better than a list of approved brands. Put the policy in the handbook and reference it in the offer letter, so a new hire sees it before the first day rather than being corrected on it. Keep a written record of accommodation requests and decisions, because the process is what protects both the employee and the employer if a complaint is ever filed.

The honest cost is administrative. A vague dress code takes five minutes to write and creates years of inconsistent enforcement; a specific one with an accommodation route takes longer to draft and requires managers to actually route requests instead of improvising. Smaller employers sometimes skip the written policy entirely and rely on manager judgment, which works until it doesn't. If you are writing one, the accommodation clause is not boilerplate — it is the part that decides whether the policy survives contact with an actual employee.

Remote and hybrid work: formatting the arrangement, not just the document

Telework is a mainstream arrangement, not an exception, and the numbers tell you how to format a remote-work agreement. In March 2026, 22.6 percent of workers teleworked or worked at home for pay, and the rate has ranged from 21.5 percent to 23.0 percent over the last year. For context, teleworkers accounted for 22.9 percent of people at work in the first quarter of 2024, up from 19.6 percent in the first quarter of 2023, and the 2023 annual average across all U.S. states was 19.7 percent. The telework rate is defined by the U.S. Bureau of Labor Statistics as the number of people who telework or work at home for pay as a percentage of those who were employed and at work during the survey reference week. Those figures describe a stable, sizable share of the workforce — which means the formatting question is not whether to allow remote work but how to write the arrangement down.

A remote-work agreement needs to specify the schedule (which days, which hours, which time zone), the location expectations, the equipment and reimbursement terms, the security and confidentiality rules, and the review cadence. Vague arrangements — "you can work from home sometimes" — create disputes about expectations that a two-page document would have prevented. The same logic applies to how work gets formatted once you are remote: shared documents with consistent heading structures, meeting notes with decisions separated from discussion, and file naming that lets a colleague find the right version without asking. Distributed teams live or die on whether the written record is legible to someone who wasn't in the room.

The trade-off is flexibility versus accountability. A tightly specified agreement is easier to enforce and harder to adapt when someone's circumstances change; a loose one is humane in the short term and a source of friction at review time. The middle path most teams land on is a written baseline with a documented process for changing it — which is itself a formatting decision, because the process has to be findable and the changes have to be recorded somewhere a manager can point to.

Documents, spreadsheets, and slides: formatting for the next reader

Format every working document for the person who will open it without you. That means consistent heading levels so the navigation pane works, a table of contents on anything longer than a few pages, page numbers, and a title block with the author, date, and version. It means styles rather than manual bold and font-size changes, because manual formatting breaks the moment someone edits the document and styles survive. It means tables with header rows that repeat across pages and columns wide enough to read without scrolling horizontally. None of this is fussy; it is the difference between a document that can be revised by a colleague and one that has to be rebuilt.

Spreadsheets need a different discipline. Put raw data on its own sheet and never type over it, keep formulas in a consistent column, freeze the header row, and label every tab so a stranger can navigate without a guided tour. Color-code inputs versus calculations if you like, but add a legend, because the color scheme you invented is not self-evident to anyone else. Slides have the loosest rules and the highest cost of getting them wrong: one idea per slide, a font size large enough to read from the back of a room, and a consistent title position so the deck doesn't jump as someone clicks through. Speaker notes are where the detail goes; the slide is a signpost.

The cost of all this discipline is time on the front end and a certain loss of spontaneity. A styled document takes longer to set up than a blank page with bolded headings, and a well-structured spreadsheet takes longer than a flat list. That cost is paid once and recovered every time someone else touches the file. The teams that skip it are the ones where institutional knowledge lives in one person's head and one person's messy workbook, and where the handover takes weeks instead of an afternoon.

Formatting for accessibility and for the reader you can't see

Accessible formatting is not a separate project; it is the same discipline done properly. Use real heading styles rather than bold text that looks like a heading, because screen readers navigate by heading structure and a document with fake headings is a document with no map. Add alt text to images that carry information. Don't use color alone to convey meaning — pair it with a label or a pattern. Make sure link text describes the destination rather than saying "click here." Check contrast between text and background, and set tables up with actual header rows rather than visual alignment.

The same principle extends to the formats you can't see at all. A PDF exported without tagged structure reads as an undifferentiated wall of text to assistive technology. A scanned document with no text layer can't be searched or read aloud. A video without captions excludes anyone in a noisy room or with hearing loss. These are formatting choices, made at the point of creation, and they are much cheaper to make then than to retrofit after someone asks for an accessible version and you have to rebuild the file from scratch.

The trade-off is that accessible formatting constrains design. Some layouts that look striking in a mockup fall apart when you require heading structure and alt text and readable contrast. That constraint is usually a sign the design was carrying meaning in decoration rather than in content, and the accessible version is often the clearer one for every reader, not just the ones using assistive technology. Where the constraint genuinely costs you something — a chart that needs a data table alongside it, a poster that needs a plain-text companion — build both. The redundancy is the point.

Across all of it, the test is the same: hand the document, the policy, the spreadsheet, or the arrangement to someone who wasn't there when you made it, and see whether they can use it without asking you a question. If they can, the formatting worked. If they can't, no amount of content quality will save the file, because they will have stopped reading before they got to the good part.