Why nothing finalises without you
Where the approval points are, what each one is protecting, and the one route where a machine presses submit and how to know you turned it on.
There are four places the product stops and waits for you, and one route where it does not. Knowing which is which is the whole of this page.
The four stops
- The change list. Every rewording and reordering is shown next to the line it replaces, with a reason. Nothing is applied because it was suggested.
- Offered evidence. Anything drawn from an answer you typed elsewhere is proposed with the date you wrote it, and waits.
- The last read-through. The document as it will exist, before it exists.
- The file itself. No PDF and no Word file is written until you ask for one.
What each stop is protecting
| Stop | The failure it prevents |
|---|---|
| The change list | A sentence about your work that you did not write, discovered in an interview |
| Offered evidence | A claim attributed to an employer you did not name |
| The last read-through | A document that reads worse to a parser than the one you started with |
| The file | A download you did not want, in a folder you forgot about |
The extension is a fill, not a send
The toolbar button fills the form in front of you and stops. It never submits, never overwrites a field you already filled, and never ticks a consent box. You read the form and press the employer's own button.
The one route where a machine presses submit
A queued sending run does submit, and that is the point of it. It is fenced accordingly:
- It needs an active Pro Max plan.
- The start button is disabled until you tick the consent line for the sending mode.
- Each job in the queue shows its route and reason before anything opens.
- Jobs are worked twenty to forty-five seconds apart.
- Everything that goes out lands on the tracker with a date and a stage.
- A board that refuses automation is reported as refused rather than attempted, and LinkedIn is never sent to at all.
The filling mode of the same queue prepares everything and stops, leaving each tab open for you. It is a different plan grant and a different consent, because "we will fill two hundred forms for you" and "we will send two hundred applications in your name" are two different promises.
Autofill vs auto-apply sets the two side by side.
What is never automated
Consent tick boxes, and every question about work authorisation, visa status, citizenship, clearance, criminal record, disability, veteran status, ethnicity, gender or date of birth. Those are answers with legal weight and they stay yours, in every route, on every plan.
Questions about this
Is there any way a document gets sent that I never saw?
Only through a queued sending run, which needs Pro Max and a consent tick before it will start, and every job in it lands on the tracker.
Does the toolbar fill button ever submit?
No. It fills and stops. The employer's own submit button is yours to press.
What if I close the tab halfway through?
Nothing was written. The base CV is untouched and no application is recorded.
Can I undo a change after approving it?
Yes, before the file exists. Reopen the change list, reject it, and rebuild.
Know which of the two you are running
Filling and sending are different buttons with different plans behind them. If you are not sure which one is about to run, the queue screen says so per job before it starts.
Open Involve Resume