Safety at a Glance
Safety at a Glance is a single-page employee reference for immediate danger, everyday safety basics, local emergency-number setup, and reporting workplace concerns through Safety Hub. Replace its clearly marked fictional examples with verified site instructions before publishing.
Every employee gets a seat — priced per employee in Communications & Intranet, quoted with this template ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
Built for: Manufacturing · Logistics and distribution · Corporate offices · Field and service operations
Overview
Safety at a Glance is a single-page employee safety reference built around a practical distinction: immediate danger requires local emergency services and posted site instructions, while workplace concerns should be raised through the local process and recorded in Safety Hub when available. Its sections cover everyday safety basics, a location table for verified emergency details, ordered reporting steps, app guidance, and a reminder to check local instructions. The sample uses fictional Northstar locations and explicitly fictional emergency numbers; none are ready for real-world use.
Use this page as a quick service reference for employees who need to know what to do, where to report a concern, and where to find fuller safety resources. Before rollout, the designated safety content owner should confirm each location's applicable emergency number, posted procedures, role-specific rules, site response contacts, Safety Hub access, and alternative reporting route. Keep the emergency warning near the top so employees do not mistake app reporting for emergency response.
This page is not an emergency plan, a task-specific safe-work procedure, or a substitute for local legal and operational requirements. Do not use it to establish unverified policy, standardize procedures across sites that differ, or imply that Safety Hub features are enabled without checking the organization's setup. Link to authoritative local procedures when employees need detailed instructions, and maintain one approved source for each procedure rather than copying competing versions into this reference.
Standards & compliance context
- Treat emergency numbers and local response instructions as jurisdiction- and site-specific; have the responsible safety contact verify them before publication.
- Use the page as a quick reference alongside applicable local law, approved emergency plans, and task-specific procedures, not as a replacement for them.
- Keep reporting and escalation directions consistent with the organization's approved incident-reporting process, including an alternative route when the app is unavailable.
- Apply WCAG 2.1 AA accessibility practices so employees can read and navigate the safety instructions across devices and assistive technologies.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Notice Banner
-
If someone is in immediate danger, contact the local emergency service using the verified number for your location and follow posted site instructions. Safety Hub is for workplace safety guidance and reporting; it is not an emergency-response service.
Everyday safety basics
These sample expectations orient employees while making clear that current site and role instructions take precedence.
-
Fictional Northstar sample guidance At Northstar, employees are expected to follow posted site instructions and task-specific procedures, wear the protective equipment required for their work, and keep walkways and work areas clear. If a task, condition, or piece of equipment appears unsafe, pause work when it is safe to do so, keep others clear of the hazard where practical, and raise the concern with the site response lead or your manager. Do not restart affected work until the appropriate site process says it is safe. These are illustrative examples, not verified Northstar policy. Follow the current instructions for your work location and role.
Emergency numbers — fictional examples
This table shows where verified location-specific emergency details belong, while explicitly warning that its sample numbers are not for use.
-
These illustrative numbers are not for use. Replace them with verified local emergency numbers and confirm which applies at each Northstar location before publishing. Example location Fictional example number Before publishing United States office 911 (fictional sample) Verify the applicable local emergency number and posted office procedure. United Kingdom distribution site 999 (fictional sample) Verify the applicable local emergency number and posted site procedure. Singapore service centre 995 (fictional sample) Verify which emergency service and number apply locally.
How to report a safety concern
The ordered steps distinguish immediate response from local escalation, app reporting, and site follow-up.
-
For injuries, near misses, hazards, and other workplace safety concerns Use local emergency procedures first when there is immediate danger. Then report through the approved workplace route as soon as practical. Deal with immediate danger Contact local emergency services using the verified number for your location and follow posted site instructions. Notify the site response lead when it is safe to do so. Raise the concern locally Tell your manager or designated site safety contact about an injury, near miss, hazard, or unsafe condition. If safe, note where and when it happened and what you observed. Record it in Safety Hub Open the Safety Hub app and submit the report using the options available to you. Report as soon as practical; do not delay emergency help to complete an app report. Follow the site process Use the location's follow-up instructions and respond to requests for additional information. If you cannot access Safety Hub, ask your manager or designated safety contact for the approved alternative reporting route.
Safety Hub is the workplace safety destination
This callout explains the app's intended role and prompts the publisher to verify access and available options.
-
Use the Safety Hub app for reporting and detailed safety resources, not emergency response. Northstar's app access and available features depend on its setup. Confirm the connection, employee access, and reporting options before publishing this page. Open Safety Hub from the apps available to you. Choose the reporting or safety-resource option available in your organization's setup. If the app or a feature is unavailable, follow your site's approved alternative route.
Check your local instructions
This closing guidance points employees back to location-specific procedures and identifies the need for an accountable page owner.
-
Emergency contacts and response procedures can differ by country, site, and work activity. Follow the instructions posted where you work and confirm location-specific details with your manager or designated safety contact. Content owner: Northstar's designated safety content owner should maintain this page. Review it when emergency contacts, local procedures, or Safety Hub reporting options change, and confirm the example numbers have been replaced before employees rely on the page.
How to use this template
- Replace each fictional location and emergency-number example with details verified for the applicable site, and confirm the posted emergency procedure with the responsible safety contact.
- Confirm the everyday safety rules, role-specific expectations, site response lead, and approved alternative reporting route for every audience covered by the page.
- Check that employees can access Safety Hub and verify which reporting and resource options are actually available before describing them as usable.
- Publish the page in the employee safety area with a clear owner and a verified link to any authoritative local procedure that employees need next.
- Ask a representative employee and local safety contact to follow the page from immediate danger through routine reporting, correcting any unclear or unavailable step.
- Review and update the page when emergency contacts, site instructions, reporting routes, or Safety Hub options change, and remove any obsolete details.
Best practices
- Keep the immediate-danger instruction at the top and state plainly that app reporting must never delay emergency help.
- Verify each emergency number and the service it reaches with the responsible local authority or safety contact before publishing it.
- Separate location-specific instructions from organization-wide guidance so employees can identify what applies to their site and role.
- Keep the reporting sequence in operational order: respond to danger, raise the concern locally, record it through the approved route, then follow up.
- Name the accountable safety content-owner role and make the correction or help route clear on the page.
- Describe only Safety Hub features and access routes confirmed in the organization's setup, and state an approved alternative for access failures.
- Use short, observable instructions such as keeping others clear of a hazard where practical instead of vague reminders to stay safe.
- Check the page on a phone and use WCAG 2.1 AA practices, including clear headings, readable tables, and text that does not rely on color alone.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
Who should use this safety reference?
It is designed for employees who need a quick route to basic workplace safety guidance, emergency instructions, and reporting steps. The sample covers office, distribution-site, and service-centre contexts, but its rules and contacts are fictional examples. Confirm applicability for each location and role before publishing.
How often should the page be reviewed?
Review it whenever local emergency contacts, site procedures, reporting routes, or Safety Hub options change. The designated safety content owner should also set a review cadence that matches the organization’s change-control process. Do not treat the sample page as current until its details have been verified.
Who owns and maintains the page?
The sample identifies a designated safety content owner as responsible for maintenance. In your published version, name the accountable role and explain how employees can raise a correction or request help. Local managers or safety contacts can confirm site-specific instructions, but should not be implied to own the page unless that is confirmed.
Can employees use the example emergency numbers?
No. The numbers in the table are explicitly marked as fictional examples and must not be used. Replace each with a verified number that applies to the specific location and emergency service, and confirm the associated posted procedure before employees rely on the page.
Does Safety Hub replace emergency services or local reporting procedures?
No. The page directs employees to contact local emergency services and follow posted instructions when someone is in immediate danger. Safety Hub is described as a workplace safety guidance and reporting destination, not an emergency-response service. Preserve each site's approved alternative reporting route for employees who cannot access the app.
What should we customize before rollout?
Replace the fictional location names and numbers with verified local details, confirm the everyday rules for the audience, and check that reporting steps match approved site processes. Verify Safety Hub access and the reporting or resource options available to employees. Remove or revise any instruction that does not apply to a particular role or location.
Does this template connect to Safety Hub automatically?
No automatic connection is specified. The callout tells employees to open Safety Hub from the apps available to them, but the page notes that access and features depend on organizational setup. Confirm the app entry point, employee access, and available options before publishing; use only a verified destination if adding a link.
What is the main pitfall when publishing a safety page like this?
The most consequential pitfall is leaving an illustrative emergency number or generic procedure in place as if it were verified local guidance. Check every location-specific detail with the responsible safety contact and clearly distinguish emergency response from subsequent app reporting. Also keep the page owner and alternative reporting route visible.
How is this different from an ad-hoc safety announcement?
This template puts immediate-danger guidance, everyday basics, location-specific emergency details, ordered reporting steps, and Safety Hub direction on one reference page. An announcement can communicate a timely change, but it is not a substitute for an authoritative, maintained set of instructions. Link to the relevant approved procedure when additional detail is needed.
Related templates
Go deeper on the topic
-
A modern intranet is a specific surface — typically the home-base destination where employees get company news, find policies, and access key apps. A digital...
Ready to use this template?
Every employee gets a seat. Request pricing for Communications & Intranet and we quote into a workspace with Safety at a Glance ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.