What this category's data looks like
The materials for the kindergarten safety protection and emergency drills category mainly come from hazard inspection forms, drill plans and sign-in sheets, access control and school bus inspection records, rectification notices, and responsible person signature pages. When these materials enter the conversation logs and auditing feature, each plays a different role: hazard items and rectification deadlines are used to check closed-loop status; drill participant counts and sign-ins are used to compare the plan with actual participation; access control and school bus inspection items are used to confirm item-by-item ticking; responsible person signatures are used to confirm that rectification and drill results are traceable. In terms of update cadence, hazard rectification and drill records change as activities occur, access control and school bus inspections are updated daily or weekly, and signature pages are archived after review. Field characteristics center on hazard number, rectification deadline, drill date, participant count, inspection item name, signer, and signature date. After materials enter the conversation record interface, they are only pulled as session evidence and do not directly generate a version ledger.
Configuration and implementation checks
This step is performed by the conversation record interface (by application and session dimension), outputting a session message list and total record count, including role and reference information. The "version ledger and change records" are then completed manually or by an external system. The interface returns only session messages and the total count; the business deliverable must be separately registered, exported, and reviewed.
| Object | Check | Verification action |
|---|---|---|
| Hazard inspection form | Whether hazard items correspond one by one with rectification deadlines, and whether unclosed items are marked | Pull records by application and session dimension, verify that chatId matches the actual session, and check whether hazard number and rectification deadline fields appear in pairs |
| Drill plan and sign-in sheet | Whether the drill participant count matches the sign-in count, and whether the drill record matches the plan steps | Page through to retrieve all records, compare the sign-in count with the plan count, and check whether the drill date and plan date fall within the same batch |
| Access control and school bus inspection records | Whether inspection items are missing and whether responsible person signatures are complete | Open a single record to check the inspection item list in value, confirm that each item has a signer and signature date, the status code is 200, and the total record count total matches the list length |
| Version ledger and change records | Whether the current version is unique, whether old versions are traceable, and whether references are synchronized | After changing one piece of content, pull the records again, check whether the version number and reference information are updated synchronously, and record dataId to locate a single message |
Three common errors
- Symptom: The hazard inspection form has a rectification deadline but no closed-loop mark. Cause: The result was not filled in after rectification was completed, so the old version still shows unclosed, and the version ledger cannot determine the current status.
- Symptom: The drill record does not match the plan steps, and the sign-in count does not match. Cause: After the drill, items were not checked one by one against the plan, the sign-in sheet and the plan were archived separately, and references were not updated synchronously.
- Symptom: Access control and school bus inspection items are missing, and responsible person signatures are absent. Cause: The inspection form was not ticked item by item, the signature page was not archived together with the record, and it cannot be traced during review.
How to verify the setup
Pull records by application and session dimension, verify that chatId matches the actual session, and pull two pages in succession to compare the total count and offset.
Open a single record to check the role, reference, and elapsed time fields in value, and confirm that dataId can be used to locate the message.
- This feature acceptance: page through by total record count total to retrieve all records, sample one record to check role, reference information, and time, confirm the status code is 200, the list length matches the total count, and the reference count is recorded separately by array length.
- Business test: change one piece of content and see whether the version number and references are updated synchronously.