Consulting and recruiting
Data inventory for consulting firms: proposals, staffing and project reviews
By SourceX Editorial · Updated
Short answer
A data inventory for a consulting firm lists each record family, the system that holds it, its date range and a client-confidential flag. Start with three families that firms own but rarely map: proposals, staffing records and project reviews. Flag anything that contains client information before anyone discusses reuse, internal AI tools or licensing.
Key takeaways
- Proposals, staffing records and project reviews are the firm-owned families most often missing from consulting inventories.
- Every row needs a client-confidential flag, because one embedded client detail changes how a record can be used.
- An inventory records metadata only; no files move while it is being built.
- PSA and CRM systems hold the structured history, while shared drives and chat hold the narrative that explains it.
- Rows marked mixed need a preparation plan before any reuse, not a simple yes or no.
Why consulting firms need a records inventory#
A consulting firm records inventory shows what the firm knows, where that knowledge sits and which parts belong to clients. Without one, partners debate AI tools, knowledge projects or an eventual exit on guesses about what the archives contain.
Consulting firms are unusual because their most useful records are mixed. A proposal combines the firm's method with a client's problem; a project review combines the firm's delivery lessons with the client's facts. The inventory's job is to separate those strands at the row level, before anyone opens a file.
Pre-filled rows: proposals, staffing and project reviews#
The pre-filled rows below cover the record families most consulting firms hold, with a default client-confidential flag for each. Adjust the systems to your stack and change a flag wherever your contracts say otherwise.
| Record family | Typical system | What it captures | Client-confidential flag |
|---|---|---|---|
| Proposals and pitch decks | SharePoint or Google Drive proposal library, CRM attachments | Problem framing, approach, team and pricing logic | Mixed: client names and context inside |
| Statements of work and engagement letters | Contract repository, CRM | Scope, deliverables, assumptions and change terms | Mixed: client terms and identities |
| Win/loss records | CRM opportunity stages and loss reasons | Outcome and stated reason for each pursuit | Firm-owned, client names present |
| Staffing requests and assignments | PSA such as Kantata or Certinia, resource tools | Roles requested, who was assigned, skill gaps | Firm-owned, employee personal data present |
| Skills profiles and utilization | PSA, HR system, spreadsheets | Consultant skills, certifications and billable time | Firm-owned, employee personal data present |
| Status reports | PSA project records, email | Progress, risks and decisions over the project | Mixed: client details throughout |
| Project reviews and lessons learned | Confluence, Notion, review templates | What worked, what failed, what changed in delivery | Mixed: often names clients and data |
| Playbooks and methodologies | Knowledge base, training materials | The firm's repeatable methods | Firm-owned, check for client examples |
| Final client deliverables | Engagement folders, client portals | Reports, models and recommendations | Client-owned in most contracts |
| Client-provided data | Engagement folders, analytics workspaces | Client extracts and source files | Client-owned, return or destroy applies |
What the client-confidential flag means#
The client-confidential flag tells everyone how a record family may be handled before anyone opens a file. Use a short, fixed set of values so partners, IT and counsel read the inventory the same way.
When unsure, flag up, not down. Moving a row from mixed to firm-owned should require a documented reason, such as a contract review or a decision to strip client details, and the person who approved the change.
| Flag value | Meaning | Default treatment |
|---|---|---|
| Firm-owned | Created by the firm for its own operations, with no client information | Available for internal reuse; licensing still needs a rights review |
| Firm-owned, personal data present | Firm records that identify employees or contacts | Reuse only with personal details removed and notices checked |
| Mixed | Firm method combined with client names, facts or data | Needs a preparation plan or contract review before reuse |
| Client-owned | Deliverables or data the client owns or controls | Excluded from reuse; follow the engagement terms |
What staffing records reveal that proposals do not#
Staffing records reveal how the firm actually delivered, which proposals only promise. A staffing request shows the roles a partner believed the work needed; the assignment shows who was available; utilization and timesheets show where the hours really went; and change orders show where the plan broke.
Most firms keep these records in a PSA, but the reasoning behind them sits in resourcing meetings, chat threads and email between practice leads. Note those locations in the inventory even if you never plan to use them, because they explain decisions that the structured fields record only as outcomes.
Staffing records also carry employee personal data, such as performance notes, rates and availability. Flag them as firm-owned with personal data present, and check your employee notices before any use beyond running the firm.
How to build the inventory without moving files#
Building the inventory is a metadata exercise that a COO or operations lead can run with system owners over a few working sessions. Nobody exports, copies or samples anything.
- List every system the firm pays for, using finance's software subscriptions as the starting point.
- For each system, record the owner, the record families it holds and the earliest year still accessible.
- Note whether records link together, for example a CRM opportunity tied to a PSA project and a project review.
- Apply the client-confidential flag and note which client contracts drive it.
- Record known restrictions such as return or destroy clauses, data processing terms and employee notices.
- Mark the export route for each system, such as native export, API or vendor-assisted extract, without running it. Some routes need lead time: BQE, for example, says a CSV backup of a CORE database is available for a fee, must be requested in writing by the company owner and typically takes 1 to 3 working days.
Illustrative: an operations consultancy maps its records#
Illustrative: a fictional operations consultancy serving mid-market manufacturers builds its first inventory after partners disagree about launching an internal proposal assistant. The COO lists HubSpot, Kantata, a SharePoint proposal library, Confluence and Microsoft Teams.
The inventory shows that loss reasons are recorded consistently in HubSpot, that Kantata holds staffing history back to the firm's early years, and that project reviews in Confluence name clients on almost every page. The partners approve the assistant for proposals and playbooks flagged firm-owned, and send project reviews through a de-identification pass before any reuse.
Mistakes that make a consulting inventory misleading#
The most common mistake is inventorying folders instead of record families. A folder called Clients says nothing about whether it holds proposals, deliverables or raw client extracts, and a reviewer cannot flag what nobody has named.
Other mistakes include assuming the PSA holds everything about delivery when most narrative sits in email and chat, flagging playbooks as firm-owned without checking for embedded client case studies, and recording company age instead of accessible history after past system migrations. Each one overstates what the firm can actually use.
Linkage deserves a column of its own. A proposal that can be traced to a won project, its staffing plan and its final review tells a much richer story than the same documents stored in separate silos.
How SourceX uses a consulting firm inventory#
SourceX uses the inventory as the Supply step of the SourceX five-step transaction: a metadata view of what exists, with nothing shared during the initial assessment. Rows flagged client-owned are excluded, and mixed rows go through the Rights and Preparation steps before anything else happens.
The SourceX Enterprise Data Value Framework then gives qualitative ratings on drivers such as domain expertise, human-generated signal, recency and rights, while preparation cost and privacy burden reduce net value. Linked proposal, staffing and review records usually reveal more about how consulting work gets done than any single document type.
Frequently asked questions
Who should own the inventory in a consulting firm?
Usually the COO or head of operations, with a named owner for each system. Partners review the flags for their client relationships, and counsel reviews rows where contract terms drive the flag. IT confirms export routes and access, but the inventory is an operating document, not an IT asset list.
Should timesheets be in the inventory?
Yes. Timesheets and utilization records show how effort was actually spent across roles and project phases, which complements staffing plans. They contain employee personal data, so flag them accordingly and check your employee notices before any reuse beyond operations and billing.
How often should the inventory be updated?
Update it whenever the firm adds or retires a system, signs a contract with unusual data terms, or starts a reuse project such as an internal AI tool. A light review during annual planning catches drift that nobody reported along the way.
Is the inventory itself confidential?
Treat it as internal and confidential, but keep it free of client data. Because it records metadata such as system names, record families and date ranges, it can circulate among partners, counsel and advisors without exposing any engagement or any client's information.
Should the inventory include records from acquired firms?
Yes, as separate rows. Records inherited through an acquisition or a merger of practices may sit in legacy systems with different contract terms, client relationships and employee notices. List the source entity, the system and any transition agreement that governs the records, so rights review starts from the right documents.
Sources
- A CSV backup of a BQE CORE database is available for a fee, requested in writing by the company owner, typically in 1 to 3 working days. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.