Turn a client’s exclusion request into a reviewed, precisely scoped placement decision—and check that booking changes match it before closing the case.
A client says, “Do not send this worker back.” The coordinator records a DNR flag, but next week’s booking remains active. Another recruiter reads the same flag as a ban on every client. Both errors start with the same problem: the request, the agency’s decision and its scheduling effects were treated as one thing.
A staffing do not return review workflow should keep those records separate. This guide is for agency operations teams placing temporary employees with clients. It covers the Manage → Review → Assign boundary: review the request, implement only the approved restriction, and hand eligible workers back into assignment review. It is not a dismissal procedure or a rulebook for independent contractors.
Define what the restriction actually changes
Write “do not return” in full in the case record. Specify the client, site, department or role affected, the effective time and the person authorized to decide. A request concerning one department should not silently become an agency-wide eligibility decision.
Separate four questions before changing the worker record:
- What did the client request? Preserve its wording and the authorized contact’s identity.
- What has the agency reviewed? Identify verified facts, disputed statements and missing information.
- What may change now? Record the exact approved boundary and any interim control separately.
- What remains undecided? Other-client eligibility, employment status, existing bookings and review outcomes need explicit treatment.
Actual platform behavior varies. NextCrew’s DNR documentation, for example, distinguishes hiding future client jobs from handling existing bookings and manual assignments. That is a useful reason to test every booking route, not evidence that another system behaves the same way.
Open a decision record, not an unexplained flag
The receiving account manager owns the case until a named reviewer accepts it. A scheduler owns booking actions; an authorized HR or employment reviewer owns personnel decisions. A client request does not transfer those responsibilities to the client.
Use the following record specification as recommended operating practice. Your organization’s approved policy, agreements and applicable rules determine the decision rights and deadlines.
| Record group | Required working detail | Owner and release condition |
|---|---|---|
| Identity and request | Worker reference, assignment, client/site/unit identifiers, requester authority, original message and receipt time | Account manager; request is attributable and scope is understood |
| Evidence and response | Specific event, date, relevant work standard, source records, worker account and unresolved differences | Reviewer; distinguish allegations from findings |
| Interim instruction | Immediate action, reason, affected shifts, authorizer, review time and communication owner | Qualified operational/safety owner with HR involvement as appropriate; not mislabeled a final finding |
| Reviewed decision | Approved scope, effective time/time zone, rationale, approver, other-client eligibility and linked employment review if needed | Authorized agency reviewer; no ambiguity passed to scheduling |
| Implementation and communication | Each affected booking, change result, worker/site contact evidence, unresolved contact and scheduler handoff | Scheduler; actual effects checked against the decision |
| Review or reversal | Next review date, review owner, new evidence, approved change, effective time and verification results | Authorized reviewer; history retained under approved record rules |
Keep sensitive evidence in the approved restricted record. A scheduler needs an actionable eligibility instruction, not unrestricted access to medical information, allegations or an investigation narrative. Record access and retention decisions through your organization’s responsible owners rather than copying the case into a general talent spreadsheet.
Separate urgent protection from a final conclusion
If someone may be at immediate risk, activate the established emergency or safety procedure and involve the qualified owner. Do not wait for routine case closure. At the same time, document any interim assignment instruction as temporary and reviewed; it should not quietly become a permanent adverse finding.
Ask the client for specific facts rather than accepting “not a fit” as a complete explanation. Give the worker an appropriate route to provide their account. ESHYFT’s published DNR policy illustrates one provider’s worker-response and removal-of-restriction arrangements; it is not a universal procedure or deadline.
Escalate the reason, not just the missing paperwork
In the United States, the EEOC’s contingent-worker enforcement guidance, particularly Questions 7–8, explains that a staffing firm can be liable when it honors discriminatory assignment or removal requests. It also discusses corrective measures within the firm’s control. The guidance explains existing requirements; it is not itself binding law.
Have HR or qualified counsel review suspected discrimination, retaliation, accommodation issues or disputed employment consequences. Do not assume that obtaining a written client instruction makes the action lawful. Use the contingent worker complaint process when a worker raises a concern, while keeping the placement decision and its owner visible. Applicable rules and corrective action depend on the facts and jurisdiction.
Test the scheduling boundary before closing the case
A correctly worded decision is not proof of correct implementation. Use the matrix below with a scheduler, system owner and reviewer. Fill in the actual observed result and evidence reference for each applicable row. For configuration testing, use approved test records rather than creating real bookings for a restricted worker.
| Test case | Expected result to define | Evidence to retain |
|---|---|---|
| New booking in the restricted unit | Cannot proceed without the approved eligibility decision being enforced through the defined control | Booking attempt result; manual or system control used |
| Different unit at the same client | Follows the exact approved scope, not an assumed client-wide rule | Unit identifiers and reviewer-confirmed outcome |
| Different client | Uses separately confirmed agency eligibility; no accidental global exclusion | Eligibility review and matching result |
| Already-confirmed future shift | Receives an explicit reviewed disposition, not an assumption that a flag cancelled it | Original booking, change instruction and contact evidence |
| Recurring booking or copied roster | Does not recreate a prohibited assignment unnoticed | Next occurrence/copy check and responsible owner |
| Manual assignment or administrator route | Uses the same decision boundary; any override requires authorized review | Route tested and override decision, if applicable |
| Duplicate worker profile | Identity resolution prevents a second profile bypassing the intended restriction | Profile references and identity-owner resolution |
| Approved reinstatement | Releases only the restriction actually reversed; other valid restrictions remain | Reversal authority, scope, effective time and retest |
| First booking after reinstatement | Still requires normal availability, readiness and assignment approval | New assignment acceptance and readiness record |
If a system cannot enforce a required boundary, identify the manual check, owner and point in the booking process where it must occur. Record the limitation and obtain the appropriate operational approval before relying on that control. Do not label an untested warning or hidden job listing a hard block.
Keep the case open when an affected shift has no accepted disposition or an implementation result contradicts the decision. Work completed, pay review and client replacement arrangements stay in their own linked processes; a restriction record should not overwrite them.
Work through a disputed unit-level request
Illustrative scenario: a client supervisor asks an agency to exclude Worker A from all of its locations after a disagreement in Unit North. The worker disputes the supervisor’s account. The account manager preserves both accounts and asks the agency reviewer to assess the reason and requested scope. No allegation is recorded as a proven fact.
The authorized reviewer records an interim instruction for specified Unit North bookings while the concern is reviewed, with a named review time. The scheduler checks the worker’s confirmed shifts individually and records the appropriate contact and coverage actions. A Unit South booking is referred for an explicit decision because the original client request and interim scope differ; the scheduler does not guess.
Later, the reviewer authorizes removal of the Unit North restriction. The system owner clears only that restriction and retests future, copied and manual booking routes. The recruiter then confirms availability and follows the candidate redeployment process. Reinstatement is not proof of acceptance of a new shift, and this invented example does not establish what action would be lawful in a real dispute.
Where Workhint fits
Workhint’s Workflow Engine describes defined request steps, role-based approval routing, and requirements for details, files or notes before progression. These are relevant building blocks for separating an account manager’s request from an authorized review decision.
The Staffing Managers solution describes worker profiles, documents, approval status and matching with manager review. That supports a configuration discussion about the worker and assignment records involved. It does not establish a native DNR feature, automatic investigation, legal determination or restriction across every booking route.
Use the test matrix to establish which scope rules, role permissions and assignment checks your proposed setup actually supports. Keep an explicit manual owner for unsupported steps rather than assuming an approval status performs them.
FAQ
Does a client DNR automatically end agency employment?
Do not use a client restriction as an employment-status shortcut. Record the site or client decision separately and refer employment consequences to the authorized agency reviewer under applicable rules.
Does adding a DNR flag cancel upcoming shifts?
Not necessarily. Check actual platform behavior and each confirmed booking. Preserve the original assignment and record the reviewed change, communication and follow-up owner.
When should a restriction be reviewed?
Set the review owner and date when the decision is recorded, based on approved policy and the case. New evidence, a disputed scope or a reinstatement request may require earlier review. There is no universal expiry period in this guide.
What proves that reinstatement is complete?
The approved reversal, the actual record change, and successful checks of the affected booking routes. Keep the decision history; do not treat deleting a flag as the entire process.
Leave a Reply