HEPO's evidence modules supply the operational records used to examine a business process. Works records what needs doing and how it progresses; Calendar Events records scheduled occurrences; Communication carries exchanges; Presence supplies participation context. Their relationships help a process owner follow a case across those different activities.

The same modules support People & Culture and Process Orchestration. Here the question is how work moves: where it waits, what returns for rework, which information reaches a decision, and what changed after an improvement.

Reconstruct the quotation's handoffs

A quotation was completed later than expected. The work item shows its progress, the calendar shows the agreed review and deadline, a communication thread contains a request for missing information, and participation records help establish who attended the review.

Read together, the records can help locate the delay. They may show that finance was waiting for information, rather than simply taking longer to respond. They may also reveal an incomplete record. Evidence gives the discussion a basis; it does not supply every explanation for what happened.

The process owner first defines the case, period, and question. Implementers connect the relevant records through the shared relationship system and agreed adapters. The evaluation engine can then produce observations against the organization's process definitions.

Four sources with different contributions

Each measure needs an appropriate definition. Cycle time covers the interval from the selected start to completion; blocked duration concerns time in selected waiting states. They answer different questions. Rework also depends on which transitions count as a return to earlier work.

A calendar invitation is not evidence of actual attendance. Duration multiplied by participant count expresses person-time, not a financial cost unless a suitable cost basis is supplied. Other records also have timestamps: calendar events contribute scheduled context rather than owning the whole temporal dimension.

Read relationships as well as counts

A task can be linked to the meeting where it was discussed, the thread that followed, and the people involved. Those connections help distinguish a communication about the case from an unrelated message sent on the same day.

A long thread may represent collaborative resolution or an unresolved problem. A late reply may reflect an agreed handoff, an absent colleague, or missing information. Counts and classifications need context before they become conclusions about process performance.

Presence and communication records can contain personal information. Select evidence for the stated operational purpose and apply the appropriate access. A process delay is not, by itself, a verdict on the person associated with a record. The P&C trust explanation develops that distinction.

From record to observation

Adapters bring selected operational records and integrated external information into a common evidence contract. The record retains information about its source, timing, subject, and the characteristic it informs.

The evaluation account includes normalization, filtering, classification, scoring, time-based weighting, and combination across relevant sources. These operations support a defined reading; their presence does not establish that every input is accurate or that every configured measure is valid. The owner needs to understand the selected definition, coverage, period, and interpretation.

The output is an observation that Process Analytics can use in readings and reports. The Orchestrator has a different job: it executes the defined process and routes its outcomes. An observation may inform a recommendation without itself authorizing a change.

Include existing systems deliberately

The organization may already hold part of the quotation context in an ERP, CRM, calendar, or another agreed source. Data Integration describes connectors, field mappings, schedules, and delivery records. Imported evidence needs its own source context just as a HEPO work record does.

Start with enough evidence to answer one useful question. The process owner and colleagues explain the work; implementers establish the relationships and extraction; the delivery partner supports review of the first readings. When the records do not answer the question, that is a reason to improve the evidence or interpretation before extending the claim.

Walk through the records behind one delayed decision with us.