OHS in IT is no less important than in manufacturing — the risks are simply different. There are no machines or hard hats, but there are long hours at a computer, stress and fatigue, electrical hazards, office fire safety, wartime-related risks, and remote-work rules. The Racio team explains: legal requirements, typical IT risks, the minimum document set, how to run online briefings, and how to verify the system actually works. At the end — a 30-day implementation checklist.
Is OHS legally required for an IT company?
The basic principle is simple: if you employ people, the employer must provide safe working conditions. This applies to office-based work, hybrid formats, full remote work, and gig contracts. That’s why OHS in IT is not an “option” — it’s part of business responsibility.
Who is responsible:
- Employer (director/owner): process setup, appointing responsible persons, resources.
- Department/team leaders: enforcing rules on the ground, initial/refresher briefings.
- Employee: following instructions and reporting hazards.
A common IT misconception is “we’re not manufacturing.” But the law doesn’t divide businesses into “dangerous” and “safe” by industry — it looks at employment relationships and real workplace risks.
IT risk specifics: what makes it different
IT risks are rarely about machinery injuries — they are often “slow-burn” factors that accumulate over time: eyesight, back and posture, nervous system, sleep, burnout. Plus typical office risks: electricity, fire, evacuation, trips and falls due to cables or slippery floors. That’s why OHS in IT focuses on ergonomics, work режим, training, and workspace organization.
Psychosocial risks and burnout
Deadlines, overtime, night releases, client conflicts, constant requirement changes — all of this нагрузка mental health. If a company ignores it, turnover increases, focus drops, and mistakes rise, impacting product quality. In practice, OHS in IT here is not “psychology for show,” but clear rules: realistic schedules, breaks, overtime management, and support for team leads during crisis periods.
Long computer work: eyesight and musculoskeletal risks
8–10 hours at a screen create risks for the neck, lower back, wrists, and vision. The worst scenario is when discomfort becomes “normal,” until medical visits and sick leave are needed. In this block, OHS in IT comes down to basics: posture, monitor height, lighting, breaks, simple exercises, and proper workstation setup.
Workplace ergonomics: office and meeting rooms
Ergonomics is not “an expensive chair for a few.” It’s a minimum standard: the right desk height, a chair with back support, good lighting, удобное keyboard/mouse placement, and no glare. In a well-run OHS system, these rules aren’t left to personal preference — they are documented and checked during onboarding or workplace reviews.
Remote work: what changes in OHS
When people work from home, the company doesn’t “switch off” responsibility. The format changes: more online briefings, more self-checks, more digital evidence. OHS in IT for remote work usually includes simple home-workstation rules: lighting, chair, cables, extension cords, breaks, and safe use of electrical devices.
Information security and cyber hygiene as part of corporate safety culture
Cybersecurity doesn’t replace OHS, but it logically complements a broader safety culture in IT. Passwords, MFA, access hygiene, equipment rules — that’s company “hygiene.” Just don’t replace one with the other: OHS is about health and physical safety, while cyber hygiene is about protecting data and processes.
How to organize OHS in an IT company
A risk-based approach works best: identify risks first, implement measures next, then control and improve. In IT this feels very natural — like a backlog of tasks. That’s how OHS stops being a “paper project” and becomes a real system.
A practical logic:
- Risk assessment (office/home office/meeting rooms/server room/electrical switchboard room).
- Prevention (ergonomics, rules, briefings, electrical and evacuation routines).
- Control (checklists, walkthroughs, internal audit 1–2 times a year).
- Improvement (corrective actions after incidents or changes).
One more critical element is culture. If briefings are done only “for signatures,” people won’t take rules seriously. But when a team lead removes a cable from a walkway and asks people not to block an emergency exit — that shapes behavior better than any document.
OHS documents for IT/office: the minimum set
Most IT companies don’t need hundreds of instructions. They need a basic but accurate set that matches real processes and job responsibilities. OHS in IT often “breaks” here: files exist, but there are no responsible-person appointments, no logs, and no clear briefing procedure.
The minimum set usually includes:
- internal orders on OHS organization and appointment of responsible persons (for the office and sites);
- instructions: working with a computer, office safety rules, basic electrical safety, fire safety, evacuation actions;
- briefing logs or another approved way of recording (including online);
- training programs and knowledge checks — if required by role or work type;
- a remote-work procedure: how briefings are delivered, how acknowledgment is confirmed, how evidence is stored;
- medical checks and PPE — if needed (e.g., for technical staff or higher-risk work).
Briefings and training in IT: how to avoid formalism
The classic problem is “everyone signed the log and left.” But if an employee doesn’t know where the emergency exit is or what to do in case of smoke, a document won’t help. That’s why IT OHS benefits from short, regular, clear training formats.
What makes it work in real life:
- induction briefing as part of onboarding: 20–30 minutes + a mini test;
- initial workplace briefing: show real routes, fire exits, and risk zones (switchboard room, kitchen, server room);
- refresher briefings on a set schedule: better short and regular;
- unscheduled briefings after changes: relocation, ремонт, layout change, new equipment;
- for remote work: video/instruction + confirmation + evidence stored in the HR system.
Online works well if you have three things: concise content, understanding verification (test/quiz), and proof (protocol/log in the system).
Office and “home office”: an ergonomics checklist
Ergonomics is the simplest way to reduce risk in practice. Ideally, the company provides a short checklist and asks employees to self-assess quarterly. This makes OHS part of routine, not a “once-a-year” event.
2-minute checklist:
- monitor at eye level, comfortable distance, no glare;
- chair supports the lower back; feet on the floor or a footrest;
- keyboard and mouse at the same height; wrists not bent awkwardly;
- sufficient lighting, no harsh contrast (“dark room — bright screen”);
- cables don’t create loops in walkways; extension cords aren’t overloaded;
- breaks are taken: at least 5 minutes every 50–60 minutes;
- at home, the workstation is separated as much as possible (not “working on the couch with a laptop”).
How to measure that your OHS system works: simple KPIs
When a company has metrics, leadership can see whether you’re moving forward. In IT, this is natural: if we measure delivery, why not measure safety? For OHS in IT, a few indicators are enough — no “rocket science analytics” required.
- % of up-to-date briefings — how many employees have valid records/confirmations.
- Number of incidents and near-misses — not only injuries, but also “almost happened” cases.
- Response time to a hazard — from report to устранення (e.g., a cable in a walkway, a faulty socket).
- Anonymous channel for stress/burnout reports — and evidence that submissions are actually addressed.
A small practical detail: when an office adds a simple QR code “report a hazard,” people start reporting small issues. And those small issues are often what prevent bigger problems.
Common mistakes IT companies make
These are the mistakes that make OHS in IT “not work”:
- “We’re an office, so we don’t need OHS” — and then panic before an inspection.
- Briefings “for signatures” — employees don’t know basic actions in case of fire or incident.
- Remote work without rules — no documentation, no minimum workstation requirements.
- No responsible persons in teams — everything sits on HR or the office manager.
- Documents aren’t updated after changes — relocation or renovation happens, but instructions remain outdated.
30-day OHS implementation checklist for IT
A plan you can actually execute without “reorganizing everything.” Works for office and hybrid teams. This is how OHS in IT can be launched as a project with clear steps.
- Week 1: status audit. Collect documents, check emergency exits, electrical safety, and real office risks.
- Week 2: risks + plan. Create a short risk register and action plan: what to fix immediately vs. within a month.
- Week 3: documents. Internal orders, appointment of responsible persons, basic instructions, remote-work procedure.
- Week 4: briefings and training. Induction for new hires, initial office briefing, set up online tracking for remote staff.
In parallel: control and improvement. Start 1–2 KPIs, set up a reporting channel, and schedule refresher briefings.
FAQ
Do we need an OHS engineer if we have fewer than 50 employees?
Yes. Ukrainian OHS law requires that “OHS function responsibilities” be performed regardless of headcount. Someone must organize documentation, briefings, control, and coordination with team leads. Many companies cover this via outsourcing or a hybrid model.
How do you run briefings remotely?
Short online training, acknowledgement confirmation (test/quiz), and evidence stored in an HR system or another repository. The key is being able to prove the employee received and understood the rules.
Which documents are definitely needed for an office?
Orders appointing responsible persons, office safety instructions, working at a computer, fire safety, basic electrical safety, briefing logs/approved tracking method, and incident response procedures.
Are medical checks required in IT?
It depends on roles and conditions. For some office positions, medical checks may not be mandatory, but requirements can differ for drivers, technical staff, or specific tasks. It’s best to verify based on your roles/work list after a workplace assessment. The only case when the answer is clearly “no” is for employees under a remote-work contract format — but only when this format is set де jure.
Order an IT-focused OHS audit
If you need to quickly bring order and confirm whether OHS truly works in your IT company, Racio can help in three formats: an OHS audit for an IT office, documentation preparation and updates, briefing setup (including online), or full outsourcing support. At the start, a short assessment and a 30-day plan is usually enough — to make safety a system, not “a folder on a drive.”
Summary
In IT, safety doesn’t “shout” — it accumulates: chronic fatigue, back and eye strain, electrical issues, evacuation readiness, and remote work without rules. That’s why OHS in IT should be simple, evidence-based, and alive: identify risks, implement rules, train people, and set up control. Then the company becomes more resilient — for people and for business.
