What the checkers do
Three different checks run on three different documents. Which one is telling you about your history and which is telling you about our output.
Three checks run in this product and they read three different things. Confusing them is why people fix the wrong thing.
1. The gap scan, on the document you uploaded
Reads the CV you sent us and reports what a filter would find missing: a contact detail, a bullet with no result in it, a section a parser cannot place.
These are yours to fix, because they are facts about your history that no generator can write for you. This screen is where a missing phone number or an unquantified achievement gets caught.
2. ATS compliance, on the document we generated
Reads the file we are about to hand you, in the order a parser meets it.
| Check | What it is about |
|---|---|
| Name | A parser takes the first strong line as the name |
| Every applicant tracking system keys its record on it. No email, no record | |
| Reachable | A phone number or a link, so a match can be acted on |
| Columns | A sidebar is a second column, and in Word a table cell. Cells are extracted before the cell beside them, so a skills column can land in the middle of a job title |
| Headings | A parser matches headings against a vocabulary. One it does not know files everything under it as nothing |
| Role dates | An undated role cannot be placed on a timeline, so the system reads a gap where the job was |
| Employer | The employer is its own field in every system |
| Bullets | A role with a title and nothing under it reads as filler |
| Recoverable text | No block may carry text that flattening drops |
| Control characters | Tabs, control characters and the bullet glyph inside the text itself all survive into the extracted string and break a keyword match |
Most findings here are about a choice the generator made rather than about your history, which is why they are fixable by switching a design or a country format rather than by editing your career.
The one honest exception is a role with no employer on it. That is a fact only you have.
3. Weak bullets
Reads individual lines and finds the ones that state an activity and no result. This is where a bullet gets a number in it, typed by you, in your own words.
There is a reference screen of examples for your field, linked from that page, when you are stuck on the wording.
Where each one lives
| Check | Screen |
|---|---|
| Gap scan | ATS compliance, under Applying |
| Generated document | The last read-through, before the file exists |
| Weak bullets | Fix weak bullets, under Your resume |
The order worth running them in
- Check the parse, so everything downstream is reading your real history.
- Fix weak bullets once, at the source, because it helps every application.
- Tailor for the posting.
- Read the compliance findings on the generated document.
- The last read-through, then download.
All three live in the app, under the headings named above. What the two scores in front of them mean is in Fit vs CV readiness.
Questions about this
Why does the same document pass one check and fail another?
Because they read different things. One reads the file you uploaded, one reads the file we generated, and one reads individual bullets.
What is a blocker versus a warning?
A blocker is something that loses content or loses the record, like a missing email or text a parser would drop. A warning is something that reads worse rather than something that breaks.
A finding says the two-column layout is a problem, but I chose that design.
Then the finding is about a choice we offered you. Switch the design, or accept it knowingly on a market where it is normal.
Do I need to pass everything before applying?
Fix the blockers. The warnings are judgement, and a document that reads well to a person is worth more than a perfect score against a checklist.
Fix blockers, read warnings
The blockers are the ones that lose you the record entirely. Everything else is a conversation about the document.
Open Involve Resume