Run a Quality Check
Start a check on the draft in front of you, and know what it reads, what it looks for, and what the click costs.
You have written something and you want to know whether it is worth sending. A Quality Check is the fast answer: one run reads the text of your draft and tells you where it is likely to lose the reader, which lines are working, and what it found nothing wrong with. It reads your words and nothing else, with no persona involved.
Where it lives
Open a document. The rail down the right of the editor has two segments at its top, Quality Check and Simulation, and it opens on Quality Check. Before any run it is headed Is this ready to send?, with the line One run checks the text in Current across every factor. underneath.
What the check runs
Under WHAT THE CHECK RUNS is the list of factors this document will be read against.
| Factor | What it asks |
|---|---|
| Hook Check | Does the opener earn a skim past line 3? |
| Spam Reflex | What makes this feel templated or sales-shaped? |
| CTA Pressure | Is the ask earned, clear, and cheap enough? |
| Value Clarity | What does the reader get even if they never reply? |
| Sequence Coherence | Does every step add something new? |
| Reading Flow | Where does the argument stall, jump, or repeat? |
Not every factor applies to every kind of document, and the list you see is exactly the set that will run. A sequence adds Sequence Coherence, because it has more than one step to hold together. A post is not read for CTA Pressure. An article is read for Hook Check, Reading Flow and Value Clarity.
Expand any row to see Looks for patterns like and examples of what that factor hunts for. Expanding is only reading: rows run nothing on their own, and there is no way to run a single factor.
Starting a run
Write something. Run stays dimmed on an empty draft and says why: Write something first — there is nothing to check yet. That is the only reason the button refuses a click.
Look at the line under the button. It says either Included in your plan, which means the click is free, or a figure and the word credits, which means your included checks are spent and this run will cost 2 credits.
Press Run. If a check already exists for this document the button reads Re-run instead. Your draft is saved and frozen before the read starts, so what gets checked is exactly what was on screen when you pressed.
Wait, or go and do something else. The rail shows Preparing your diagnostic map while the job starts. If it has to queue, a QUALITY CHECK · QUEUED chip appears with Safe to leave — this job continues in the background. Once the read opens the heading becomes Building your diagnostic map, a timer runs, and findings land one at a time: Findings appear as the check moves through the text.
A run freezes a version, so every check you run also adds a snapshot to the document's history. The findings stay attached to that snapshot and can be reopened from it later. Typing after you press does not change the run that is under way.
What a check costs
Included checks belong to your organisation rather than to you personally, and they are counted against two windows at once: a rolling five-hour window and the UTC calendar month. Whichever you exhaust first, the next check starts costing credits. Hover the credit figure and the tooltip completes Included checks reset with the date and time, in UTC, when free checks come back.
A run that fails costs nothing, and the failure panel says so: A failed job is not charged.
When a run will not start
If something blocks the check you get a panel headed Couldn’t start the check with the specific reason and a working Run or Re-run button. The same reason also appears as a toast. Common ones are You’ve reached your check limit for now. Try again later., You need more credits to run this check., This document is too large or malformed to check. Trim it and try again. and This document changed since you started. Reload it, then run the check again.
When that panel says No job was created. nothing started and nothing was spent. A different title, Couldn’t confirm the check started, means the app could not tell either way. Pressing Re-run on the same saved text reconciles with the job that may already exist instead of starting a second one, so you are not charged twice.
If a check fails after it started you get Quality Check didn’t finish with No result was saved. Your text and the previous snapshot are unchanged. If a start fails while an older verdict is still on screen, that verdict stays put and the failure appears as a strip below it.
Where to go next
Version history
Look back through the frozen copies of a draft that unpitch saved for you, and bring an earlier wording back into the document you are editing.
Reading the verdict
Work down the result panel from the headline to the findings, and move between a finding and the words in your draft it points at.