Why we built the app to be used without looking at it

An inspection is a two-handed job. You are holding a frame that weighs two kilos, wearing gloves, and standing over thirty thousand insects that would rather you left. Any records system that needs a finger on a screen has already lost.

The checklist problem

The traditional answer is a paper checklist and a pencil in your veil. It works, and it produces a stack of sheets nobody transcribes. Ask a beekeeper with fifty hives where last year's inspection sheets are and the honest answer is a drawer. The information exists; it just cannot be compared, charted or searched, which is most of what information is for.

The first digital answer was the same checklist on a screen, which is worse: it takes longer, the screen does not work in gloves or in sun, and the phone is in your hand at exactly the moment you need both. We tried it. The inspections got shorter because people stopped recording halfway through, not because the tool was faster.

Ten phrases instead of a form

So the app does not have a checklist. It has ten phrases, and you learn them in an afternoon:

• Beehive number one selects the hive. Everything after it applies to that hive until you name another.
• Seven frames space is how many frames the box holds. Said once per hive.
• Five frames population, two frames pollen, six frames honey: how many of those frames are covered by bees, stored pollen, and honey.
• Three frames open brood and three frames closed brood, recorded separately, because capped brood forecasts the next three weeks and eggs describe today.
• Queen exists or no queen, and queen twenty twenty-four to record her year.
• Queen cells marks the hive as preparing to swarm or replace its queen.
• Varroa, nosema, American foulbrood, European foulbrood name a detection. You say them only when you find something; silence means absent.

Quantities are always relative to a whole frame, the order of the phrases does not matter, and every one of them is a thing you would have said out loud to yourself anyway. That is the design: the app listens to the running commentary a beekeeper already keeps in their head.

The beep is the contract

Each recognised phrase is confirmed with a short beep, so you know it landed without looking. If the beep does not come, the phrase was not recognised, and the app has recorded nothing, so you say it again rather than carrying on. Wind across the microphone and a phone inside a zipped jacket are the two usual reasons.

The rule is deliberate. A records system that guesses at what you probably said is worse than one that stays silent, because a wrong number written with confidence is the kind of error that survives into a chart. Silence is honest.

Offline, on purpose

Recognition runs on the device. Apiaries are in places without signal, which is usually why they are good apiaries, and a records system that needs a connection to record is a records system that fails on the days you most need it. The inspection is stored on the phone and uploads later, when it finds a network on the drive home. Then it appears on the dashboard as one row per visit, every reading across, dates down the side, ready to correct in place if a figure is wrong.

What the row becomes

The point of getting the readings out of the apiary is what happens to them afterwards. A season of rows for one hive is a chart. The platform reads each new inspection against the hive's history and writes a short diagnosis: a population that has fallen across three visits, brood disrupted out of season, a treatment that never moved the mite count. A recorded detection of varroa becomes a scheduled course of treatment with dates. The date on each row is what makes all of it arithmetic instead of memory.

None of that exists if the recording step is the one that gets skipped. So the recording step is the one we made disappear.