Job search pipeline For people changing or looking for a job who want a pipeline they can leave and come back to. Steps 14
Checklist items 74
Language English
What it is for
Run a job search over weeks: a CV built from real achievements, applications you approve one by one, follow-ups, interviews, an offer decision and a weekly review.
For people changing or looking for a job who want a pipeline they can leave and come back to.
Steps and what they prove 14
Goals and constraints The GOALS note exists and holds the one-sentence target (title, level or "not decided", place, floor) plus deal-breakers sorted into must have and would prefer. The floor figure is written with currency, gross or net, period and its source, or is marked "personal, not checked against the market". The deadline is written as a number of weeks and a date, and `maxWeeks` equals that number (or the 8-week default, stated as a default). `maxPerWeek` is set (default 5) with the hours per week it was based on, and `week` is 1 and `interviewsOpen` is 0. The person's own words confirming the GOALS note are quoted in the run. Base CV and achievements bank The ACHIEVEMENT notes hold at least 5 rows, each with what, action, result with a number (or "no number known"), evidence and year, numbered A1 upward. A table with the named columns ID, What and action, Result with a number, Evidence, Year was shown to the person and each row was confirmed as true. Each bullet of the base CV is mapped to a row ID or to a confirmed fact about employer, title, date or education; none uses a number outside the bank. Every gap in the work history has a one-line reason from the person, and every requirement not covered is listed as "not in the bank". The person's wording approving the base CV text is quoted with the date, and nothing was sent anywhere. Profile and story The profile texts (two headline options, About, 60-second story of about 150 words) are written and pasted in the run for the person to publish themselves. Every number in the About text and the story is listed with its ACHIEVEMENT row ID; any claim without a row is removed or marked "not in the bank". A consistency table with the columns Item, In the CV, In the profile or story, Match covers current title, employers, dates and numbers, and has no "no". The person said the story aloud once and named the sentences they stumbled on, which were revised. The person confirms in their own words that they will publish the texts themselves, or says why the profile stays unchanged. Targets, sources and people to ask At least 10 TARGET notes exist, each with a name or company, a reason, a source and a date, saved in the form TARGET T<n> | name | why | source | date. For each posting in the first batch, the pasted text with its read date and pay line ("stated in posting", "not stated" or "unconfirmed") is quoted or attached. The channel note lists the sources the person will check each week and who checks them. Each referral message is drafted with the contact's name and marked "not sent" until the person confirms the send date. `applicationsLeft` is set to the number of pasted postings chosen (0 to `maxPerWeek`, 0 when nothing was pasted) and the number is shown with its calculation. Pick the next application Variables read and stated in one line: week, maxWeeks, applicationsLeft and maxPerWeek, with applicationsLeft not above maxPerWeek (or corrected and explained). listNotes APPLICATION and TARGET read; the chosen company and role are not already in an APPLICATION note (duplicate check stated). Posting text pasted by the person with its link and the date it was read (all three present), or the step stays open. No APPLICATION note with approved documents and status "not sent" is left waiting for a sent date from an earlier pass (notes closed as skipped, withdrawn or abandoned are fine). If applicationsLeft is 0 or lower: status counts (not sent, sent, reply, interview, rejected, silent, offer) given from the notes before "applications done for now". Read the posting and decide the fit Posting pasted in full by the person with its link and the date read; a snippet-only paste is marked "unconfirmed" and the decision waits. Match table written with one row per requirement: type, A number or "not in the bank", gap; every must-have has a row. Pay stated as one of four cases (range, single figure, none, unconfirmed) with its source and date, compared with the step 1 pay floor. Decision sentence written: apply or skip, with a reason that names the count of must-haves covered and any deal-breaker. APPLICATION P<n> note written with status "not sent" and the link with date read; on a skip the reason is in the note and applicationsLeft is lowered by one. Tailor the CV and the letter listNotes ACHIEVEMENT read; every new or changed CV line has an A number written beside it in the chat, or is a heading or a contact line. Version names written: "CV for P<n> v1" (and "Letter for P<n> v1" if a letter is used) with the date, and the base CV left unchanged. Gap list table with columns Requirement, Status (covered A<n> / partial / not in the bank) and What the documents say, one row per must-have from step 6. Full text of the CV and letter shown to the person, with their statement that each sentence is true or the list of sentences they corrected. Layout checked and stated: single column, standard headings, no photo, no tables or graphic skill bars, no contact data in header or footer. Approve the exact documents Full text of the CV (with version name) and of the letter (with version name) shown in the chat on the day of approval, not a summary. Checklist table filled with a result in each of its seven rows; "not verified" or "not pasted" written where the file or form was not seen. Every number in the documents compared with its ACHIEVEMENT note, and the company name and role compared with the pasted posting, stated in one line each. Person's approval sentence quoted, naming the CV version and the letter version; the APPLICATION note holds both version names and the approval date with status "not sent". For "changes needed": the list of fixes written; for "do not apply": the reason in the APPLICATION note and applicationsLeft lowered by one. Record what was sent APPLICATION note for this posting is written with all seven fields; the sent date is a calendar date confirmed by the person, or the status is "not sent" with date "not confirmed". Follow-up date written as a calendar date with the rule used (cold, referred, posting instruction or default), or "not set" when nothing was sent. Close-as-no-reply date written, and the CV file name and version plus letter yes/no are in the note. Source tag written (cold, referred, recruiter or from-target-list) so the weekly review can compare groups. applicationsLeft lowered by one and the new number told to the person before advancing. Replies and follow-ups Table of open applications shown with today's date, columns P number, company, role, status, sent date, follow-up due, days since sent, and corrected by the person. Every pasted reply is classified with a named class and a newer APPLICATION line (date received, new status); automatic receipts are not counted as replies. Each overdue follow-up has a draft and an attempt number (first or second); sent dates are recorded only after the person confirms them. Silent and rejected applications are marked with dates; each rejection has a reason or "no reason given". Counts told to the person (open, replied, interview, rejected, silent, offer) and interviewsOpen compared with the notes before advancing. Prepare and debrief an interview Interview details recorded (application P number, round, date, format, interviewers) with every unconfirmed item marked, and the newer APPLICATION line saved. Story map table with columns quality, bank story, result with number, gap; every quality has an ACHIEVEMENT number or the words "not in the bank". At least 4 STAR stories written, each with a result number copied from its bank entry, and one mock-interview answer with one feedback line. Research sheet from pasted material only, with an "unconfirmed" list, and 4 to 5 questions for the interviewer. After the interview: INTERVIEW note saved with questions asked, stories used, timing said, and the thank-you date the person confirmed (or "not sent"). interviewsOpen changed (lowered at debrief, raised for a confirmed next round) and the route named before advancing. Offer and decision Pasted offer text with its arrival date and reply deadline is recorded; calls are marked "said on a call" Terms table filled: base, bonus, contract type, probation, notice, working time, place, start date, non-compete, each with a confirmed-in-writing yes or no Comparison table has one row for every floor item and deal-breaker from step 1, each with a result (meets, below, broken, unconfirmed) Market figures for any counter are pasted with source and date, or the person states there is no counter A list of questions for the employer about every unconfirmed or unclear term is written An APPLICATION note with status offer and an OFFER note exist, and the person has stated the decision Weekly review and feedback A table of funnel counts (read, sent, replies, interviews, offers) is filled from the APPLICATION notes, with the week and the total Every application past its closing date has a new APPLICATION note with status silent, or a stated reason it stays open Rejections are listed with the reason given or "none given" and the stage; no reason is invented Own ratios are computed and compared with the indicative benchmarks, each labelled with whose data it is, or the sample (under about 10 sent) is named too small A WEEK n REVIEW note exists with counts and exactly one main decision Unless the search stops, week was raised by one; for "keep going", applicationsLeft set to a number not above maxPerWeek, both stated back to the person Search summary The outcome is written in the person's own words with a date, and marked "not confirmed" if no written confirmation was pasted The final pipeline table shows a count per status taken from the latest APPLICATION note of each application, with the P numbers Each application still open has a stated status (silent, abandoned or live) or a message the person will send to withdraw A list of people to thank is written, each with what they did and a draft message Up to three lessons are listed, each with a count from the notes and a sample-size remark A SUMMARY note exists and the person confirmed its text The assistant closes a checklist item only with evidence of what it did, so a finished run shows the work was done, not only claimed.
Use it
Create a free account, connect your assistant and run this workflow in a chat. You come back to this page after signing up.
Use this template
Not sure yet? Watch a demo run first, no account needed.
Already have an account? Sign in