What this category's data looks like
Exception tracing and manual review for vocational training subsidy claims draw on three types of materials: training class filing records, attendance records, and completion assessment forms. Class filing records contain the institution name, class number, start and end dates, student roster, and signature of the person in charge; attendance records log student names, attendance dates, and personal signatures on a daily basis; completion assessment forms state the assessment subjects, scores, assessment dates, and signatures of the assessors. The three types of materials are archived by training institutions by class and updated with each claim batch, with fields centered on names, quantities, dates, and signatures. When entering this function, class filing records provide the class and personnel baseline, attendance records provide the fact of attendance, and completion assessment forms provide the basis for results; the three are aligned by class number and student name to generate an exception list and review conclusions.
Configuration and implementation checks
This step is carried out by the memory turns and prompt configuration in the application settings, which output the range of referenced historical messages and the answer constraints. The exception list and review conclusions are then completed by the model, while the external entry point and authorization are handled by the publishing service and file permissions. The memory turns control how many previous turns of dialogue can be referenced at most when answering; too small a value fails to use the preceding context, while too large a value brings in irrelevant content and increases consumption.
| Object | Check | Verification action |
|---|---|---|
| Training class filing records | The institution name, class number, start and end dates, student roster, and signature of the person in charge are complete, and the class number is consistent with the attendance records and completion assessment forms | Check the current memory turns value in the application settings, run a trial with two consecutive questions, and compare whether the preceding class number in messages is correctly carried forward |
| Attendance records | Student names, attendance dates, and personal signatures are verifiable day by day, and the same student's name and dates match across the two materials | Compare the usage records of two runs to confirm that after adjusting the turns, the session corresponding to chatId can still trace back to the original personnel baseline in the class filing records |
| Completion assessment forms | The assessment subjects, scores, assessment dates, and assessor signatures are complete, the version is synchronized with the latest filing, and entries missing signatures or receipts are listed separately | Use variables to mark the fields to be checked, review the range of historical messages one by one, and confirm that the answer constraints do not treat the opening message as preceding context |
Three common errors
- Symptom: The same student's name and attendance dates do not match between the attendance records and the completion assessment forms. Cause: The two materials were entered separately and were not aligned and checked by class number and student name.
- Symptom: The class filing records have been updated, but the attendance records and completion assessment forms still use the old version. Cause: The versions were not synchronized, and the latest filing was not used to overwrite and retain receipts during archiving.
- Symptom: The review conclusion lacks the signature of the assessor or the person in charge, and the exception entries cannot be processed. Cause: Signatures or receipts are missing, and the traceability chain is broken at the signature step.
How to verify the setup
Acceptance of this function: ask two consecutive follow-up questions and see whether the second question carries forward the reference from the first; check whether the range of referenced historical messages and the answer constraints in messages match.
Business test: create an exception record, see whether it can be traced back to the source material, and confirm that the exception is supported by original records and the reviewer's signature.
- Check the current memory turns value in the application settings, match it with the range of preceding context required by the question, and run a trial with two consecutive questions.
- Compare the usage records of two runs to confirm that after adjusting the turns, the run consumption changes accordingly, and that the exception list can be traced back to the class filing records, attendance records, and completion assessment forms.