Check your document against a list of requirements
Upload the thesis regulation, the tender document, or the audit program. Each point comes back with where your document covers it and on which page, or with the fact that it doesn't and how many pages were searched.
It returns a table you can cite, review, and correct.
- Each point with its passage and its page
- Absence is claimed by stating how much was checked
- The report downloads as a file that opens in Word
The document with the requirements is read in your browser and is not saved.
A table with evidence, not an answer
Asking a model whether your thesis meets the regulation returns a paragraph you can't cite. Here each point is a row, and each row comes with the passage and its page.
| Requirement | Where it is covered | Completeness |
|---|---|---|
| 1. Must include a methodology chapter with a justification of the sampling design | p. 34 The design is purposive, not probabilistic… p. 36 Case selection followed the criterion of… |
4/5 · unconfirmed |
| 2. Must include an annex with the instruments used | Not found. All 214 pages of the document were searched and no passage was found. | — |
The claim of absence rests on two things: that the pass through the document was complete, and that the requirement came from a source that is cited. If any part of the pass fails, the table says so and stops asserting absence.
When the list already exists and has to be crossed
The program against the working papers
Point by point, with the passage that supports each one and the page where it is.
The clause checklist against the contract
What is missing before signing, and in which clause what does appear is.
The regulation against the draft
When there is no time left to read it all again.
The tender document against the bid
Before submitting it, so you aren't disqualified over a formal requirement.
What the score means
When a requirement turns up as covered, how complete it is gets evaluated on a fixed scale. The scale is written into the prompt; the model doesn't improvise it.
- 5 There is a dedicated passage that covers everything the requirement asks for.
- 4 It addresses it head on, but leaves out part of what it asks for.
- 3 It is covered in scattered pieces, with no passage that addresses it directly.
- 2 There are mentions that touch on the topic but don't address it.
- 1 Something was found, but it doesn't correspond to what the requirement asks for.
A requirement that doesn't appear gets no score: there is nothing to evaluate, and “it isn't there” is a different finding from “it is poorly covered”. Each score arrives with its rationale and as a proposal: until a person confirms it, the report prints it saying that nobody confirmed it.
No. It is read in your browser, split into points, and discarded. It isn't added to your projects, doesn't go to the cloud, and doesn't enter the analysis of the document you are reviewing.
You can type the list by hand, one requirement per line. If it has its own numbering —“art. 26”, “3.1.2”, “b)”— it is kept, so the table crosses against the original without translating numbering.
It can. It searches by meaning, not by keyword, so a requirement covered in very different vocabulary can slip past. That's why each point comes back with its evidence and not with a verdict: the table is for someone to review, not to replace them.
Up to 50 per run. If the list is longer, the first 50 are taken and you are told how many were left out.
Word (.docx) and PDF, just like the document being reviewed. You can also paste the text.
No. It uses AI, so it needs an account. A free account comes with 100 welcome hilos (a hilo is the unit HILO uses to measure AI usage); after that, a pack of hilos or Premium.
Before and after checking
Cross your first list
Open the document you want to verify, upload the regulation, and see point by point what is covered and what is missing.