Process intelligence without clean event logs
Start with documents, partial logs, and workshop evidence. In configured Pro video analysis, review recorded activities before creating an editable BPMN draft.
Direct answer
A process-intelligence project can start from imported models, PDFs, screenshots, partial logs, API data, and workshop evidence, then improve as better data arrives. In configured Pro video analysis, review activities extracted from a recording against timestamped evidence, clarify uncertainty, and confirm scope and sequence before creating an editable BPMN draft. One recording does not establish unseen business rules or process metrics.
Best fit
- Geist fits teams whose process evidence is spread across diagrams, documents, systems, and human knowledge.
- A pure process-mining tool may fit when the company already has clean, complete, case-linked event logs.
Pressure points
- Manual and physical work often leaves weak system traces.
- Partial logs can still anchor a model when paired with timestamps, annotations, and process-owner review.
- Every generated model should show confidence and invite correction.
Read next
Go deeper
FAQ
Frequently asked questions
01Can process intelligence work before event logs are clean?
Yes, if the first output is treated as a reviewed model with provenance and confidence rather than a finished measurement system.
02Which messy inputs are useful?
Existing BPMN, PDFs, images, screenshots, workshop notes, partial logs, API records, and manual annotations can help create the first model. In configured Pro video analysis, users can review recorded activities and confirm their sequence before creating an editable BPMN draft.
03When do event logs become important?
Event logs become important when the team needs variants, cycle time, conformance, bottlenecks, and repeatable measurement against real execution.
Source checks