What this category's data looks like
This page addresses the school safety hazard inspection and campus incident reporting scenario, involving three types of materials: safety inspection checklists, hazard rectification ledgers, and emergency incident reports. Safety inspection checklists are filled in item by item by area by the inspector, usually updated daily or weekly, with fields including inspection item, location, date, and signature. Hazard rectification ledgers are compiled by the safety officer, updated weekly or monthly, with fields including hazard name, quantity, rectification deadline, responsible person, and receipt. Emergency incident reports are submitted immediately by the duty personnel, with fields including incident name, number of people involved, date of occurrence, handling person, and signature. When materials enter this feature, the safety inspection checklists and emergency incident reports serve as the original records providing the objects of comparison, and the hazard rectification ledger serves as the baseline ledger providing the reference; material verification and discrepancy location revolve around whether the name, quantity, and date of the same record are consistent, and a discrepancy list is output for the reviewer to confirm and write back.
Configuration and implementation checks
This part is executed by the 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 uses a slider to control the length of a single answer; if set too low, the answer will be truncated, and if set too high, consumption will increase.
| Object | Check | Verification action |
|---|---|---|
| Safety inspection checklist | Check against the hazard rectification ledger whether the name, quantity, and date of the same hazard are consistent | In the application settings, check the switch and slider position, and compare the hazard name, quantity, and date in the checklist and the ledger item by item |
| Hazard rectification ledger | Check against the emergency incident report whether the name, number of people involved, and date of occurrence of the same incident are consistent | View the name, quantity, and date fields of the ledger and the report, mark inconsistent items, and record the version number |
| Emergency incident report | Check against the safety inspection checklist whether the date, handling person, and signature of the same incident are complete | Check the date, signature, and receipt of the report and the checklist; list missing items in the discrepancy list |
| Response limit | Match the answer length required by the page | Ask a question that requires a long answer and look at the ending, and check the maxResponse and maxContext, quoteMaxToken settings |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the safety inspection checklist and the hazard rectification ledger. Cause: The two materials were filled in by different personnel at different times, and no field-by-field comparison was made.
- Symptom: The version of the hazard rectification ledger is not synchronized, and the old and new versions coexist. Cause: After updating, it was not uniformly replaced, and the reviewer received an outdated ledger.
- Symptom: The emergency incident report lacks a signature or receipt, and the safety inspection checklist has no corresponding confirmation. Cause: The reporting process was not completed, and the signature and receipt steps were skipped.
How to verify the setup
Feature acceptance: Ask a question that requires a long answer and see whether the ending is complete; if it breaks off in the middle of a sentence, the response limit is too low and can be appropriately increased, while also paying attention to changes in single-use consumption.
Business test: Use a real record to find a field inconsistent with the ledger, write it into the discrepancy list, and hand it to the reviewer for confirmation and write-back.
- In the application settings, check the response limit switch and slider position, and confirm that the values of
maxResponseandmaxContext,quoteMaxTokenmatch the answer length required by the page. - Compare the usage of two runs to confirm that the change in single-use consumption after adjusting the limit is within an acceptable range, and check that the endings of longer answers are complete.