Convention
Define arbitrary segments and controlled values; release an immutable version.
Platform · Document Control
Control the document before the file exists.
Create the convention, allocate the identity, govern the deliverable and record every revision. Bind a Forma file when it arrives—or keep the record entirely in Foreman.
Foreman-native, Forma-ready. Number identities, Proposed documents and deliverables governance do not require a Forma file or document.
Control line · DC-001Status · governed
01ConventionDefine the grammar
02RequestAllocate by policy
03Held identityReserve before upload
04DocumentCreate or bind
05RevisionRecord each issue
06Delivery / auditProve what happened
Lifecycle · One controlled line
From convention to delivery evidence.
Foreman keeps the steps connected, so a promised deliverable does not begin life as an unexplained filename in a folder.
Request
Generate directly or route an internal or public allocation request for approval.
Held identity
Hold the unique identity while authorship continues, with no file required.
Document
Create a Foreman-only Proposed document or bind the identity to a Forma file.
Revision
Capture revision-specific metadata and keep the document history intact.
Delivery / audit
Track delivery, decisions and activity; notify people and export the evidence.
Model · Four connected records
Conventions define the grammar. Deliverables define the promise.
A naming convention describes how an identity is formed. A deliverable configuration describes the fields, teams, milestones and allowed conventions for a register. The identity reserves the controlled number. The file is an optional physical expression of that record.
- 01Convention: editable segments, controlled values and immutable released versions.
- 02Deliverable configuration: the register type, fields, milestones, teams and permitted conventions.
- 03Identity: a held or assigned number that exists independently of file storage.
- 04File: optionally bind the record to a physical Autodesk Forma item when the document arrives.
Identity · More than one reference
One document can carry the references each party needs.
Keep a delivery-team number, client reference or another governed convention on the same document. Roles make the purpose explicit; the underlying references keep their own convention and history.
- ADelivery-team reference · ARC-ZZ-00-DR-A-1032
- BClient reference · CLT-PKG-004871
- CDocument record · one revision and delivery history
Evidence · Built into the record
Governance that survives the deadline.
Approval policies control allocation and issue. Released convention versions stay immutable. Activity records show who requested, approved, assigned or changed each record.
- ✓Approval decisions and request context
- ✓Immutable released versions and revision-specific metadata
- ✓Activity records, completion-email status and notifications
- ✓CSV and protected Excel exports for review or handover
Specialist sheets · Continue the journey
Go deeper into the two control instruments.
FAQ · Document control
Questions from the control desk.
Does every document need a file in Autodesk Forma?
No. Number identities, Proposed documents, placeholders and deliverables governance can exist in Foreman without a physical file. Forma binding is optional and can happen later.
Does Foreman replace Autodesk Forma?
No. Foreman adds document-control governance around the CDE without requiring every record to live there. When a physical file exists, it can remain in Forma while Foreman manages its identity and delivery context.
Can one document have a client number and our own number?
Yes. A document can carry multiple references with explicit roles, including delivery-team and client references, even when those identities follow different conventions.
Are MIDP and TIDP fixed deliverable types?
No. They are common examples. Teams can configure multiple deliverable-list types with their own fields, controlled values, milestones, teams and allowed conventions.
Give every document a controlled beginning.
Start with governance. Bind the file when it is ready.