Press · Demo walkthrough
A read-along guide to QueryTek Review for editors and analysts. It takes about 15 minutes and needs no account.
Fictional example: Clockfold Technologies and the people named here are invented. The documents and findings are illustrative and do not come from a QueryTek client.
Each step names the person, their role, and what they see on screen. Every step is shown, not hands-on: we don’t issue demo logins. The finished scorecard is published as a fictional showcase you can open at any point.
Clockfold Technologies is refreshing its employee handbook for the new benefits year. Corporate communications wants a human check for regulatory and plain-language risk before it goes to every employee.
Step 1 · Shown, not hands-on
Bailey Robbins · Client user
Bailey signs in to the client portal, opens Documents, and uploads the handbook draft. She picks the Content Risk module and describes the audience: all employees.
What you would see: The document appears in the Documents list with status Quoted and a per-word price. A quote notification arrives by email.
Step 2 · Shown, not hands-on
Gabriella Baird · Client admin
Gabriella, who manages billing for the team, reviews the quote and completes checkout.
What you would see: The status changes from Quoted to Paid. Review work starts only after payment.
Step 3 · Shown, not hands-on
Oliver Winslow · Review lead
Oliver opens the review queue, where paid documents wait for assignment, and assigns the handbook to Daniel, a reviewer qualified for Content Risk. Iris Wright could take it instead.
What you would see: The document leaves the queue and appears on Daniel’s assignments. The client sees the status In review.
Step 4 · Shown, not hands-on
Daniel Dunwoody · Reviewer
Daniel reads the full handbook in the review workspace. For each problem passage he records a finding with a severity and a note, then scores the Content Risk dimensions: risk, bias, audience, context, and accessibility. He submits the scorecard for lead review.
What you would see: A scorecard with five dimension scores and findings tied to quoted passages, marked as submitted for lead review.
Step 5 · Shown, not hands-on
Oliver Winslow · Review lead
Oliver checks Daniel’s findings and scores and approves the scorecard for delivery.
What you would see: The document status becomes Completed and the client is notified.
Step 6 · Shown, not hands-on
Bailey Robbins · Client user
Bailey opens the completed document and reads the Communication Risk Scorecard, then downloads it to share with HR and legal.
What you would see: The same scorecard published in the handbook showcase: overall score, dimension scores, and each finding with its note.
Clockfold Technologies product marketing drafted customer release notes with an internal language model. The risk team wants a person to check the claims and tone before publication.
Step 1 · Shown, not hands-on
Bailey Robbins · Client user
Bailey uploads the model-drafted release notes and picks the AI Output module.
What you would see: The document appears with a per-word quote.
Step 2 · Shown, not hands-on
Oliver Winslow · Review lead
After payment, Oliver assigns the document to Daniel.
What you would see: The document moves to In review.
Step 3 · Shown, not hands-on
Daniel Dunwoody · Reviewer
Daniel compares each claim with the source changelog, flags unsupported claims and generic filler, and scores the AI Output dimensions.
What you would see: An AI Output Evaluation Report with a critical finding on an absolute security claim.
Step 4 · Shown, not hands-on
Oliver Winslow · Review lead
Oliver approves the report, and Bailey reads it in the portal.
What you would see: The same report published in the release notes showcase.
Open the finished deliverables, try the API in the developer sandbox, or ask us for a live screenshare of the reviewer and review lead views.
