Issue & Improvement Log
Operational problems rarely explode; they smolder. A shared log keeps every smolder visible, owned, and scheduled for a fix.
What's Included
- How to use this log
- Open issues
- Improvements underway
- Verification and follow-up
Best For
Any recurring operational friction — reviewed at every operations review until verified closed.
Target Audience
Small-business teams that want a simple, reviewable ops log instead of a heavyweight register.
How to Customize
Keep severity to three levels, force one named owner per row, and archive — don't delete — verified rows.
When to Use
Start it on day one, then walk the open rows at every operations review.
Full Document Preview
Preview the actual editable ZuffSuite document.
OPERATIONS / LOG
Issue & Improvement Log: Ridgeline Coffee Roasters
One honest list of what is going wrong (issues) and what we are deliberately making better (improvements). Walked out loud at every operations review — not kept in someone's head.
How to use this log
Add a row the moment something hurts quality, speed, money, or people.
Give every row one owner — a person, not a team — and a target date.
Separate issues (happening now) from improvements (choices to get better).
Close the loop: mark the verification done only after the fix has held for a while.
Open issues
Issue | Owner | Category | Severity | Identified | Target fix | Corrective action |
|---|---|---|---|---|---|---|
Wholesale orders ship late on Fridays | Dana Kim | Fulfillment | High | September 22, 2026 | October 9, 2026 | Pre-stage Friday wholesale orders on Thursday afternoons |
Grinder burrs past their service interval | Marcus Lee | Equipment | Medium | September 25, 2026 | October 12, 2026 | Order replacement burrs and book a swap-in before peak hours |
Improvements underway
Improvement | Owner | Category | Status | Started | Target | Verification |
|---|---|---|---|---|---|---|
Card-only checkout at the café counter | Priya Nair | Service | In progress | September 15, 2026 | October 20, 2026 | Compare queue times for two weeks after launch |
Verification and follow-up
Friday staging: verified only after three consecutive Fridays ship on time.
Grinder swap: verified by the first calibration check after installation.
Card checkout: verified with the two-week queue-time comparison.
A row with no owner, no corrective action, and no target date is not being managed — it is being hoped at. A recurring issue may deserve its own Root Cause Review.
Related templates
Standard Operating Procedure
A formal operational procedure template detailing version control, responsibilities, step-by-step instructions, and compliance checklists.
Meeting Notes
A structured meeting record capturing objectives, discussion points, key decisions, and assigned action items with checkboxes.
Project Risk & Issue Log
Track what could go wrong and what already has — with one owner, a severity, a status, and a mitigation for every row.