By Rovaryn Digital · 9 min read
Why Vague Job Descriptions Slow Down RTW
A warehouse supervisor opens an email from the treating physician's office: the worker is cleared to return with a 20-pound lifting restriction and no repetitive overhead reaching. The supervisor needs to answer one question — does the role as actually performed on the floor that day require more than 20 pounds of lifting or any overhead reaching? If the only document on file is the HR job posting, the answer is "we're not sure," and the physician is in the same position. The worker waits.
That gap — between what an HR description says and what a job actually demands physically — is the most common reason transitional-duty offers stall before they start. The physician cannot approve a job description that does not describe the job in physical terms. The coordinator cannot propose a meaningful temporary assignment without knowing which tasks in the original role fall inside the restriction window and which do not. And if an ADA interactive-process question arises later, essential-function documentation is the factual foundation the analysis stands on.
A completed job demands and essential functions record solves all three problems from a single document. This article explains what belongs in that record, how to build it, and how to keep it current so it is ready the next time a claim opens.
What a Job Demands Record Actually Contains
A job demands record is not a job posting and not a performance review. It is a structured physical and operational profile of a specific position as it is performed — not as it is ideally described. The document has two connected layers.
The physical demands profile quantifies what the body does during a normal shift: lifting floor-to-waist, waist-to-overhead, and carry distances; pushing and pulling forces; walking and standing duration; sitting duration; reaching range (at, below, and above shoulder); gripping and fine-motor requirements; and environmental factors such as heat, vibration, or respiratory hazards. Each demand is rated by frequency (never, occasionally, frequently, continuously) and, where load is involved, by weight or force.
ONET Online provides a structured starting point for this layer. The ONET system covers 1,016 occupation titles and codes and includes over 19,000 occupation-specific task statements, with physical-demand ratings scaled by intensity and frequency for each occupation. Those ratings are a reasonable anchor for common roles, but they describe the occupation at the national level — they do not describe your facility, your equipment, or your production pace. An ONET rating for a general-warehouse-activities occupation will not capture that your receiving dock requires lifting 60-pound boxes from a low conveyor, or that your production line runs 10-hour shifts with mandatory overtime in Q4. Site-level observation and supervisor verification must complete what ONET begins.
Includes information from O*NET 30.3, used under CC BY 4.0. O*NET® is a trademark of USDOL/ETA.
The essential functions layer identifies which tasks are fundamental to the position — meaning the job exists to perform them, they occupy a significant portion of work time, or removing them would fundamentally alter the role. This language tracks the Americans with Disabilities Act's framework, which is why the record is useful for both RTW and ADA purposes. Essential functions are distinguished from marginal functions: tasks that are incidental, could be redistributed to other employees, or are performed rarely. Documenting that distinction before a claim opens is far more useful than reconstructing it afterward under legal pressure.
Together, the two layers give a treating physician something concrete to review and sign, give a coordinator a factual basis for duty matching, and give HR or legal a defensible essential-functions record if an accommodation request reaches the interactive process.
The Five Elements Every Record Needs
Regardless of the form or tool used, a usable job demands and essential functions record contains these five elements.
1. Position identification. Job title, department, shift (length and schedule), and the date the record was last verified in the field. Include the supervisor name who confirmed the physical requirements. A record without a verification date is unreliable because job conditions change — new equipment, layout changes, and production-rate adjustments all alter demands.
2. Physical demands grid. A table listing each demand category (lifting, carrying, pushing, pulling, standing, walking, sitting, reaching, gripping, kneeling, climbing, driving), its frequency (never / occasional: up to 33% of shift / frequent: 34–66% / continuous: 67–100%), and the relevant weight or force where applicable. Separate lifting into at least floor-to-waist and waist-to-overhead because restriction letters almost always distinguish between them.
3. Essential functions list. Numbered tasks that are fundamental to the role, each described in observable behavioral terms ("loads pallets to truck bed using powered pallet jack"), not outcome terms ("ensures shipping accuracy"). For each task, note whether it requires physical effort (and which demand category), uses specialized equipment, must be performed at a specific time, or requires a license or certification. Marginal functions go in a separate section with a brief note on how they could be redistributed.
4. Equipment and environmental conditions. Specific machinery operated (model number optional, type mandatory), PPE required (respirator, steel-toe, harness), and environmental exposures relevant to medical restrictions (heat index, cold storage, chemical exposure, noise level, vibration).
5. Physician signature block. Space for the attending provider's written approval of a specific transitional assignment, the dates approved, the restriction parameters in effect, and any conditions on the approval (e.g., "approved for four-hour shifts, ground-level stacking only"). Washington's Stay-at-Work program requires written provider approval of the light-duty job description; a pre-built signature block ensures that requirement is met on the first submission rather than requiring a separate document exchange. Confirm current form requirements directly with WA L&I before submitting.
Building the Record: A Practical Sequence
The most reliable approach runs in four steps and takes one to three hours for a frontline role the first time.
Step 1: Pull the O*NET base profile. Identify the closest O*NET occupation code for the role, download the physical-demands and task ratings, and use them as a draft checklist. This ensures nothing obvious is missed and provides a structured format to begin with. See O*NET duty matching explained for how to translate occupation codes into a usable starting point.
Step 2: Observe the job as performed. Walk the shift with the supervisor. Watch each task in real conditions. Time how long the worker stands, walks, sits. Measure lifting heights and estimate weights by weighing representative loads. Note the frequency of each physical demand. Where demands vary by shift or season, document the peak as the standard — restrictions must hold at the hardest point of the role, not the easiest.
Step 3: Draft with the supervisor, verify with workers. A supervisor understands the job structurally; experienced workers often know the physical peaks better than anyone. Draft the physical demands grid after observation, then review it with two or three workers currently in the role. Correct anything that does not match what they actually experience. Have the supervisor sign off on the final version.
Step 4: Stage for physician use. Format the document so that the physical demands grid is on the first page and the essential functions list is on the second. The physician's signature block should be the last element, with a clear instruction that approval covers the specific parameters listed — not the role in general. When a claim opens, send this document to the provider's office alongside the transitional-duty offer. For an overview of how to structure that offer letter itself, see the light-duty job description guide.
How the Record Connects Across the RTW Process
A completed job demands and essential functions record is not a one-time form — it is a reusable asset that intersects with multiple points in the RTW workflow.
Duty matching. When a coordinator is building a transitional assignment, the physical demands grid is the comparison document. The worker's restriction profile (from the attending provider's form) is set against the demands of candidate tasks. Tasks that fall inside the restriction window are candidates; tasks that exceed it are excluded. That comparison is the core of duty matching. The transitional duty task bank guide explains how to build a library of pre-vetted assignments organized by physical-demand level so this comparison runs quickly when a claim opens.
Physician communication. Providers who receive a vague description of a job are conservative — appropriately so. A provider who receives a specific physical demands grid can make a precise determination. The same document that was used to build the transitional offer becomes the physician's review document. When approval comes back in writing, attach it to the case file and note the effective dates.
ADA interactive process. If a worker's condition becomes a disability under the ADA, the essential functions layer of the same record is the starting point for the interactive process. The distinction between essential and marginal functions is central to determining whether a reasonable accommodation is available and what it looks like. Documentation built before the claim opens — not assembled under litigation pressure — carries more weight. See ADA and workers' comp interactive process for how that process runs and what employers are expected to document.
Audit and carrier review. Carriers and TPAs reviewing a claim file look for evidence that the transitional-duty offer was genuine — that the employer had a real, documented position, not a manufactured role. A signed, dated job demands record with supervisor verification is that evidence. It also supports a Washington Stay-at-Work reimbursement application: the program requires an approved written job description, and a pre-built record with a physician signature block satisfies that requirement cleanly.
Keeping Records Current
A job demands record that reflects conditions from three years ago can create more problems than having no record at all. A restriction approved against an outdated physical profile may not hold in practice — and a physician who learns the actual demands differ from the approved description will lose confidence in future submissions.
Build a review trigger into the process: any equipment change, layout change, or significant production-rate change prompts a record update before the next claim opens. Annual verification by the supervisor — a ten-minute desk review of whether the physical demands grid still matches conditions — is sufficient for stable roles. Record the review date and the reviewer's name in the document header each time.
When a new role is created or an existing role is significantly redesigned, complete the record before the position is filled. The cost of one hour of observation up front is small against the delay of reconstructing demands during an open claim.
Starting Point for Your Records
The Job Demands & Essential Functions Workbook provides a structured template built around the five elements above — physical demands grid, essential/marginal functions table, equipment and environment section, and physician signature block — formatted for immediate field use and physician submission. It is designed to serve as both the coordinator's duty-matching reference and the physician's approval document in a single package.
Download the workbook, complete one record for your highest-frequency injury role first, and have it staged before the next claim opens.
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
