Specialist sheet · Numbering
A document numbering system shaped around your convention.
Define any segment structure, publish controlled versions and allocate identities through direct generation, ranges or governed requests—before a Forma file exists.
No fixed project, originator or discipline schema. Every segment, value and label is user-defined; the ISO 19650 starters are editable starting points.
Convention builder
Drag, add or rename segments. Choose free text, controlled values, generated keys or sequences.
Live preview
Identity register
| Number | Status |
|---|---|
| …-0001 | Held |
| …-0002 | Assigned |
| …-0003 | Voided |
| …-0004 | Retired |
Convention library · Organisation-wide
Start from ISO 19650. Finish with the way your organisation works.
Use international, UK or Spanish ISO 19650 starter families, then edit every segment, delimiter, rule and controlled value. Save conventions in an organisation-wide library for projects to adopt.
- 01International, UK and Spanish starter variants—all editable
- 02Immutable released versions with an auditable change history
- 03Namespaces prevent collisions between convention families
- 04Projects pin a version or follow the latest approved release
- 05Promote a proven project convention into the organisation library
Allocation · Direct, batch or requested
Issue the right identities without losing control.
Different teams need different routes into the same governed register. Foreman keeps the policy, requester and outcome attached to every allocation.
Generate one number—or reserve a range.
- ADirect generation for authorised document controllers
- BContiguous ranges for planned packages and bulk work
- CSave drafts and resume incomplete generation sessions
- DBatch deep links return teams to the exact allocation
Route requests around the way you approve.
- AInternal requests from signed-in project teams
- BPublic request forms for controlled external access
- CApproval policies decide when allocation needs review
- DRequester and requester-organisation directories keep names consistent
- ECompletion-email status shows whether the result was delivered
Identity register · State is explicit
Know which numbers are available, in use or gone forever.
The document identity register follows each number through Held, Assigned, Voided, Expired and Retired. Voiding is permanent, preserving the gap and its reason instead of quietly recycling the identity.
- ✓Assign a held identity to an existing or Proposed document
- ✓Create Proposed documents in bulk from a generated batch
- ✓Permanently void identities with activity evidence
- ✓Export the register to CSV and share batch deep links
Next actions · Use the rule or see the platform
Test a filename. Then govern the identity behind it.
FAQ · Numbering
Questions about controlled numbers.
Does the convention require fixed ISO 19650 fields?
No. Segment structures are arbitrary and user-defined. ISO 19650 international, UK and Spanish profiles are editable starters, not locked schemas.
Can we reserve numbers before documents or files exist?
Yes. Held identities can be created directly, by range or through an approved request. Assign them later to a Proposed document or a document bound to Forma.
What happens to a voided number?
Voiding is permanent. The identity remains in the register with its reason and activity history and is not recycled.
Can external organisations request numbers?
Yes. Public request forms work alongside internal requests, with requester and requester-organisation directories plus approval policies.
Make the register authoritative before upload day.
Build your convention, release a version and control every allocation.