Hashlogics
Case study · Animal Care

Trident Elite

A kennel that knows which care was missed.

An operations web app where staff check in and out of every activity, so missed care shows up for the owner without anyone reporting it.

Client
Trident Elite Protection Dogs
Industry
Animal care · Protection-dog training and boarding
Engagement
Operations web app · Full-stack development
Overview

Trident Elite Protection Dogs runs its day on a kennel management web app that Hashlogics built. Staff check in and out of every activity, and the app flags any activity that never got a check-in. Paper and whiteboards only show the care someone remembered to write down. So the one thing the owner needs to know, what didn't happen, stayed hidden.

The challenge

The problem we set out to solve.

01

Nobody could say for sure which dog got which care, from whom, and when.

02

A missed activity only came to light if someone chose to mention it, which is a welfare risk for a high-value animal.

03

Health notes were scattered instead of held against each dog.

04

Paper could record that something happened, but it had no way to show that something didn't.

05

To see how the day went, the owner had to ask staff and piece it together.

What success needed to look like

  • Tie every activity to a dog, a person and a time.
  • Flag missed activities automatically.
  • Pull up the health reports for any one dog.
  • Give the owner analytics across the whole kennel, without a daily debrief.
Our approach

How we delivered it.

  1. 01

    Model the kennel as records

    Dogs, kennels and staff became first-class records, so every later entry has something real to point at.

  2. 02

    Capture care as it happens

    Staff check in and out of each activity. That stamps every entry with the dog, the staff member and the time.

  3. 03

    Work out what was missed

    Because the schedule is known, the app compares expected activities with logged ones and flags the gaps itself.

  4. 04

    Split the app by role

    Staff get a view built around checking in and out, while the owner gets analytics, flags and the log. That split is enforced at the server, so a hidden menu item is never the only lock.

  5. 05

    Keep the log append-only

    Activity records are only ever added. Each one stays tied to its dog, person and timestamp, so nobody can reassign an entry later.

The solution

What we built.

Trident Elite's app holds every dog, kennel and staff member in one system. Staff check in and out of each activity, so each one is logged against a dog, a person and a time. Because the schedule is known, the app works out a missed activity from the check-in that never came. Nobody has to own up to it.

Health reports sit with each dog and build into a history you can pull up later. The owner signs in to a separate view with analytics, the missed-activity flags and a full activity log. Staff and owner privileges are split at the server, so each role only reaches its own screens and data.

How one activity moves through the systemLive
  1. Check-inA staff member checks in and out of an activity for a dog.
  2. Activity recordThe entry carries the dog, the staff member and the time.
  3. Schedule checkLogged activities are compared with the expected ones.
  4. Missed flagAny gap is flagged instead of passing in silence.
  5. Owner viewAnalytics and the full log show the owner the day.

A missed activity is worked out from what didn't happen, so it never depends on self-reporting.

A registry of every dog, kennel and staff member, kept as structured records.
Check-in and check-out on each activity, stamped with the dog, the staff member and the time.
Missed-activity flags worked out from the schedule, with no self-reporting involved.
Health reports per dog, with checks for eyes, ears, teeth, coat and weight, building a history over time.
Analytics that show the owner the operation at a glance.
A full activity log the owner can review entry by entry.
Role-based access, enforced at the server.
How it's built

Platform capabilities

  • Role-based access control
  • Check-in / check-out tracking
  • Missed-activity detection
  • Health records
  • Analytics
  • Activity logging

Architecture

  • Web app with role-based views
  • Server-enforced permissions
  • Append-only activity records
  • Analytics built on the activity log

Data model

  • Dogs
  • Kennels
  • Staff
  • Activity records
  • Health records

Users

  • Kennel staff
  • Owner
The takeaway

The core idea was recording something that never happened. A form can capture an activity a staff member did, but it can't capture the one nobody did. So the app had to know the schedule first, then treat a missing check-in as a fact worth flagging. This only works where you can say in advance what should happen. If your operation runs on daily checks like that, the absence is the data you're missing.

By , CEO, HashlogicsUpdated
Start

Let’s deploy working AI into your business.

We build AI agents and automation, ship them into the tools you already run, then stay on under an agreed service level. A senior engineer reads every brief, and your call gets scheduled within 24 hours.

What happens next

  1. 01

    You send a brief or book a call

    Two minutes, whichever you prefer.

  2. 02

    A senior engineer replies within 24 hours

    Not a sales rep.

  3. 03

    Honest scoping, in writing

    And if we’re not the right fit, we say so.

Abdul Basit, CEO of Hashlogics

“I started Hashlogics because too many teams ship a demo, get paid, and disappear. We build to a standard we’d run ourselves — and we stay to keep it running.”

Abdul Basit · CEO · a direct line

Not ready to talk? Take the checklist.

12 questions to ask any AI agency before you sign. They separate a demo shop from a team that ships to production.

Get the checklist

Free · no newsletter