Connect vehicle permissions to what happens at the entry point

A vehicle’s arrival should be checked against the permissions the school actually granted. Veramast connects the registration, the permit, and the plate read. Staff can see what arrived, what was allowed, and which record supports that answer.

A family submits a request on the school’s own page. Staff approve it, request information, or decline it. Approval links the people and the vehicle and issues a permit for the appropriate zone and dates. Sensitive answers are held sealed, and opening one is recorded.

A permit can be Valid, Expiring, Expired, Scheduled, or Suspended. A suspension carries its reason and author. If a permit moves to a replacement vehicle, the history records the move rather than losing the connection to the earlier vehicle.

At an entry point, Veramast matches a resolved plate read to the school’s registry and checks the permit. A valid permit with no hotlist match needs no response. An expired or invalid permit is identified in the Entry log. A hotlist match follows the school’s alert instructions.

Where an approved Vio rule applies, an observation can open or advance a case. The case keeps its rule and evidence together. A permit mismatch does not give Vio permission to take any action it chooses; the campus’s rules, automation level, and jurisdiction determine what can follow.

If the plate cannot be resolved, the record says Plate unreadable. It produces no alert or citation. Staff can make a recorded correction when they have better information, with the original observation retained.