For hiring managers

What is a pre-identified candidate? How MSP and VMS programs route them, and how agencies submit one

On this page
  1. Why do MSP and VMS programs have a pre-identified route?
  2. How does a pre-identified candidate move through the program?
  3. How does SAP Fieldglass handle a named worker?
  4. What does a pre-identified worker cost compared with a recruited one?
  5. How is a pre-identified candidate different from the other routes in?
  6. How should a staffing agency submit a pre-identified candidate?
  7. Which pre-identified mistakes cause problems?
  8. Questions people ask

A pre-identified candidate (also called a pre-identified, client-identified, referred or payrolled worker) is a contingent worker the hiring manager found on their own, such as a former contractor, a retiree or someone from their network, rather than one a staffing supplier sourced through the client's contingent workforce program. In a managed service provider (MSP) or vendor management system (VMS) program, that person is still brought in through the program: the requisition goes to one designated supplier, usually a payrolling supplier or the agency the worker already came from, which submits the named person, employs them and bills at a payrolling rate instead of a recruiting markup. SAP Fieldglass calls this a Named Job Posting (as of November 2026).

This page explains why programs have a pre-identified route, how the worker moves through it, what it costs compared with a recruited worker, and what a staffing agency should do when it receives one. For the master vendor and MSP models these programs run on, see MSP vs. VMS and what is a master vendor.

Why do MSP and VMS programs have a pre-identified route?

Allegis Global Solutions, an MSP, describes pre-identified workers as "those that are sourced outside of your regular contingent labor program, process and supply base." Managers will always find some people themselves. Without a route for them, those workers get hired off-program, at rates nobody approved and without the program's background checks, tenure limits and co-employment controls. The pre-identified route keeps the manager's choice and brings the worker inside the rules.

The mechanism is usually payrolling. Staffing Industry Analysts' lexicon defines payrolling as an arrangement in which a client "recruits or otherwise identifies personnel whose services it needs and refers them to be employed by a service provider", and assigned back to the client. The economics are covered in payrolling services explained.

How does a pre-identified candidate move through the program?

  1. The manager flags the worker when opening the requisition, choosing a "payrolled" or "named" template instead of a recruited one, with the worker's name and contact details.
  2. The program checks its rules: whether the role belongs in the program, whether the worker is a former employee or former contractor subject to a waiting period or tenure limit, and whether the proposed pay fits the rate card.
  3. The requisition goes to one supplier, not to the whole supplier list: the program's payrolling supplier, or the supplier the worker is already associated with.
  4. The supplier contacts the worker, confirms interest and the pay rate, and runs onboarding: background check, drug test if required, Form I-9 and any client policies.
  5. The supplier submits the named worker against the requisition in the VMS.
  6. The program creates the work order and the worker starts; timesheets and invoices then run like any other assignment.

Harvard's MSP manager training (2023, published on its campus services site) sets out the same sequence: job posting creation and approval, then onboarding and compliance with the payrolling supplier, then "Supplier submits worker to Job Posting in Fieldglass and PMO hires worker", with a payrolled timeline of 7 to 14 business days against 3 to 4 weeks for a recruited worker.

How does SAP Fieldglass handle a named worker?

SAP's own Fieldglass training lesson, Selecting the Job Posting Source (checked November 2026), describes the Named Job Posting:

  • It is for hiring managers who "have already identified the best fit candidate for a given position outside of SAP Fieldglass".
  • "The job posting is only sent to the supplier associated with the selected job seeker, and only that job seeker can be submitted for the job posting."
  • It starts from the Quick Create menu, with the Named Job Posting for Worker option on the Contingent Labor card; the manager selects the worker's record (the lesson notes that some organizations "re-hire many of the same workers"), and the create page adds a Created For field holding the worker's name.

Other VMS platforms have their own labels for the same idea; your program guide will name the template to use.

What does a pre-identified worker cost compared with a recruited one?

Less, because the supplier did no recruiting. The lexicon's entry on contractor payrolling says payrolling services "are typically billed at significantly lower mark-ups than traditional temporary staffing" for that reason. Two public examples, each one program's own terms:

ProgramPre-identified (payrolled) workerRecruited workerSource
Harvard MSP (2023 training)Markups of 19.25% to 20.5% in Massachusetts and 19.1% to 19.35% out of state, depending on the payroll provider; no conversion fee if Harvard later hires the workerMarkup capped at 40% (with one supplier on a trial at 50%)Harvard/DZX MSP manager training
Massachusetts statewide contract PRF85Flat fee of $1.75 per paid hour when the contractor acts as payroll service provider for "employees identified by the Buyer"Maximum markup of 36.5% of the hourly pay ratePRF85 contract user guide, as of November 2026

These are contract terms for two buyers, not market rates. They show the pattern a supplier should expect: a pre-identified worker earns a payrolling margin, not a recruiting one, and the program decides which applies. Tennessee's pro forma MSP contract in RFP 32110-38726 treats them separately too: it caps the MSP's own share of contingent workers at 10% but excludes workers provided through payrolling arrangements from that cap.

How is a pre-identified candidate different from the other routes in?

RouteWho found the workerWho employs themUsual pricing
Pre-identified (payrolled)The hiring managerA payrolling supplier in the programPayrolling markup or flat fee
RecruitedA staffing supplier, against an open requisitionThat supplierRecruiting markup within the rate card
Direct-sourcedThe company's own talent pool or platformOften a payrolling partnerPayrolling or platform fees
ConversionA supplier, earlierThe client, as its own employeeA conversion fee, if the agreement has one

The lexicon's definition of directly sourced contingent workers covers workers "not sourced from a third-party staffing supplier", which includes pre-identified people; the difference is scale. See direct sourcing vs. MSP.

How should a staffing agency submit a pre-identified candidate?

Submit only when the program sends you the requisition. Then:

  1. Check which case you are in. If you are the program's payrolling supplier, the payrolled rate applies. If the worker came to the manager through your agency, for example your own former contractor at that client, read the supplier agreement's candidate ownership and duplicate-submission terms before you accept a payrolled rate for someone you recruited.
  2. Get the worker's written right to represent for this requisition, even if they already know the manager.
  3. Confirm the pay rate the manager discussed fits the rate card and that the worker has agreed it.
  4. Run the program's full onboarding: the same background, drug and eligibility checks as a recruited worker, and Form I-9 as the employer.
  5. Submit in the VMS against the named requisition, with a clear note (template below).
  6. Record it as payrolled in your own ATS, so recruiters are not credited with a placement they did not source and margin reports stay honest.

A submittal note you can copy (bracketed fields are yours to fill):

Requisition:        [VMS req ID] - [job title] - [site]
Worker:             [full name]   Pre-identified by: [hiring manager]
Route:              [Payrolled / named posting]   Supplier: [agency]
Right to represent: [date signed]
Pay rate agreed:    [$ / hour]   Bill rate per program: [$ / hour]
Prior work at client: [none / former contractor via [supplier], [dates]]
Onboarding:         Background [cleared date]  Drug test [n/a or date]
                    I-9 [completed date]  Client policies [signed date]
Proposed start:     [date]   Tenure limit ends: [date, if any]

For what a full recruited submittal contains, see what is a candidate submittal; for VMS terms, what is a VMS in staffing.

Which pre-identified mistakes cause problems?

MistakeWhat it causesFix
Manager agrees pay with the worker before the program sees itA rate above the rate card, or a worker who feels misledRoute the name to the program first
Skipping checks because "we know them"Uneven screening between workers, and compliance gapsSame checks for every worker in the role
Agency submits a person the manager found without being askedA duplicate or ownership disputeSubmit only on a requisition routed to you
Rehiring a former employee as a contractor without checking program rulesTenure, waiting-period or classification problemsAsk the program office before the offer
Counting payrolled starts as recruited placementsInflated fill and margin figuresTag the route on every start

Questions people ask

What is a pre-identified candidate in staffing?

It is a contingent worker the hiring manager has already found, such as a former contractor, a retiree or someone from their network, rather than one sourced by a staffing supplier through the program. Allegis Global Solutions, an MSP, describes pre-identified workers as those sourced outside the regular contingent labor program, process and supply base. In a managed program the person is still brought in through the program, usually by a payrolling supplier.

How does a staffing agency submit a pre-identified candidate?

Only when the program routes the requisition to you, either as its payrolling supplier or because the worker is already associated with your agency. You then confirm the worker's interest and your right to represent them, run the same onboarding checks as any recruited worker, and submit the named person against the requisition in the VMS at the payrolled rate the program sets. In SAP Fieldglass, a Named Job Posting is sent only to the supplier associated with the selected worker.

Why is the markup lower for a pre-identified worker?

Because the supplier did not recruit the person. Staffing Industry Analysts' lexicon says payrolling services are typically billed at significantly lower markups than temporary staffing because the intermediary has not incurred recruiting costs. Harvard's 2023 MSP training, for example, listed payrolled markups of about 19% to 20.5% against a 40% cap for recruited roles.

Can a hiring manager just hire a contractor they already know without going through the MSP?

Most programs require that every contingent worker come through the program so rates, background checks, tenure limits and co-employment controls apply to everyone. The pre-identified or payrolled route is how the program lets a manager keep the person they found while still following those rules. Check your own program's policy before agreeing terms with the worker.

Is a pre-identified candidate the same as a direct-sourced worker?

Not quite. A pre-identified candidate is one named person a manager brings to one requisition. Direct sourcing is a program the company builds to source contingent talent from its own pool, often with a payrolling partner, at scale. Both avoid a staffing supplier's recruiting, which is why both are usually payrolled.