Skip to content
ONE QUESTION, FROM SEARCH TO OUTPUT
Follow the fictional Harbour View Community Clinic case. AHU means air handling unit.
Try “delay” in the interactive illustration. Include controlled synonyms to reveal “late” and “slippage”, with each match explained.
Try the highlighted search →Invented extracts illustrate the search behaviour.In the recorded demonstration, an AHU search returns 12 records. Open the delivery note alongside the result; inspect the receipt email and its attachments.
Open the actual source-review screen ↗The baseline date is 13 July, actual receipt is 24 July and the June forecast is 27 July. Keep each date’s meaning and supporting source visible.
Follow the chronology →The programme-quality report identifies checks and exceptions for review. Combine relevant records and programme assessment to investigate the issue; these dates alone do not establish its effect on completion.
Explore the report example →THE END PRODUCT
Explore exact-word and synonym search highlights, then see how reviewed records support a traceable deliverable.
See why a record appears. Compare an exact-word search with controlled synonym expansion. The interactive example highlights matching wording and explains the reason for each result. Continue to the register, chronology and programme report to see how reviewed evidence supports the end product.
Explore search and sample outputsIllustrative layouts based on the demonstration, not unmodified software exports or issued expert opinions.
Working extract · Review decisions outstanding
You receive: matching passages with source context and review status.
Use it to: find different wording and understand why a result was returned.
Try the search highlights →Dates retain their meaning and source context
You receive: a dated account connecting the event to supporting records and programme context.
Use it to: distinguish planned, forecast and actual events before assessing their implications.
Read the chronology example →31 July revision · 43 activities
Scope, exceptions and limitations retained
You receive: programme-quality findings, exceptions and the questions requiring further review.
Use it to: prioritise investigation. Quality checks alone do not establish delay causation.
Read the assessment example →From working output to agreed handover.
Format, scope and professional review are agreed for your assignment.
WHAT YOU RECEIVE
Request a programme report sample ↗
Search results, source references, chronologies and programme findings support your review. Their status and outstanding checks matter.
Report formats: the build includes HTML, Word, Excel and PDF report routes. Available formats depend on the selected report and its prerequisites; confirm the output you need during your demonstration.
View the generated assessment screen ↗An agreed assignment may include a referenced evidence pack, chronology, programme review or independent opinion, with the scope, findings, limitations and review responsibilities explained.
Handover: agree the required documents, formats, supporting records and issue status before work begins.
The screenshot is from the fictional demonstration. The sample pack uses explanatory layouts. A software-generated working output becomes a professionally reviewed deliverable only through the agreed review and issue process.
A practical guide to evidence registers, event chronologies and programme references, with a fictional worked example.
Read the EOT records guide →