What EDGARization means
EDGARization is a commonly used term for preparing disclosure documents for an EDGAR production workflow. To EDGARize an approved source is not merely to export a file that happens to open in a browser. The permitted markup, filenames, assets, form-specific requirements and approval controls also matter.
Word to HTML conversion is one step in that process. It can preserve paragraphs and styles as a first pass, but it does not by itself prove complete content, correct financial-table relationships, valid iXBRL or a filing-ready package. Ordinary website HTML rules are not a substitute for current applicable SEC requirements.
Freeze and inspect the source first
Receive the exact approved Word/Excel/PDF version and written instructions for comments, tracked changes and unresolved content. Save read-only originals. Inventory sections, tables, footnotes, images, signatures, navigation and companions. Confirm the approver, review owner, output layer and achievable schedule.
Escalate blanks and conflicting versions rather than filling them by inference. A public final filing does not make a private Word draft public, and a conversion-only assignment does not require collection of Login.gov credentials or filing tokens.
Rebuild structure before polishing appearance
Use styles, semantic headings, tested tables and stable anchors. Preserve reading order and intended emphasis. Check row labels, merged cells, comparative periods, units, signs, note markers and totals against source. Do not rasterize a difficult financial table just to avoid reconstruction or required tagging treatment.
First-pass exports may contain Word-specific structure. Remove it only after identifying any carried content such as footnotes and symbols. Inventory permitted images and matching relative filenames; check that every referenced asset exists.
Reconcile and package the exact version
Run text, number, structure and applicable regulatory/package review passes. Use extraction/diff alongside visual proof: matching text does not prove the table relationships, while a browser accepting malformed markup does not prove XML validity.
Generate the proof from the exact working package. Process one authorized change list, increment the version and retest. Deliver the primary document, assets, manifest, issue/change log and applicable validation evidence. Conversion delivery is not LIVE filing permission or a guarantee of SEC acceptance.
Use the current controlling references
Review the SEC EDGAR Filer Manual and current form/technical guidance for the contracted workflow. iXBRL requires additional specialist checks and complete taxonomy relationships.
EDGAR conversion services · Complete HTML package checklist · XBRL versus HTML conversion.