Context and Token Budgets for Kindergarten Safety and Emergency Drills: Compare Documents and Locate Differences

Kindergarten Safety: review context & tokens for document checks. Check source versions, input mappings and the values received by downstream nodes.

What this category's data looks like

The materials for kindergarten safety protection and emergency drills mainly come from daily inspection sheets, hazard rectification ledgers, emergency drill plans and sign-in records, access control and school bus checklists, and responsible person signature pages. The update cadence is daily inspections, weekly summaries, and archiving after monthly drills. The field characteristics are concentrated in four categories: hazard items and rectification deadlines, drill headcount and sign-in, access control and school bus check items, and responsible person signatures. When materials enter this function, inspection sheets and ledgers serve as the objects to be compared, drill plans and sign-in records serve as another copy of the same object, access control and school bus checklists provide the list of check items, and signature pages are used to confirm responsibility attribution. The localization of the discrepancy list depends on whether the name, quantity, and date of the same object are consistent across the two copies of materials, thereby revealing one by one unclosed hazards, drill records inconsistent with the plan, and missing check items.

Configuration and implementation checks

This part is executed by application settings (response limit, etc.), which output the length of a single answer and the range of context that can be accommodated. The "discrepancy list" is then completed by the model. The response limit is controlled by a slider for the length of a single answer. If set too low, the answer will be truncated; if set too high, consumption will increase.

ObjectCheckVerification action
Hazard rectification ledgerThe hazard item and rectification deadline are consistent on the same object, and the rectification status is closed-loopCompare the hazard item names, rectification deadlines, and responsible person signatures in the inspection sheet and ledger one by one, and mark unclosed items
Emergency drill sign-in recordsThe drill headcount and sign-in headcount are consistent, and the drill records match the process and date in the planCheck the sign-in sheet headcount and roster against the drill plan, and check whether the records correspond to the plan steps
Access control and school bus checklistsThere are no missing check items, and both access control and school bus check items are coveredCheck off item by item against the check item list, record missing items, and mark the corresponding date
Responsible person signature pageThe responsible person for the same object has consistent signatures in the two copies of materialsCheck the responsible person names and dates in the signature page against the ledger and drill records

Three common errors

  • Phenomenon: The hazard rectification deadline has passed, but the ledger still shows it as unclosed. Cause: The rectification deadline fields in the inspection sheet and ledger are not synchronized, causing the discrepancy list to omit this item.
  • Phenomenon: The drill record headcount is inconsistent with the sign-in sheet headcount. Cause: The sign-in sheet counts actual attendance, while the drill record uses the preset headcount from the plan, and the two copies of materials are not aligned.
  • Phenomenon: Missing items appear in the access control and school bus check items. Cause: After the checklist version was updated, old-version check items were not included in the comparison scope, and the discrepancy localization did not cover newly added items.

How to verify the setup

This function's acceptance check: ask a question that requires a long answer, for example requiring the comparison results of all hazard items and rectification deadlines to be listed, see whether the end of the answer is complete, and check whether the settings of maxResponse and maxContext match.

Business test: use a real record to find a field inconsistent with the ledger, for example the sign-in headcount of a certain drill and the drill record headcount, and confirm that the discrepancy list can locate the specific field.

  • In the application settings, check the response limit switch and slider position, and confirm that maxResponse matches the answer length required by the page
  • Compare the usage of two runs, confirm the change in single-run usage after adjusting the limit, and record the tokens of the quoted text corresponding to quoteMaxToken and the number of array entries