Free worksheet

The Master Resume Inventory

Everything worth writing down once, so you never type it from memory into a resume again.

Here’s what usually happens. You write a resume. You apply to a few jobs. Then a role comes up that wants something slightly different, so you copy the file, change a few lines, and save it as a second version. By the time you’ve applied to twenty jobs, you’ve got four or five “final” resumes, and the project you did two years ago is written up four different ways, none of them quite right, because you were reconstructing it from memory each time instead of looking it up.

The fix isn’t a better memory. It’s writing each piece of your history down exactly once. Below is the inventory: the categories of content that make up a resume, broken out so you can build each one separately and pull from it for every version you ever need. Treat it like a worksheet. Go category by category, and don’t worry about which resume it belongs to yet. That part comes later.

The basics

  • Headers

    Your name, contact details, and any links you want on every resume: a portfolio, LinkedIn, GitHub, a personal site. Write it once. When your phone number changes, you fix it in one place instead of four files.

  • Summaries

    The few lines at the top that tell a recruiter who you are before they've read anything else. Most people need more than one version: a general one, a shorter one for a tight layout, maybe one angled toward a career change.

Your work

  • Roles & duties

    Every job you've held, as its own entry: title, company, dates, and the bullets underneath it. This is the bulk of the inventory, and the part that gets retyped the most if it isn't saved somewhere central.

  • Projects

    Work that didn't come with a job title: a side project, a freelance gig, something you built that's relevant to the roles you're going for next.

What you know

  • Skills

    The named abilities a hiring manager scans for: tools, methods, soft skills, whatever applies in your field.

  • Technologies

    For technical roles, the specific stack: languages, frameworks, platforms, software. Kept separate from skills so you can be precise about what you've actually used, not just what you're generally good at.

  • Certifications

    Anything with a name, an issuing body, and usually an expiration date worth tracking.

  • Languages

    Which ones you speak, and at what level, when that's relevant to the role.

What else you've done

  • Awards

    Recognition specific enough to be worth a line: an employee award, a scholarship, a competition placement.

  • Publications

    Anything you've written, co-written, or been cited in that's worth listing.

  • Volunteer experience

    Unpaid work that still shows real responsibility, especially useful if you're short on paid experience in the field you're targeting.

  • Associations

    Professional organizations, memberships, or boards you're part of.

  • Interests

    Optional, but useful if you're a student, a new grad, or applying somewhere that cares about culture fit.

Where you learned it

  • Education

    Degrees, schools, dates, and anything underneath them worth calling out: honors, relevant coursework.

Extras

  • Media

    Writing samples, portfolio pieces, or anything visual you might attach to or link from a version.

Build each piece once. Use it everywhere.

This is exactly how Vitae’s Item Editor works: write each category once, link it to any resume that needs it, and update it everywhere at the same time. It’s part of the free plan.

Create your free account

Core features are free, no credit card required. See how the Item Editor works →