The register that keeps
its own paper trail.
Document control fails at the seams: the number that means two things, the revision nobody can prove was issued, and the transmittal that no longer matches the document it named. XO-Docs closes all three.
Document control fails at the seams
Not in the middle, where the software is. At the joins, where the register stops being able to answer questions.
Which one is current?
Two documents end up sharing a number because one person typed it in lower case. Nobody can say which revision was issued, or who set it that way, so every decision downstream inherits the doubt.
What exactly did we send?
The package went out as attachments from someone's Outlook. Three weeks later the document has been re-issued twice and renamed, and reconstructing what the contractor actually received means reading old email.
Why didn't the workflow run?
A drawing skips approval and nobody finds out until it matters. Most systems record the automation that succeeded and keep nothing at all about the automation that quietly did not.
One register that can account for itself
Numbering, revisions, transmittals and deliverable plans, each recording what happened as it happens.
One numbering scheme, enforced rather than requested
Set the scheme once at company level and override it per project where a client insists on their own. Numbers are generated on upload and checked by the database, not by a reminder email.
- Company scheme, project overrideComponents, order, separators and padding, set once and inherited
- Generated on uploadThe number comes from the scheme rather than from memory
- Unique per project and document typeA database constraint, case-insensitive, so TOW-ARC-DWG-001 and tow-arc-dwg-001 cannot both exist
The register answers who, what and when
A revision moves from upload into review, on to Approved or Rejected, and then to Issued. Every transition is written with the actor, the time, and the status before and after.
- Actor and timestamp on every transitionWritten automatically as part of the change, not typed in afterwards
- Governance rules that name themselvesA blocked submit or issue returns the rule and the reason, not a generic refusal
- Submit, approve and reject reach the rest of the platformOther apps read document state from the event stream instead of asking
design-review-required: no approver assigned to this document type.The transmittal doesn't change when the document does
Select the revisions, add the recipients and issue. XO-Docs records the document number, title, revision and version as they were at that moment, generates a tracking number, renders a PDF and emails each recipient separately.
- A snapshot, not a pointerRe-issue or rename the document later and the transmittal still names what you sent
- A send record for each recipientAttempts, the time the mail server accepted it, and a reason when it was rejected
- Resend to one personFix the address that failed without re-issuing the package to everyone else
It reads the drawings. You still decide.
Drag a batch into Uploads. Every file is staged, checksummed and validated, and a file whose name suggests a different project is stopped there. Ask for suggestions and XO-Docs reads the title block, proposing a number, title and metadata with a confidence for each.
- Nothing is applied until you apply itSuggestions live in their own record and never reach the document on their own
- Every suggestion keeps its receiptStored with the reader that produced it, that reader's version and a confidence basis
- Apply the right ones, reject the restYou review the batch and decide what becomes a fact in the register
It records the workflows that didn't run
Set a rule pointing at a workflow: a document type, optionally a stage, and up to two further conditions. From then on a matching upload starts that workflow on its own. And every attempt is recorded, including the ones that never started, with a reason code.
- Attempts, not just successesSkipped and failed launches are written down with the reason they failed
- "Why didn't it run" has an answerIn the record, rather than in somebody's recollection of that week
- An automation rate you can measureAttempts that started against all attempts, and the reasons that come up most
definition_not_founddefinition_not_configuredThe plan and the register are the same screen
Build a TIDP plan from a company template, an Excel import, or straight from the project's spatial hierarchy. Submit the version, have it approved, and let real uploads match themselves to planned items by number.
- Versioned and approvedApproving a plan version is a recorded decision with a name and a time, not an email
- Uploads match themselvesA document arriving against a planned number closes that item without anyone reconciling
- Outstanding sits next to deliveredThe gap between what you owe and what exists stops living in a spreadsheet
XO-Docs works with the whole platform
Documents flow seamlessly across all BrieXO modules.
Ready to take control of your documents?
See the register, the transmittal record and the deliverable plan running against a project of your own.