Ten Employees or Fewer Can Skip the Alarm. OSHA Counts That Per Workplace, and Your Headcount Moves.

A regional operator has a store-sized location in a strip center with eight employees on a normal shift. The emergency action plan says that in an emergency the manager will shout and everyone will leave by the front or back door. It is a reasonable plan for eight people, and under OSHA's employee alarm standard it is a permitted one. In November the location adds seasonal staff. Nobody tells head office that the count has gone past ten, because nobody at head office is watching it, and nobody at the site knows that the count matters.

Employee alarms are one of the quieter obligations in the standards. They rarely feature in an incident narrative until the day an alarm does not reach someone. Across a portfolio, the question is not whether each site has an alarm. It is whether anyone can say, for every site, which of three different arrangements it relies on and whether that arrangement still fits.

What the standard covers, and what it leaves to the site

29 CFR 1910.165 applies to emergency employee alarms that are installed to meet a requirement of another OSHA standard. The usual trigger is the emergency action plan rule in 1910.38, which directs that an employer have and maintain an employee alarm system that complies with 1910.165. The plan itself is a company document. The alarm is a physical thing at an address, and it is owned, wired, tested, and sometimes silenced by whoever is on site.

Several requirements in 1910.165(b) apply to every workplace that has the system. The alarm must provide warning for the emergency action called for in the plan. It must be capable of being perceived above ambient noise or light levels by all employees in the affected portions of the workplace. It must be distinctive and recognizable as a signal to evacuate or take the action the plan assigns. Employees must be told how to report emergencies, and emergency telephone numbers must be posted where telephones serve that purpose. Manual operating devices must be unobstructed, conspicuous, and readily accessible.

Each of those sentences is written in terms of a place. "Affected portions of the workplace" is a physical idea: a loading bay with a compressor running, a back room with a door that closes, a mezzanine with a different sight line from the floor. A corporate policy can say that alarms must be audible everywhere. Only someone standing in each location with the alarm sounding can find out whether that is true.

The small-workplace allowance and why it is a counting problem

Paragraph (b)(5) is the provision that tends to define the compliance picture for small locations. It allows an employer with ten or fewer employees in a particular workplace to use direct voice communication as the means of sounding the alarm, provided all employees can hear it. Such a workplace need not have a backup system.

The text turns on the phrase "in a particular workplace." It is not a company-wide count, and it is not a test of whether the company is small. A portfolio of fifty locations with eight people each is not a small employer for this purpose in the sense that every location needs nothing. Each location is assessed on its own count, and each location that has crossed the threshold needs an alarm that is not a person shouting.

That makes the allowance a standing counting problem. The headcount at a location moves with the season, with a staffing agency's placement, with an overnight crew that overlaps the day shift, and with a lease that adds a unit. A site that qualified for voice alarm in September can fail to qualify in November without any decision having been made. The standard also requires that everyone can actually hear a direct voice warning, which is a separate question from the count. A manager in the front office does not reach an employee in a walk-in cooler, a stockroom with the door shut, or a roof.

Corporate teams have two realistic choices. They can decide that no site relies on the allowance and standardize on a physical alarm everywhere, accepting the cost for sites that could have used the exception. Or they can use the exception deliberately, which requires knowing every site's peak headcount, including temporary and contract staff who work in the space, and reviewing it at a set interval. What does not work is to adopt the allowance through silence, because a policy written at head office reads as if the question has been answered.

Testing is the obligation with the longest paper trail

For sites that do have an alarm, paragraph (d) governs maintenance and testing. It requires that employee alarm systems be maintained in operating condition except when undergoing repairs or maintenance, and that a test of the reliability and adequacy of non-supervised employee alarm systems be made every two months. Where a system has more than one actuation device, a different device must be used in each test so that no individual device is tested twice in a row. The section sets a separate and lighter testing schedule for supervised systems, meaning those with circuitry that monitors itself and reports trouble. Servicing, maintenance, and testing must be done by persons trained to do it. When a system is out of service, the employer must provide a means of warning employees in the interim.

Across a portfolio, a bimonthly test is a six-times-a-year, per-location task. Whether it happens depends on a person at the site who may change every year. The records, if they exist, sit in a binder or a phone photo in a back office. The test that mattered most, the one that would have found a dead circuit on a pull station, is the one that rotated the device, and that detail rarely survives a handover.

Supervised systems shift the burden rather than remove it. A monitored panel installed and serviced by a licensed vendor often has an annual inspection report, and that report is the evidence. But across fifty sites, the vendors are different, the reports arrive in different formats and on different dates, and the company-wide question of which locations have a current report is unanswerable without collecting them. A site whose vendor relationship ended in a lease change may have a system that nobody has serviced since.

Where leases and landlords complicate the picture

Many portfolio locations are leased. The building's fire alarm may be a landlord system, monitored by the landlord's vendor and tested on the landlord's schedule. That does not automatically satisfy the employer's obligation. The standard speaks of the employer's duty to maintain and test the employee alarm system that serves its employees. A tenant that cannot show what the landlord's tests found, or that assumes the landlord handles it, has a documentation gap even if the building is properly maintained.

The practical response is to ask for what exists. Request the landlord's test or inspection records for the alarm that serves the premises, find out whether the tenant space has its own device or relies on the building system, and note whether the alarm is audible and visible in the specific part of the space the employees occupy, such as a back-of-house area or a storage room that was added after the original fit-out.

What head office can actually see

A realistic goal is not that head office runs the tests. It is that head office can answer five questions for each location without calling anyone. Does the site have an employee alarm, or does it rely on the small-workplace allowance? If it relies on the allowance, what was its highest headcount in the last year, including temporary and contract staff? If it has an alarm, is it supervised, and when was the last vendor report? If it is non-supervised, when were the last tests, and which devices were used? And can everyone in the building perceive the alarm from where they work?

Those questions do not require new software. They can begin as a single shared sheet filled in once by site managers and reviewed each quarter, with a column for the date of the last verified test and a column for the highest headcount since the last review. The first pass will produce blanks, which is the point. A blank is a site where nobody knows, and it is better to find it internally than during an inspection or after an event.

The standard, applied to a portfolio

None of this changes what 1910.165 requires. What changes with scale is the number of places where the requirement can quietly lapse and the length of time it can stay lapsed before anyone sees it. A shouted warning is a legitimate means of alerting a handful of people, and a monitored panel is a legitimate means of alerting many. The risk is not in either choice. It is in a portfolio where nobody can say which choice each location has made, whether it is still valid, and when it was last proven to work.