I replaced my job search spreadsheet with a simpler CV workflow

My spreadsheet worked, until it didn't.

At the start of my job search, I had one Google Sheet with all the right columns: company, role, date applied, status, notes. It looked organised. I felt organised.

Then the volume went up.

More applications meant more CV variants. Backend role? One version. Product-heavy role? Another version. Client-facing role? Different emphasis again. After a few weeks, my spreadsheet had data, but it wasn't trustworthy data.

I started making mistakes:

• sending the wrong CV version
• forgetting where I'd already applied
• updating the sheet days later from memory
• scrambling when a recruiter replied and asked questions tied to a version I couldn't find

That was the moment I realised the problem wasn't effort. It was workflow design.

Where the old process broke

The biggest issue was context switching.

I wrote CVs in one place, tracked applications in another, kept notes in a third, and exported files with random names. Every apply session became a mini detective story.

Spreadsheets are great when the object you're tracking is stable. My CVs weren't stable. They changed constantly. So the tracker and the documents drifted apart.

And once trust in your own system drops, everything slows down.

The rule I switched to

I stopped trying to track everything and focused on the minimum that prevents errors.

Here's the system I now use:

1. One master CV
   This is the source file. No sending this version directly.

2. Three role profiles
   I keep specific variants for role families I actually apply to. Not ten variants. Three.

3. Every export gets a deterministic name
   Role_Company_Date.pdf

4. Track only decision-critical fields

   • company
   • role
   • date applied
   • CV version sent
   • next action date

That's it.

No giant dashboard. No 25 columns. No illusion of perfect analytics. Just enough structure to avoid avoidable mistakes.

Why this helped more than 'working harder'

Before, I'd spend energy remembering.

Now, I spend energy applying better.

That's the shift.

When a recruiter replies, I know exactly what they saw. When I follow up, I know when and why. When I tailor another application, I start from the right base version immediately.

The process feels calmer because I removed hidden decisions.

A note on tools

I tried a few popular CV tools during this period. Some were polished, but a lot of the friction moved to the end: export limits, paywalls at download, or awkward multi-version handling.

I wanted something that stayed simple for this exact workflow, so I built my own local-first setup around these rules.

The tool matters less than the system, though. If you already have a stack you like, keep it. Just make sure version tracking is a first-class part of it, not an afterthought.

If you're in the messy middle of job searching

Try this for one week:

• Reduce your CV variants to the smallest useful set
• Name exports consistently
• Log version-sent and next-action every single time

You'll feel the difference quickly.

The job market is hard enough. Your process should remove stress, not create it.