Multi-Turn Conversation and Prompts for School Timetables and After-School Scheduling: Handle Questions and Collect Missing Information

School Timetables: review conversation for question intake. Check source versions, input mappings and the values received by downstream nodes.

What this category's data looks like

In the scenario of primary and secondary school timetables and after-school service scheduling, the category materials that enter the Q&A intake stage are mainly of three types: the master timetable, the teacher assignment table, and the after-school service project table. The master timetable is usually published by the academic affairs office per semester, containing fields such as class, day of the week, period, course name, and assigned teacher; its update rhythm is mainly centralized publication at the start of the semester, with class adjustments handled through sporadic revisions. The teacher assignment table lists subjects, classes, and weekly teaching hours by teacher dimension, must be checked item by item against the master timetable, and often includes a signature column for the grade group leader or academic affairs. The after-school service project table contains project name, participating classes, time slot, venue, responsible teacher, maximum number of participants, and receipt signature, and is updated on a rolling weekly or monthly basis. When these three types of materials enter the Q&A intake and missing-item follow-up function, the master timetable serves as the backbone basis for classes and periods, the teacher assignment table is used to cross-check teaching relationships and teaching hour quantities, and the after-school service project table is used to fill in after-school time slots and project attribution. The intake records and the completed follow-up questions are generated by the model based on this; when material fields are missing, dates are not synchronized, or the signature column is empty, pending follow-up items are first formed and then transferred to the responsible person for handling.

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 records and completed follow-up questions" are then completed by the model. Memory turns control how many previous dialogue turns can be referenced at most when answering; if the value is too small, the preceding text cannot be used, and if the value is too large, irrelevant content is brought in and consumption increases.

ObjectCheckVerification action
Master timetableWhether the fields class, day of the week, period, course name, and assigned teacher are complete, and whether the date and signature column are consistent with the teacher assignment tableIn the application settings, check the current memory turns value, run a trial with two consecutive question turns, and check whether the messages range referenced in the first and second turns covers the master timetable fields
Teacher assignment tableWhether the name, quantity, and date of the same record match across the two materials, whether the versions are synchronized, and whether missing signatures or receipts are identified as missing itemsRetrieve the teacher assignment table and the master timetable, compare the teaching relationships and weekly teaching hours item by item, check the signature column, and then use chatId to locate the historical turns of the same conversation
After-school service project tableWhether the project name, participating classes, time slot, venue, responsible teacher, maximum number of participants, and receipt signature are complete, and whether the date is synchronized with the master timetableCheck the names and quantities in the project table against the master timetable and teacher assignment table, check the receipt signature, and confirm in the prompt configuration whether variables carry the project fields

Three common errors

  • Phenomenon: The course name or weekly teaching hours for the same class do not match across the two materials. Cause: The versions of the master timetable and teacher assignment table are not synchronized, and after revision only one of them was updated.
  • Phenomenon: The dates in the after-school service project table are misaligned with the periods in the master timetable. Cause: During rolling updates, backfilling was not performed, and missing items were not identified as pending follow-up items.
  • Phenomenon: Intake records lacking signatures or receipts are still processed further. Cause: Missing-item follow-up did not ask first, and the process went directly to answering, resulting in insufficient material basis.

How to verify the setup

Acceptance of this function: with two consecutive follow-up questions, see whether the second question inherits the reference from the first question, and check whether the historical message range referenced in messages matches the prompt constraints.

Business test: ask a question missing key information, see whether it asks first before answering, and confirm that the intake records and completed follow-up questions have a material basis before transferring to the responsible person for handling.

  • In the application settings, check the current memory turns value, and after matching it with the preceding text range required by the question, run a trial with two consecutive question turns and compare the usage records of the two runs.
  • Use chatId to locate the same conversation, check the reference ranges of variables and messages, and confirm that missing items are identified and followed up before transferring to the responsible person for handling.