What this category's data looks like
The materials on this page are intended for progress records and statistical verification of kindergarten safety protection and emergency drills. Sources include daily inspection forms, drill plans and sign-in sheets, access control and school bus checklists, hazard rectification orders, and responsible person signature pages. The update cadence is daily inspection records, weekly summaries, and monthly statistical verification; drill materials are archived per session, and rectification materials are updated on a rolling basis by deadline. Field characteristics are hazard items and rectification deadlines, drill headcount and sign-in, access control and school bus check items, responsible person signature, record date, and statistical scope. When materials enter workflow orchestration, the progress table and statistical scope description are completed by subsequent nodes continuing execution along branches; the inspection form, sign-in sheet, checklist, and rectification order serve respectively as input materials for branch decisions, used to verify whether the record count and statistical count match and whether the scope is written into the table header.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction state records. The "progress table and statistical scope description" is completed by subsequent nodes continuing execution along branches. When a node is triggered, the conversation enters an interaction state and the workflow state is recorded; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Hazard rectification order | Whether hazard items and rectification deadlines correspond one by one, and whether the closed-loop status and responsible person signature are complete | In the user selection node, check options and branch connections one by one, compare against the rectification order deadline field, and check whether unclosed items enter the corresponding branch |
| Drill sign-in sheet | Whether the drill headcount and sign-in are consistent, and whether the record matches the plan | Trigger a user selection node once, view the node status in the run record, and check whether the sign-in headcount and plan headcount are written into the same branch |
| Access control and school bus checklist | Whether access control and school bus check items are missing, and whether the responsible person signature is complete | Reference the selection result variable in a subsequent node and run a trial once, and check whether missing check items are intercepted by the branch |
| Statistical scope description table header | Whether the record count and statistical count match, and whether the scope and exceptions are written into the table header | Use one week of records to verify the total, check the table header scope and exception notes, and confirm that the branch direction is consistent with the statistical result |
Three common errors
- Phenomenon: hazards that are not closed-loop are still counted in completion statistics. Cause: the rectification order has no deadline branch, the user selection node does not route by closed-loop status, and subsequent nodes aggregate directly.
- Phenomenon: drill records do not match the plan. Cause: the sign-in sheet headcount and plan headcount are not verified in the same branch, and the selection result variable is not passed to the statistics node.
- Phenomenon: missing check items are not discovered. Cause: the access control and school bus checklist does not correspond item by item to branches, the process stops after interaction is completed, and missing items do not enter the verification step.
How to verify the setup
This feature's acceptance: run trials option by option, check the branch directions and interaction states in the run record, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and that variables and nodeId are queryable in the run record.
Business test: use one week of records to verify the total, see whether the scope and exceptions are clearly written, and confirm that the record count and statistical count match and that the scope is written into the table header.
- In the user selection node, check options and branch connections one by one, and check whether each option corresponds to one branch, avoiding the situation where selecting an option still follows the default branch.
- Trigger a user selection node once, view the node status in the run record, and confirm that the interaction state is recorded and that the same session does not enter the interaction repeatedly.