CV CVTailor
Blog

Three Word documents are already two too many

The problem with maintaining multiple CV files is not the files. It is that the same fact lives in three places — and at least one is wrong now.

2 min read
  • workflow
  • pool
  • tips

You start with one CV. You apply somewhere. You realise the role wants more frontend, less backend. You open the CV, you change paragraphs around, you save as cv_frontend.docx. Two CVs.

Then you apply somewhere else and the role is in English. You translate. You save as cv_en.docx. Three CVs.

Then your phone number changes.

Three Word documents are already two too many.

The problem isn’t the documents. The problem is that the same fact lives in three places. Your phone number, your last role description, the dates of your last project — every one of them has three copies, and at least one is wrong now.

The maintenance tax

Anyone who has applied for more than two roles knows this tax:

  • “Did I update the last role description in the EN file?”
  • “Wait, which one had the agency project highlighted?”
  • “Why does my LinkedIn say a different end date than cv_v3.docx?”

You don’t get a notification when one file falls out of sync. You find out when a recruiter quotes a date back at you that you no longer remember being true.

What CVTailor does about it

You write a fact once. You write your phone number once. You write your last role description once, in DE and EN. CVTailor stores it as a chapter in your pool.

When you build a version for a specific application:

  1. Pick the chapters you want.
  2. Pick their order.
  3. Pick the language.
  4. Done.

If your phone number changes, you change it in one place. Every version you ever built — including the public link you sent yesterday, if it’s still live — picks up the new number the next time anyone opens it.

What changes when versioning is cheap

This is the unobvious part. When making a new CV version stops being a 30-minute copy-and-paste job, you start to do it more.

You stop sending the same CV to a backend role and a team-lead role. You start tailoring per application rather than per quarter. You write a separate one-page summary version because it now costs you ten clicks instead of an evening.

The Word-document workflow makes you frugal with versions for the wrong reason — not because three are enough, but because three are already too many to maintain.

Where we are

Pool and versioning are live. Public link sharing and PDF export are live. We’re working on a roles view for agencies who want to manage candidate pools.

Free for individuals. We mean it.

Back to overview