GoKati / practical workflow tool

Job Search Pipeline Starter Pack

A simple way to run applications, CV versions, recruiter conversations and follow-ups like a pipeline instead of a pile of browser tabs.

The point: every serious application needs a stage, the exact document submitted, a next action and a date when that action becomes due.

1. Build The Tracker

Start with one CSV, spreadsheet or table. Do not overbuild it. Your first version needs these columns:

Column	Why it matters
Company	You need one source of truth for every live role.
Role Title	Different roles at the same company may need different positioning.
Source / Channel	LinkedIn, company site, recruiter, referral or inbound.
Date Applied	Starts the follow-up clock.
CV Version Used	Stops you guessing what the recruiter saw.
Stage	Turns a list into a pipeline.
Next Action	Names the next move.
Next Action Date	Makes the next move visible before it goes stale.
Contact	Recruiter, hiring manager or referral contact.
Notes	Keep only useful context. Do not store sensitive material casually.

2. Use Simple Stages

Use stages that describe what is actually happening:

CV Ready
Applied
Recruiter Screen
Hiring Manager Interview
Panel / Final Interview
Offer
Rejected
Withdrawn

3. Run One Application Through The System

Paste the job description into a working file.
Ask AI to extract role requirements, proof points and likely objections.
Draft or tune the CV against confirmed facts only.
Save the exact CV version name in the tracker.
Apply or send the outreach.
Set the next action and due date before closing the tab.

4. Five Prompts

JD Extraction

Read this job description and extract:
1. must-have requirements
2. useful-but-not-required requirements
3. likely hiring-manager priorities
4. proof points I should show
5. possible gaps or risks

Separate confirmed facts from inference.

CV Matching

Compare this role to my CV. Suggest only truthful changes that improve fit.

Return:
- strongest matching evidence
- missing evidence
- wording to tighten
- anything I should not claim

Follow-Up Draft

Draft a short follow-up message in this style:
observation -> insight -> question.

Use the role context below. Do not sound like a mass template.

Interview Prep

Act as the hiring manager for this role. Ask me five interview questions, one at a time.

After each answer, score:
- specificity
- commercial relevance
- proof
- risk or gap

Stale Application Review

Review these applications and identify:
- follow-ups due
- roles to withdraw
- roles needing a better contact
- roles worth deeper account research
- stale rows that should be archived

5. Keep The Boundary Clean

AI can reduce admin drag. You still own role selection, facts, relationships, interviews and the final career decision.

Included file: use Job-Search-Pipeline-Template.csv as the clean starter tracker.