Which CV version did I send them? A tracker that survives past week two

The interview where you cannot remember which CV they are holding

You applied five weeks ago. You have applied to eleven other things since. The interviewer opens with a bullet from your CV and asks you to walk them through it, and you hear a version of your own history that you half remember writing. So you answer from the version that is fresh in your head, which is the one you sent last Tuesday to somebody else, and now the document in their hand and the person in front of them are telling slightly different stories.

That is the real damage, and it is worth being precise about it. It is not that you look disorganised. It is that inconsistency reads like embellishment even when every single word you wrote was true. You emphasised delivery for one advert and cost control for another, both honestly, and in the room it comes out as a person whose account of themselves moves. Nobody is going to tell you that is what happened. You will just get the polite no.

Once you frame it that way, most of what people put in a tracker turns out to be decoration. You do not need the salary band, the job board, the recruiter's LinkedIn URL or a colour-coded status. You need to be able to open the exact file you sent, before the call, and read it. Everything on this page is built backwards from that one moment.

Now the concession I owe you. The commenter who said tracking thirty applications means you are spraying has a point hidden inside an insult. If you genuinely cannot remember which version went where, some of those versions were not tailored, they were reshuffled. Moving three bullets and swapping a job title is not a different application, it is the same application wearing a hat, and it produces exactly the version confusion without producing any of the benefit.

Where I think that commenter is wrong is the arithmetic. Thirty applications across two months is not spraying in a slow market, it is a normal search, and telling someone to apply to less so their admin gets easier is solving the wrong end of the problem. The volume question deserves its own answer and I gave it one in the piece on how many jobs to apply to per week. This page assumes you have already decided your number and now have to live with the paperwork it creates.

Why the spreadsheet dies in week two

The thread that prompted this page is on r/resumes, asking how people keep track of thirty applications. The post itself drew far more comments than upvotes, and that ratio is the interesting part: almost nobody arrived to praise their system. They arrived to describe the one that failed. One person wrote that they started a spreadsheet and stopped updating it after week two because it felt like a second job. That is one comment from one stranger, not a study, and I am quoting it because I recognised myself in it, not because it measures anything.

Here is the mechanism underneath it, and it is not about discipline. Logging is a separate action from applying. You finish the form, you get the confirmation page, you feel the small relief of being done, and the tracker is one more thing standing between you and closing the laptop. On a good day you open it. On the day you applied to four things while tired you do not, and now the sheet is wrong. A tracker that is wrong is worse than no tracker, because you stop trusting it, and the moment you stop trusting it you stop opening it at all.

Every extra column is a reason not to open the file. A tracker dies from the fields you never fill in, not from the ones you do.

The second failure is the versions themselves. People name the files sensibly on day one and then, at eleven at night, save something as CV_final_2.pdf because they will remember. Three weeks later there are four files with that shape in a downloads folder and no way to tell which one left the building. At that point the honest answer to "which version did I send?" is that it is gone, and no amount of retroactive spreadsheet work brings it back.

So the design constraint is not "be more organised". It is: the log must not be a separate action. If you have to remember to do it, you will not do it in week three, and week three is when the interviews from week one start landing.

The filename is the log entry

Here is the whole system. One folder. Every application you send produces exactly one file that already has to exist, and that file's name carries the entire record. There is no second place to update, so there is nothing to forget.

Four fields, in this order, and the order matters. The date applied comes first so the folder sorts itself chronologically without you doing anything: the top of the list is what you are waiting on, the bottom is what has gone quiet. Then the company, then the role, because two roles at the same company are two different documents and you will otherwise conflate them.

The fourth field is the one people get wrong

Do not end the name with v1, v2, v3. A number tells you the order you made them in, which is information you never need again. Name the version after the angle you led with: delivery-led, cost-led, process-led, team-led. Three weeks later "v3" tells you nothing and "retention-led" tells you exactly which version of your own story is sitting in front of the interviewer. That single change is what turns a naming convention into something you can actually use under pressure.

Name the file after the story you told, not the order you made it in. The number is for your filesystem. The angle is for you.

The second file, the one ending in ad.txt, is the only extra step I will ask you to take, and it exists for a specific reason. Advertisements come down. When a recruiter calls you eight weeks later about a role you applied to in a batch, the posting is often already gone, and it is the one piece of the application that your email cannot give back to you. Select all, paste into a plain text file, done. Everything else, the contact person, the confirmation, the salary discussion, is one search in your inbox away.

And the obvious prerequisite: this only helps if the versions are genuinely different, which means the tailoring has to be real rather than cosmetic. What actually distinguishes one version from another, and how to do it without rewriting from scratch, is a separate subject I wrote up on its own page. If your versions differ only by a job title in the summary line, you do not have a tracking problem, you have a tailoring problem.

Three facts to keep, and everything you can throw away

People build fifteen-column trackers because every column looks defensible on its own. Here is the version I would defend, with the reason each field earns or loses its place.

If you prefer a spreadsheet, keep one, but keep these columns and no others, and understand that the sheet is now a convenience rather than the record. The record is the folder, because the folder cannot go out of date. A file either exists or it does not.

Marking things dead so the list stays short enough to open

A tracker with sixty live rows is not a tracker, it is a monument. Most of them are already over and nobody told you, and the accumulated silence is a large part of why opening the file feels bad. So you need rules for closing a row that do not require anyone to confirm anything, because in most cases nobody ever will.

1. An explicit rejection arrives. Move it to closed/ the same day, before you have finished feeling anything about it.
2. You sent your one follow-up and heard nothing for three weeks after it. Close it. You can always reopen a folder.
3. The advert has come down and the role has reappeared under a new posting. Treat your application as finished rather than pending, whatever the reason for the repost turns out to be.
4. The contact person has left, the requisition is on hold, or the company has announced a hiring freeze. Closed, and not about you.

On the follow-up itself I want to be careful, because I see a specific number repeated everywhere with no source attached to it. The convention is roughly a week after applying, once, short, naming the role. I cannot point you at a study that establishes the right interval, and I am not going to pretend the difference between day seven and day ten has been measured. What is defensible is the shape: one note, not three, and a note that names the specific role, because the person reading it is holding several vacancies and cannot place you otherwise.

The honest part, which the tidy version of this advice leaves out: most of these rows will end in silence and you will never learn why. Closing them is not giving up on yourself. It is refusing to keep a folder full of open questions that nobody is going to answer, so that the eight applications still genuinely alive are visible when you open it.

What careerify's application list does, stated exactly

The product paragraph, once, and with its limits named so you can weigh it against the folder. careerify keeps one row per application. The row holds the company, the role, the exact tailored CV that was sent, the date you applied, a status, and a timeline of events on that application. It is the same four facts as the filename. You type the company and the role once, when you add the advert you are about to tailor against, and the tailored CV then attaches to that row, so you are not writing the record down a second time after you have applied.

Here is what it does not do, and I would rather you read it from me than discover it. There is no side-by-side view of two rendered CVs. The row stores a before and after score for that application, which is a pair of numbers, not two documents laid next to each other. If you want to compare two versions visually you open the two files, exactly as you would with the folder method. I would like to build the comparison view. It does not exist today, and a page whose whole argument is about knowing what you actually sent cannot afford to be vague about that.

The tailoring itself is bounded by facts you have entered yourself. It cannot add a role, an employer, a scope or a number you never gave it, because it only has your material to work with. That is a structural property rather than a promise, and it is the reason the versions it produces stay consistent with each other: they are different arrangements of the same true material, not different stories.

When you mark a row as submitted, careerify schedules a follow-up five business days later, counting Monday to Friday, so in a normal week it lands about seven calendar days after you applied. It shows up on the row when it is due. What to actually write in it is covered on the follow-up email page, because a scheduled reminder attached to a badly written note is not worth much.

Cost, so you can dismiss it quickly if it is not for you: the free plan generates one tailored CV per month, and Pro is 229 SEK or 19,90 EUR per month. If you are applying at the volume this page describes, the folder method costs nothing and works. I would rather you use it and never pay me than buy something on the strength of a claim I cannot support.