Consulting and recruiting
VMS and MSP programs: who owns contingent workforce records?
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
In VMS and MSP programs, records created inside the client's vendor management system are generally controlled by the client or the program agreement, while a staffing firm's own ATS, recruiter notes and payroll records are generally its own, subject to confidentiality and privacy duties. The safe rule: carve out anything that originated in the VMS.
Key takeaways
- VMS records such as requisitions, rate cards, client feedback, approved timesheets and scorecards are generally controlled by the client or MSP under the program agreement.
- Records a staffing firm creates in its own ATS and payroll systems are generally its own, though confidentiality and privacy terms still apply.
- The same record often exists twice, in the VMS and in the agency's systems, and the two copies can carry different rights.
- Carve out anything that originated in the VMS or identifies the client program unless the agreement expressly allows the use.
- Candidate and worker personal data needs separate privacy review whichever system holds it.
Who owns contingent workforce records in a VMS program?#
Contingent workforce records in a VMS program are split by origin: the client and MSP generally control what is created inside the vendor management system, and the staffing firm generally controls what it creates in its own systems. Contracts set ownership, not the place a file happens to be saved.
Four parties are usually involved. The client buys contingent labor. The MSP runs the program for the client, sometimes as an independent firm and sometimes as part of a staffing company. The VMS is the software platform, such as SAP Fieldglass or Beeline. Suppliers, including your firm, submit candidates and employ or pay the workers.
The supplier agreement you signed with the MSP or the client, together with any terms that flow down from the client's own agreement, decides what you may do with program records.
How records flow through an MSP program#
Records in an MSP program pass through the VMS at almost every step, which is why so many of them end up in two places. Knowing who created each record is the first step in knowing who controls it.
- Requisition and job description: created by the client in the VMS.
- Sourcing, screening and recruiter notes: created by your team in your ATS.
- Submittal: created by you and stored in both the VMS and your ATS.
- Interview feedback and selection: created by the client in the VMS.
- Onboarding documents and payroll: created by you as employer of record.
- Approved timesheets and invoices: approved in the VMS and mirrored in your payroll and billing.
- Supplier scorecards and program reports: created by the MSP from VMS data.
Ownership table: VMS data, agency ATS data and timesheets#
The ownership table shows where each record type usually sits and who usually controls it. Treat it as a starting point for counsel's review, because supplier agreements vary widely between programs.
Duplicated records are where most mistakes happen. A submittal copied into your ATS feels like your record, and in part it is, but the client feedback stored beside it and the requisition it answers may not be.
| Record | Where it lives | Usual controller | What to check |
|---|---|---|---|
| Requisitions and job descriptions | VMS, often copied into your ATS | Client | Confidentiality definition in the supplier agreement |
| Bill rates and rate cards | VMS and your billing system | Client and MSP; your copy stays confidential | Restrictions on disclosing pricing |
| Candidate submittals | VMS and your ATS | Shared: your work product held in the client's platform | Candidate representation and data use terms |
| Client interview feedback | VMS | Client | Whether you may retain or reuse it |
| Approved timesheets | VMS, mirrored in your payroll | Client for the VMS copy; you for payroll records | Retention duties and audit rights |
| Pay rates and payroll records | Your payroll system | Your firm, as employer of record | Wage law retention and employee privacy |
| Recruiter notes and sourcing activity | Your ATS | Your firm | Whether notes quote client confidential details |
| Supplier scorecards and program reports | VMS or MSP reports | MSP or client | Usually confidential program information |
Contract clauses that decide the answer#
Contract clauses in the supplier agreement decide what you may keep and use, so read them closely before reusing any program record. Flow-down terms from the client's agreement with the MSP can be stricter than the supplier agreement suggests, so ask for them if they are referenced but not attached.
Keep a register of every program the firm has worked in, with the agreement version, its confidentiality and destruction terms, and the date the program ended. Without that register, nobody can say later which records came with which obligations.
- The definition of confidential information, and whether it covers all program information.
- Data ownership and permitted use clauses.
- Return or destruction obligations when the program or agreement ends.
- Data processing or privacy terms covering worker and candidate data.
- Restrictions on publicity and on naming the client.
- Audit rights the client or MSP holds over your records.
- Candidate ownership or representation rules for submitted candidates.
The carve-out rule for licensing#
The carve-out rule for licensing is simple: exclude anything that originated in the VMS or identifies the client program unless the program agreement expressly allows the use, and license only records your firm created, after personal data is removed. The rule is conservative on purpose, because program agreements often define confidential information broadly.
What remains can still be useful. Your own recruiter workflows, screening notes stripped of identifying details, sourcing sequences and the internal coordination behind submittals describe how recruiting work gets done. Even these need review where they quote client requirements or name the program, and some agreements reach further than expected.
Apply the rule at field level as well as record level. A recruiter note created in your ATS can still contain a pasted job description, a bill rate or a hiring manager's name, and those fragments carry the client's rights with them. Preparation should find and remove them, or the note stays out.
Illustrative: an IT staffing firm with most of its work in MSP programs#
Illustrative: a fictional IT staffing firm places most of its contractors through MSP programs at large enterprise clients. Its owner wants to know whether the firm's long recruiting history could be licensed and asks counsel to review the supplier agreements first.
Counsel finds that the agreements treat requisitions, rates, feedback and program reports as client confidential information, with destruction required at program end. The firm carves out every VMS-originated record and every field naming a client, keeps payroll on its wage law schedule, and limits any licensing review to its own ATS workflows with candidate details removed. The remaining scope is narrower than the owner hoped, but it is defensible.
How SourceX handles program-restricted records#
SourceX handles program-restricted records in the Rights step of the SourceX five-step transaction, before any preparation work starts. The firm's counsel confirms which records are the firm's to license, and carve-outs are written down rather than assumed.
The SourceX Evidence Packet for each package states provenance, licensing rights and permitted use, so the exclusion of VMS-originated and client-identifying records sits alongside the privacy record and the firm's release authorization. Laws and contract terms are assessed deal by deal with the firm's counsel.
Frequently asked questions
Can we export our submittal history from the VMS?
Some programs let suppliers download reports of their own activity and others restrict it. Even when a download is possible, the data may remain client confidential under the supplier agreement. Check the agreement and ask the MSP in writing before exporting or reusing program reports.
If we submitted a candidate, do we own that candidate's data?
No one owns a person, and candidate data is governed by privacy law as well as contracts. Your firm generally controls the records it created while recruiting, while the copy in the VMS falls under program terms. Representation rules about who submitted a candidate first are a separate commercial matter.
What happens to program records when an MSP program ends?
Supplier agreements often require return or destruction of client confidential information when the program ends, sometimes with written certification. Your own payroll and employment records usually stay with you under wage and tax retention rules. Map both before the program closes.
Can we use program data for our own internal benchmarks?
Possibly, if the agreement allows internal use and the benchmarks do not reveal client information. Aggregated internal reporting carries less risk than external use, but confidentiality clauses can still apply. Have counsel confirm before rate or performance data from a program feeds any product or published report.
Does the MSP's own staffing arm see our records?
In some programs the MSP belongs to a group that also supplies workers, which is why many program agreements include neutrality and confidentiality commitments. Ask how supplier data is separated, who can see your submittals and rates, and what the agreement says about the MSP's own use of program data.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.