The business-specific assignment
Assemble using counsel-approved exhibit labels and order. Identify missing schedules and referenced attachments without deciding whether an exhibit is legally required.
Your coordinator: Securities paralegals and filing coordinators.
The source context may include approved agreements, exhibits, signatures and disclosure revision lists.
Illustrative production scenario
A reference to an annex does not establish that production has received the annex; reconcile it against the manifest.
This is an example of the control to test, not a measured client result or an accepted filing. Ask the named reviewer to define success before production starts.
Inputs and outputs
Provide these inputs:
- Primary document and all companion files
- Client-approved exhibit order and naming instructions
- Applicable taxonomy set if tagging is in scope
A scoped handoff can contain:
- Filename/role/version manifest
- Referenced-asset and internal-link findings
- Organized review package with open-item disposition
Review focus
- Check filename case, relative paths and matching references.
- Keep unrelated client files and source drafts out of the delivery folder.
- Verify the proof was generated from the same package version.
Counsel owns legal wording, form/exhibit classification and disclosure approval.
What is outside this assignment
The client determines legal exhibit classification and submission metadata; assembly does not establish acceptance.
Consolidate comments through one authorized contact; do not ask production to select legal language.
Plan the handoff
Agree source freeze, version naming, one instruction stream, correction allowance and escalation contact. Confidential materials belong only in the separately approved transfer route.
Read the full service scope → · Return to your business →