Multi-Turn Conversation and Prompts for Kindergarten Healthcare and Meal Management: Draft Materials and Hand Over Responsibilities

Child Health and Meals: review conversation for material handover. Check source versions, input mappings and the values received by downstream nodes.

What this category's data looks like

Kindergarten health care and meal management involves fields such as ingredient names and specifications, retention sample times and batches, disinfection periods, and categorization of absence causes. Material sources include daily menus, purchase orders, retention sample records, disinfection logs, and absence tracking sheets, with an update cadence of per meal, daily, and weekly summaries. When entering this feature, the memory turn count controls how many previous dialogue turns the answer may reference at most, the prompt constrains the answer scope, and the model uses this to draft signable material drafts and handover records, and to check that fields are complete, responsible persons are clear, and versions and dates are consistent. Material drafts and handover records must be signed off by the next stage, and missing items must be blocked.

Configuration and implementation checks

This step is executed by the memory turn count and prompt configuration in the application settings, outputting the referenced historical message range and answer constraints. The signable material drafts and handover records are then completed by the model, while the external entry point and authorization are handled by the publishing service and file permissions.

ObjectCheckVerification action
Retention sample recordsRetention sample time and batch must match the document batchCheck the retention sample time and batch fields, use messages to record the turns and compare chatId
Menus and purchase ordersMenu categories must match purchase categoriesCheck ingredient names and specifications, use variables to mark discrepancy items
Disinfection recordsDisinfection periods must be complete with no omissionsCheck the disinfection period fields, inspect whether any period is missing and record it
Absence tracking sheetCategorization of absence causes must be clearCheck the categorization of absence causes field, confirm sign-off by the responsible person

Three common errors

  • Phenomenon: documents and retention sample batches do not match. Cause: the retention sample time and batch fields were not updated in sync with the documents, and items were not checked one by one during handover.
  • Phenomenon: menu and purchase categories are inconsistent. Cause: ingredient names and specifications were not unified, and the purchase order and menu were maintained separately, causing discrepancies.
  • Phenomenon: disinfection records are missing periods. Cause: the disinfection period fields were not filled in item by item according to meal or period, and completeness was not checked during handover.

How to verify the setup

Acceptance for this feature: ask two consecutive follow-up questions and see whether the second question carries forward the reference from the first; check whether the references to messages, chatId, and variables within the historical message range are consistent.

Business test: draft one copy according to the template and complete one handover, and see whether missing items are blocked.

  • In the application settings, check the current value of the memory turn count and confirm it matches the prior context range required by the question.
  • Run a trial with two consecutive questions, check whether the second round correctly carries forward the reference from the first round, and compare the usage records of the two runs.