What this category's data looks like
This page focuses on the vocational school student internship management category. The source materials are three types of process documents: internship agreements, internship plans, and internship logs. The update cadence advances with internship batches; each batch adds agreements and plans, while logs are submitted on a rolling weekly or daily basis. Field characteristics center on agreement number, student name, position name, internship start and end dates, mentor signature, school and unit seals, log date and signature, and the week numbers and task entries in the plan. When the materials enter the Q&A intake and missing-item follow-up function, the agreement serves as the basis for identity and agreements, the plan serves as the basis for tasks and timing, and the log serves as the basis for process and signatures; the intake record and the items to be completed are generated accordingly. After missing items are identified, follow-up questions are asked first before answering, and the matter is then transferred to the handler.
Configuration and implementation checks
This part is executed by the memory turns and prompt configuration in the application settings, and the output references the historical message range and answer constraints. The "intake record and items to be completed" are then completed by the model.
| Object | Check | Verification action |
|---|---|---|
| Memory turns | Matches the range of prior context required by the question | Check the current value in the application settings, and run a trial with two consecutive questions to observe whether the second turn can carry forward the references from the first turn; if necessary, check the correspondence between messages and chatId |
| Internship agreement | Whether the agreement number, student name, position name, start and end dates, and signatures and seals are complete, and whether they are consistent with the internship plan | Check the agreement fields one by one, mark entries missing signatures or receipts, and compare the name and dates in the plan for the same record |
| Internship plan | Whether the week numbers, task entries, mentor, and dates are complete, and whether they correspond item by item with the logs | Expand the plan by week number, check the log dates and task names, and when the counts or dates do not match, add them to the missing-item follow-up list |
| Internship log | Whether the log date, signature, receipt, and week number are continuous, and whether they mutually corroborate with the agreement and plan | Sort the logs by date, check the signatures and receipts, mark logs whose versions are not synchronized or whose fields are missing, and record the items to be completed in variables |
Three common errors
- Symptom: The same student's name or position name does not match between the agreement and the plan. Cause: The two documents were filled in at different stages, and no field-level comparison or receipt confirmation was performed.
- Symptom: The log dates are misaligned with the plan week numbers, and the counts also do not match. Cause: The plan version was not synchronized, the logs were submitted under the old week numbers, and missing signatures or receipts were not identified.
- Symptom: When references are used in the second question, the answer does not address the question, responses become slower, and consumption increases. Cause: The memory turns value is too large and brings in irrelevant prior context, or the opening message is treated as prior context.
How to verify the setup
Acceptance for this function: ask two consecutive follow-up questions, see whether the second question carries forward the references from the first question, and check whether the messages range and chatId are consistent.
Business test: submit a question that lacks key information, and see whether it asks a follow-up question first before answering.
- Check the memory turns value in the application settings, run a trial with two consecutive questions, and compare the usage records from the two runs.
- Check the fields, dates, and signatures item by item for the three types of materials: agreements, plans, and logs; after marking missing items, generate the follow-up items to be completed and transfer the matter to the handler.