What this category's data looks like
Kindergarten safety protection and emergency drill materials mainly consist of hazard ledgers, drill plans and sign-in sheets, access control and school bus inspection forms, and responsible-person signature pages. The sources are daily inspections and drill archiving at the kindergarten, and the update cadence advances by weekly inspections, monthly drills, and quarterly reviews. Hazard items and rectification deadlines are the main line of the closed loop; drill headcount and sign-in are used to verify consistency with the plan; access control and school bus inspection items are recorded per occurrence; the responsible person's signature confirms the rectification and drill results. When materials enter the workflow, the hazard ledger and inspection forms serve as intake inputs, the drill plan and sign-in sheet serve as the basis for comparison, and the signature page serves as the confirmation voucher. Missing-item follow-up questions are generated after comparing the material fields item by item.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting the branch direction and interaction state records. "Intake records and the questions to be completed" are continued and completed by subsequent nodes according to the branches. When triggered, the conversation enters the interaction state and records the workflow state; after the selection is completed, the corresponding option is followed to continue execution along the branch.
| Object | Check | Verification action |
|---|---|---|
| Hazard ledger and rectification deadlines | Whether hazard items and rectification deadlines correspond one by one, and whether the closed-loop status is traceable | Check the hazard item and rectification deadline fields one by one, inspect unclosed items and record follow-up points; reference variables and nodeId to locate the branch |
| Drill plan and sign-in sheet | Whether the drill headcount and sign-in are consistent with the plan, and whether there are records that do not match the plan | Compare the plan headcount, sign-in list, and drill records, mark inconsistent items and generate follow-up questions; check the variables transfer result |
| Access control and school bus inspection forms | Whether access control and school bus inspection items are missing, and whether responsible-person signatures are complete | Check cell by cell according to the inspection items, mark missing items and missing signatures as pending follow-up; reference nodeId in subsequent nodes for a trial run |
| User selection node | Whether each option corresponds to one branch, and whether the interaction state is recorded | Run a trial for each option and check the branch direction and interaction state in the run records |
Three common errors
- Symptom: hazards are not closed. Cause: rectification deadlines and hazard items do not correspond one by one, missing items are not followed up, and the intake record is directly transferred to the handler.
- Symptom: drill records do not match the plan. Cause: drill headcount and sign-in are not compared, the plan version and sign-in sheet are not synchronized, and follow-up does not cover the discrepancy items.
- Symptom: inspection items are missing. Cause: the access control and school bus inspection forms are not checked completely cell by cell, missing responsible-person signatures are not identified, and follow-up questions are not triggered.
How to verify the setup
This feature's acceptance: run a trial for each option, check the branch direction and interaction state in the run records, and confirm that variables and nodeId can be referenced in subsequent nodes.
Business test: submit a question missing key information, see whether it asks follow-up questions before answering, and check whether the basis for the follow-up questions comes from the material fields.
- In the node, check the options and branch connections one by one, and confirm that each option corresponds to one branch.
- Trigger the user selection node once, and check the node status and interaction state records in the run records.