Document Formatting Services: What to Prepare and Confirm

Document formatting aligns a file with an agreed visual or structural specification. Depending on the scope, this may include heading styles, margins, spacing, page numbers, section breaks, tables, figures, captions, or a consistent reference-list layout.

Formatting does not establish that a document meets every legal, journal, university, or regulator requirement. The client must supply the current instructions and approve any content or data changes.

Send the editable source document whenever possible, along with the exact template or instructions. A PDF can show the intended appearance, but it is not always suitable as the source for editing because its text and layout may not be easy to adjust reliably.

Before work begins, confirm the number of pages or words, document format, required styles, deadline, and whether tables, references, appendices, or multiple files are included. Ask whether the service includes visual checks, accessibility tagging, or only basic layout consistency; do not assume these are included.

If a regulator, journal, university, or client provided requirements, name the issuing organisation and provide the relevant version. Requirements can vary by document type and may change, so the supplied source should guide the work.

If the document contains several versions of the same section, identify which one is approved and whether earlier material should be retained as a comparison. Clarify how many revision rounds are included and whether the formatter will return questions for content decisions. Agree these details before work starts so a request to change the brief does not become an unexpected schedule or price change. For a multi-file package, specify how captions, labels, and filenames should correspond across the main document and supporting items.

Formatting becomes inconsistent when a file is judged against several overlapping examples. Decide which source controls: an institutional template, journal instructions, client brand guide, regulator form, or a specific style manual. If two sources conflict, ask the document owner which one takes priority rather than mixing the rules.

Send the exact file or link and identify its version or access date. If your department provides a sample document, explain whether it is an official template or simply an example. Tell the formatter about local exceptions and required sections, such as declarations or submission labels. A clear source of truth helps avoid unnecessary revisions and makes later review easier to reproduce.

In an editable document, built-in heading styles help keep type, spacing, hierarchy, and navigation consistent. A manually bolded line may look like a heading but fail to appear in the contents page or assistive technology. Ask whether the scope includes applying semantic styles or only matching the visible appearance of the supplied page.

Review the hierarchy from title to chapter, section, and subsection. Check that similar levels look alike and that the text does not jump from a top-level heading to a deeply nested level without a clear reason. Avoid using formatting alone to communicate structure when the final file will be read electronically. If the client has a template with styles already configured, keep a copy before changing it so the original can be restored if necessary.

Page numbers, heading numbers, table captions, figure labels, footnotes, and the table of contents may be generated by fields. Manual numbering can become outdated after an insertion or deletion. Confirm whether the formatter will update fields and cross-references, and whether the author should refresh them again after final revisions.

Inspect numbering for gaps and duplicates, and compare every caption with the item it describes. Cross-references should point to the correct section, table, figure, or appendix. If numbering is managed by a template, follow its sequence rather than adding custom labels. A visual check should also confirm that captions stay with the relevant object and do not split awkwardly across pages.

Tables should have clear column labels, sensible alignment, visible units, and enough space for notes. Check whether a long table should continue across pages, repeat its header row, or move to an appendix under the supplied rules. Figures need legible labels, captions, sources, and enough resolution for the final viewing or print size.

Ask the author or subject-matter owner to verify all values, symbols, dates, and category names against the approved source. Formatting can improve presentation but cannot confirm the data are correct. Also confirm permission and source notes for any reproduced material. Compare the Word or source file with the exported PDF because scaling, font substitution, or page breaks can make a previously readable object difficult to interpret.

Reference presentation may include indentation, line spacing, punctuation, italics, capitalisation, ordering, and consistent DOI or URL display. The correct pattern depends on the selected style and source type. Share the required guide and any institution-specific exceptions rather than expecting a formatter to infer them from a mixed reference list.

Missing authors, dates, titles, page ranges, or identifiers are content questions, not purely layout problems. Do not ask a formatter to guess them. Mark incomplete entries for author verification and compare the final list with in-text citations if that check is included. A formatting review can identify visible inconsistency; a full bibliographic verification is a separate task that should be agreed explicitly.

Review margins, page size, orientation, spacing, line breaks, headers, footers, section breaks, and blank pages against the supplied requirements. Look for headings stranded at the bottom of a page, captions separated from tables, oversized whitespace, or a single landscape page that causes later numbering to reset unexpectedly.

Check that the page-number sequence follows the instructions across front matter, main chapters, and appendices. Different numbering formats may be required for different sections. Do not remove a section break just because the next page looks unusual; it may control page orientation, header content, or numbering. Ask the document owner before changing a layout rule with a functional effect.

A visually polished file is not automatically accessible. Depending on the format and scope, accessibility work may involve semantic headings, table headers, alternative text, reading order, document language, meaningful link text, and checks in an accessibility tool. These tasks should be requested explicitly rather than assumed as part of standard formatting.

For PDF delivery, confirm the export settings and inspect the exported file itself. Check fonts, symbols, bookmarks, links, page order, metadata, and whether any comments or tracked changes remain. If the receiving portal specifies a file size, naming convention, or security setting, include it in the brief. The client should validate the final PDF against the submission portal's current instructions.

A clean handoff includes the latest source file, applicable instructions, assets, and a short note explaining what should not change. Use clear filenames and label the reference version separately from the editable source. If there are several files, include a simple inventory that identifies the main document, appendices, figures, and supplementary material.

Before sending, remove duplicate versions from the transfer folder or clearly identify which one is current. Tell the formatter how to ask questions and who can approve changes. If the document contains tracked changes or comments, explain whether these are part of the task or should remain untouched. A tidy handoff reduces confusion about which requirements and files were used.

Formatting does not establish that a journal submission meets every editorial rule, that a regulatory filing is compliant, or that a university will accept the document. It also does not verify the truth of data, the completeness of a legal disclosure, or the accuracy of references unless those checks are separately included and performed by the appropriate reviewer.

The person or organisation responsible for the document should approve its content and confirm current requirements. If the work is regulated or legally consequential, involve the qualified compliance or legal reviewer responsible for that context. An editor can apply supplied instructions and flag inconsistencies; the final authority remains with the client or recipient.

Open the returned file in the software you will use to submit it. Check page breaks, headers and footers, contents-page links, table and figure numbering, cross-references, and whether symbols or fonts display as expected. Compare the final document with the source instructions, not only with the editor's preview.

Then export the required final format and inspect that exported copy. Our [document formatting service](/document-formatting) page explains the available support; you can also read the [thesis tables, figures, citations, and references checklist](/blog/thesis-tables-figures-references-checklist).