Why no change is final without you
Where you approve things, what each approval protects you from, and the one case where software presses submit, and how to know you turned it on.
There are four places where we stop and wait for you. There is one case where we do not. This page explains which is which.
The four stops
- The change list. You see every rewording and every move next to the line it replaces, with a reason. We never apply a change just because we suggested it.
- Offered proof. Anything taken from an answer you typed somewhere else is offered with the date you wrote it, and waits for you.
- The last read-through. You see the resume exactly as it will be, before the file is made.
- The file itself. We make no PDF and no Word file until you ask for one.
What each stop protects you from
| Stop | What could go wrong without it |
|---|---|
| The change list | A sentence about your work that you did not write, which you only discover in an interview |
| Offered proof | A claim linked to an employer you did not name |
| The last read-through | A resume that hiring software reads worse than the one you started with |
| The file | A download you did not want, in a folder you forgot about |
The extension fills in forms. It does not send them
The toolbar button fills in the form in front of you and stops. It never submits, never replaces something you already typed, and never ticks a consent box. You read the form and press the employer's own button.
The one case where software presses submit
A sending run in the application queue does submit. That is what it is for, so it has strict limits:
- It needs an active Pro Max plan.
- The start button stays off until you tick the consent line for sending.
- Each job in the queue shows how it will be sent, and why, before anything opens.
- We wait twenty to forty-five seconds between jobs.
- Everything that is sent goes on your tracker with a date and a stage.
- If a job site does not allow automation, we mark it as refused and do not try. We never send anything on LinkedIn.
The same queue also has a filling mode. It prepares everything and stops, leaving each tab open for you. It is a different plan and needs a different consent. "We fill in two hundred forms for you" and "we send two hundred applications in your name" are two different promises.
Autofill vs auto-apply compares the two.
What is never automated
Any question about work permits, visa status, citizenship, security clearance, criminal record, disability, military service, ethnicity, gender or date of birth. These answers have legal weight, so you always answer them yourself, on every plan.
Consent tick boxes also stay yours, with one clear exception. The toolbar button never ticks one. A sending run does not either, by default: it stops at the box and tells you. The exception is the switch called “Tick that box for me from now on” on the auto-apply screen. If you turn it on, a sending run ticks the employer’s privacy, terms and GDPR boxes for you. Otherwise the employer would not accept the form, and it could not be sent for you. If you leave the switch off, the run stops at the box instead.
Questions about this
Is there any way a document gets sent that I never saw?
Only through a sending run in the application queue. That needs Pro Max and a consent tick before it starts, and every job it sends goes on your tracker.
Does the toolbar fill button ever submit?
No. It fills in the form and stops. You press the employer's own submit button.
What if I close the tab halfway through?
No changes were saved. Your main resume is unchanged and no application is recorded.
Can I undo a change after approving it?
Yes, before the file is made. Open the change list again, reject the change, and rebuild.
Know which of the two you are running
Filling in forms and sending applications are different buttons on different plans. If you are not sure which one will run, the queue screen tells you for each job before it starts.
Open Involve Resume