What this category's data looks like
This page addresses progress records and statistical verification for kindergarten safety protection and emergency drills. Materials include the hazard item and rectification deadline ledger, drill participant counts and sign-in sheets, access control and school bus checklist items, responsible person signature records, as well as the progress table and statistical scope notes summarized from these. The ledger is updated weekly, sign-in and checklist items are updated per session, and signature records are backfilled as rectification closes the loop. When entering the database and operations function, each material plays a different role: the ledger and checklists are write objects of the main business database, sign-in and signatures are the original vouchers for verifying totals, and the progress table and scope notes are the final deliverables, which must allow weekly verification of record counts against statistical counts.
Configuration and implementation checks
This step is executed by the deployment environment's connection configuration (server-side), not by the capability of a model node; it outputs whether the connection is available (service startup result and connection logs). The "progress table and statistical scope notes" are completed subsequently by deployment handover and follow-up business processing.
| Object | Check | Verification action |
|---|---|---|
| Hazard item and rectification deadline ledger | Each hazard item must correspond to a rectification deadline, and each item must have a closed-loop marker; it is not acceptable to only register without closing items | Export the ledger weekly, verify the number of unclosed items and the deadline field, and confirm item by item whether the responsible person's signature has been backfilled |
| Drill participant counts and sign-in sheets | The number of sign-ins must match the number listed in the drill plan; discrepancies must have an exception note | Take one week of drill records, verify totals session by session using the sign-in sheets, and write discrepancies into the exception column of the scope notes |
| Access control and school bus checklist items | Checklist items must be checked off one by one; omissions must be traceable to the specific session and inspector | Spot-check one week of records against the checklist template, count the number of omitted items, and verify whether they have been marked in the progress table |
| Responsible person signature records | Signatures must cover both hazard rectification and drill records; missing signatures must be listed separately | Summarize signature records weekly, verify their correspondence with the ledger and sign-in sheets, and write missing signature items into the statistical scope notes |
Three common errors
- Phenomenon: The hazard ledger has registrations but no closed-loop marker for a long time. Cause: Rectification deadlines and item closure are not included in the same progress table; when counting, only the number of registrations is counted, and unclosed items are missed.
- Phenomenon: The number of drill sign-ins does not match the number listed in the drill plan. Cause: Records are not verified session by session against the plan, discrepancies are not written into the exception column of the scope notes, and the totals naturally deviate.
- Phenomenon: Access control and school bus checklist items have omissions, but the weekly total is still counted as full items. Cause: The checklist is not checked off item by item, the progress table assumes all items are complete by default, and omitted items are not listed separately.
How to verify the setup
This function's acceptance: connect once to the main business database, log database, cache, and vector database item by item, and verify the connection results in the startup logs; check against the deployment instructions whether the values of MONGODB_URI, REDIS_URL, and PG_URL match the instance addresses; when the log database is left blank, confirm that the main database is reused.
Business test: use one week of records to verify totals and see whether the scope and exceptions are clearly written; align the record counts and statistical counts of the four material types—hazards, drills, access control and school bus, and signatures—separately, and write discrepancy items into the header scope.
- In the deployment environment, verify the connection variable values for the main business database, log database, cache, and vector database, and confirm that the startup logs show no persistent connection timeouts.
- Export the four material types' records weekly, verify record counts against statistical counts item by item, and write exceptions and scope into the progress table header before including them in weekly or monthly reports.