Production guide

What a complete HTML handoff contains

The primary document alone rarely tells the whole handoff story.

Illustrative controlled document production layers

List files and roles

Include the agreed HTML, every referenced permitted image, approved exhibits and a manifest. Required taxonomy companions belong in the package when tagging is contracted.

Test references without browser cache

Check relative names and filename case. A cached image can hide a missing delivery file; review the assembled package in a clean environment.

Tie proof to version

Generate the proof from the delivery candidate. Log the source version, package version and review disposition so nobody approves one package while submitting another.

Separate handoff from acceptance

A production handoff allows the authorized team to perform its own checks. Upload, TEST processing and LIVE acceptance are distinct stages; do not label an unsubmitted package accepted.

Scope and primary reference

Educational production guidance only. Client disclosure approval, legal/accounting judgement, qualified tagging review and filing authority remain separate. Confirm the appropriate qualified review and current requirements for each live assignment.

Reference: Current official SEC guidance. Verify the current requirements for the agreed job.

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.