What this category's data looks like
The materials for kindergarten safety protection and emergency drills come from daily inspections, drill plans, access control and school bus checklists, and hazard rectification orders. The update rhythm rolls forward according to the beginning of each semester, before and after drills, and the deadlines for hazard discovery and rectification. Field characteristics are concentrated in hazard items and rectification deadlines, drill headcount and sign-in, access control and school bus check items, and responsible person signatures. When materials enter workflow orchestration, hazard rectification orders are responsible for closed-loop verification, drill records are responsible for aligning with the plan's headcount and process, access control and school bus checklists are responsible for item-by-item confirmation without omissions, and handover records are responsible for linking responsible person signatures with version dates.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction state records. "Material drafts and handover records that can be issued" are then completed by subsequent nodes continuing execution according to the branches.
| Object | Check | Verification action |
|---|---|---|
| Hazard rectification order | Whether hazard items and rectification deadlines form a closed loop, and whether responsible person signatures are complete | Check hazard items, rectification deadlines, and signatures one by one, verify options and branch connections one by one in the node, and confirm that unclosed items go through the corresponding branch |
| Drill record | Whether drill headcount and sign-in are consistent with the plan, and whether the record matches the plan | Compare the plan headcount, sign-in sheet, and drill process, trigger one run to view node status in the run record, and route inconsistent items through the correction branch |
| Access control and school bus checklist | Whether check items are omitted, and whether responsible person signatures and dates are consistent | Check check items and signature dates one by one, reference the selection result variable in subsequent nodes and run a trial once, and route omitted items through the supplementary inspection branch |
| Handover record | Whether version and date are consistent, and whether the responsible person is clear | Check the version number, date, and responsible person signature, and confirm that branch direction is consistent with the interaction state record |
Three common errors
- Phenomenon: hazards enter the next step before being closed. Cause: rectification deadlines and responsible person signatures were not checked item by item, and the branch did not route unclosed items through correction.
- Phenomenon: drill records do not match the plan. Cause: headcount and sign-in were not compared with the plan, and record fields are disconnected from the plan process.
- Phenomenon: omitted check items are still signed off. Cause: item-by-item verification of the access control and school bus checklist is missing, and missing items were not blocked during handover.
How to verify the setup
This feature acceptance: run trials option by option, check the branch direction and interaction state in the run record, confirm that the selection result variable has been passed to subsequent nodes, and verify that variables, nodeId, and branch connections are consistent.
Business test: draft one according to the template and complete one handover, and see whether missing items are blocked.
- In the node, verify options and branch connections one by one, and after a trial run, view the node status and branch direction in the run record.
- Reference the selection result variable in subsequent nodes and run a trial once, and verify
variables,nodeId, and the handover record's version, date, and responsible person signature.