Getting started

How a checklist review works, from sign-in to the annotated document.

Already have an account? Sign in.

The review workflow

1 Sign in. Use single sign-on or your account credentials. Your interface language is a separate setting from the language reviewers write comments in; both live on your account page.
2 Create or open a workspace. A workspace isolates one checklist, its documents, and its review runs. Start empty or from a template.
3 Configure the checklist. Each criterion has an id, a pass/fail prompt, a severity, and whether it depends on a context document. Import or export the whole checklist as YAML.
4 Upload documents. Target documents are the ones being reviewed and annotated. Context documents (e.g. a call for proposals or a policy) are background the checklist is measured against.
5 Start the review. Pick the target document and an output language, then watch live progress per criterion.
6 Read the results. Every finding is pass, fail, or needs review, each with its reasoning and a verbatim quote from the source. Download the annotated Word document, the formatted report, and the machine-readable findings.

A vague criterion produces a vague finding. Say exactly what counts as a pass and what counts as a fail:

Vague	Precise
"Is the proposal well written?"	"Does the work plan give each work package at least two measurable milestones with a month? Fail if milestones are missing or vague."
"Check data protection."	"Does the proposal name concrete technical and organizational measures for GDPR compliance during model inference? Warn on mere statements of intent."

Every quoted finding is located character-for-character in the source document before it is shown: a finding whose quote cannot be found is flagged, not silently accepted.
Criteria are checked one at a time, which avoids models losing track of the middle of long documents.
This is a copilot, not an autopilot: it gives you a first pass with evidence attached. The decision stays with you.