Time attached to decisions, not timesheets
Effort and Time Intelligence records how long real project decisions take by observing workflow events already produced by the work: document intake, comparison, review, correction and approval. It replaces recalled timesheet estimates with evidence tied to a specific decision.
At a glance
What each figure meansDerived from work, not manual entry
Effort binds to an episode, not a week
Design target for the procurement pilot
Illustrative model until pilot data exists
Product tour
The view below is an illustrative layout, not customer data. Real dashboards are generated from a customer’s own declared workflow fields.
A weekly timesheet records that eight hours went to procurement. It cannot show that six of them went to reconciling one vendor deviation against an outdated specification revision.
Document intake, comparison runs, review requests, corrections and approvals are already discrete events. Reading them in order reconstructs effort without asking anyone to log it.
When elapsed time is bound to a specific evaluation, the delay can be traced to a missing document, an unavailable approver or an ambiguous requirement.
Operating matrix
The matrix separates source evidence, intelligence work, governing authority and the resulting artifact.
| Subject | Input | Intelligence operation | Human / policy control | Output |
|---|---|---|---|---|
| Working time | Active workflow events | Sequence and total | Aggregate reporting | Effort per decision |
| Waiting time | Gaps between events | Classify blocking reason | Human confirmation | Delay cause |
| Rework effort | Correction cycles | Count and total | Manager review | Avoidable-cost evidence |
| Cycle time | Intake to approval | Compare across episodes | Explained by owner | Planning benchmark |
Controlled sequence
Each transfer preserves context, ownership and the human gate required before consequential action.
Design boundary
Credibility begins where automation stops and accountable professional judgment starts.
The purpose is to explain decision cycle time, not to score attendance or activity.
Effort evidence may inform commercial discussion, but the platform is not an invoicing tool.
Cycle-time figures become real only after the first instrumented pilot.
Questions answered
Open a question to inspect the operating position, not a marketing promise.
No. Effort is reconstructed from workflow events the work already produces, which is why it can be attached to a specific decision.
Most procurement delay is waiting: for a document, a clarification or an approver. Separating them shows whether the fix is capacity or process.
Get started
Bring a workflow your team already repeats. We define the evidence, the approver and the outcome to measure, then instrument it end to end.
We are working with a small number of design partners across engineering and procurement workflows.