Home → Workflow → Distribution
Distribution
Once a manual is published, tracking who has which copy and which contractor received which revision becomes its own workflow. Ironmark holds two first-class surfaces for that: Controlled Copies for custodian-assigned distribution, and Deliverables for contractor and program-office releases.
Controlled Copies
Every controlled copy is a distinct record — recipient, custodian, issue number, effective date, and disposition (active / superseded / returned / destroyed). When a new revision publishes, the system flags out-of-date copies for recall and notification.
- Recipient + custodian — who holds the copy and who's responsible for it
- Issue + effective date — which revision they hold and from when
- Disposition — active / superseded / returned / destroyed, with transition timestamps
- Audit-linked — every state change lands in the audit chain with actor and reason
Deliverables ledger
Program deliverables — cuts sent to a contractor, a customer program office, a partner — are recorded per revision on the Deliverables surface. Each row is a shipped artifact with the destination, revision, format, size, and admin download link for a same-source re-cut.
Portal delivery — the customer-facing side
Portal-facing customers pull the current published revision themselves and (optionally) file redlines against it — see the portal workflow for that side of the equation. Controlled Copies and Deliverables record what was sent to whom; the portal is the actual pickup surface.