See the proposed application
From source information to a reviewed next step
A useful application helps a person inspect the evidence and decide what happens next. Explore this fictional example of Knowledge and Process Intelligence supporting the same task.
Illustrative prototype
A project-start review you can inspect
All information is fictional. Choose a scenario to see prepared source material, a review output, a human decision and the checks for a first build. No live analysis or customer systems are connected.
The project record is incomplete and an old note disagrees with the current procedure.
1 · Agreed information
Inspect the source material
Approved delivery procedure
Version 3 · Section 2 · Current approved guidance
Before project work starts, the approved scope, budget confirmation and a named project lead must be recorded. The delivery owner reviews these checks before authorising the start.
2 · Proposed output
What needs checking before work starts?
Fictional Harbour onboarding project- The project record confirms scope and budget, but has no named project lead. [2]
- The approved procedure requires a named lead and a delivery-owner review. [1]
- The earlier handover note disagrees with that requirement. Its wording should not be silently combined with the current procedure. [1][3]
Review required
Hold for review: confirm the approved guidance and assign the project lead before authorising work.
3 · Human review
Choose the next step with the evidence in view
A person checks the sources and remains responsible for the decision. Try the prepared review action below.
No review decision selected yet.
This changes this screen only. Nothing is saved, sent or authorised, and no project system is updated.
4 · Acceptance checks
What to look for in this scenario
- Each finding points to an inspectable source and version.
- The conflicting note remains visible for the reviewer.
- The missing project lead is flagged.
- Reviewing the guidance does not automatically authorise the project.
These are prepared examples of expected behaviour. A client build needs an agreed evaluation set, source/access testing and sign-off from its business reviewer.
Start with your task
What would a useful first review look like for your team?
A scoped discovery defines your approved information, users, sample output and acceptance checks before a build is agreed.