Service scope

Package assembly & exhibit checks

A package is more than its primary document.

Illustrative controlled document production layers

Assignment and fit

Organize the agreed primary document, exhibits and referenced assets into a versioned handoff. Identify missing files and broken relationships before the authorized filing team begins its own processing.

Inputs needed to quote

  • Primary document and all companion files
  • Client-approved exhibit order and naming instructions
  • Applicable taxonomy set if tagging is in scope

Identify whether the material is public, synthetic or private. For private work, confirm permitted processing and the transfer channel before sending the source. A source receipt is not automatic acceptance of its deadline.

Concrete deliverables

  • Filename/role/version manifest
  • Referenced-asset and internal-link findings
  • Organized review package with open-item disposition

Production checks

  • 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.

Reference: SEC production / role guidance. Verify the current requirements for the agreed job.

Scope boundaries

The client determines legal exhibit classification and submission metadata; assembly does not establish acceptance.

The contracted review owner approves the final candidate. A later edit changes the version and may require renewed approval. Production acceptance and filing authorization are separate.

Business-specific handoffs

Quote and schedule

Cost follows source complexity, output layer, review effort and revision allowance—not a universal HTML page count. A rush slot is accepted only when inputs and reviewer availability fit the actual capacity.

How quotes are structured →

Google optional storage is denied by default. These controls send Google consent signals and remember your choice for up to 180 days. They do not block third-party script loading or control Jotform chat. Tags inside Tag Manager must be configured to respect consent.

Read the storage and integration inventory. Do not share confidential files or credentials in the chat.