Vio follows the whole school rulebook

Vio’s remit is the school’s whole rulebook: vaping, weapons, restricted access, visitors, and vehicle rules. The aim is one security workflow across connected systems, from the source of an observation to the school’s permitted response. Vehicle enforcement is one part of that platform.

A sensor event, an access record, a camera observation, and a staff report carry different information. Vio’s workflow is designed to preserve that distinction. A vaping sensor event is a signal from a sensor; it does not identify a person. A staff report of a weapon is a report to assess, not a verified finding or a claim that a camera detected one.

In this product-direction example, a connected sensor supplies the location, time, and event it recorded. Vio would connect that signal to the school’s vaping procedure and prepare the response the school allows. Staff would see the source event beside the rule and response history. The sensor connection is planned; this example does not describe a live vaping detector in Veramast.

A separate planned staff-report connection would preserve who reported a concern, where, and when, and keep the report marked unverified. The school’s procedure would determine who receives it and what response is allowed. The report would remain distinct from a camera observation. This is a planned workflow, not an automated weapon detector or an automated safety response.

The current case workflow already connects observations to school-approved rules. The school approves a version before Vio uses it. A rule sets the condition, tolerance, and permitted actions. A case keeps the observations, the rule in force, and a timeline of what happened. Each new source needs its own supported connection before it can participate.

Consider an illustrative rule for a vehicle without a permit in a zone. It allows a notice first, another notice and a front desk task after 30 minutes, and a citation proposal after 60 minutes only with a confirming observation. Those timings describe this example; the school sets its own rules.

At the default Auto level, permitted notices and tasks can run within the bounds the school approved. The citation waits for a person’s decision. If the vehicle leaves before the next step is due, the case resolves as Vehicle left. Staff can inspect the evidence, decline a proposal with a reason, or dismiss the case.

A hotlist match alerts the people the school selected. The entry names the school’s instructions, its source, and its expiry. Staff acknowledge the alert and record its resolution. If nobody answers, the configured escalation brings it to the next people. That alert history stays available alongside the underlying read.

Ask Vio can explain a case using the campus records the member is already allowed to read. Its answer names the evidence. A request in chat can create a proposal; carrying it out always requires a person to open the approval and decide.

The school chooses how much authority Vio has. Cautious requires approval for every action. Auto uses the school’s approved bounds and keeps citations and tows for a person. Unrestricted grants more authority where the jurisdiction permits it. The case records the rule, the evidence, the action, and who can reverse it.