Catch failed QC tests before bad batches ship
Every hour, WebRun opens Mar-Kov, reads the latest quality test results for overrun, fat content, and bacteria counts, logs every result to a Google Sheet, and posts an immediate Microsoft Teams alert for any batch that falls outside spec so it can be held before it reaches the freezer.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I get alerted the moment a QC test result falls out of spec?
WebRun checks Mar-Kov every hour for new quality test results, capturing the batch number, test type, value, and spec range for each. Every result gets logged to a Google Sheet, and any batch that falls outside spec triggers an immediate Microsoft Teams alert to your QA lead with hold instructions, so a failed test never moves on to the next production step unnoticed.
- Out-of-spec batches get flagged within the hour instead of at end-of-shift review
- QA opens Teams to a ready-to-act hold alert instead of scanning raw data
- Every test result is logged automatically for your quality records
Built for ice cream QA teams · frozen dessert quality managers · production supervisors · plant lab technicians
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 - check new test results
mar-kov.com How to Automate Mar-Kov
WebRun opens Mar-Kov to check new test results. - Open Mar-Kov and pull test results logged since the last check
- Capture the batch number, test type, result, and spec range for each
- Mark each result as pass or out of spec
Done when Every new test result since the last run is captured with its pass or fail status.
-
2
Google Sheets - log every result
google.com How to Automate Google Sheets
WebRun opens Google Sheets to log every result. - Open the QC Test Results tracker
- Append a row for every result with batch number, test type, value, spec range, and pass or fail
- Keep out-of-spec rows highlighted so they stand out in the sheet
Done when Every test result from this run is logged, with failures visually flagged.
-
3
Microsoft Teams - alert QA to failures
microsoft.com How to Automate Microsoft Teams
WebRun opens Microsoft Teams to alert QA to failures. - Post an alert to the QA Teams channel for every out-of-spec result
- Include the batch number, the test, the result, and the spec range it missed
- Tag the QA lead so the batch can be held before it moves to finishing
Done when QA has an alert with hold instructions for every out-of-spec batch found this run.
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
Does it hold or release the batch itself?
No. WebRun only flags an out-of-spec result and alerts your QA lead in Teams. Holding, releasing, or dispositioning a batch stays a human decision made in Mar-Kov.
What tests does it check?
Whatever result types your team logs in Mar-Kov, typically overrun, fat content, titratable acidity, and bacteria counts. Anything outside the spec range you've set gets flagged the same way.
Will passed results clutter my QA alerts?
No. Passing results are logged quietly to the tracking sheet for your records. Only out-of-spec results trigger a Teams alert, so QA only gets pinged when action is needed.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.