Skip to content

Systems and records

What dates and contract conditions belong in a placement guarantee task?

By SourceX Editorial · Reviewed by Noah Loul ·

10 sections

Short answer

A placement guarantee task needs the guarantee terms in force for that placement, the dates that start and stop the clock (offer, agreed start, actual first day, departure, invoice due and payment), the departure reason as the contract classifies it, any client conditions such as timely payment or notice, the remedy chosen, and the evidence behind each. Without the dates and conditions linked per case, nobody can tell whether the obligation applied.

License terms

Recruiting placement

This page covers what dates and contract conditions belong in a placement guarantee task.Illustrative

Key takeaways

  • A guarantee outcome is computed from dates and conditions; the guarantee period typed into the ATS is only one input.
  • The contract decides which date starts the clock, whether the actual first day, the agreed start or another date, and the ATS may hold several start dates.
  • Client-side conditions such as payment by the due date and written notice of departure can decide the case before the departure reason does.
  • Departure reasons are sensitive employee information: classify them into contract categories and drop the narrative before a case leaves the firm.
  • Label each case with its outcome only when every date and condition has evidence; otherwise leave it unresolved and route it to review.

What dates and contract conditions belong in a placement guarantee task?

A placement guarantee task belongs together only when it holds the terms that applied to that placement, every date the terms count from, every condition the client or firm had to meet, the departure as the contract classifies it, the remedy that followed, and a pointer to the evidence for each. Recruiting placement guarantee data is useful for AI work, and for the firm's own reporting, only in that linked form.

A permanent placement agreement may promise something if the hired person leaves within a set period after starting: a replacement search, a credit or a partial refund. Whether that promise was triggered is not a field anyone types. It is an answer derived from the start date, the departure date, the departure category, and conditions such as whether the client paid on time and told the firm promptly. A task brief has to carry those inputs so a reviewer, or a model, can reproduce the answer and see why it came out that way.

This page gives that brief field by field, explains which dates and conditions usually decide the case, and shows one illustrative case resolved two ways depending on which start date is used.

Why the placement record alone cannot settle a guarantee

The placement record stores the agreed period, not the facts that decide whether the period was met. Bullhorn's public REST entity reference is a good example of what an applicant tracking system holds: its Placement entity has a daysGuaranteed field, described as the number of days the candidate is guaranteed for a permanent placement, and a daysProRated field for the point after which a prorated portion becomes due.

Those two numbers are terms, not outcomes. The same entity carries separate dateBegin and employmentStartDate fields, and the reference notes that the employment start used for payroll can differ from the placement start date. Status values such as Completed or Terminated and a free-text terminationReason record what the recruiter entered, which may not match how the contract classifies the departure.

Edits matter too. Bullhorn's reference says placements cannot be modified directly; a user submits a PlacementChangeRequest for approval, with an approving user and an approval date. A start date that moved after the offer therefore leaves a trail, and the brief should keep it, because a guarantee computed from the original date and one computed from the approved change can disagree.

Which dates start and stop the guarantee clock?

Depending on the wording, the clock may start on the hired person's actual first day of work or on the agreed start, and stop on the last day worked or the date of notice; the contract controls, so the brief records every candidate date and names the one the contract uses. Counting convention matters as well: calendar or business days, and whether the first day counts as day one.

Keep the computed day count beside the inputs rather than in place of them. If a reviewer later finds that the contract counts from the employment start date rather than the placement start, the case can be recomputed instead of relabeled by hand.

Which dates start and stop the guarantee clock?
DateTypical system of recordRole in the guaranteeCommon trap
Offer acceptedATS submission or offer stageUsually none; sometimes starts an invoice clockTreated as the start of the guarantee period
Agreed start dateATS placement startStarts the clock only if the contract says soLeft unchanged after the start slips
Actual first day workedClient confirmation or payroll startUsual start of the guarantee periodNot recorded at all for direct-hire roles
Approved date changeChange request with approver and dateReplaces the agreed start for countingLost when only the current value is exported
Last day worked or notice dateClient email, ATS status changeUsual end point for the day countStatus change entered days after the departure
Invoice issue and due datesBilling or accounting systemFeeds payment conditionsDue date computed from the wrong start
Payment receivedAccounts receivableDecides whether a payment condition was metPartial payments recorded as paid
Client notice of departureEmail or portal messageDecides any notice conditionNotice given by phone with no record

Which contract conditions decide whether the obligation was met?

The conditions to check first are on the client side: paying the invoice by its due date, notifying the firm of the departure within a set window, and asking for the remedy in writing. The departure category comes next, because an agreement may exclude layoffs, position eliminations or material changes to the role from the guarantee.

At a glance

Which contract conditions decide whether the obligation was met

Write each condition as a test with a yes, no or unknown answer and an evidence pointer. Unknown is a legitimate answer; it is better than a guess, and it tells the reviewer which document to find.

Statute can also apply. California's employment agency law requires the contract with a fee-paying jobseeker (Civil Code 1812.504) to include a right-to-refund statement: when a jobseeker leaves for just cause, or is discharged for reasons other than work-connected misconduct, within 90 days of starting, the agency must reduce the charge to the temporary-employment rate and refund any excess within 10 days of a request. That rule protects the jobseeker and does not govern an employer-paid search contract, but a firm that places workers who pay for the service must record which regime applies to each case.

  • Period condition: did the departure fall within the guarantee period, counted the way the contract counts?
  • Payment condition: was the invoice paid in full by its due date, and was the due date itself computed from the right start?
  • Notice condition: did the client notify the firm within the agreed window, and in the form the agreement requires?
  • Departure category: is the departure covered, or excluded as a layoff, restructuring, role change or relocation?
  • Remedy condition: did the client choose a replacement, credit or refund, and within any deadline for choosing?
  • Regime: is this an employer-paid agreement, or a jobseeker-paid arrangement where state employment agency law sets the terms?

How do you join ATS, billing and client correspondence into one case?

Join on the placement, not on the person. The ATS placement id links the job order, the start dates and the status history; the invoice usually carries a placement or job order reference that links billing; and client correspondence about the start, the departure and the remedy has to be matched by date and job order, often by hand.

Export the history, not only the current values. A placement export that shows only today's start date and status hides the change request that moved the start and the day the status changed. Ask for the change requests or field-level edit history alongside the placement rows, and keep the timestamp of each edit as well as the effective date it set.

Expect gaps and record them as gaps. Direct-hire clients often never confirm the actual first day in writing, notice of a departure may have come by phone, and a replacement search may have been opened as a new job order without a link to the original placement. Each gap becomes an unknown condition in the brief rather than an assumption, and the share of cases with unknowns is itself a useful quality figure for the set.

Finally, pin the agreement. Guarantee terms can be negotiated per client and changed at renewal, so the version in force on the start date is the one that applies. Store the version identifier with the case so later amendments do not silently change the label.

The administrative task brief, field by field

The brief below is the asset: one row per field, the record it comes from, how privacy is handled before the case leaves the firm, and who signs off. A team can copy it into a spreadsheet or a JSON schema as is. Fields marked for counsel must be confirmed against the signed agreement, not the ATS defaults.

At a glance

The administrative task brief, field by field

Fill one brief per placement. Keep the outcome field blank until every condition has an answer and an evidence pointer, and store the date the brief was completed and the version of the agreement it relied on.

The administrative task brief, field by field
FieldWhat it holdsSource recordPrivacy handlingReview owner
case_id and agreement_versionStable case key and the signed terms version in forceContract repository, ATS placement idReplace ATS ids with a new keyCounsel
guarantee_termsPeriod length, counting rule, pro-rata point, exclusions, remedy optionsSigned agreement or terms scheduleNo personal data; mask client nameCounsel
start_datesOffer, agreed start, actual first day, approved changes with approver roleATS, change requests, client confirmationShift all dates by one per-case offsetOperations
end_dateLast day worked or notice date, with which one the contract usesClient notice, ATS status historySame per-case date offsetOperations
day_countComputed days in period and the rule usedDerivedNone neededOperations
payment_conditionInvoice due date, payment received, met or not metBilling and receivablesDrop invoice numbers and amountsFinance
notice_conditionNotice date, channel, met or not met or unknownEmail or portal recordKeep date and channel onlyOperations
departure_categoryContract category: covered, excluded or unknownATS terminationReason mapped to contract termsCategory only; drop narrative and health, leave or conduct detailPrivacy
remedyReplacement, credit, refund or none, and the date chosenClient correspondence, follow-up job orderLink the replacement case by key onlyOperations
outcome_and_evidenceObligation applied, did not apply or unresolved, with a pointer per inputAll of the abovePointers to internal records, never copiesCounsel

Worked case (illustrative): a start date that slipped one week

This case is invented to show the mechanics; the dates and periods are illustrative. The agreement offers a replacement search if the hire leaves within 90 calendar days of the start date, counting the start date as day one, provided the invoice is paid within 30 days of the start date. The client accepted the offer on March 3 with an agreed start of March 17. The start slipped, and an approved change request moved it to March 24. The client paid on April 20. The hire left on April 30, and the ATS status reads Terminated with a performance reason.

Counted from the agreed start of March 17, the invoice was due April 16, so the April 20 payment was late and the guarantee would not apply. Counted from the approved actual start of March 24, the invoice was due April 23, payment was on time, and the departure fell on day 38 of 90. The agreement excludes only layoffs and position eliminations, so a performance-related departure is covered and a replacement search is owed.

The two answers differ only because of which start date the system exported. A brief that kept just the current ATS value, or just the original one, would have produced a confident label that a reviewer could not check. Keeping both dates, the change approval and the contract's counting rule is what makes the case resolvable.

Cases that should go to counsel or privacy review before anyone labels them

Stop and route the case when the answer depends on reading the agreement rather than applying it. Typical triggers are a side letter or email that changed the terms, a departure the client describes as a restructuring after the hire was told the role was safe, a hire who moved to a different role at the same client, or a client that withheld payment because of a dispute about the replacement.

Narrow the scope rather than forcing labels. A set of cases where every condition was met or clearly failed is more useful than a larger set padded with guesses. Mark the rest unresolved, keep them out of any training or evaluation split, and record the reason so the next reviewer does not repeat the work.

Also stop when the evidence itself is sensitive: a departure caused by medical leave, a protected complaint or a legal dispute should be reduced to an excluded or unknown category, or removed, before any brief is shared.

What to strip from separation evidence before a case leaves the firm

Keep the contract category of the departure and drop everything that describes the person. Departure narratives often contain performance comments, health or family information and conduct allegations. California's Attorney General states that the CCPA exemptions for employment-related personal information expired on December 31, 2022, so applicant and employee data held by covered businesses now falls under the law's protections.

The client employer usually holds the authoritative separation records. Federal EEOC rules (29 CFR 1602.14) require employers to preserve personnel records, including those about termination, for one year from the record or the action, and to keep records relevant to a discrimination charge until it is resolved. A guarantee brief should point to the client's confirmation of dates, not copy the employer's personnel file, and should exclude any case under a legal hold.

Shift every date in a case by one random offset so intervals survive and calendar dates do not, replace names and ATS ids with case keys, and remove client names unless the client contract allows their use. De-identification reduces privacy risk; it does not create a right to license the records, which depends on the firm's client agreements.

Taking resolved guarantee cases into a licensing review

Resolved guarantee cases are linked operating records: terms, dated events, conditions and an outcome with evidence. That structure is what makes them useful for training or evaluating models that reason over contracts and schedules, and also what makes the rights and privacy review specific rather than general.

A staffing firm that licenses resolved cases through SourceX hands off the sourcing, rights review, contracting, data preparation, delivery and payment steps. The firm's signature on scope and terms comes first; no case is delivered before it. A staffing firm can find out whether it qualifies through a short company assessment; no candidate or placement data is uploaded for it.

Frequently asked questions

Does a placement guarantee start at offer acceptance or on the first day of work?

The signed agreement decides, so record the offer date, the agreed start and the actual first day, and note which one the contract names. If the start moved, keep the approved change and its date.

Is a replacement guarantee the same as a refund guarantee?

No. A replacement guarantee obliges the firm to run a new search, while a refund or credit guarantee returns or offsets part of what the client paid. An agreement may offer one or the other, or let the client choose within a deadline, so the brief should record the remedy options and which one was chosen.

Can the reason a hire left be included in a guarantee case?

Include only the contract category, such as covered, excluded as a layoff, or unknown. The narrative behind a departure often contains performance, health or conduct details that are sensitive employee information. Map the ATS termination reason to the contract category, then drop the text.

What if the ATS guarantee period differs from the signed agreement?

The signed agreement wins. ATS fields such as a default guarantee period can be set once per client or per firm and not updated when terms are negotiated. Record the agreement version used for each case and flag disagreements for counsel.

Do state employment agency laws affect placement guarantees?

They can when the jobseeker pays for the placement. California's Civil Code 1812.504, for example, requires the jobseeker's contract to promise a reduction and refund when a jobseeker leaves for just cause or is discharged for reasons other than misconduct within 90 days of starting. Employer-paid search agreements are usually governed by their own terms, so record which regime applies.

Sources

  • Bullhorn's Placement entity documents daysGuaranteed and daysProRated for permanent placements, separate dateBegin and employmentStartDate fields that can differ, and status and terminationReason fields. Source
  • Bullhorn placements cannot be modified directly; a PlacementChangeRequest is submitted for approval and records the approving user and approval date. Source
  • California Civil Code 1812.504 requires jobseeker contracts to state a right to a reduction to the temporary-employment rate and a refund within 10 days of request when a jobseeker leaves for just cause or is discharged for reasons other than work-connected misconduct within 90 days of starting. Source
  • The California Attorney General states that the CCPA exemptions for employment-related personal information expired on December 31, 2022. Source
  • 29 CFR 1602.14 requires employers to preserve personnel records, including those on termination, for one year, and records relevant to a charge until its final disposition. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies