A carpenter shows up at 6:30 a.m. with a hand he hurt at home over the weekend. He says nothing, climbs a ladder at 9:00, and by 10:00 the incident is on your OSHA log and your experience modification rate. Or a worker leaves site at 3:30 with a strained back from moving material, says nothing at check-out, and calls in a claim two weeks later. Nobody can say whether it happened on your job.
Both situations come down to the same thing: you did not ask, and you did not write down the answer. A simple, consistent fit-for-duty check at check-in and check-out will not prevent every injury. It does give your supervisors a chance to intervene before work starts, and it gives you a record when questions come up later.
This article is general operational guidance, not medical or legal advice. Rules about health inquiries, medical confidentiality and recordkeeping vary by jurisdiction. Review your screening program with qualified counsel and, where appropriate, a medical professional.
What is a fit-for-duty check in construction?
A fit-for-duty check in construction is a short, consistent question asked when a worker checks in, and often again at check-out, to confirm whether the worker is able to work safely that day and whether they were injured during the shift. When a worker reports being sick or injured, the check routes them to a supervisor and records the report. It is a safety and documentation tool, not a medical examination.
Why ask at check-in and check-out?
The two moments answer different questions:
- At check-in: "Is this person able to work safely today?" A worker who is ill, injured, or otherwise not fit can be redirected before they get on a lift, operate equipment or work at height.
- At check-out: "Did anything happen today?" A worker who was hurt during the shift gets a clear, low-pressure prompt to report it while details are fresh.
Asking at both points creates a simple bracket around the shift. If a worker says they were fine at check-in and fine at check-out, and later reports an injury from that day, the record helps everyone reconstruct what happened. If a worker reports an injury at check-out, your team learns about it the same day instead of weeks later.
What a good fit-for-duty question looks like
Keep it short. A long questionnaire at the gate slows everyone down, and long questionnaires get answered on autopilot. Most programs use a single question with a few clear options.
| Moment | Question | Options | If the worker reports a problem |
|---|---|---|---|
| Check-in | How are you feeling today? | I'm fine / I'm sick / I'm injured | Optional note; either allow check-in and flag, or block and route to supervisor |
| Check-out | Were you injured during your shift? | No, I'm fine / Yes, I was injured | Note describing what happened; supervisor follow-up |
Allow or block?
Decide in advance what happens when a worker reports a problem at check-in. There are two common approaches:
- Allow and flag. The worker can still check in, but the report is recorded and the supervisor follows up. This suits minor issues and sites where supervisors are close at hand.
- Block and route. The worker cannot check in and is told to contact their supervisor. This suits high-hazard work where you want a conversation before anyone starts.
Either way, the worker should never feel punished for answering honestly. A screening program that discourages honest answers is worse than none.
Legal and privacy guardrails
Health questions touch areas of employment law that deserve care. A few principles to discuss with your counsel:
- Ask only what you need. Under the Americans with Disabilities Act, employers' medical inquiries of current employees are generally limited to those that are job-related and consistent with business necessity. A simple "fit to work safely today?" question is very different from asking about diagnoses or medications.
- Keep health information confidential. The ADA and EEOC guidance require medical information about employees to be kept confidential and separate from general personnel files. Limit who can see health logs and do not share them beyond those who need them.
- Apply it consistently. Ask everyone the same question, every time. Selective screening invites discrimination claims.
- Consider who is asking whom. On a multi-employer site, the GC may be screening subcontractor employees. Make sure the subcontracts and site rules cover this, and that each employer handles its own workers' follow-up.
- Check state and local rules. Some states have additional privacy and medical-information requirements. Confirm before rollout.
- It is not a substitute for injury recording rules. A worker's report through a screening tool does not replace OSHA's injury and illness recordkeeping requirements (29 CFR Part 1904) or your company's incident reporting procedure.
Step-by-step: rolling out a fit-for-duty check
- Write a one-page policy. What is asked, when, what happens with each answer, who sees the results, and how long records are kept. Have it reviewed by counsel.
- Decide allow vs. block for sick and injured reports. You can choose differently for each.
- Brief supervisors first. They need to know what to do when they get a report: talk to the worker, decide on light duty or sending them home, and document the decision through your normal process.
- Explain it to the crews. Cover it at orientation and a toolbox talk. Emphasize that the goal is to keep people safe, that honest answers are expected and that reports are confidential.
- Restrict access to the logs. Only people who need to act on health reports, typically safety managers and designated supervisors, should be able to view them.
- Review blocked check-ins and injury reports weekly. Look for follow-up gaps: a worker who was blocked and never contacted, or an injury report with no matching incident record.
- Connect it to incident reporting. An injury reported at check-out should trigger your accident or incident process the same day.
A sample policy outline
Your written policy does not need to be long. A one-page outline like this covers what most crews and supervisors need to know. Have counsel review the final version for your jurisdictions.
- Purpose. To help make sure everyone on site is able to work safely and that injuries are reported promptly.
- Who it applies to. All workers checking in to the site, including subcontractor employees.
- What is asked. At check-in: whether the worker is fine, sick or injured. At check-out: whether the worker was injured during the shift.
- What happens next. For each answer, who is notified and what the supervisor does.
- Confidentiality. Who can see health reports, where they are stored and that they are kept separate from general personnel records.
- Retention. How long health reports are kept and how they are deleted.
- No retaliation. A clear statement that workers will not be disciplined for reporting honestly.
- Relationship to incident reporting. Injury reports trigger the company's incident reporting procedure.
What supervisors should do with a report
The check only works if the response is consistent. Give supervisors a short playbook:
| Report | Supervisor action |
|---|---|
| Sick at check-in | Talk with the worker privately. Decide with them whether they can work safely, need a modified task, or should go home. Follow company policy and the worker's employer's policy. |
| Injured at check-in (off-site injury) | Talk privately. Confirm whether the injury affects their ability to do the planned task safely. Consider alternative tasks where appropriate. |
| Injured at check-out | Talk with the worker before they leave if possible. Start the incident reporting process the same day, including first aid or medical referral as needed. |
| Blocked check-in | Contact the worker promptly so they are not left waiting at the gate. Document the decision through normal channels. |
Supervisors should avoid asking for diagnoses or medical details beyond what is needed to decide whether the worker can work safely today.
Common mistakes
- Too many questions. Workers stop reading them. One question at each end of the shift is enough for most sites.
- Paper forms at the gate. They get lost, are hard to search and are visible to anyone walking past.
- No follow-up. If a report goes into a log nobody reads, workers learn that answering does not matter.
- Health data mixed into general records. Keep health logs separate and access-controlled.
- Using it to discipline. Screening should route people to help, not to punishment.
Fit-for-duty and broader site safety
A health check is one layer. It works best alongside the other basics:
- Site orientation before first check-in. Every worker should know the hazards and rules of the specific site. See our guide on jobsite visitor management with QR check-in for applying the same discipline to visitors.
- Prompt incident reporting. Make it easy to report accidents and near-misses from the field, with photos.
- Knowing who is on site. In an emergency, you need a reliable list of everyone who checked in and has not checked out. Our construction manpower report guide covers how accurate check-ins support this.
- Heat and environmental hazards. Several states, including California, Washington and Oregon, have heat illness prevention rules. A daily check can be one of the prompts that reminds supervisors to watch for symptoms.
How ADRO handles this
ADRO includes a Worker Health module that adds a fit-for-duty check to the check-in and check-out workers already do.
- Check-in question. When the module is enabled, workers are asked how they are feeling: I'm Fine, I'm Sick, or I'm Injured, with an optional note.
- Check-out question. At check-out, workers are asked whether they were injured during the shift, and can add a note describing what happened.
- Allow or block, your choice. Company admins decide separately whether to block check-in for workers who report being sick and for workers who report being injured. Blocked workers are told to contact their supervisor, and the report is still recorded.
- Health logs for follow-up. Admins can review every report by date, worker, project, location, type (sick or injured), phase (check-in or check-out) and whether check-in was blocked, and filter by any of those fields.
- Access control. Role-based permissions let you limit who can view health information, and an audit trail records changes.
- Connected to the rest of site safety. Safety orientations, accident reporting with photos, visitor check-in and presence alerts all live in the same platform.
To see how health checks fit with the rest of the check-in experience, including offline kiosks, read offline time tracking for jobsites with no signal, or explore the ADRO jobsite safety and workforce platform.
Key takeaways
- A fit-for-duty check is one short question at check-in and one at check-out.
- It gives supervisors a chance to intervene and creates a same-day record of injuries.
- Decide in advance whether reports allow or block check-in.
- Keep health information confidential, separate and access-controlled; review with counsel.
- Follow up on every report, and connect injury reports to your incident process.
Want to see it on your own jobsite? Book a 20-minute ADRO demo and we'll walk through it with your projects.