How to Run a Job Search With a Simple Application Tracker
A guide to Define What You Are Looking For, Build the Tracker Before You Apply, Apply in Small, Repeatable Batches, Keep Momentum Between Replies, Review, Adjust and Close the Search
A job search becomes stressful when it lives only in your head and in six different inboxes. You forget which version of a document you sent, whether a role has already closed, or when to follow up. A tracker does not need to be elaborate: one table, a few consistent fields and a short weekly review remove most of that uncertainty. It also makes the search measurable in a useful way - not by counting rejections, but by seeing which step is actually slowing you down. The 32 steps below start with a written definition of the role you want, build the tracker before the first application, then cover applying, following up and knowing when to stop. If you only do one thing today, do step 7. Browse all illustrated guides or the Work World category for more illustrated walkthroughs on Howcompass.
How do you run a Job Search With a Simple Application Tracker?
Define What You Are Looking For
Name two or three job titles you will search for
Name two or three job titles you will search for. Titles are how listings are found. Pick the ones that describe work you can actually do, and write them as the employer would spell them. For the primary source behind this phase, see LinkedIn — career and job-search resources.
List the non-negotiables separately from the nice-to-haves
List the non-negotiables separately from the nice-to-haves. Location, working pattern, contract type or a hard constraint belong on a short first list. Everything else is a preference, and treating preferences as requirements quietly removes good roles.
Write one sentence on the kind of work you want more of
Write one sentence on the kind of work you want more of. A sentence about the tasks you want to repeat is more useful than a sentence about a dream company. It becomes the test you apply to each listing.
Make one base document you can tailor quickly
Make one base document you can tailor quickly. Keep a complete version with every role and project on it, then shorten it for each application. A full base document means tailoring is editing, not rewriting from memory.
Collect links to work you are allowed to show
Collect links to work you are allowed to show. Check that any example is public and that you have permission to share it. Put the links in one place so you never paste an expired or private URL in a hurry.
Draft a short introduction you can adapt
Draft a short introduction you can adapt. Three sentences: what you do, what you noticed about the role, and one concrete example. Keep the middle sentence genuinely specific to the employer.
Build the Tracker Before You Apply
Use one table, in a tool you already check daily
Use one table, in a tool you already check daily. A spreadsheet, a notes table or a simple document all work. The best tracker is the one you open without deciding to, not the one with the most features. For the primary source behind this phase, see GOV.UK — official UK government services. Related on Howcompass: write a resume that gets read.
Keep the columns few and unambiguous
Keep the columns few and unambiguous. Employer, role, link, date sent, status, next action and next date cover almost everything. Every extra column is a field you will leave blank by week three.
Agree a fixed vocabulary for the status column
Agree a fixed vocabulary for the status column. Use four or five words only, such as found, sent, replied, interviewing, closed. Consistent words let you filter the table; free-text notes do not.
Give every row a next action and a date
Give every row a next action and a date. A row without a next action is a role you have quietly lost. Write the one small thing that moves it forward and the day you will do it.
Keep the listing link in the row, not in your browser history
Keep the listing link in the row, not in your browser history. Listings disappear or change. Save the address and a short note of the key requirements so a closed page does not leave you guessing later. Browse all illustrated guides or the Work World category for more.
Record which version of your documents you sent
Record which version of your documents you sent. A short filename or a note is enough. If an employer replies three weeks later, you want to reread exactly what they read.
Apply in Small, Repeatable Batches
Set two short search windows per week
Set two short search windows per week. Fixed windows stop job hunting from filling every spare hour. Outside them, note a promising listing in the tracker and return to it at the next window. For the primary source behind this phase, see Acas — workplace rights and employment guidance.
Add every candidate to the tracker before applying
Add every candidate to the tracker before applying. Capture first, decide second. A row marked 'found' costs nothing and gives you a list you can prioritise calmly rather than under the pressure of an open tab. Related on Howcompass: prepare for a job interview and your first 90 days.
Check the listing is current and legitimate
Check the listing is current and legitimate. Confirm the role appears on the employer's own site where possible, and be cautious of any process that asks for payment or sensitive details unusually early.
Mark the three requirements the listing repeats
Mark the three requirements the listing repeats. Repeated wording usually signals what matters most. Address those three in your document instead of rewriting everything to match a long list.
Change the summary paragraph for each role
Change the summary paragraph for each role. Keep the evidence and reorder the opening so the most relevant experience appears first. One targeted paragraph is enough for most applications.
Read the form fields before pasting anything
Read the form fields before pasting anything. Some portals split names, dates and links into separate boxes. Paste carefully and check the result in the preview rather than trusting a single paste.
Send a small batch, then stop and log it
Send a small batch, then stop and log it. Two or three considered applications in one sitting are easier to track than twenty rushed ones. Update the rows immediately, while the details are still in front of you.
Keep Momentum Between Replies
Set a follow-up date that respects the listing
Set a follow-up date that respects the listing. If the employer states a timeline, use it. Otherwise choose a reasonable interval, write it in the tracker and let the date do the remembering for you. For the primary source behind this phase, see Purdue OWL — writing and citation guide.
Keep a follow-up short and factual
Keep a follow-up short and factual. One line confirming the role, the date you applied and your continued interest is enough. Restating your whole case makes a brief message harder to answer. Related on Howcompass: build a clean personal portfolio website.
Mark a role closed when the evidence says so
Mark a role closed when the evidence says so. A clear rejection, a filled listing or a withdrawn process is a closed row, not a failure column. Closing rows keeps the active list short enough to be encouraging. Browse all illustrated guides or the Work World category for more.
Keep one page of notes per interview stage
Keep one page of notes per interview stage. Write the date, who you spoke with, the questions asked and what you still want to know. These notes are also the raw material for a thoughtful thank-you message.
Check the practical details in advance
Check the practical details in advance. Time zone, format, location and the name of the person you are meeting are easy to confirm a day early. Avoid spending the first minutes of a call on logistics.
Prepare questions that come from the notes
Prepare questions that come from the notes. Two or three specific questions about the work are more useful than a long list. Refer back to something mentioned earlier to show the conversation has been followed.
Log every reply in the tracker on the same day
Log every reply in the tracker on the same day. A reply changes the next action and the next date. Update the row before closing the inbox so the table remains the single place you trust.
Review, Adjust and Close the Search
Once a week, count where rows are stuck
Once a week, count where rows are stuck. Many rows at 'found' means sourcing is fine and applying is the bottleneck. Many at 'sent' with no replies may mean the target or the documents need adjusting. For the primary source behind this phase, see Coursera — online courses.
Change one variable, then watch the next two weeks
Change one variable, then watch the next two weeks. Adjust the titles you search, the summary paragraph or the batch size - one at a time. Changing everything makes the next review impossible to interpret. Related on Howcompass: ask thoughtful reverse-interview questions.
Keep a short list of what you learned
Keep a short list of what you learned. Note recurring questions, requirements you keep seeing and skills worth building. The list is useful even after the search ends, and it turns waiting into something concrete.
Close the remaining rows when you accept a role
Close the remaining rows when you accept a role. Mark each open application closed with a short reason. Leaving a handful of 'maybe' rows is how an old search keeps nagging at you for months.
Archive the documents you used
Archive the documents you used. Keep the base document, the last tailored version and your notes in one folder. They are the starting point for the next move, not clutter to delete in a cleanup.
Write a short handover to your future self
Write a short handover to your future self. Record which channels produced the useful conversations and which step you would change first. Two honest lines are more valuable than a detailed system you will not reread.
Frequently Asked Questions
Question: Should I use a spreadsheet or a dedicated app?
Whichever you already open daily. A tool that requires a new habit is a second project; the value comes from consistent rows, not from features.
Question: How many applications should I send a week?
As many as you can tailor properly and log accurately. A small batch with complete rows is more useful than a large one you cannot remember next week.
Question: What if an employer never replies?
Follow the stated timeline if there is one, send one short factual follow-up, then close the row. Keeping a role open indefinitely adds noise without adding an option.
Question: Should I keep rejected applications?
Keep the row, marked closed with a date and reason. It prevents duplicate applications and shows patterns in your weekly review; it does not need a detailed post-mortem.
Tips
- Sweep: Add every new listing and clear any row with a past-due next date.
- Count: Tally how many rows sit at found, sent, replied and interviewing.
- Choose: Pick one small change for the coming week and write it at the top of the table.
Warnings
- Building a tracker with twenty columns: Every extra field is a promise to maintain it. Seven plain columns that stay filled beat an elaborate database abandoned after a week.
- Applying before writing the row: Retro-fitting a week of applications from memory produces gaps. Add the row at the moment you find a role, then decide whether to apply.
- Treating every silence as a rejection: Timelines vary and listings change. Use a written follow-up date and a clear definition of 'closed' instead of reading meaning into each quiet day.
- Changing the whole approach after one quiet week: Adjust one variable and give it two weeks. Constant reinvention means no single change is ever observed long enough to judge.
References (9)
- LinkedIn — career and job-search resourceslinkedin.com
- GOV.UK — official UK government servicesgov.uk
- Acas — workplace rights and employment guidanceacas.org.uk
- Purdue OWL — writing and citation guideowl.purdue.edu
- Coursera — online coursescoursera.org
- USA.gov — official U.S. government servicesusa.gov
- TED — talks and ideasted.com
- American Psychological Associationapa.org
- Khan Academy — free courseskhanacademy.org
Sources are listed so you can read the underlying guidance yourself. Our editorial policy explains how guides are reviewed.
Did this article help you?
0 readers found this helpful — add your vote.



No comments yet — be the first to share your results.