Agency CV Management: Build a Searchable Candidate Database

Agency CV Management: Build a Searchable Candidate Database

Agency CV management is the work of taking every CV that reaches your team, whatever the channel, and turning it into one accurate, searchable, access-controlled candidate record. For most small agencies and HR teams, that means getting CVs out of a shared inbox and into a database. It also means setting a few rules so the database stays clean: a standard format, duplicate checks, clear permissions and a retention policy. This guide walks through each step, shows what to look for in a tool, and explains where a lightweight database fits better than a full applicant tracking system (ATS).

A quick note on terms. In the US, a resume is typically short, while a CV can be longer and more detailed. Outside the US the two words are often used interchangeably. If your agency places candidates internationally, you will receive both, and your process should treat them the same way.

TL;DR

• Most agency CV problems start in the shared inbox: attachments get buried, versions overwrite each other and nobody can search the archive.
• Fix the process before the tool: one CV standard, one naming rule, one place where records live, and a named owner for each.
• Detect duplicates at intake, not at the quarterly clean-up. Match on email, phone and name together.
• Set retention and access rules early. US employers must keep hiring records for at least one year, while EU rules push the other way, toward deleting data you no longer need.
• A simple CV database that connects to your existing mailboxes is often enough for teams that do not need a full ATS pipeline.

Table of Contents

• What agency CV management actually covers
• Why the shared inbox breaks down
• Step 1: Set one CV standard for the agency
• Step 2: Decide what must be searchable
• Step 3: Process the shared inbox without retyping
• Step 4: Catch duplicates at intake
• Step 5: Set privacy, access and retention rules
• Perspective: what we have seen in agency inboxes
• Choosing a simple candidate database or a full ATS
• Where RecrutFlo fits
• A one-week rollout for a small agency
• FAQ
• Sources

What agency CV management actually covers

It is easy to picture CV management as storage: a folder, a spreadsheet, perhaps an inbox label. In practice it has five jobs.

1. Intake. Capturing CVs from email, job boards, referrals and walk-ins without losing any.
2. Extraction. Pulling the facts out of the document: contact details, roles, skills, languages, location, availability, salary expectations.
3. Organization. Turning those facts into a profile you can filter, rather than a PDF you must open.
4. Quality. Keeping one record per person, current and consistent.
5. Governance. Deciding who sees what, how long data is kept and how it is deleted.

Teams that do the first job well and skip the others end up with a very large, very messy inbox. That is the usual starting point, and it is why recruiters keep re-reading the same CVs for each new vacancy.

Why the shared inbox breaks down

A shared mailbox such as jobs@ or cv@ feels efficient because everyone can see it. The cracks show up as volume grows.

• No structure. A CV is an attachment. You cannot search by “Spanish-speaking accountant in Austin” unless someone has typed that into a spreadsheet.
• Duplicated effort. Two recruiters open the same CV, or one replies to a candidate who was already contacted last week.
• Lost versions. A candidate sends an updated CV and a recruiter saves it over the old one, or the reverse. We cover this problem in resume version control for recruiters.
• Unclear access. Everyone with inbox access sees every application, including those for roles they have nothing to do with. See which shared inbox permissions to check.
• No audit trail. If a candidate asks what data you hold, or a client asks who handled their application, you are reconstructing history from email threads.

None of these are people problems. They are what happens when a document store is asked to behave like a database.

Step 1: Set one CV standard for the agency

Before you touch software, decide what a “finished” candidate record looks like. Agencies that present candidates to clients benefit most from a written standard covering template, section order, date style, anonymization, which edits are allowed, file naming, length and presentation. Glo Careers Services makes this case for a reason that is operational, not cosmetic: when every CV looks the same, clients compare candidates faster.

Note the difference between two documents:

• The original CV, exactly as the candidate sent it. Never edit it. Keep it as the source of truth.
• The presentation version, reformatted to your template for clients.

Store both against the same record. Many disputes (“I never wrote that”) disappear when the original is preserved.

Name files predictably

A naming rule seems trivial until an upload fails because of a stray symbol in a file name. Pick a pattern such as Lastname_Firstname_Role_YYYY-MM and avoid special characters. Our note on CV file names and the symbols that break uploads lists the usual offenders.

Step 2: Decide what must be searchable

The point of a database is retrieval. Work backward from the searches your recruiters run most often. A CV typically contains contact information, education, experience and skills, and depending on the background it may add certifications or licenses, publications, awards and professional associations.

For agency work, we suggest these fields as the core searchable set:

The last column matters. Data you extract is only as good as its consistency, so decide how you will record skills and titles (a controlled list or free tags) before the database fills up.

Step 3: Process the shared inbox without retyping

Manual entry is where agencies lose hours. A recruiter opens an email, downloads the attachment, reads the CV, and types the same facts into a sheet. Multiply that by dozens of CVs a week.

Automating this has three parts:

1. Connect the mailbox. The tool reads incoming mail from the shared inbox, so nobody forwards anything.
2. Detect CV attachments. Not every attachment is a CV. Cover letters, certificates, signatures and images should be ignored or filed separately.
3. Parse and structure. PDF, DOC and DOCX files are read and the key facts are extracted into fields.

Parsing is never perfect, particularly with designed layouts or scanned documents. A sound workflow keeps the original file one click away and lets the recruiter correct any field. Automation should remove typing, not remove judgment. We describe the full path in how to turn the CVs in your inbox into a searchable candidate database.

Treat attachments as untrusted

A CV is a file from a stranger, which makes it a convenient way to deliver malware. One UK security write-up on recruitment firms advises protecting ATS credentials and sandboxing email attachments to defend against malicious CV files. In practice: use multi-factor authentication on every account that touches candidate data, and open unfamiliar attachments in a controlled environment rather than on a recruiter’s main machine.

Step 4: Catch duplicates at intake

Duplicates are the quiet tax on every candidate database. A person applies through two job boards, sends an updated CV six months later, or uses a personal address once and a work address another time. Each submission becomes a separate record, and your “talent pool” count is inflated.

A practical duplicate policy:

• Match on several signals. Email alone misses people who switch addresses. Combine email, phone number and normalized name.
• Flag, do not auto-delete. A match is a suggestion. A recruiter should confirm before records merge, because two people can share a name or a family email.
• Merge, never overwrite. Keep every document version attached to the merged profile, with the date received.
• Check at the door. Running detection when a CV arrives is far cheaper than a periodic clean-up.
• Audit occasionally. Even with intake checks, a short periodic review of near-matches catches what rules miss.

To see how this plays out with a concrete example: a candidate named Maria Lopez applies in March from a personal Gmail account with a 2024 CV. In September she sends a new CV from a different address, but the same phone number. A system matching on phone and name flags the pair, and the recruiter merges them. The record now shows both documents and the later one is marked as current.

Step 5: Set privacy, access and retention rules

Candidate data is personal data, and agencies hold a lot of it. Three decisions deserve to be written down.

Who can see what

Give people access by role and by workspace. A recruiter working one client’s vacancies does not need the full archive. Keep a log of who opened, edited or exported records, so you can answer questions later. For a deeper checklist, see our permissions guide.

How long you keep CVs

The answer depends on where your candidates live, and the rules point in different directions.

• United States. Federal regulations require employers to preserve application forms and other hiring records for one year from the date the record was made or the personnel action taken, whichever is later. If a discrimination charge is filed, relevant records must be kept until the matter is finally resolved. Some states and federal contractors have longer requirements, so confirm with counsel for your situation.
• France (EU). The data protection authority, the CNIL, says candidate data should be kept only as long as necessary, and for talent pools recommends, in principle, no more than two years from the last contact. It also says processing must be transparent to candidates.
• Company policies vary. One UK employer’s published privacy policy, for example, keeps unsuccessful applicants’ CVs and notes for six months from notification unless earlier deletion is requested.

If you recruit across borders, the practical approach is to set a retention period per candidate location, apply the stricter rule where you are unsure, and delete on a schedule rather than when someone remembers. Our GDPR recruitment compliance guide for small teams covers the European side in more detail.

How much automation to allow

Parsing and search are low-risk. Automated ranking or rejection is different. UK guidance summarized by one advisory firm says AI screening requires a data protection impact assessment, and significant automated decisions need transparency, human intervention on request and a right to contest. Whatever your jurisdiction, a safe default is to let software organize and surface candidates while a person makes every decision about them.

Perspective: what we have seen in agency inboxes

We build for teams that live in shared mailboxes, and the pattern is consistent. The agencies struggling most rarely lack candidates. They lack retrieval. A strong CV arrived eight months ago, nobody can find it, and the recruiter starts a fresh search from job boards, paying again for something already owned.

Our view is that most small teams do not need to adopt a new platform to fix this. Moving everyone onto an unfamiliar system, with an onboarding call and an implementation project, is a lot to ask of a five-person agency. We think the database should come to the inbox, not the reverse: connect the mailbox the team already uses, extract the facts, flag duplicates, and leave the recruiter in control of every decision. Automation handles the repetitive typing. People handle the judgment.

We also think privacy should be a design input, not an afterthought. Workspace isolation, an audit trail and team access control are not premium extras for a business that stores other people’s careers.

— Marco

Choosing a simple candidate database or a full ATS

An ATS is built around a hiring pipeline: job postings, career pages, stages, interview scheduling, offers. If you run that process daily, you need one. Many small businesses and agencies, though, mainly want a clean, searchable pool of CVs that arrive by email. For them, a full ATS can mean paying for and learning features they never use.

Use these questions to decide:

The two are not exclusive. Some teams start with a database, prove the workflow, and add an ATS later if their pipeline grows. For a longer comparison, read recruitment inbox vs traditional ATS.

What to check before you buy

• Mailbox support. Does it connect to the mail system you actually use? RecrutFlo works with Microsoft 365, Outlook and IMAP mailboxes, with Gmail coming soon.
• Parsing coverage. PDF, DOC and DOCX at a minimum.
• Price transparency. Published plans and clear limits, not a mandatory sales call.
• Export. You should be able to get your data out as CSV at any time.
• Isolation and audit. Separate workspaces and a record of who did what.
• Duplicate handling. Detection that flags rather than silently merges.

Where RecrutFlo fits

RecrutFlo is recruitment software for small and growing businesses, agencies and HR teams that receive CVs in shared inboxes. It connects to your mailbox, detects CV attachments, extracts candidate details, and builds searchable profiles you can filter by skills, experience, languages, location and role. It flags duplicates, supports CSV export, and includes workspace isolation, an audit trail and team access control.

There is no onboarding call or implementation project, and you can test the workflow on the free plan first. Paid plans are published: Starter at 19 € per month, Professional at 49 € per month and Business at 149 € per month. If you need more capacity, extra processing runs are a one-off purchase: 100 for 9 €, 500 for 29 € or 1,000 for 49 €. See the full plan details on the pricing page, or look at how it works before you sign up.

A one-week rollout for a small agency

You do not need a long project. Here is a realistic sequence.

1. Day 1: Write the standard. One page: template, naming rule, which fields matter, who owns the database.
2. Day 2: Clean the inbox. Archive the noise. Decide which historical CVs are worth importing and which fall outside your retention period.
3. Day 3: Connect and test. Link the mailbox and run a batch of 50 to 100 CVs. Check the extracted fields against the originals and note where parsing needs correction.
4. Day 4: Set access. Assign roles, confirm who can export, and make sure the audit trail is on.
5. Day 5: Run real searches. Take two open vacancies and search the database before posting anywhere. If you find three viable candidates, the process has paid for itself.

Afterward, review monthly: duplicate rate, fields that parse poorly, records past their retention date. Small habits keep the database useful for years.

FAQ

Is a CV the same as a resume?

In the US, a resume is usually a short summary, while a CV tends to be longer and more detailed. In many other countries the two words mean the same thing. For database purposes, treat both as candidate documents and extract the same core fields.

How do we find CVs from last year in a shared inbox?

Inbox search only matches words in the email or file name, so it misses skills and experience inside the attachment. Parsing the attachments into structured profiles lets you search by role, skills, languages and location instead. Keep the original file attached to each profile so you can always check the source.

How long should an agency keep candidate CVs?

It depends on where the candidate and your business are. US federal rules require hiring records to be kept for one year, while French regulators recommend no more than two years from last contact for talent pools. Set a retention period for each region, delete on schedule, and ask your lawyer about your specific case.

Do we need an ATS to manage CVs?

Not necessarily. If your main need is organizing and searching CVs that arrive by email, a simple candidate database can cover it at a lower cost and with less setup. If you manage job postings, interview stages and offers for many roles at once, a full ATS is the better fit.

Sources

• CV Format Guide: How To Write a CV (Indeed)
• Setting a CV standard for your agency (Glo Careers Services)
• 29 CFR § 1602.14, Preservation of records made or kept
• Guide recrutement : les fondamentaux (CNIL)
• Privacy Policy (Nourish Care)
• Cyber Security for Recruitment UK 2026
• How to use AI in recruitment without breaking UK law

Recommended

• How to Turn the CVs in Your Recruitment Inbox into a Searchable Candidate Database
• Resume Keyword Search: Reveal Hidden Candidates in Your CV Inbox
• Search Candidates by Location: From CV Data to Map Results
• Resume Version Control for Recruiters: Stop Inbox Overwrites in a Day