01 · Scope and intake
Confirm the document, form family, amendment status, approved source, requested output and deadline with time zone. Name the authorized requester, content approver, specialist reviewer where needed and escalation contact. Accept only an achievable job.
02 · Source audit and freeze
Inventory sections, tables, assets, exhibits and hidden source elements. Resolve comments, tracked changes, placeholders and conflicting dates through the approver. Preserve originals and record which version controls.
03 · Build the agreed layer
Prepare editable source or reconstruct permitted HTML according to the scope. Map every section to output. Tagging is a separate specialist lane, not something implied by conversion.
04 · Reconcile the proof
Check text, numbers, structure and package requirements. Generate the proof from the candidate package. Use visual and extracted-text comparison together, with qualified review for data meaning where required.
05 · Revise under control
Process one authorized change list and record requester, old/new wording, impact and retest. A late edit must not quietly bypass approval or create an untracked package.
06 · Exact-version handoff
Deliver the agreed files, proof, manifest and issue/change log. The client’s authorized team performs its submission workflow. Production delivery does not authorize TEST or LIVE filing.
Reference: EDGAR Filer Manual. Verify the current requirements for the agreed job.
Stop-work conditions
- Conflicting source versions or no named approver.
- Unresolved material placeholders, missing exhibits or missing assets.
- A tag decision that changes meaning without specialist approval.
- Unapproved people, tools or transfer route.
- A schedule that can be met only by skipping QA.