Blog · Topic
Operations
Writing from Sawhorse Engineering on operations.
- Articles
- 25
- Category
- Topic
- 26 September 2026Daycare and boarding reports built during the shiftCapture useful observations as care work happens, then review what is shared with the household without turning photos into the only record.
- 26 September 2026Pet service packages with an explainable session balanceTrack prepaid entitlements through bookings, attendance, cancellations and corrections without treating one editable balance as the entire record.
- 26 September 2026Recurring dog walks with exceptions that do not duplicateSeparate a standing walking arrangement from each visit so holidays, cover and one-off changes do not corrupt the next week of work.
- 26 September 2026Grooming schedules that learn from the work recordUse reviewed service history and explicit resource rules to estimate grooming appointments without treating breed alone as a reliable duration.
- 26 September 2026Boarding capacity is more than a count of kennelsRepresent suitable spaces, overlapping stays, household sharing and review requirements before confirming a boarding reservation.
- 26 September 2026Reviewed cleaning hours from rota to payroll exportKeep planned shifts, attendance events, approved hours and exported records distinct so corrections remain traceable across the payroll handoff.
- 26 September 2026Site consumables replenishment without duplicate ordersConnect site counts, approved replenishment and delivery receipts while keeping requested, ordered and available stock separate.
- 26 September 2026Client cleaning reports that explain exceptionsBuild a client portal around completed work, unresolved exceptions and follow up actions instead of a wall of green checkmarks.
- 26 September 2026Cleaning cover swaps that preserve site access rulesA replacement cleaner needs more than an empty shift. Model eligibility, access instructions, acceptance and handover as part of cover scheduling.
- 26 September 2026Cleaning attendance exceptions without false proofUse check-in signals to find uncovered shifts while recognising the limits of location, shared devices and site codes.
- 26 September 2026Turning a cleaning contract into versioned site checklistsTranslate a site scope into daily and periodic work without losing the agreement behind each task or rewriting the history of completed visits.
- 26 September 2026Service request forms that give dispatch useful informationAsk for enough context to route a home-service request without turning the first contact into a diagnostic questionnaire or a false booking confirmation.
- 26 September 2026Offline job notes without losing office changesDesign a technician workflow that preserves field observations during a connection loss while keeping assignment and approval decisions authoritative.
- 26 September 2026Arrival windows that do not promise an impossible dayOffer home-service appointment windows from real capacity, then keep confirmation, estimates and changes distinct in the customer experience.
- 26 September 2026Van stock and return visits need one parts workflowConnect part requests, reservations, van transfers and job consumption so a return visit is scheduled against more than an expected delivery date.
- 26 September 2026Equipment history that survives a technician changeConnect sites, installed equipment and service visits without turning every note into an unsearchable customer timeline.
- 26 September 2026A dispatch board that understands the job, not just the calendarModel skills, travel, parts and job state before letting a dispatch board assign technicians. A free rectangle is not proof that a visit is feasible.
- 19 September 2026How to handle chargebacks in softwareA dispute is a workflow with a deadline, not an email. What to build so evidence is assembled automatically and nothing expires unanswered.
- 14 September 2026The handover package: a checklistWhat a complete software handover contains, and the test that tells you whether it is real.
- 13 September 2026Automations that stop when the customer repliesThe most damaging automation failure is not a missed send. It is a sequence that keeps chasing someone who already answered.
- 11 September 2026Why your spreadsheet is the most valuable document in the businessThe file one person maintains usually contains rules nobody has written down. Extracting them is the highest value part of a modernization project.
- 8 September 2026Dead letter queues, and why silence is the worst failureA failed integration needs a visible recovery path. Retry budgets, failed work queues and reconciliation prevent errors from disappearing into logs.
- 25 August 2026Where AI should hand over to a personThe handover is a design decision with commercial consequences. Getting it wrong in either direction is expensive.
- 23 August 2026Reconciliation: the job that runs when nothing is wrongScheduled comparisons can find missing or inconsistent records even when no request reported an error.
- 19 August 2026Taking deposits and charging a balance laterA deposit now and a balance in six weeks touches holds, saved payment methods, authentication rules and cancellation policy. Here is the whole flow.
Let’s talk about the system you need.
Tell us where the current process breaks down. We can map the workflow, examine the integration requirements and define a practical scope for the build.
- A mutual NDA is signed before project details are shared.
- Scope is fixed in writing before any build starts.
- You own the source code, the IP and the documentation at delivery.
- Support plans are available and tailored on a discovery or technical call.