School safety and compliance
campus fence other buildings this one
School safety and compliance
Check-in writes are in parity mode. A check-in made here is recorded in a shadow collection and will not appear on the live board. That is expected while the previous system is still the one of record.
Drills scheduled, running, or waiting for their report. A drill leaves this list when its report is filed, and comes back if the report is returned for changes; every drill, filed or not, is in Drill records.
For a drill the school has already run. The same questions the district's form asks. Nothing on this report is measured by the system: the times are the ones you give, and the record says so.
For a drill not yet held. On the day, press Start when it begins and End when it is over: the system measures the times, then the report is written.
Lay out the rest of the school year's required drills at once. The planner suggests days; you change any of them, check the plan against the state's requirements, then schedule the drills. A plan is only a plan: the record counts the drills that are held.
Every drill on record, in one list: what schools submitted before this system (imported, as submitted), drills run in this system, and drills reported here after they were held. Open one to see every answer, print it, or save it as a PDF.
The documents a compliance visit asks for besides drills — meeting minutes, training certificates, exemptions and the like — filed for each school with the date of the document and the file itself. A record here shows that a document was filed. It does not show that a requirement is met.
Every check-in and check-out in the existing system’s log, for the dates and places you may see, newest first. Check-ins made through this service while both systems run side by side are included and marked Recorded here only.
Every document the district’s other apps have created, in one place: accident reports, travel and drone requests, fleet records. You can only read them here, and each time you open one it is recorded.
Who can do what. Every district account can already check itself in; everything else is a role given here. A change takes effect on the person's next action; they reload the page to see new tabs.
Campuses carry a compliance record; check-in places (the District Office, support buildings) only take check-ins. Another name a campus goes by — an alias — is how a check-in or an imported drill spelled differently still lands on the right campus.
Who did what in this system, newest first.
Drill deadlines are counted in school days on this calendar. When the schools close unexpectedly — a storm, an emergency — add the closure here, and every deadline after it moves.
The rule that asks for an emergency drill every reporting period counts drills inside these dates. Each period runs from its first date to its last, both included.
Neither a staff day nor a holiday is a school day, so both are counted exactly as closures always were. The type only changes what Today, the map and the wall say; check-in, lockdown and roll call work on every day.
Days the published calendar holds in reserve. Turn one on when the district uses it as a school day.
The outside services this system uses, and which one does each job. Nothing is switched on until it is saved here, and every change and every test is written to the audit trail.
Reminders and notices about drills and reports, worked out from the compliance record. Everything is off until it is switched on here, it starts in test mode, and every change, preview and run is written to the audit trail.
Who the district's people are — names, buildings, positions — read from the district's own source, never typed here. Screens use it to show a name beside an address, and a report uses it to count the staff on a campus's roster. Every change and every refresh is written to the audit trail.
Each night every check-in is cleared, the live feed is wiped and the manual queue is emptied, so nobody shows as on campus from the day before. One system does it. Until this service is switched on here and writes are live, it only reports what it would clear.
The existing dashboard reads a copy of the check-ins in the Realtime Database. A job compares that copy with the check-ins every 30 minutes. Until this service is switched on here and writes are live, it only reports what differs; the existing system's own trigger does the repair.
What the full-screen wall shows. Saved here once; every television picks it up on its next refresh, with no new link to copy.
The documents the district’s other apps create, searched in one place on the Documents tab. Switch an app on or off, tell this service where its web app lives (for “Open in its app”), and check that it can be read. This service only ever reads them. Every change is written to the audit trail.
The district’s status board reads one shared spreadsheet. This service and the risk-management service each write their own rows to it every ten minutes. Set the sheet here, switch publishing on or off, and see what each service’s last beat came to. Every change is written to the audit trail.
What the header shows — the district's name, the app's name, the logo — the icon on the browser tab, and the colours. A field left empty uses the district's default. Every change is written to the audit trail.
The service looking at itself: the database, the live feed, email, the scheduled jobs, campus cover, and the side-by-side switch. A check that could not look says Could not run; the overall answer is green only when every check that counts ran and was fine.
What people sent with Report a problem, newest first. Each says whether it was sent on and where it was sent. Sent on means the provider accepted it; this system cannot see that anyone has read it. The status is yours to set, and every change is written to the audit trail. Where reports go is set in Settings ▸ Integrations ▸ Support.
in session open, not in session closed or no hours lockdown campus fence
Your device sends where it thinks it is. The server decides whether that is on campus, and records the answer either way — so a refusal is kept with its reason and its distance, not silently dropped.
If your phone cannot place you, somebody at the school can check you in instead — somebody else, never you. They are confirming that you are standing in front of them, which is the whole value of it.
Run today's drill here. Press Start when it begins and End when it is over — the system measures the times — then write the report. A drill is not a lockdown: check-ins carry on while it runs, and each school's panel on Today says a drill is in progress — unless a test lockdown is run with it, which stops check-ins there until the drill ends.
For a drill nobody scheduled ahead. It goes on the record for today and starts at once — the same as scheduling it and pressing Start.
The template's columns are the fields this system stores, so a file built from it needs no column matching at all. Paste your existing records into it, or upload the file you already have and match the columns in step 3.
CSV or Excel. Nothing is written by uploading — the next step shows you exactly what would be recorded, and you decide.