Blog · Topic
Guide
Writing from Sawhorse Engineering on guide.
- Articles
- 34
- 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 2026Household permissions for pet booking portalsSeparate booking, payment, pet information and pickup permissions instead of assuming everyone linked to a household has the same authority.
- 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 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 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 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.
- 24 September 2026What PCI DSS actually requires of a small merchantPCI DSS scope is decided by how card data flows through your systems, not by your size. Here is what changes when the card never touches your servers.
- 23 September 2026How to tell whether a task is an AI problemFour questions that separate work worth evaluating with a model from work that belongs in ordinary code.
- 22 September 2026EMV, tokenization and 3D Secure explained properlyThree payment security mechanisms that get confused with each other. What each one actually does, where it applies, and what it protects you from.
- 21 September 2026Retrieval over your own documents: what decides qualityMost retrieval systems fail on chunking, metadata and permissions rather than on the model. What to get right before choosing anything else.
- 18 September 2026Build versus buy: the questions that decide itMost build versus buy debates go wrong by comparing a licence fee to a project cost. The real comparison is different.
- 17 September 2026Payment orchestration: when it is worth it and when it is notRouting payments across several processors solves real problems at scale and creates real complexity below it. How to tell which side you are on.
- 15 September 2026Idempotency: the idea that prevents duplicate everythingA lost response can turn a reasonable retry into a duplicate order, email or charge. Idempotency helps, but its boundary must include the actual effect.
- 10 September 2026When to use an orchestrator and when to write codeA workflow tool and a service solve the same problems differently. Four criteria that settle which one a specific process needs.
- 9 September 2026Deciding which system owns which fieldA sync cannot resolve conflicting business rules on its own. Decide who can write each field before connecting the systems.
- 7 September 2026Integrating with a system that has no APIExports, database replicas and file exchange are all workable. Screen scraping usually is not, and here is how to tell the difference.
- 6 September 2026Fixed scope is a feature, not a constraintAgreeing exactly what gets built before building it protects the client more than the supplier. What a written scope actually contains.
- 5 September 2026Webhooks done properlyReceiving webhooks is easy. Receiving them so that duplicates, replays, out of order delivery and outages do not corrupt your data takes six specific things.
- 4 September 2026Testing what matters rather than chasing coverageA coverage percentage tells you almost nothing. Ranking behaviour by what a failure would cost tells you where to spend.
- 3 September 2026Building an API other people will useAn internal API that becomes a partner API exposes every undocumented assumption. What to settle before the first external caller.
- 2 September 2026Performance budgets, and why averages lieA page that is fast on a development machine with fifty records tells you nothing. Set the budget first and measure against real conditions.
- 31 August 2026Accessibility as an engineering requirementDefine accessibility behaviour while components are designed, then verify it in the complete workflow. Automated checks are only part of that evidence.
- 29 August 2026Why the database should refuse invalid dataApplication validation holds only for the paths someone remembered. A constraint holds for every path, including the import script written at midnight.
- 27 August 2026Evaluating an AI feature before it shipsWithout a fixed set of real cases, the only available verdict on a prompt change is that it seems better. Here is how to build one that is worth trusting.
- 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.