Shared CV Database: One Source for Sales, Delivery and HR

CV Management & TemplatesRecruitment & HR

Sales has a consultant’s CV in a bid folder from last spring. Recruitment has a newer version in the ATS. Delivery tracks the same person’s current project in a spreadsheet, and HR holds their certifications somewhere else again. Each team is right about its own copy, and nobody has the full picture. A shared CV database exists to end that.

This post looks at why consultant information fragments across departments, what those scattered copies cost, and how one governed source lets sales, delivery, recruitment and HR work from the same profiles without giving up their own ways of working.

TL;DR
  • Sales needs consultant CVs for tenders, recruitment for candidate selection, delivery for staffing and HR for its own processes.
  • Each department tends to keep its own copy, in SharePoint, shared folders or internally built systems.
  • The copies drift apart, so the same consultant is described differently depending on which team you ask.
  • People spend time looking for information, reconciling versions and asking other teams, instead of using it.
  • A shared CV database keeps one governed profile per consultant that every department works from.
  • Role-based access lets each team see and use what it needs, while each keeps its own workflows.
  • Updates made by one team reach every other team immediately, so nobody works from an outdated copy.

Who Needs Consultant CV Information, and Why

Consultant CV information is used across the business, for different reasons. Sales needs it for tenders and client proposals. Recruitment needs it to select candidates. Delivery needs it to staff projects and talk to clients about the people on them. HR needs it for reviews, careers and certifications.

Leadership needs it too, in aggregate: which skills the company has, where the gaps are and how ready it is for the next opportunity.

These needs overlap far more than the separate storage suggests. All of them depend on the same underlying facts: what each consultant has done, when, with which technologies and with which certifications.

TeamWhat it needs from consultant CVsWhere it often lives today
Sales and bidsProfiles in tender and client formatsFolders of exported Word files per bid
RecruitmentSkills and experience for candidate selectionATS records and CVs in different formats
DeliveryCurrent experience for staffing and client conversationsSpreadsheets and team-maintained lists
HRCertifications, career history and reviewsHR systems and shared folders
LeadershipA company-wide view of skills and readinessReports consolidated by hand

How Each Department Ends Up With Its Own Copy

Because each team needs the information for its own purpose, each one tends to store it in its own place. Companies may use SharePoint, internally developed systems, shared folders or a mix of all three, often different ones per department.

The copies start identical and drift. Sales updates a CV for a bid and saves it in the bid folder. Recruitment adds a new project in its own system. HR records a certification that never reaches the CVs sales is using. Nobody is doing anything wrong, but the information is no longer the same.

Over time, the question of which version is correct has no clear answer. The latest CV is wherever the last person who touched it saved it.

Growth adds to the problem. New offices, new practices and acquired companies bring their own storage habits, so the number of places consultant information lives keeps rising even when nobody decides it should.

Why does every department keep its own version of consultant CVs?

Because each one needs the information for a different purpose, and nobody owns a shared source they all trust.

Sales needs CVs formatted for tenders, recruitment needs them for selection, delivery needs them for staffing and HR has its own systems. Without a common source, each team keeps the copy that suits its work, and those copies quietly diverge.

What Fragmented CV Information Costs

The most visible cost is time. People spend time looking for information instead of using it: searching folders, asking colleagues in other teams, comparing versions to find the most recent one.

The less visible cost is accuracy. A bid team submits a CV that is missing a certification HR recorded months ago. A delivery manager proposes a consultant without knowing about a recent project recruitment logged. Decisions get made on partial information, and nobody notices until a client does.

Fragmentation also makes the talent base harder to see. When skills sit in different systems under different names, the company cannot answer simple questions about who it has, and every new requirement starts with a search across several places.

The same question also gets asked again and again. Sales asks recruitment whether a consultant has a certain skill, delivery asks HR about a certification, and the answers depend on who replies and which copy they check.

Isn’t a shared folder on SharePoint enough?

It centralises files, but not the information inside them.

A shared folder still holds documents. Several versions of the same CV can sit side by side, skills remain hidden inside text, and each team still edits its own copy. A shared CV database holds structured profiles, so there is one current record per consultant, searchable by skill and usable by every team.

What a Shared CV Database Changes

A shared CV database replaces the copies with one structured profile per consultant. Experience, projects, skills, certifications and languages are held once, in the same fields, and every team reads from and writes to the same record.

The outputs each team needs are generated from that profile. Sales produces tender and client CVs in the required template, recruitment compares candidates on structured skills, delivery sees current experience, and HR keeps its certification and career information on the same record.

Generating those outputs relies on a portfolio of CV templates, so each team gets the format it needs without keeping its own version of the document.

Search works across everyone at once. A requirement can be matched against every consultant in the shared CV database, regardless of which team added them, as covered in automate candidate shortlisting with Sprint CV Match.

Giving Each Team the Right Access to the Shared CV Database

Sharing one source does not mean everyone sees everything. Role-based access lets each team work with the information it needs, while sensitive data stays limited to the people responsible for it.

Managers can see and act on the consultants they are responsible for. Sales can generate CVs for tenders without seeing HR-only details. Groups with several companies or countries can limit access to the part of the business each person works in.

In practice, the change is often welcomed by the teams themselves. Sales stops waiting for recruitment to send a CV, delivery stops maintaining its own spreadsheet, and HR stops answering the same certification questions every week.

Will teams lose control over their own work if they share one source?

No. They share the data, not the workflow.

Each department keeps its own way of working: sales prepares tender CVs, recruitment runs selection, delivery plans staffing. What changes is that they all read from and write to the same profiles, so the information each team relies on is the same information everyone else sees.

Keeping One Source Current Across Teams

A shared source only helps if it stays current, and that becomes easier once there is only one record to maintain. An update made by recruitment, HR or the consultant reaches every team immediately, because there is no other copy to fall behind.

Consultants can update their own information and confirm their CV is still valid, and targeted questions can collect specific missing details when a team needs them. Each confirmed answer improves the profile for everyone, not just for the team that asked.

Because the shared CV database holds structured fields rather than documents, small updates stay small. Adding a new project or certification takes minutes, and nobody has to reopen and reformat a CV to do it.

Collecting those details is described in how to launch a questionnaire.

Profile completeness can then be tracked across teams. If one department’s consultants are consistently out of date, it shows up in the data instead of in a missed bid.

Ownership also becomes clearer. Instead of every team being partly responsible for its own copy, the company can decide who validates which parts of a profile, and everyone benefits from that validation.

Moving From Scattered Copies to a Shared CV Database

Moving from scattered copies to one source is easier in steps. A practical sequence looks like this:

  • ✓List every place consultant CV information is stored today, by team
  • ✓Agree which fields every consultant profile must contain, whatever team uses it
  • ✓Load existing CVs into the shared structure, starting with a representative batch
  • ✓Define role-based access for sales, recruitment, delivery, HR and managers
  • ✓Point each team’s workflow at the shared profiles, and retire local copies
  • ✓Decide who validates updates, and how consultants confirm their own information
  • ✓Track profile completeness across teams to see whether the shared source is being kept current

Bringing every team onto the same consultant profiles, with their own workflows and access, is what an Enterprise CV Manager provides.

Frequently Asked Questions

What is a shared CV database?

It is one central repository of structured consultant profiles that sales, recruitment, delivery and HR all use, instead of each department keeping its own copies of CVs.

Why is CV information scattered across departments?

Each department needs consultant information for a different purpose and stores it in its own place, such as SharePoint, shared folders or internally built systems, so separate copies build up over time.

How is a shared CV database different from a shared folder?

A shared folder centralises documents, which can still exist in several versions. A shared CV database holds one structured, current profile per consultant that every team can search and use.

Can each department keep its own way of working?

Yes. Teams keep their own workflows and outputs while reading from and updating the same consultant profiles, with access set by role.

Who keeps a shared CV database up to date?

Consultants, recruiters, HR and managers can all contribute updates, with validation rules deciding who confirms changes. Because there is only one profile, every update reaches every team.

Final Thought

Consultant information fragments across departments because every team has a real need for it and nowhere shared to keep it. The result is time lost searching, decisions made on partial data and a talent base nobody can see whole.

A shared CV database gives every team the same, current picture of each consultant, while letting each one keep the workflows that suit its job. Questions between teams get answered by the data instead of by email. Sales, delivery, recruitment and HR stop maintaining their own versions of the truth, and start working from one.

How many versions of each consultant exist across your teams?

See how one shared, governed consultant profile serves sales, recruitment, delivery and HR, with each team keeping its own way of working.

Book a demo with Marco Pincho

Beatriz Carreira

About the Author

Beatriz Carreira joined Sprint CV to turn how the product actually works into content people can follow on their own, from tutorials and videos to blog posts and guides. With a background in digital marketing, her focus is finding where a recruitment or consulting team usually gets stuck and writing the piece that gets them past it. Connect with Beatriz on LinkedIn →