What this category's data looks like
This page addresses material drafting and responsibility handover in vocational school student internship management, involving three types of materials: internship agreements, internship plans, and internship logs. Internship agreements come from tripartite negotiation among the school, the enterprise, and the student, with fields including the names of the three parties, position, term, insurance, signatures, and dates; internship plans come from on-campus instructors and enterprise on-the-job mentors, with fields including batch, position rotation, week number, and signatures; internship logs are filled in daily by students, with fields including date, position, task, work hours, and on-the-job mentor signature. The update rhythm is: agreements are issued once, plans roll forward by batch, and logs are added daily. When materials enter this feature, agreements and plans assume the role of constraints and basis, while logs assume the role of process traceability; together the three support signable material drafts and handover records.
Configuration and implementation checks
This part is executed by application settings (reply limit, etc.), which output the length of a single response and the range of context that can be accommodated. "Signable material drafts and handover records" are then completed by the model.
| Object | Check | Verification action |
|---|---|---|
| Internship agreement | The names of the three parties, position, term, insurance, signatures, and dates are complete, and consistent with the batch, position, and start/end dates in the internship plan | Compare the names, quantities, and dates in the agreement and the plan item by item, and check the signatures and receipts; check whether maxResponse and maxContext match long-text drafting |
| Internship plan | The batch, position rotation, week number, on-the-job mentor, on-campus instructor, signatures, and dates are complete, and consistent with the date range in the logs | Retrieve the plan and logs by batch, and check whether the week numbers, position names, and dates match; record the quoteMaxToken budget and the tokens of the quoted text |
| Internship log | The daily date, position, task, work hours, and on-the-job mentor signature are complete, and correspond to the week number and position in the plan | Spot-check the same record in the logs, plan, and agreement, and check the names, quantities, and dates; block if a signature or receipt is missing |
| Handover record | The handover person, receiver, material list, version number, date, and signature are complete, and consistent with the versions of the agreement, plan, and logs | Sign off item by item according to the list, and check the versions and dates; use maxResponse to control the length of a single response to avoid the list being truncated |
Three common errors
- Symptom: The position name and batch quantity for the same student do not match between the agreement and the plan. Cause: The two materials were drafted separately, without checking names and quantities against the same record.
- Symptom: Log dates are misaligned with plan week numbers, and this is only discovered at handover. Cause: Versions were not synchronized, and the old plan was not updated with the batch.
- Symptom: The agreement or logs lack signatures or receipts, so the materials cannot be issued. Cause: The handover step did not check signatures and receipts item by item.
How to verify the setup
Feature acceptance: ask a question that requires a long answer, and see whether the ending is complete; check whether maxResponse and maxContext match the answer length required by the page, and confirm that the answer is not cut off mid-sentence.
Business test: draft one according to the template and complete one handover, and see whether missing items are blocked.
- In the application settings, check the reply limit switch and slider position, and confirm they match the answer length required by the page.
- Compare usage from two runs to confirm the change in single-run usage after adjusting the limit; record the
quoteMaxTokenbudget and the number of quotes separately.