Aug 27, 2026
4 min read
Most grading rubrics include a line item for "formatting" or "presentation" worth a small, fixed percentage — and most students lose it not from ignorance but from assumption: they format on autopilot using whatever their document's default settings happen to be, which frequently don't match what the assignment brief actually specifies. This is a five-minute checklist, done once per document, that recovers those marks reliably.
The default in most word processors isn't universal — check the brief first, then set explicitly:
| Setting | Common academic default | Where to set it (Word) | Where to set it (Google Docs) |
|---|---|---|---|
| Margins | 1 inch (2.54 cm), all sides | Layout → Margins → Normal | File → Page setup → Margins |
| Page size | Letter (US) or A4 (most other regions) | Layout → Size | File → Page setup → Paper size |
| Line spacing | Double-spaced (essays), single (technical reports) | Home → Line Spacing | Format → Line spacing |
Institutions in different regions default to different page sizes — a document formatted on a US-configured template can silently reflow when opened on an A4 default printer or PDF export, shifting page counts. Set the page size explicitly rather than trusting the software default.
Rubrics rarely specify an exact font, but they do expect consistency — one font family and size throughout the body, with headings distinguished by weight or size, not by switching fonts entirely:
Reviewers navigate a document by page number in feedback and viva discussions — a missing page number is a small but real friction point.
In Word: Insert → Page Number → choose position (bottom-center is the safest default absent other instructions).
In Google Docs: Insert → Page numbers → choose position and starting page.
If the brief requires a running header (student ID, course code, or a shortened title on every page), add it through the same Insert menu rather than typing it manually into each page — a manually-typed header breaks the moment page counts shift during editing.
A common self-inflicted formatting bug: pressing Enter repeatedly to push content onto a new page. This looks fine until an edit earlier in the document shifts everything down, leaving a page of blank lines in the middle of the paper. Use an actual page break instead:
Ctrl+Enter).Ctrl+Enter).A real page break stays anchored to the intended content boundary regardless of how much text gets added or removed above it.
When a course has 40+ students submitting to the same folder or portal, "Assignment1_Final_v2.docx" is indistinguishable from twenty other files with the same name. A format that survives any submission system:
LastName_FirstName_StudentID_AssignmentTitle.docx
Consistent, sortable, and immediately identifiable without opening the file — most institutions that specify a naming convention in the brief are asking for exactly this pattern or a close variant.
If the brief specifies PDF, submitting a .docx risks a formatting shift on the grader's machine — different default fonts or missing fonts can silently reflow the entire document. Export to PDF and open the exported file yourself before submitting, checking that margins, page breaks, and headers all survived the conversion exactly as intended.
Formatting and length are two separate rubric items, but they interact — margins set too wide or line spacing set too loose can push a document past a strict page limit even when the actual word count is well within bounds. Once formatting is finalized, run the actual text through the Word Counter to confirm you're within the assignment's stated word or page limit before submitting — formatting the document correctly and then discovering it's 15% over length is a frustrating way to spend the last hour before a deadline.
Discuss tutoring, code review, project mentoring, or research-method guidance.