What this category's data looks like
This page focuses on the progress records and statistical verification of vocational training subsidy applications. The materials come from three categories: training class filing records, attendance records, and completion assessment forms. The class filing records include the institution name, class number, start and end dates, student roster, and signature field; the attendance records include the daily attendance date, student name, attendance status, and supervising person's signature; the completion assessment forms include the assessment date, score, assessment conclusion, and responsible person's signature. The three categories of materials are updated weekly and summarized at the end of the month. When entering this function, the class filing records serve as the roster of classes and personnel, the attendance records provide the attendance transaction flow, and the completion assessment forms provide the final results. The fields and dates of the three must be compared item by item.
Configuration and implementation checks
This step is executed by the tool invocation node in the workflow (whether to invoke is decided by the model, and the node performs execution), outputting the tool invocation results (the input parameters and return values in the invocation record). The "Progress Table and Statistical Scope Description" is then completed by subsequent AI nodes or manual verification.
| Object | Judgment | Verification Action |
|---|---|---|
| Training session filing | Whether the institution name, class number, start and end dates, student roster, and signature field are complete, and whether the dates connect with the first day of the attendance records | Open the filing materials, verify the fields and signatures item by item, then compare with the date of the first day of the attendance records |
| Attendance records | Whether the daily attendance date, student name, attendance status, and supervising person's signature are complete, and whether the names are consistent with the filing roster | Export the attendance log by week, compare person by person with the filing roster, and mark entries with missing signatures or name mismatches |
| Completion assessment form | Whether the assessment date, score, assessment conclusion, and responsible person's signature are complete, and whether the assessment date falls within the filing start and end dates | Open the assessment form, verify the date and signature, then compare with the filing start and end dates |
| Statistical scope description | Whether the record count matches the statistical count, whether the scope is stated in the table header, and whether exceptions are clearly described | Use one week of records to verify the total, check the table header scope and exception descriptions, and confirm that the number of array entries and the tokens of the referenced text are recorded separately |
Three common errors
- Phenomenon: The same trainee's name is written inconsistently in the sign-in records and the completion assessment form. Cause: The two documents were filled in at different stages, the name format was not standardized, and the versions were not synchronized.
- Phenomenon: The number of trainees in the class opening filing does not match the total number of people in the sign-in records. Cause: Mid-course additions or withdrawals were not written back to the filing, and the statistical criteria were not specified in the table header.
- Phenomenon: The completion assessment form lacks the responsible person's signature or receipt confirmation. Cause: After the assessment was completed, the signature was not added in a timely manner, and no signature verification was performed before the materials were archived.
How to verify the setup
Acceptance for this feature: run a trial with a query that is missing a required parameter, check the inputs and returns in the call records, and confirm whether it prompts a follow-up question or invokes according to the description; at the same time, verify the values and connection status of toolChoice and functionCall in the call records.
Business testing: use one week of records to verify the totals, check whether the calculation rules and exceptions are clearly stated, and confirm that the number of records matches the statistical counts.
- Open the description and parameter configuration of each tool node one by one, verify the two items of parameter description and whether it is required, and confirm that they correspond to the fields in the business materials.
- On the canvas, verify the diamond-shaped interface connections and node status, run a trial with a query that is missing a required field, and observe whether it asks a follow-up question first.