What this category's data looks like
This page addresses the category of school safety hazard inspection and campus incident reporting. Source materials include three types: safety inspection checklists, hazard rectification ledgers, and emergency incident reports. Safety inspection checklists are generated weekly or per inspection, with fields including inspection item, location, discovery time, and inspector signature; hazard rectification ledgers are updated on a rolling basis by hazard number, with fields including hazard description, rectification deadline, responsible person, review conclusion, and signature; emergency incident reports are filed separately per incident, with fields including incident course, persons involved, reporting time, and receipt acknowledgment. When materials enter deployment, operations, and application handover, safety inspection checklists are used to verify inspection coverage, hazard rectification ledgers are used to verify rectification closure and responsibility placement, and emergency incident reports are used to verify the reporting chain and receipt retention. In terms of update cadence, checklists are appended with each inspection batch, ledgers are updated at each rectification milestone, and incident reports are supplemented as handling progresses. The names, quantities, dates, and signatures of the three types of materials must be aligned item by item during handover.
Configuration and implementation checks
This step is performed by the connection configuration of the deployment environment (server side), not by the capability execution of a model node; it outputs whether the connection is available (service startup result and connection logs). "Handover-ready deployment status and operation records" are then completed by deployment handover and subsequent business processing. The connection addresses of the primary business database, log database, cache, and vector database are configured separately via environment variables; if the log database is not configured separately, it reuses the primary database.
| Object | Check | Verification action |
|---|---|---|
| Safety inspection checklist | Inspection item, location, discovery time, and inspector signature must be consistent with the corresponding entry name, quantity, and date in the hazard rectification ledger | Extract the same hazard number, compare the hazard description, discovery date, and signature fields in the checklist and the ledger, and verify item by item whether they are consistent |
| Hazard rectification ledger | Rectification deadline, responsible person, review conclusion, and signature must be correspondable with the reporting time and receipt acknowledgment in the emergency incident report | Sort by rectification deadline, spot-check completed rectification items, and verify whether the review conclusion signature matches the incident report receipt date |
| Emergency incident report | Incident course, persons involved, reporting time, and receipt acknowledgment must be synchronized with the version records of the safety inspection checklist and ledger | Verify the report number against the ledger version number, check whether the reporting time falls within the checklist coverage period, and confirm whether the receipt is retained |
| Deployment connection configuration | The primary business database, log database, cache, and vector database can point to different instances respectively and be connectable | In the deployment environment, verify that the values of MONGODB_URI, REDIS_URL, and PG_URL match the database addresses, and check the connection results in the startup logs |
Three common errors
- Symptom: The name, quantity, and date of the same hazard do not match between the checklist and the ledger. Cause: The two materials were entered separately, no cross-check was performed by hazard number, and only a single material was reviewed during handover.
- Symptom: The emergency incident report has been updated, but the checklist and ledger remain at the old version. Cause: Versions were not synchronized, and the handover form did not record the current version number and update time of each material.
- Symptom: The rectification review conclusion or incident receipt acknowledgment lacks a signature. Cause: The signature fields were not completed as the materials circulated, and during handover it was not verified item by item whether signatures and receipts were retained.
How to verify the setup
This feature acceptance: connect once to the primary business database, log database, cache, and vector database item by item, check the connection results in the startup logs, and confirm that MONGODB_URI, REDIS_URL, and PG_URL point to the actual database addresses consistently.
Business test: verify once item by item according to the handover form, see which record is missing, and focus on verifying whether the fields, dates, and signatures of the safety inspection checklist, hazard rectification ledger, and emergency incident report are complete.
- In the deployment environment, view the startup logs, confirm that the connection results of the primary business database, log database, cache, and vector database are all available, and record the correspondence between connection addresses and instances.
- Verify the fields, dates, and signatures of the safety inspection checklist, hazard rectification ledger, and emergency incident report item by item according to the handover form, mark missing items, and note the version number.