Process discovery
Process discovery from documents
ThinkPrior is AI process discovery from DCube Data Sciences Corp. Teams upload documents they already have, such as SOPs, transcripts, policies, decks, and recordings. ThinkPrior drafts a current-state process map, about 70 percent complete, and leaves gaps visible. An analyst confirms the scope and finishes the seams. Engagements run in an isolated cloud environment, or on an on-premise appliance where the documents stay on the operator's machine.
- Source · PDFFulfillment SOP
- Source · TranscriptSteerco interview
- Source · WordCredit policy
- Action StepReceive order
- Decision PointCredit?
- GapApproval limit missing
- OutcomeShip
The pile drafts the map. A limit the SOP never states stays a gap.
01 · The files you already keep are the evidence
What is process discovery from documents?
Process discovery from documents is the work of reading the files a team already keeps and drafting the process those files describe.
ThinkPrior takes SOPs, interview transcripts, policies, decks, and recordings, and produces a current-state map. The map is about 70 percent complete on purpose. Steps the documents support are tied to a source passage.
Steps the model infers are marked as inferences. Anything the pile never explains stays a gap, so the drawing does not grow a box just to look finished. Consulting teams and internal analysts use that map before they improve the work, prepare a compliance review, or design automation.
~70%
Draft completeness. The rest stays open on the map.
3 states
A step is cited, inferred, or left as a gap.
02 · Scope first, then the seams between documents
How does ThinkPrior turn a document pile into a map?
ThinkPrior reads the uploaded pile and drafts the process boundaries before it draws the detail inside each one.
The analyst confirms that scope on one screen. Each in-scope process is then mapped with its steps, branches, and handoffs. A connection that spans two documents of the same process becomes an ordinary arrow, which is how a seam between an intake SOP and a risk SOP shows up.
Endings that are the same business outcome are merged. Two steps that share a phrase but belong to different actors stay separate. The analyst then finishes the gaps, and the map leaves in the formats the team already presents in.
Scope first
The analyst confirms process boundaries on one screen.
6 exports
Visio, Word, PDF, Miro, HTML, and Markdown.
03 · A missing step stays missing
What stays visible when the documents are incomplete?
Gaps stay on the map when the documents never explain a step, a handoff, or a decision.
ThinkPrior leaves that hole visible. An inferred step is marked as an inference so a reviewer can see it is not a quotation from the pile. Completeness follows what was uploaded.
Irrelevant files are triaged out of the engagement. Missing evidence remains a gap for the analyst to close with the people who do the work. The as-is picture includes those holes, because a complete-looking map that invented the missing steps would hide the real state of the process.
Visible
Missing evidence stays on the map.
Triaged
Irrelevant files leave the engagement.
Three steps from the pile to a current-state map
- 01
Upload the documents
SOPs, transcripts, policies, scans.
SOPorder-fulfillment-sop.pdf
Transcriptsteerco-interview-transcript.txt
Policycredit-approval-policy.docx
SOPorder-fulfillment-sop.pdf
Transcriptsteerco-interview-transcript.txt
Policycredit-approval-policy.docx
Drop files here - 02
AI produces a ~70% map
A structured process map with Gaps flagged for analyst review.
order-management.thinkprior - 03
Analyst-in-the-Loop finishes Gaps
Confirm the scope. Fill seams. Export to tools you use.
Analyst review queue
Credit threshold above $50kGapException escalation pathConfirmed
The as-is from the pile you already have. Your analyst finishes the seams the documents never explained.