By Rovaryn Digital · 11 min read
The Moment Restriction Data Goes Sideways
The work status report arrives — faxed, photographed, or handed in at the front desk. A coordinator reads it, summarizes the key numbers in an email to the supervisor, types a condensed version into the job offer letter, and later re-enters parts of it again when assembling the reimbursement application. By the third pass, "no lifting over 20 lbs, dominant right hand only, no overhead reach" has become "light duty, restricted lifting" in the supervisor's inbox and something slightly different still in the filed offer letter.
No single transcription was reckless. Each person was working from the last person's version, not the source document. That drift — from specific to vague, from the physician's exact words to an interpreter's summary — is where disputes begin. A carrier auditing a Washington Stay-at-Work reimbursement application wants to see that the light-duty work performed matched the attending provider's approved job description. A Texas BFOE must document restrictions accurately enough that an injured worker and their attorney cannot later argue the offer exceeded medical restrictions. An ADA accommodation request lives or dies on whether the employer's records show what the physician actually said.
The fix is not more careful re-keying. It is a single structured physician work restrictions intake that captures the restriction data once, in a form that every downstream document can draw from without retranslation.
This article explains what structured restriction intake means in practice, what data fields it must capture, how it connects to the rest of the return-to-work workflow, and where the common errors occur.
Why "Captured Once" Is a Process Design Principle, Not Just a Convenience
Return-to-work documentation is a chain. Every document that follows the first one — the job description, the offer letter, the supervisor's briefing, the reimbursement claim — should trace back to a single authoritative source of restriction data. When they do not, you create divergence risk: the possibility that two documents in the same file describe the same worker differently.
Divergence matters for several concrete reasons.
Duty matching depends on exact parameters. Matching a worker to a transitional task requires knowing the actual weight limit, the actual posture restrictions, the actual hours approved. A vague summary ("light duty") cannot drive a defensible match. A structured intake that records "lift max 10 lbs, no repetitive gripping right hand, seated or standing alternating, 4 hours per day" can.
Reimbursement eligibility is tied to what the physician approved — specifically. In Washington, a light-duty day worked outside the approved job description or approved hours is ineligible for Stay-at-Work reimbursement. (WA L&I, 2025) That ineligibility is not theoretical — it shows up at audit, when the reimbursement application is compared against the physician-approved job description. If the job description was written from a vague summary, the day-level comparison becomes difficult to defend.
ADA confidentiality compliance requires separation of restriction data from diagnosis data. Medical information must be kept on separate forms, in a separate medical record, accessible only to authorized personnel with a legitimate business need. (29 CFR 1630.14(c)(1); JAN, 2025) Supervisors and managers receive restrictions and accommodations only — not the diagnosis. (EEOC via Gordon Feinblatt, 2024) A structured intake form that separates the functional restriction fields from any diagnostic narrative makes it operationally straightforward to share what supervisors need without sharing what they should not see.
Audit trails require a document that is fixed at a point in time. A copy-and-paste from an email thread is not an audit record. A completed, dated intake form with an identified source document is.
What a Structured Physician Work Restrictions Intake Must Capture
The intake form is not a replacement for the physician's form — it is a structured extraction layer on top of it. The source document (the work status report, the Activity Prescription Form, the DWC-073, or whatever the treating provider sends) is retained in the case file. The intake form pulls the functional data from that source into fields your downstream documents can use.
The following fields are the minimum for a useful, defensible intake.
Identification fields
- Worker name and claim number
- Date of the physician's assessment (not the date you received the form — those are different)
- Physician name, practice, and contact
- Source document type (e.g., WA APF, TX DWC-073, OR 827, carrier form, letter)
- Date intake was completed and by whom
Physical demand fields — quantified where the physician provided quantification
- Maximum lifting weight (floor, waist, overhead — separately if specified)
- Carrying weight and distance
- Pushing and pulling force (if specified)
- Dominant/non-dominant limb differentiation if relevant
- Posture: seated, standing, walking, kneeling, crouching — permitted/limited/prohibited
- Overhead reach — permitted/limited/prohibited
- Fine motor / gripping / pinching — affected side and level of restriction
- Driving — prohibited, permitted, permitted with conditions
Hours and schedule fields
- Total hours approved per day
- Any restrictions on consecutive standing or sitting time (e.g., "must alternate every 30 minutes")
- Scheduled breaks required by restriction (distinct from normal breaks)
- Days per week if specified
Duration and review fields
- Restriction effective date
- Next scheduled physician review date
- Whether restrictions are stated as temporary, permanent, or unspecified
- Whether the physician explicitly approved a specific job description (yes/no, and if yes, document reference)
Prohibition and condition fields
- Specific tasks explicitly prohibited
- Environmental conditions prohibited (e.g., heights, confined spaces, extreme temperatures, vibration)
- Equipment the worker may not operate
- Any conditions on the restrictions (e.g., "may lift 20 lbs if using brace")
Documentation-chain fields
- Copy of source document retained: yes/no/location
- Physician-signed job description on file: yes/no/date
- Carrier/TPA notified: yes/no/date
- Restriction data entered into case tracking system: yes/no/date
This is a checklist of fields, not a prescribed form layout. Your intake form should be organized so that the physical demand fields align with the physical demand categories used in your transitional job descriptions — so that matching is a comparison, not an interpretation.
The Four Points Where Restriction Data Most Commonly Degrades
Understanding where errors enter helps you design the intake process to intercept them.
Point 1 — The physician form is read selectively. Work status forms, including state-issued forms like the Washington Activity Prescription Form and the Texas DWC-073, contain multiple sections. Coordinators under time pressure sometimes transcribe the headline restriction ("sedentary duty") while missing the specific prohibitions listed in a separate section. The structured intake form's field list forces a complete read of the source document.
For guidance on reading the Washington APF specifically, see the Activity Prescription Form guide on this site. For the Texas DWC-073, see the DWC-073 work status guide.
Point 2 — Quantitative restrictions are softened in retelling. "No lifting over 10 lbs with the right hand" becomes "limited lifting" in a summary. "Four hours per day" becomes "part-time." These softened versions are usable for casual communication but not for a job description, an offer letter, or a reimbursement application. The intake form preserves the original quantification.
Point 3 — Restriction updates are applied to some documents but not others. Restrictions frequently change at follow-up appointments. If the original restrictions live in a single dated intake record that is superseded by a new intake record at each update, you have a clear chronological chain. If restrictions are edited in-place in a summary email or spreadsheet, the prior version is lost and the change is undocumented.
Point 4 — The physician-approved job description is not retained or linked. In states with reimbursement programs — Washington in particular — the attending provider must approve the transitional job description in writing. (WA L&I Complete Stay at Work Guide, 2024) That signed approval needs to be in the file and linked to the specific restriction intake record it corresponds to. When the approval exists but is filed separately from the intake record, audits require reconstruction rather than retrieval.
Connecting Restriction Intake to Duty Matching and Downstream Documents
A restriction intake form that sits in a folder and is re-read every time someone needs restriction data has not solved the re-keying problem. The intake form's value comes from its use as the single source for every downstream step.
Duty matching. The physical demand fields from the intake feed directly into a comparison against the physical demands of candidate transitional tasks. If you are using O*NET-based demand data to structure your transitional job descriptions, the intake fields map to the same demand categories — lift weight, posture, hand use, hours. A structured intake makes that comparison explicit and documentable rather than a judgment call each time. See how O*NET-based duty matching works for the mechanics of that comparison.
Job description drafting. The transitional job description is written from the intake, not from memory of a conversation about the intake. The maximum weight in the description comes from the intake field; the hours come from the intake field; any prohibitions come from the intake's prohibition fields. When the physician reviews and signs the job description, that signature covers a document that reflects their form accurately.
Offer letter. A written offer of transitional duty — required by the Texas BFOE rules to meet 28 TAC §129.6 and useful in every other state as a contemporaneous record — draws its restriction language from the job description, which drew from the intake. The chain is clean and consistent.
Reimbursement applications. Washington's Stay-at-Work reimbursement application requires documentation that the work performed matched the physician-approved job description. When the intake, the job description, the physician approval, and the daily log are all keyed to the same source document and restriction record, assembling the application is a retrieval task. When they are not, it is a reconstruction task — slower, and more likely to surface inconsistencies.
Carrier and TPA communication. Many carriers want to see restriction documentation when a transitional assignment is established. A structured intake that can be exported or transmitted as a clean record — rather than a summary email — provides a more defensible communication artifact.
For a broader view of how restriction intake fits into the full case management workflow, see the return-to-work case management guide.
Physician Communication and the Intake Loop
Restriction intake is a two-direction process. You receive restriction data from the physician; you also send information back — specifically, the proposed transitional job description for the physician's review and approval.
That communication loop should be documented in the intake record. When did you send the job description? To which provider? What form did you use to transmit it? When did you receive approval (or modification)? Did the physician modify the job description before signing, and if so, was the intake record updated to reflect the approved version?
These steps are easy to lose in a high-volume caseload. A case management workflow that builds the outbound communication step and the approval receipt step into the intake process — not as separate tasks that rely on individual memory — is more likely to complete the loop before the worker's first day in the transitional assignment.
For guidance on structuring outbound physician communication as part of the RTW workflow, see the physician communication guide.
Getting the Intake Form Right the First Time
The practical question for most coordinators is not whether structured intake is useful — it clearly is — but how to stand one up without a multi-month implementation project.
The minimum viable intake is a single-page structured form — paper or digital — that covers the field categories above, assigns a case identifier, and requires a date and a completing-coordinator signature. It can be implemented immediately, before any software change.
The next step is ensuring the intake form's field structure aligns with the field structure of your transitional job descriptions, so that comparison during duty matching is a mechanical process rather than a re-interpretation each time.
If you are starting from scratch or replacing an informal process, the Work Restriction Intake & Physician Communication Kit provides structured templates designed to support this flow — intake form, outbound job description transmittal, physician approval record, and update log — formatted for direct use or adaptation to your existing case management process.
A Note on Scope
The intake form and the documents that flow from it are employer-side documentation tools. They capture what the physician communicated; they do not interpret, modify, or override the physician's judgment. Restriction intake is not a claims adjudication function, and the structured data it produces does not determine eligibility or benefits. Any question about whether a specific restriction or accommodation is clinically appropriate belongs with the treating provider. Any question about whether a specific offer or accommodation satisfies a legal standard belongs with qualified counsel or the relevant state agency.
The intake form's job is to make sure that what the physician said is what the rest of your program acts on — nothing added, nothing lost, nothing softened in translation.
Get the next RTW guide in your inbox
Practical guides and WA Stay-at-Work updates — no spam.
Automate the full RTW workflow
Transitional Duty Manager replaces manual RTW documentation with O*NET duty matching, WA SAW reimbursement packet export, and an immutable audit trail.
See how it works
