What this category's data looks like
The materials for progress records and statistical verification of enterprise new employee onboarding training include the onboarding training plan, course sign-in sheets, and job descriptions. The plan lists course names, dates, and responsible person signatures by batch; the sign-in sheets record personnel, dates, and personal signatures or receipts by session; the job descriptions give the job title, department, and effective version date. The three types of materials are maintained separately by the training organizer and the hiring department, updated weekly and archived monthly. When entering the tool calling and plugin stage, the plan serves as the reference ledger for courses and dates, the sign-in sheets serve as the original evidence for headcount and attendance, and the job descriptions serve as the basis for verifying personnel affiliation and job titles. The field characteristics are concentrated in four items: name, quantity, date, and signature. If any material version is not synchronized or a signature is missing, gaps will appear in the subsequent statistical criteria.
Configuration and implementation checks
This step is executed by the tool calling node in the workflow (the model decides whether to call, and the node executes), outputting the tool call result (the input parameters and return in the call record). The "progress table and statistical criteria description" is then completed by a subsequent AI node or manual verification.
| Object | Check | Verification action |
|---|---|---|
| Onboarding training plan | Whether the course names, planned dates, and responsible person signatures correspond one by one with the sign-in sheets, and whether the version dates are synchronized | Take one week's plan and sign-in sheets and compare them side by side, checking names, dates, and signatures row by row, and mark missing items separately |
| Course sign-in sheet | Whether the actual attendance number, sign-in date, and personal signature or receipt are consistent with the planned sessions, and whether exceptions are stated | Summarize the number and dates by session, compare with the number of planned courses, and state the reason for sessions with missing receipts |
| Job description | Whether the job title, department, and effective version date are consistent with the affiliation of the signed-in personnel | Check the job titles and departments against the personnel list, and mark those with inconsistent version dates as pending confirmation |
| Tool calling node | Whether the tool introduction, parameter introduction, and whether it is required correspond to the material fields, and whether the input parameters and return in the call record are readable | Open the tool node to check the introduction and parameters, run a test with a question missing a required field, and inspect the call records of toolChoice and functionCall |
Three common errors
- Phenomenon: The same person is written with a full name in the plan and an abbreviation in the sign-in sheet, and is counted as two people during statistics. Cause: The name fields in the two materials are not unified, and there is no cross-reference rule.
- Phenomenon: The plan has been updated to a new version, but the sign-in sheet still records sessions according to the old version, so the totals do not match. Cause: The version was not synchronized, and the effective date was not checked during archiving.
- Phenomenon: A session in the sign-in sheet lacks a personal signature or receipt, but the progress table still counts it as attended. Cause: The exception was not stated, and confirmed versus pending items were not distinguished during verification.
How to verify the setup
Acceptance of this feature: run a test with a question missing a required parameter, check the input parameters and return in the call record, and confirm whether it asks a follow-up question or calls according to the introduction; at the same time, check whether the call records of toolChoice and functionCall are readable.
Business test: use one week's records to verify the totals, see whether the criteria and exceptions are clearly stated, whether the recorded number and statistical number match, and whether the criteria are written in the header.
- Check the names, quantities, dates, and signatures of the onboarding training plan, course sign-in sheets, and job descriptions row by row, and mark missing items as pending supplementation.
- Open the tool calling node, check the three items of tool introduction, parameter introduction, and whether it is required, run a test with a question missing a field, and retain the call record.