How to Build a Transitional Duty Task Bank Before an Injury Happens

Why a Task Bank Built After an Injury Is Always Too Late

Picture the call: a finishing line worker has a confirmed rotator-cuff strain and the attending physician has faxed a restriction sheet limiting overhead reaching to zero and lifting to ten pounds. The RTW coordinator has two business days before a lost-time classification attaches to the claim. She opens a blank document and starts typing.

That blank document is the problem. The task bank does not exist yet. She will spend the next several hours — pulled from every other obligation on her desk — hunting down supervisors, guessing at task names, and drafting restrictions she has never matched to physical demands. If the offer she assembles does not fit the physician's restrictions precisely, the carrier may reject it. If she gets it wrong and the employee re-injures on a task that was not properly scoped, the consequences compound.

The employers who move from injury notification to a valid written offer in under an hour are not faster thinkers. They built a transitional duty task bank before anyone got hurt. They have a curated, site-specific inventory of tasks with documented physical demands, and when a restriction sheet arrives they are matching rather than inventing.

This article explains how to build that inventory: where to start, how to make it site-specific, how to keep it current, and what makes an entry usable when a physician is reviewing it.

---

What a Transitional Duty Task Bank Actually Is

A transitional duty task bank is a structured library of discrete work tasks — not full job titles — that your site can offer to an injured worker under physician-imposed restrictions. Each entry answers four questions:

1. What does the worker do? (a specific, observable task, not a vague job function)
2. What are the physical demands? (lifting limit in pounds, posture, repetitive motion, duration on feet)
3. What department or crew owns it? (so a supervisor can actually absorb the person)
4. What is the available capacity? (hours per day, days per week the task is genuinely available)

The bank is not a list of job titles. "Light duty" is not a task. "Warehouse associate" is not a task. "Applying shipping labels to outbound cartons at a sit-stand workstation, maximum 8 lbs, no overhead reach" is a task. The specificity is not bureaucratic — it is what a physician needs to approve an assignment and what a claims adjuster needs to honor it.

A well-built bank typically contains 20 to 60 entries for a mid-sized single-site operation, drawn from every department that could realistically absorb a restricted worker. The tasks do not need to be glamorous or permanent. They need to be real.

---

Layer One — Seed from O*NET, Then Strip It Down

The fastest way to start is to use the national occupation data as a scaffold, then replace generic language with your site's actual conditions.

The O*NET database contains 1,016 occupation titles and codes and more than 19,000 occupation-specific task statements, each tagged with work-activity categories, physical-demand levels, and tools used (DOL / O*NET OnLine, 2025). For any occupation code that maps to a role at your site, O*NET gives you a starting list of tasks with at least a generalized physical profile. Pull the task statements for your four or five most common job families — material handlers, production operators, maintenance technicians, drivers, patient-care aides, whatever your operation runs — and use them as a first draft.

Includes information from O*NET 30.3, used under CC BY 4.0. O*NET® is a trademark of USDOL/ETA.

The national data will overstate complexity in some areas and understate physical demand in others. A warehouse picking task in the O*NET database does not know your racking height, your floor surface, or whether your pickers pull a cart or use a powered tugger. That is exactly what the next layer corrects.

For how O*NET task statements translate into duty-matching logic, see How O*NET Powers Duty Matching in RTW Programs.

---

Layer Two — Site-Scope Every Entry

After you have a draft list of tasks from O*NET, walk each department with a supervisor and a tape measure. For each task, document:

Physical demand parameters — the six that matter for restriction matching:

Parameter	What to document	Why it matters
Maximum lift (lbs)	Heaviest object actually handled, not the job-title limit	Physician restrictions cite specific weight limits
Carry distance	Feet, not "short distance"	Affects shoulder and back load
Posture	Seated / standing / stooped / overhead / combination	Single-plane restrictions are common
Repetitive motion	Body part, cycles per hour	Carpal-tunnel and tendon restrictions often cite frequency
Duration on feet	Hours continuous, hours total shift	Lower-extremity and lumbar restrictions use both
Environmental conditions	Wet floors, temperature extremes, vibration, respirator required	Some restrictions are environmental, not postural

Operational parameters — the three that determine real availability:

• Department and supervisor name. If no named supervisor owns the task, it will not absorb anyone on an actual RTW day.
• Available hours per day and days per week. A task that exists three mornings a week is a three-morning-a-week offer. Do not misrepresent availability — it creates problems when the worker shows up on a day the task does not exist.
• Minimum effective capacity. Some tasks require a worker to be productive enough to justify the assignment (e.g., a QC visual inspection task requires acceptable eyesight and concentration). Note those thresholds plainly.

Documenting these parameters for the first time takes roughly two to three hours per department for a site with fewer than 200 employees. It is the highest-yield two hours in your RTW program because every subsequent claim draws from it. For guidance on how physical demands connect to essential-functions documentation, see the Job Demands and Essential Functions Guide.

---

Layer Three — Structure Each Entry for Physician Review

A task bank entry that cannot go directly into a light-duty job description is only half finished. Physicians approve specific written descriptions of the work, not a spreadsheet row. Structure your entries so the description can be copied or adapted with minimal editing.

A usable entry follows this pattern:

Task: Sorting and scanning inbound returns at the receiving desk. Physical demands: Sedentary to light. Maximum lift 15 lbs (tote bins from belt to table). Seated 80% of shift with option to stand at height-adjustable workstation. No overhead reach. No kneeling or crouching. Repetitive hand use (scanning trigger, mouse): approximately 300 cycles/hour. Environment: Climate-controlled, dry floor, no respirator required. Department: Receiving — Supervisor J. Harmon. Availability: Monday–Friday, 7:00 a.m.–3:30 p.m. (30 available hours/week). Last verified: [date] by [name].

The "last verified" line is not decorative. A task that existed at this physical demand level eighteen months ago may not exist the same way today — equipment changes, layout changes, and staffing changes all affect what a worker will actually do. A stale entry used to justify an offer that does not match real conditions creates a re-injury risk and an audit exposure.

For detailed guidance on what makes a light-duty job description defensible at the carrier and physician level, see How to Write a Light-Duty Job Description That Holds Up.

---

How to Keep the Task Bank Current Without Rebuilding It Every Year

A task bank that is accurate at build time and never touched again has a shelf life of roughly one to two production cycles, depending on how often your operation changes equipment and layout. The goal is lightweight maintenance, not a full annual rebuild.

Three triggers that require an immediate update:

1. Equipment or process change that alters physical demands. A new conveyor height, a powered lift assist, or a shift from manual to automated packing changes the physical profile of every task in that area.
2. A restriction the bank could not match. If a coordinator searched the bank and found no suitable task for a specific restriction pattern (e.g., unilateral hand restriction with no pinch grip), add the task or tasks that would have fit. Let operational reality train the bank.
3. A task that was offered but could not actually be delivered. If a supervisor reported the task was unavailable on the day the worker reported, the availability entry is wrong. Fix it.

Scheduled maintenance — once per year at minimum:

Walk each department entry with the supervisor, confirm physical demands have not materially changed, update the "last verified" date, and remove tasks that no longer exist. For most single-site operations this is a half-day exercise once the bank is built.

Who owns this:

Assign one named person — the RTW coordinator or safety manager — as the bank's custodian. The bank does not maintain itself, and shared ownership means no ownership. The custodian is the person who fields the "do we have something for a shoulder restriction?" call at 8:30 a.m. on a Monday.

---

Seeding the Bank for Specific Sectors

The physical demand profiles that appear most often differ meaningfully by industry. A few starting points by sector:

Manufacturing: Inspect and sort finished parts at a seated QC station; apply labels or documentation to packaged goods; perform visual quality checks on conveyor output; calibrate instruments under bench conditions; update production logs and maintenance records.

Construction: Perform site safety observations and documentation; conduct tool inventory and inspection; assist with permit-to-work administration; perform sedentary estimating or plan review tasks in the site trailer.

Healthcare: Assist with scheduling calls and patient check-in (non-clinical); perform medical records filing and scanning; stock supply rooms within lifting limits; serve as a patient-flow coordinator at a fixed station.

Warehousing/transportation: Scan and verify inbound shipments at a fixed station; perform inventory audits (cycle counts, seated or light walking); assist with carrier documentation and manifests; perform workstation housekeeping within lifting limits.

None of these are complete entries — they are starting points to walk back through Layers Two and Three with your supervisors. They illustrate why site-scoping matters: the same "inventory audit" task in a three-story racking facility with a pallet jack and in a flat-floor small-parts operation have entirely different physical demand profiles.

For a complete template set built around these sector patterns and pre-mapped to common restriction categories, the Modified Duty Job Description Library provides ready-to-customize entries your team can site-scope in hours rather than building from scratch.

---

From Task Bank to Offer: The Matching Step

A task bank is an input to a process, not a finished product. When a restriction sheet arrives, the matching step works like this:

1. Pull the restriction parameters from the physician's note (lifting limit, postural restrictions, hours per day authorized, any environmental restrictions).
2. Filter the task bank for entries whose documented physical demands fall within — not at the edge of — all stated restrictions. When in doubt, err toward the more conservative interpretation of a restriction and confirm with the treating provider.
3. Confirm availability with the supervisor on the actual proposed start date before drafting the offer.
4. Draft the written offer using the task entry as the source document. The offer should describe what the worker will actually do, not just reference a task-bank category.
5. Submit the written job description to the attending provider for approval before the worker reports.

The matching step is a judgment exercised by a person — the RTW coordinator, HR manager, or supervisor — using the bank as a decision-support resource. Task bank entries are not auto-assignments. The coordinator reviews the match, confirms the offer is realistic, and makes the call.

For an overview of how to structure the broader RTW program that the task bank feeds into, see How to Build a Transitional Duty Program.

---

Start Before the Next Claim Opens

The window between injury notification and a lost-time classification is narrow — and in most operations, the coordinator is managing it alongside two or three other open claims. A transitional duty task bank built in advance compresses that window from hours to minutes. The physician gets a specific, pre-verified task description. The supervisor has already confirmed availability. The coordinator is matching, not inventing.

Building the bank is a defined project, not an ongoing obligation: a few hours per department, one named custodian, and a maintenance cadence tied to process changes and annual walk-throughs. The output is a library that serves every claim your site will ever have.

Download the Modified Duty Job Description Library for pre-built, sector-specific task entries your team can site-scope and load into your RTW workflow today.