Skip to content

Shift-End Production Output Capture and Catch-Up Plan

Example prompt: "At the end of each shift, post a Slack prompt to the production lead asking for output per work centre. Compare against this week's production schedule in Google Sheets, compute the variance, and draft a catch-up plan for tomorrow that the production manager can review."

The Problem

The weekly production schedule goes out on Friday afternoon, lasts until Tuesday lunchtime, and from Wednesday morning it is a fiction nobody trusts because the actual output for Monday and Tuesday has not been recorded anywhere the schedule can see. The production lead knows the press was down for two hours on Monday, the laser bay ran ahead of plan, and a material shortage held the assembly cell for half of Tuesday. None of that is in the spreadsheet. By Wednesday's stand-up the production manager is rebuilding the picture from memory and Slack scrollback, the sales team has not been told the order due on Friday will slip, and the buyer is finding out late that more steel was needed on Tuesday morning.

How GloriaMundo Solves It

We build a workflow that closes the loop at the end of every shift. An integration step posts a structured prompt in #production-floor at 4pm asking the production lead for actual output per work centre, run hours, and an issue code per work order. If the lead does not reply within 90 minutes, a nudge tags the production manager as a fallback so the day does not end without a log. An LLM step extracts a structured response from the lead's reply with a confidence guard — if the reply is ambiguous, the workflow asks for clarification rather than guessing. A code step writes the day's actuals to the Production Output Log (with corrections preserved on a history tab), aggregates the week's actuals against the planned work-order quantities, and identifies work orders running behind. For each flagged work order, the workflow looks up the issue context — for 'Material short' it cross-references open purchase orders and surfaces the expected arrival; for 'Machine down' it suggests a substitute work centre if one is configured. An LLM step composes a readable catch-up plan grouped by work centre and drafts it to the production manager. Glass Box preview shows the structured ask going into Slack, the extracted output from the lead's reply, the variance computation, and the proposed catch-up plan before any of it lands.

Example Workflow Steps

  1. Trigger (schedule): Every working day at 16:00, skipping UK bank holidays.
  2. Step 1 (integration): Read the 'Work Centres', 'This Week Schedule', 'Production Output Log', 'Production Issues', 'Work Orders', 'Purchase Orders', and 'Work Centre Substitutes' tabs for today's context — the latter three are needed by the catch-up step (Step 7) for cross-referencing material-short and machine-down issues, and reading them upfront keeps the workflow's data access in one block.
  3. Step 2 (integration): Post a thread root in #production-floor tagging the production lead with each work centre's planned output and the structured ask.
  4. Step 3 (conditional): If the lead does not reply within 90 minutes, post a nudge in the same thread tagging the production manager.
  5. Step 4 (llm): When a reply lands, extract per-work-centre actual_quantity, run_hours, issue_code, and issue_note with a confidence score; ask for clarification rather than guessing when confidence is low.
  6. Step 5 (integration): Append one row per (work_centre_id, work_order_number) to the 'Production Output Log'; on dedupe collision, overwrite the row and preserve the prior values on a 'Production Output Log — History' tab.
  7. Step 6 (code): Aggregate this week's actuals per work_order_number, compute remaining_quantity against the work order's total, and flag is_behind_schedule where the planned_completion_date is today or earlier.
  8. Step 7 (llm): Compose a readable catch-up plan grouped by work centre, cross-referencing the 'Purchase Orders' tab for material-short issues and the 'Work Centre Substitutes' tab for machine-down issues.
  9. Step 8 (integration): Draft a Gmail to the production manager with the catch-up plan and a closing note that the published schedule has not been changed; log each flagged work order to 'Production Issues' with status 'Catch-up drafted'.
  10. Step 9 (integration): At 18:00 — half an hour after the 17:30 nudge window closes — post the day's shift summary in #production with planned vs. actual per work centre, work orders behind, issue-code breakdown, and 'On plan' work orders completing today.

Integrations Used

  • Slack — the #production-floor end-of-shift prompt with the production lead, the 17:30 nudge to the production manager, and the #production day summary at 18:00
  • Google Sheets — the Work Centres, This Week Schedule, Production Output Log (and history), Work Orders, Purchase Orders, Work Centre Substitutes, and Production Issues tabs
  • Gmail — the catch-up plan drafted to the production manager with the proposed actions per behind work order

Who This Is For

The production manager at a small manufacturer running on a weekly schedule out of a Google Sheet, where the daily picture lives in the production lead's head until Wednesday's stand-up and the buyer and the sales team are finding out about variances later than they need to.

Time & Cost Saved

The end-of-shift log is fifteen minutes done by the lead at the end of a long day, which is why it often does not happen until Wednesday's stand-up reconstructs it from scrollback. The workflow keeps the ask structured and short and produces the catch-up plan automatically. The bigger saving is the variances surfaced the same day rather than two days later — material shortages reach the buyer in time to chase the supplier, machine-down work goes onto the substitute centre tomorrow morning rather than at the end of the week, and the sales team learns about a Friday slip on Tuesday afternoon when the customer can still be told.