A multi-location coffee operation needs one readable service history without pretending that every site, machine, and symptom follows the same path. An asset tag, a clear site name, and a separate field for each stage prevent a note about one espresso machine from being attached to another.
The log is an operational record. It does not replace the manufacturer manual, a technician’s findings, or a current service agreement. It also should not promise a portfolio-wide response, uptime, or restoration time.
Start with the site and asset identity
Create a stable record for each café, restaurant, hotel outlet, office, or other location. Add the address or internal site name, contact, access rules, operating constraints, and the equipment’s asset tag. Record brand, model, serial number, installation area, and the function that matters to the operation.
Include espresso machines, grinders, brewers, water treatment, filtration, pumps, and related equipment when they are part of the service history. Do not combine several machines under a label such as “coffee bar.” The coffee service hub provides service context but cannot substitute for an inventory.
Capture the original symptom
Record the first report in the operator’s words, date, time, cycle, display message, water or power state, heat or steam behavior, sound, leak location, and function affected. Add whether the issue is constant, intermittent, or tied to startup, brewing, rinsing, steaming, filling, or grinding.
Keep the original report separate from a manager’s theory. “Low flow at one group” is an observation. “Pump failure” is a diagnosis that requires testing. This separation makes the handoff useful even when the first label was wrong.
Add recent history and conditions
Record the last cleaning, filter change, water-treatment change, relocation, power interruption, prior service, part replacement, and recurring symptom. Note if the site has restricted access, a locked service area, a pet, a construction condition, or a narrow operating window.
Do not add a guessed part or deadline to make the log look complete. Use “unknown,” “not recorded,” or “needs confirmation” when the fact is not available. An honest missing field is more useful than a confident wrong one.
Use the locations hub for service-area context. Keep each site’s access and schedule information with its own asset.
Separate finding, estimate, and approval
When a technician inspects the equipment, record the finding, test category, recommended scope, estimate reference, approval status, and work completed as separate fields. A recommended part is not an approved part. An approved repair is not complete until the service record says what was done and tested.
If the scope changes, add the new finding and the approval message rather than editing the original report. Do not invent a parts lead time. Record “awaiting source,” “available,” or another status only when the service record supports it.
Track parts and warranty context
Record the part description or category when provided, compatibility note, supplier or source if known, order status, return or exchange condition, and the next update owner. Avoid choosing a part solely from an error message or online result.
Keep warranty wording tied to the equipment and work category. Coffee repair coverage is 6 months on parts and 90 days on consumables. Do not extend that term to unrelated equipment or promise coverage for a condition the written record does not identify.
The coffee FAQ hub can explain general process questions. The job file should carry the actual estimate and warranty terms.
Make the next update visible
Use clear statuses such as reported, access pending, acknowledged, diagnosed, estimate sent, approval pending, approved, parts pending, scheduled, completed, and follow-up needed. Add the person or role responsible for the next message and the date the status was last checked.
This makes a multi-location list useful without turning it into an unsupported service-level promise. A portfolio view can show open items; each site record still needs its own equipment, access, findings, and approval.
Protect access and privacy
Keep only the information the service handoff needs. Do not leave keys, alarm codes, payment details, or customer information in an open log. Use the site’s approved access process and tell the technician which details are available through the manager.
Before a visit, make the machine accessible without asking staff to move a heavy plumbed unit or open a panel. Record if the site cannot provide safe access. An access issue is a handoff condition, not a machine diagnosis.
Use the service boundary clearly
Commercial articles must not promise uptime, response time, food-code compliance, or restoration time without a current source. The log should describe the operational impact, but an operator must use its own safety, product, and business-continuity procedures.
The service facts are: deposits are $150 for standard brands, $175 for Jura and Miele super-automatics and home La Marzocco machines, and $250–550 for commercial La Marzocco equipment. Deposits include pickup, bench diagnosis, and return and are not credited toward repair. Extra bench time is $150 per hour for standard brands and $175 per hour for Jura, Miele, and La Marzocco. A written estimate comes after diagnosis and before repair work. Coffee repair coverage is 6 months on parts and 90 days on consumables. Diagnostics can take up to a week; most repairs run 3–4 weeks. The service area is 56 cities plus San Francisco for coffee equipment.
Use the contact page to send the asset record, symptom, access, service history, and approval status. A good log makes the next step visible without pretending to control the timing of a diagnosis or part.
Deposits start at $150 and include pickup, bench diagnosis, and return. They are not credited toward repair.
Review the portfolio without flattening it
At a regular management review, group open items by status or equipment type, then open the individual site record before deciding what needs attention. A shared filter change, water event, or power outage can explain several reports, but each machine still needs its own symptom and finding. Do not copy a completion status from one location to another.
Keep changes visible. If a symptom recurs after a temporary reset, add a new entry linked to the old one. If an asset is replaced or moved, close the old identity and create a new record rather than rewriting the history. This preserves a useful trail for operators and service teams.