User GuideVersion 1.0 · Screens captured July 2026

Compliance Dashboard
every deadline that can bite you, on one screen

How to read everything your site owes on one calendar, add the obligations no module produces, track respirator fit tests, and stay ahead of every review and corrective action before it lapses.

Short answer

ShieldSphere's Compliance Dashboard is one calendar of everything your site owes. It gathers six things the software already knows are due - policy reviews, training, fit tests, corrective actions, ZeroState inspections and SDS reviews - and lets you add a seventh: the obligations no module produces, like EPCRA reporting, permit renewals and insurance certificates.

1What the Compliance Dashboard does


The Compliance Dashboard answers one question - what do I owe, across everything - and answers it on a calendar.

Deadlines in ShieldSphere are generated by six different modules, each on its own schedule. Read module by module and you are doing the merge in your head. This page does the merge for you: everything with a date lands on one calendar, whatever produced it.

The page has three bands:

BandWhat it is for
Status cardsCompact counts across the top - the shape of the month in one glance.
The calendarThe working surface. Every due item from every source, by date.
Module tabsThe detailed trackers, unchanged, underneath. Where you go to work one source properly.
Training has moved to its own module

Training records used to be created and managed on this dashboard. They now live in Training, which also covers toolbox talks, sessions with QR sign-in, and the requirements matrix. Training deadlines still appear on this calendar - the dashboard shows them, the Training module owns them. See the Training User Guide.

2The calendar


Seven sources feed the calendar. Six are generated by the software from records you already keep; the seventh is whatever you type in yourself.

Compliance dashboard with status cards across the top, a month calendar showing due items from six sources with a colour legend, and the module tabs below
One calendar, seven sources. Overdue reads the same way whatever produced it, so nothing hides behind a module's own colour.
SourceWhat it puts on the calendar
Policy ReviewsWritten programs due for their periodic review (from the Policies module).
TrainingTraining and certifications reaching their expiry date (from the Training module).
Fit TestsRespirator fit tests due for annual renewal, per OSHA 1910.134(f).
Corrective ActionsOpen corrective actions from every module, by due date.
ZeroStateLockout/tagout procedures and their periodic inspections.
SDS ReviewsSafety Data Sheet reviews for the chemical inventory.
Compliance tasksAnything you enter yourself - see the next section.

Switch between the month view and the agenda view depending on what you are doing. Month is for planning - you can see where the load falls. Agenda is for working - it is the ordered list of what is overdue and what is coming.

Overdue looks the same whatever produced it

Each source has its own colour for items that are merely pending, but anything overdue is shown the same way across all seven. An overdue SDS review cannot look gentler than an overdue fit test just because its module's colour is calmer.

3Tasks you enter yourself


Most safety obligations are not produced by a module. They are produced by a regulator, a landlord, an insurer or a client - and they are the ones that get missed.

Compliance tasks are the seventh source: Tier II and EPCRA reporting, permit renewals, insurance certificates, internal audits, anything else with a date on it. Adding one puts it on the same calendar as everything else, which is the whole point - a filing deadline you keep in a spreadsheet is a deadline you will find out about late.

Add a compliance task dialog with title, due date, repeat interval, category, priority, email reminder and notes
Add a compliance task. Category is free text - use it to group the obligations that come from the same place, like EPCRA or Insurance.
1

Give it a title, a location and a due date

Tasks belong to a site, so they follow the same per-location access as everything else. The optional Category is free text - EPCRA, Permits, Insurance, Audits - and is how you group obligations that come from the same source.

2

Set how often it repeats

One-time, Monthly, Quarterly, Every 6 months, Annually, or a Custom interval in days. Recurrence is what makes the task worth entering once instead of remembering it every year.

3

Set the priority and who to remind

Priority is Low, Medium or High. Remind (email) names the person who should hear about it, which is often not the person entering it.

A recurring task does not drift

When you complete a recurring task, the next due date is calculated from the date it was scheduled, not the date you ticked it off. An annual filing due 1 March that you submit on the 20th stays due 1 March next year, instead of sliding three weeks later every year until it is in April.

4Fit test tracking


Anyone in a respirator needs a fit test on record, renewed annually. ShieldSphere tracks the clock.

Open the Fit Tests tab. The records follow OSHA 29 CFR 1910.134(f): the employee, the respirator make and model, the test date and next-due date, the method (QLFT or QNFT), the result, and a status that flips to Due soon and then Expired as the year runs out.

Fit test records with respirator, test date, next due, method, result and status
Fit test records. Click Add Record after each fit test. A Failed result is its own status - a worker who failed a fit test should not be in that respirator until it is resolved.

5Corrective actions across all modules


Corrective actions are raised all over ShieldSphere. This is the one place you see every one of them together.

Corrective actions across all modules grouped into overdue and due-in-30-days
Corrective actions, everywhere. Actions from incidents, inspections and hazard scans, grouped into Overdue and Due in 30 days, each showing its source module and priority.

Work the Overdue group first - these are the ones already past their date - then the Due in 30 days group to stay ahead. Clicking any action takes you to it in its home module, where you assign, work and close it.

6Policy and SDS reviews


The Policy Reviews, ZeroState and SDS Reviews tabs are windows into those modules' schedules. Policy Reviews lists written programs coming due for their periodic review; ZeroState shows lockout procedures and their annual inspections; SDS Reviews tracks the chemical inventory's review dates.

Close it at the source

You can mark a policy review complete from this dashboard, but the record lives in the Policies module. When the calendar and a module ever seem to disagree, the module is the source of truth.

7Troubleshooting


SymptomCause and fix
An item is still showing but I fixed itConfirm you closed it in its home module. The calendar mirrors the module - it updates when the source does.
A training shows expiredRecord the renewal in the Training module - that is where training records now live. The calendar follows it.
A fit test is due soonThe annual renewal is within 30 days. Schedule the fit test and add the new record when done.
A task I added is not on the calendarTasks belong to one location. Check the profile filter matches the site you added it to.
The dashboard is for the wrong siteCheck the current profile in the sidebar - compliance is shown per site.
An overdue corrective action will not clearOpen it from the calendar and close it in its module - the count follows the action's real status.

Try Compliance Dashboard in ShieldSphere

Start a free hazard scan and see the platform these guides describe - no credit card required.

Screens captured from the live application in July 2026 using a demonstration site - your screens will show your own data. Because ShieldSphere ships changes regularly, check the version above against the current release before circulating this guide widely. Questions? Contact support.