Document management inside the process, not beside it.
Industry analysts split document work into two markets: intelligent document processing (IDP) — capturing, classifying and extracting information from documents — and document management — their custody: versions, permissions, retention and signature. Dexon BPM works where both have to act: the document is not an attachment to the process but a governed object that can stop it.
The term and the brand
The category is established. What differs is where the document lives.
IDP is a category every major analyst firm names the same way — Gartner, Everest Group, QKS Group and IDC all call it intelligent document processing. Its neighbouring market is the custody of documents — what Gartner today evaluates as document management, formerly content services platforms, formerly ECM. Dexon's distinction is the intersection of the two: the document as a governed object that can stop the process it belongs to, which neither market claims on its own.
The difference worth stating: in most stacks the document sits in a repository beside the workflow, and nothing stops a case that lacks it. In Dexon BPM the document is a requirement of the process state — a case without its document does not advance, and every document action leaves the same audit trail as any other activity.
The mapping
What this market expects, and where it lives in Dexon BPM
The document lifecycle inside a governed process: how it enters, how it is found and issued, and how it governs the case.
Capture, find and issue
Intake by email →
Documents and cases enter from monitored mailboxes and land on the record they belong to — not in a shared inbox.
Search by content →
Documents are indexed by their content and found by relevance, always within the permissions of whoever is searching.
Signed, time-stamped output →
Documents issued from templates filled with the process data, with a handwritten signature captured on screen, an RFC 3161 time stamp and a QR code to validate them.
Govern
Versions and custody →
Versions with authors and dates, permission-controlled access, and the physical location of the original on record — the archival half of the category.
Documents that gate →
Document requirements enforced per process state: the case cannot close, or even advance, until the required evidence exists.
Evidence, attached to everything →
Any object of the architecture — a case, an asset, a risk treatment — carries its documents, and the audit reads them where the decision happened.
Bring one document-heavy process
Contracts, applications, authorisations, supporting evidence. We will show the document entering the process, the requirement that blocks progress without it, the signed and time-stamped output, and the audit trail that survives the auditor's questions.