Workplace Violence Prevention Readiness for Executive Support in 2026

Research question

What operating evidence shows that an executive office can prevent, receive, escalate, and learn from workplace-violence concerns without making an executive assistant act as a security specialist?

Executive assistants often sit close to the practical edge of workplace safety. They may know who is expected, notice an unusual calendar request, receive a distressed caller, arrange a sensitive termination meeting, or manage access to an executive suite. That visibility does not make the assistant responsible for judging threats or confronting people.

A sound system turns observations into a controlled handoff to trained owners.

This analysis uses public guidance from the Occupational Safety and Health Administration and the Cybersecurity and Infrastructure Security Agency. OSHA explains that a written and implemented prevention program, supported by controls and training, can reduce the potential for workplace violence. CISA offers resources on reporting, insider-threat mitigation, workplace security, and pathways to violence.

The sources support an operating framework; they do not supply a universal legal standard or a prediction model. Applicable requirements vary by jurisdiction and workplace.

What the public guidance establishes

OSHA's workplace violence overview describes workplace violence broadly and recommends a prevention program that can stand alone or sit within a wider safety and health program. The agency emphasizes worksite assessment, engineering and administrative controls, training, investigation, and remediation. It also says a policy should cover workers, clients, visitors, contractors, and others who may contact employees.

CISA's insider-threat mitigation resources extend the evidence base with reporting templates, prevention materials, security-awareness resources, and program-evaluation tools. Their presence is useful because executive-office concerns do not arrive in a single form. A concerning message, access anomaly, escalating interaction, or disclosure by a colleague may each require a different immediate response but the same disciplined reporting path.

Neither source says an executive assistant should assess a person's dangerousness. That distinction is central. The assistant's role is to observe, preserve relevant information, follow immediate-safety procedures, and route the concern.

Security, human resources, legal, emergency services, or another designated owner evaluates and responds according to policy.

Map the executive-office exposure points

Start with the workflow, not a list of threatening behaviors. Map where executive support affects people, places, and information: visitor invitations, reception handoffs, building access, off-site meetings, travel arrivals, executive contact details, public events, deliveries, and meetings involving sensitive employment or commercial decisions.

For each point, document the normal owner, an alternate owner, the information required for handoff, and the action that the assistant must never take. A reception workflow might require confirming the host, checking the approved visitor list, issuing time-limited access, and contacting building security when identity or purpose cannot be confirmed. It should not require an assistant to physically block entry or conduct an improvised interview.

Include virtual and hybrid work. Repeated unwanted meeting invitations, publication of private itinerary details, or an attempt to obtain an executive's location can create a safety concern even when no one is at the office. Route design should connect digital reports with physical-security and people owners rather than leaving separate fragments in email, chat, and reception logs.

Risk mapping must not become demographic profiling. Use observable events, policy conditions, and verified access facts. Nationality, disability, job level, communication style, or unfamiliarity is not evidence of a threat.

Legal and HR owners should review criteria for bias, privacy, labor, and accommodation implications.

Build a reporting path that works under pressure

A report should be possible without searching a policy library. Give executive-support staff a short decision card with three levels. Immediate danger uses emergency services and the site's emergency procedure.

An urgent concern uses a monitored security or safety channel. A non-immediate concern uses the approved case intake. Local experts must define the boundaries and numbers.

The intake should capture facts rather than conclusions: when and where the event occurred, what was observed or communicated, who else was present, whether immediate help was requested, and where supporting material is preserved. Do not ask the reporter to diagnose motive, mental health, or credibility. Free-text speculation increases bias and distracts reviewers from the event.

Design for privacy. A general executive briefing document is not a safety case file. Limit access, separate medical or employment information where required, and prevent screenshots or messages from being copied into broad team channels.

A case identifier can let the assistant track receipt and ownership without exposing investigation details.

Acknowledgment matters. The system should confirm that a report reached a monitored owner and state what the reporter should do if circumstances change. An unacknowledged web form is not a reliable escalation channel.

Test the alternate route during leave, travel, nights, and weekends if the executive office operates then.

Separate prevention controls from incident response

Prevention includes ordinary controls that reduce ambiguity: current visitor lists, named meeting hosts, access expiration, private itinerary handling, reception escalation, room-selection standards, and clear ownership for sensitive meetings. These controls should be proportionate. Turning every office interaction into a security event can create fear, discrimination, and reporting fatigue.

Incident response begins when a defined threshold is reached. The response plan should identify who can call emergency services, secure a location, notify affected workers, preserve evidence, manage family or media inquiries, and authorize return to normal operations. Executive assistants may support communications and calendars, but they should work from approved direction and should not become the single coordination point.

Plans must account for the executive's preferences without allowing preferences to override safety controls. A principal who routinely accepts unplanned visitors creates a conflict between hospitality and access policy. Resolve that conflict in advance through a documented exception or a redesigned reception process.

Do not expect the assistant to negotiate it during an escalating encounter.

Recovery is also part of readiness. Define how the organization checks on affected workers, handles schedule changes, preserves confidentiality, reviews control failures, and updates training. Avoid circulating vivid incident details beyond those who need them.

A useful after-action review focuses on systems, decisions, timing, and resources rather than blame.

Train for role clarity, not heroics

Training should let an assistant recognize the reporting threshold, locate the correct channel, describe observable facts, protect private information, and act during immediate danger. Scenario exercises can cover an unlisted visitor, a troubling communication, a distressed former worker, an online disclosure of an itinerary, and an unavailable primary contact.

Each exercise should test a small number of controls. Was the current emergency information accessible? Did the alert reach a monitored owner?

Did the assistant know where to wait or exit? Did building security receive enough information? Did a case record avoid unnecessary sensitive detail?

Did an alternate owner respond?

Do not measure success by whether a trainee guessed the outcome of an ambiguous scenario. Measure whether the approved process worked. Track training completion, acknowledgment time, escalation ownership, unresolved control actions, and exercise findings.

Report denominators and exclusions rather than a context-free pass percentage.

Contractors and remote assistants need inclusion. If an agency-employed assistant works in a client's office, the agency and client should agree whose emergency plan applies, how the assistant receives training, and which reporting routes cross organizational boundaries. The worker should not have to decide between two incompatible instructions during an emergency.

Evidence to request from an executive-assistant provider

An organization evaluating support can ask for a role-level safety handoff instead of generic claims that assistants are vetted or trained. Useful evidence includes the current policy acknowledgment, escalation contacts, site-specific onboarding, confidentiality rules, scenario frequency, alternate coverage, and how agency and client responsibilities are divided.

Ask how the provider handles a concern involving the supported executive, the client's employee, or the assistant's own manager. A route that only escalates upward through the person implicated is not independent. Ask whether reports can be made without placing sensitive detail in shared client systems.

Review a de-identified exercise record. It should show the scenario, expected actions, actual response, gaps, owners, due dates, and closure evidence. It should not expose personal reports or pretend that exercise completion predicts future safety.

Limits and decision use

This framework is not a threat assessment, emergency plan, or legal opinion. OSHA notes that there is no single specific federal OSHA workplace-violence standard, while state rules and sector requirements may add obligations. Local emergency services, security professionals, HR, counsel, facilities, and worker representatives should define the applicable process.

No checklist eliminates violence, and a reported concern does not prove intent. The operating goal is a fair, accessible, timely route from observation to qualified review. Controls should be evaluated for both effectiveness and unintended effects, including discriminatory access decisions or retaliation against reporters.

Teams can place this framework beside the executive operations research library and the service boundaries for C-suite executive assistant support. Organizations that need to define a safer visitor, calendar, and escalation handoff can start a support-design conversation with their safety, HR, legal, and facilities owners present.