Somewhere around month eighteen, the number goes first. You still know you rebuilt the onboarding flow and that it worked, but the figure that made it worth reading, the 40 percent, the eleven days, the three thousand users, has quietly left your head. What survives is a vague sense that the job went fine.
A master CV is the file that stops that happening. It is private, you never send it, and it holds everything: every role, every project, every tool, every certificate, every sentence about your own work that you once got right. Each application is a cut from it, not a rewrite.
The forgetting is the whole reason
Most people build a CV backwards. They decide to look for work, open last year's document, and try to reconstruct two and a half years of employment from memory on a Sunday night. The reconstruction is always thinner than the reality. Projects that ran for four months compress into one bullet, numbers turn into "significantly", and the parts you remember are the parts that were emotionally loud: a launch, a bad quarter, a manager you liked. Those are not the same as the parts that persuade a hiring manager.
The master document flips the direction. You write into it while the work is fresh and the figure is still on a dashboard you have access to. Then, when a posting appears on a Tuesday and closes on Friday, you are editing rather than remembering.
There is a second benefit that only shows up later. Once you have a few pages of your own accumulated record, you start seeing patterns invisible from inside a single job: that you keep getting handed broken handovers, that your best results land in the first six months of anything, that you have quietly become the person who writes the documentation. That is career information you would not get any other way.
What goes in that would never survive a real CV
This is the part people get wrong. They treat the master document as a long CV, which means they keep applying CV rules to it and filtering things out. Do the opposite. The master document holds exactly what a real CV rejects.
- Dead ends. The project cancelled after five months. You will not send it, but that work produced a technique you still use, and you will want the details when an interviewer asks about failure.
- Internal tools and systems, by name. The ticketing system nobody outside the company has heard of, the internal reporting stack, the exact version of the ERP. Useless on a sent CV, essential the day a job ad names the same system.
- Numbers with their source. Not "reduced processing time by 30 percent" but the figure, the date you measured it, the report it came from, and the baseline it was measured against. The source is the bit you forget, and it is the bit you need when someone asks how you know.
- The reason each role ended. Restructure, contract end, a relocation, a manager change, you resigned. Nobody puts this on a CV. You get asked about it in most interviews, and the honest wording is far easier to write now than under pressure.
- Bullets you wrote and cut. A phrasing you spent twenty minutes on for one application is worth keeping even if it did not make that final version.
- The unglamorous admin. Employee numbers, exact start and end dates, line manager names, the former colleague who agreed to be a reference. Background checks ask for this, and you will not remember the dates by then.
Yes, this makes the document long. Length rules belong to the CV you send, not to this one: four pages is normal and ten is not a problem.
Structure it so cutting is fast
A master CV that is awkward to cut from gets abandoned after two applications. The structure has one job: let you find the right material in seconds.
Group by role, in reverse order, the way a CV would. Inside each role, keep four blocks. First the boring facts: title, dates, employer, team size, what the role actually involved. Second, achievements written as full unedited entries with their numbers and sources attached. Third, alternative phrasings. Fourth, a keyword dump of tools, methods, systems and certifications.
The alternative phrasings block saves the most time by a wide margin. The same achievement reads differently depending on who is reading it. A migration you ran is a cost story for a finance-facing role, a reliability story for an engineering one, a stakeholder story for a project role. Write all three versions the day you write the first, while you still hold the full picture. Six months later you can only reproduce the one you happened to need at the time.
Then keep a closing section with no equivalent on a real CV: a bank of every measured result you have, stripped of context and sorted by size. Percentages, money, headcount, timelines, volumes. When a posting leans hard on impact language, you shop from this bank first and then go find the role the figure belongs to.
If an entry in your master document has no number, no date and no proper noun in it, it is not finished.
Versioning that does not turn into a mess
The usual ending is a folder holding fourteen files called cv_final, cv_final_2, cv_new_final_ok. That happens because the base document and the sent versions get versioned in the same place with the same logic.
Separate them. The master is one file and it only ever gets edited, never duplicated. Put a dated line at the top each time you touch it, one sentence on what changed. That line is your evidence of whether the document is current, and it costs four seconds.
The tailored cuts are a different animal. They live in their own folder, one file per application, named for the employer and the date, and they are disposable. You do not maintain them. How you name the file you actually send is a separate question with its own rules, and it is not this one.
Keep the master in a format you can edit anywhere, phone included, because most of the moments when you remember something useful happen away from your desk. Plain text beats a designed template here. Formatting happens at the cut, not in the source.
The fifteen-minute cut
With a working master document, a tailored CV is an editing job.
- Read the posting twice and write down, in your own words, the five things this employer is actually buying.
- Copy the master into a new file. You are cutting now, and nothing you delete is lost.
- Delete whole roles that do not serve those five things, or compress them to one line each.
- For every role you keep, pick one phrasing per achievement from your alternatives, matching the vocabulary the posting uses.
- Pull two or three figures from the results bank into the top third of the page.
- Cut until it fits the length your sector expects, then format.
Nothing on that list requires writing a new sentence. That is the whole point. The writing happened months earlier, in calm conditions, with the data in front of you.
How it actually fails
The master document does not fail loudly. It goes stale in silence. You build it during a job search, it gets you the job, you close it, and you do not open it again for three years. When you next need it, the most recent eighteen months of your work, the relevant part, are missing. You are back to reconstructing from memory on a Sunday night, except now the document also tells you a comforting lie: that it is complete.
The fix is a calendar entry rather than willpower. Once a month, ten minutes, put in whatever happened. Better still, write the entry the week the thing happens, while the number is still on screen. A finished project, a new tool, written praise from a client, a figure from a review. Paste it in raw, badly worded, with its source. Tidy it later or never.
If you want a starting point instead of a blank page, exporting your LinkedIn profile or running it through a tool like Postulit gives you the skeleton of dates and titles in a few minutes. The skeleton is the easy half. The numbers and their sources are what you have to supply, and nobody else has them.
Start today with one entry: the most recent thing you finished, its figure, and where that figure came from. Ten minutes now against two hours of archaeology in eighteen months is not a close call.