The job search field kit. Set your profile once. Then work jobs, not forms. None of it leaves your browser.
This replaces the setup questions that used to sit inside the Scout builder. Fill it once and it drives the scout brief, the decision gates, the message drafts, and the interview prep. Change it whenever the search changes.
The one in use fills in this profile, it is what the Apply station checks each posting against, and the Board reports which version is getting replies. Every version you have sent is kept, behind View all. PDF is fine. No resume is uploaded and no file leaves your browser. Print a clean copy rebuilds the one in use into the structure a scanner reads, without changing a word.
The scout speaks as you. These lines are what it reasons from.
Numbers, scale, named programs, and outcomes beat adjectives. These become the opening line of your outreach messages.
Titles and geography drive every search that runs.
Number one is the job you want most. The scout leads with the top of this list. Start typing and take a suggestion, or type your own title and add it. Anything you type is kept. Several at once is fine: separate them with commas, or paste a list.
Nothing here yet. Every search that runs starts from this list, so add at least three.
Check this list before your next scout run. It was read from the titles you had typed before, and more than one title was found on a single line. Those were titles no search ever ran on.
Most wanted first. Start typing and take a suggestion, or type your own industry and add it. Anything you type is kept. Several at once is fine: separate them with commas, or paste a list.
Add common ones
Nothing here yet. Industry decides which employers the scout even looks at, so name at least two.
Check this list before your next scout run. It was read from the industries you had typed before, and more than one was found on a single line.
Name them. Without a list the scout invents a commute radius.
The county list says which areas count. This says how far inside them you will actually drive. Give both and the scout uses both. Leave these blank and it uses the county list alone, which is how it worked before.
Numbers, not sentences. The floor is a hard gate and nothing below it is ever surfaced. The range and the minimum are scoring inputs.
Check these before your next scout run. They were read from the salary text you had typed before. Nothing here reaches a scout run until you confirm it.
One line. This becomes your level gate. Example: Senior Manager equivalent scope or above.
Anything listed here never reaches your shortlist again.
One per line, with a short reason.
Employer career pages beat job boards. Fresher postings, and no staffing firm in the middle.
Organizations you would actually work for, by name. The scout opens three of these before it touches a board. Government and institutional pages belong here too, and they carry senior seats the boards never show.
Not sure who belongs here?
The app sends nothing anywhere. Copy the prompt, paste it into ChatGPT or Claude, then paste the answer back below. Your resume text is built into the prompt so the answer fits your actual background, which means you are handing it to that tool yourself, on purpose.
The first six are Priority 1 and get searched on every run. Everything below the sixth line is Priority 2 and is only reached once those are done. Reorder by retyping the list. Put sites that serve a plain page to an assistant at the top. Indeed, LinkedIn, Glassdoor and ZipRecruiter block automated readers hard, so a run that spends its Priority 1 slots on those four opens nothing and comes back empty. They still belong on the list, lower down, where a block costs nothing.
Add common ones
Defaults are ready to use. Adjust the weights only if you know why.
The Board in this app is your tracker. Change this only if you keep your history somewhere else.
Pick who runs it. Everything below changes to match.
Copy the prompt.
Open a new chat, paste it, and send. The search starts on that message.
Copy the whole report it writes you and paste it into Decide. Every role lands on your board at once, with the facts and the requirement lines already filled in. You retype nothing.
This is what stops the same role coming back every week. It is pulled from your Board and written into the prompt, so there is no separate file to export and no tracker to upload.
Updates live as you type.
Nothing open yet.
The summary board covers every role on your Board at once, sorted by Worth.
Paste the full text of the job posting. The tool pulls the lines that read like requirements and ignores the boilerplate. If Decide already carries requirement lines for this role, they are here waiting.
Your resumes live in your profile so you add each one once. Tag this role with the version you are sending, and the Board reports which version is getting replies.
Every line from the posting, marked Required or Preferred, with the coverage the tool computed from your text. Override any call you disagree with.
Auto leaves the call to the tool. Covered, Partial, and Absent are yours.
No lines yet. Paste a posting above and pull the requirement lines.
These are the layout choices that break scanners. Answer them about the file you are about to send, not about the text you pasted.
Every fault in this part is layout, not writing. Print a clean copy, on the card at the top of this station, fixes all of them in one press without changing a word, and hands you a PDF to send.
This app cannot rewrite your resume. There is no model in it and it never sends your text anywhere. What it can do is build the entire request for you, so an assistant gets the posting, the requirement lines, the coverage call on each one, the document flags, and your full resume in a single paste.
Use ChatGPT, the same place the free scout runs. The packet works in any assistant, but what comes back varies, and some will not run it at all. That is why the packet ends with a self check the assistant has to run on its own draft before it answers you. Read what comes back against your own resume either way.
Read this before you paste. This is the one step where your text leaves this device, and it leaves only because you paste it. Every other part of Postcheck stays in your browser. The packet carries your whole resume, so use an assistant you would trust with the file itself.
The packet asks for the whole revised resume, not a pile of loose bullets, so what comes back is ready to paste into your profile as a new version. It also asks for a log of every line that changed, because a full document hides its own edits and things go missing quietly. Read the log first.
A rewrite closes a partial, because a partial is their wording for something you already did. It cannot close an absent line. Absent means the work is not in your history, and the packet forbids inventing it. Running the same request a second time returns the same answer, and a third returns it again.
The station stops asking for a packet once a revised resume has come back and a required line is still absent. That is not the tool giving up. It is the tool refusing to send you around the same circle a third time.
The scout has nothing to do with this. It finds roles and it never reads your resume, so a rewrite is no reason to run it again.
Nothing open yet.
The fix list is the block to keep. The term gap shows their phrasing against yours. The rewrite packet is the whole request for an assistant, posting lines and resume included, written to forbid any claim you cannot back. Part 5 on the left copies it in one press.
Find the name yourself. These open the usual places in a new tab.
One line, and it has to be real. This is the sentence that separates your note from a template, and its absence is why most cold notes die.
Thirteen templates. Each one is a different door, and they are not interchangeable.
Pick a template above.
This is the part that makes the Board work. Log the send and both follow up dates get set for you. Four business days, then seven days after that, then stop.
Rate a required line Strong in the Decide station and its proof appears here.
Proof points come straight from the evidence map you built in Decide. If nothing shows here, the message has nothing concrete to carry, and that is worth fixing before you send it.
The stage and the lane decide which questions you get. Change either one and the set rebuilds. Title and organization come from the role you selected above.
One card per question, the posting's own required lines first, then the generic set for this stage and lane. The number field is the point of the whole exercise. Volume, budget, headcount, percentage, count of findings, days to stand up. A card with no number is a story, and a story loses to the candidate who brought arithmetic.
Grouped by what the answer actually reveals. Pick four or five. The ones you choose tell them as much as your answers did.
0 selected.
One per line. These print with the rest.
Check these during or right after the conversation, not before. Three or more and you are looking at a seat that will not hold.
Fill this within an hour of walking out, while you still remember what they actually said. It saves to the role and prints with the rest.
A number is not an offer. Nine things are. Rate each one from what you actually know, and leave anything unknown at the middle mark rather than guessing high.
Quote the terms. Start date, reporting line, review cycle, anything conditional.
Write it before you negotiate, not during. A number and a condition.
Nothing open yet.
Print the prep sheet the night before. Fill the debrief the same day.
Selecting a whole posting by hand is the slow way to do this. The clipper is one bookmark that reads a posting and copies it in a single press, and it makes no network call of any kind.