tm.hub
Discuss a task

PRODUCT / LIVE

Requirements check

Checks technical assignments and functional requirements for completeness, omissions, and contradictions.

Check a document ↗ View a sample report ↗
RU interface
LIVE
  • DOCX / PDF / XLSX
  • Findings with references
  • Reproducible result

01

What it solves

  • Breaks down requirements
  • Identifies omissions and contradictions
  • Links each finding to its source requirement

02

How it works

  • You upload a document
  • Rules are used to break down the requirements
  • The result is linked back to its source

03

What the client receives

  • A structured list of requirements
  • A list of findings and checks
  • A source clause for every finding

04

Review workflow

  1. 1Document
  2. 2Requirements breakdown
  3. 3Findings
  4. 4Source

REAL CASE

Requirements check for a data centre

54lines / requirements reviewed
17findings
6critical
0LLM calls
FoundSection 7 is missing from the list of sectionsSource: list of sections
FindingSubsection 6 is missing from Section 5Source: Section 5
Needs reviewThe assignment does not define the completion datesSource: general requirements
0 LLMDeterministic review without calling a language model

RULES AND MODELS

Why we avoid neural models where precision matters

Requirements are checked using rules, not a model. The same file will produce the same result tomorrow.

Every finding is linked to a document clause, so the result can be reviewed and shown to a contractor.

Models are used only where necessary, such as recognising a scan without a text layer or matching different names.

05

Who it is for

Teams working with technical assignments, functional requirements, and project documentation.

06

Pricing and terms

One tariff covers the catalogue modules. Trial access includes 10 checks for 14 days, free and without a card.

All tariffs ↗RU interface

Requirements check

Checks technical assignments and functional requirements for completeness, omissions, and contradictions.

Check a document ↗