Plan every flavor changeover for the shop floor
Every night, WebRun opens Mar-Kov, reads the next day's production run in flavor order, builds a changeover schedule that flags any switch requiring an allergen cleandown, posts each changeover as an event on the shared Google Calendar, and sends shift leads a Slack rundown so the line never stalls waiting on instructions.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I schedule flavor changeovers and allergen cleandowns automatically?
WebRun reads tomorrow's production run from Mar-Kov every night, in flavor order, and flags any changeover where the allergen profile shifts from one flavor to the next. It posts each changeover as an event on the shared Google Calendar and sends shift leads a Slack rundown, so the floor knows the sequence and cleandown needs before the shift starts.
- Shift leads know tomorrow's changeover order before the shift starts
- Allergen changeovers are flagged automatically instead of relying on memory
- The production floor calendar always reflects the current Mar-Kov run order
Built for ice cream production managers · frozen dessert plant supervisors · shift leads · food safety coordinators
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
mar-kov.comin a real browser with your saved login - no setup, no API keys. -
1
Mar-Kov - read tomorrow's production run
mar-kov.com How to Automate Mar-Kov
WebRun opens Mar-Kov to read tomorrow's production run. - Open Mar-Kov and pull tomorrow's production run in scheduled order
- List each flavor-to-flavor transition and the estimated run time before it
- Flag any transition where the next flavor doesn't share the same allergen profile as the last
Done when Tomorrow's full run order is listed with every changeover and any allergen flags.
-
2
Google Calendar - schedule each changeover
calendar.google.com How to Automate Google Calendar
WebRun opens Google Calendar to schedule each changeover. - Open the Production Floor Google Calendar
- Add an event for each changeover with its start time and expected duration
- Mark allergen changeovers with a distinct label so they stand out on the calendar
Done when Every changeover for tomorrow's run has its own calendar event, allergen ones clearly labeled.
-
3
Slack - brief the shift leads
slack.com How to Automate Slack
WebRun opens Slack to brief the shift leads. - Post tomorrow's changeover rundown to the production Slack channel in run order
- Call out allergen changeovers and the extra cleandown time they need
- Tag the shift lead responsible for the first changeover of the day
Done when Shift leads have tomorrow's changeover order in Slack before the shift starts.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
How does it know which changeovers need an allergen cleandown?
It compares the allergen profile of each flavor to the one running before it in Mar-Kov. Any transition between different allergen profiles gets flagged and labeled separately on the calendar.
Does it change the production schedule itself?
No. WebRun only reads the run order Mar-Kov already has and turns it into a calendar and a Slack rundown. Changing the actual production sequence stays in Mar-Kov with your planners.
What if the run order changes overnight?
It reads the live schedule from Mar-Kov each night, so the next run picks up whatever order is current, and any calendar event can be adjusted by hand if a change happens mid-shift.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.