Word to EDGAR HTML: the handoff checklist that prevents rework

Word-to-EDGAR conversion should preserve approved disclosure, not rewrite it. A useful handoff identifies exactly which source is approved, what the conversion includes and who can authorize changes. The SEC's document-format requirements belong to the applicable Filer Manual and submission instructions, rather than to Word's export settings. Official manual.

Start with one approved source

A folder containing several files named "final" does not establish an approved source. Name one version as the conversion baseline, record its timestamp or version identifier and identify the person who can resolve ambiguities. Keep a separate record of later changes instead of silently replacing the baseline.

Resolve tracked changes and comments through the disclosure owner's process. A converter should not guess whether a deleted paragraph or an unresolved comment belongs in the public filing. If approval is incomplete, label the output as a draft proof.

Give financial tables their own review

Tables often carry the highest concentration of production risk. A missing parenthesis can change a reader's understanding of a number; a displaced column heading can misidentify the period. Review both the visible layout and the relationship between headings, figures, units and footnote markers.

• Reconcile column headings and reporting periods against the approved source.
• Check negative values, dashes, decimals and scaling labels.
• Inspect merged cells and multi-row headings after conversion.
• Confirm that footnote references still point to the right note.
• Compare totals to the approved source without independently changing accounting values.

This is a production checklist, not an audit procedure. Refer a suspected inconsistency back to the responsible reviewer rather than correcting it without approval.

Separate styling from meaning

Word documents can use tabs, text boxes, floating objects and page positioning to create a layout. A web-readable document may need a different underlying structure. Preserve meaning and reading order instead of forcing every page break to behave like a printed page.

For an illustrative example, a heading visually placed above a table could be stored in a floating text box. A direct export might separate it from the table in the resulting reading order. A controlled conversion checks that relationship explicitly. The example describes a potential failure mode, not a defect in every Word export.

Define the proof and revision loop

Ask for a proof that the disclosure team can review in the intended viewing environment. Return consolidated corrections against a named proof version. Avoid mixing email instructions, spreadsheet notes and handwritten changes without a single reconciliation log.

After revisions, check the changed text and nearby content. Replacing one sentence can shift a footnote marker, heading or table boundary. Keep the final approval associated with the exact deliverable, not an earlier preview.

Do not confuse HTML with Inline XBRL

A document can look correct in HTML without containing the required structured-data tagging. The SEC describes Inline XBRL as a single human-readable and machine-readable document. If tagging is in scope, identify its owner and validation stage separately. SEC Inline XBRL overview.

What a complete request contains

Provide the form type, approved source version, reporting period, exhibit list if relevant, target proof time, filing time zone and authorized approvers. Use the agreed secure transfer method for nonpublic material. The final filing package must be evaluated against the relevant EDGAR requirements; an ordinary browser preview alone does not establish acceptance.