A calendar you have to remember to check is not really a calendar, it's another thing to forget. The fifth thing FarmHQ is built around is a calendar that finds you instead.
FarmHQ computes every statutory deadline, such as the 27-day passport window or the 3-day movement report, directly from the farm's own recorded events, and pushes the reminder to the farmer server-side, not only inside the app. That means a deadline still arrives on time even if the app has not been opened in weeks, because the calendar does not depend on anyone checking it.
Most calendars are passive. You put something in, and it waits patiently for you to look at it again. That works for a meeting you already know about. It works badly for a deadline that gets created automatically by something that happened on the farm, like a calf being born or an animal moving off the holding, where the person who needs the reminder often has no reason to think to set one.
FarmHQ's calendar is built the other way round. Every statutory deadline on a livestock farm, the 27 days to apply for a cattle passport, the 3 days to report a movement, the point at which a medicine record has to be kept for 5 years, the date a VAT return is due, is computed the moment the underlying event is recorded, not typed in separately by a farmer who has to remember the rule.
This sits alongside the other four things we set out to build from day one: livestock compliance, the money, Red Tractor and farm records, and people. The calendar is the piece that connects all four, because a deadline from any of them can appear on it, computed the same way regardless of which part of the farm it came from.
A phone calendar or a to-do list is only as good as what gets put into it, and putting something into it is a second step that depends on someone remembering to do it, on top of already having done the thing that created the deadline in the first place. On a farm during calving or a busy movement week, that second step is exactly the one that gets missed.
It also depends on someone knowing the rule well enough to calculate the date correctly. Twenty-seven days from a birth is easy to get wrong by a day or two if you are doing it from memory at the end of a long day, and a day or two either side of a statutory deadline is often the entire difference between compliant and not.
The calendar is not a separate feature bolted onto the records, it is a direct consequence of them. When a calving is recorded, whether spoken into the app from the calving pen or typed in later, the passport deadline is calculated from that exact birth date and added to the farm's calendar immediately, not estimated or left for the farmer to work out. The same happens the moment a movement, a death, or a medicine treatment is recorded.
Because every deadline is derived from an actual recorded event rather than entered by hand, there is no separate place for the date to be wrong. If the birth date on the record is correct, the deadline calculated from it is correct too, and it stays attached to that specific animal or record rather than floating as a generic reminder that someone has to match back up to the right animal later.
This is the part that actually matters. A calendar entry inside an app is useless to a farmer who has not opened that app, and during a genuinely busy stretch, not opening an app for days or weeks at a time is completely normal, not a failure on the farmer's part. FarmHQ's deadlines are pushed server-side, meaning the reminder is generated and sent from FarmHQ's own systems on a schedule, not triggered by the farmer opening the app and the app then checking what's due.
In practical terms, that means a notification about an approaching passport deadline arrives whether or not anyone has looked at the app since the calf was born. The calendar does its job in the background, on its own schedule, and the app is where you go to act on it, not where the reminder itself lives and waits to be discovered.
This is the same reasoning behind why we built FarmHQ offline-first rather than offline-tolerant. A feature that only half works without a live connection, or only works once you remember to open it, has quietly become optional. A calendar you can forget about is a calendar you will forget about, so the reminder had to leave the app and come to you instead.
No, and it isn't meant to. The calendar tells you what's due and when, computed correctly from your own records, but it doesn't submit anything on your behalf and it doesn't assume the record it was built from is definitely right. That's the same rule that runs through everything else in FarmHQ: Joe drafts, you confirm, and the calendar is no exception to it.
What it does remove is the specific failure that causes most missed deadlines on a working farm, which is rarely refusing to comply and almost always simply forgetting under pressure, or getting the date wrong by a day while distracted. A calendar that finds you, correctly calculated, closes that gap without taking the actual decision away from you.
The honest answer is not drama, it is a handful of small things that would otherwise have gone unnoticed until too late. A passport application that would have been filed on day 29 instead of day 27, because nobody remembered until the animal was due to move. A medicine record that quietly aged past its retention point without anyone checking. A VAT date that arrived as a surprise rather than as something already flagged a week earlier.
None of those individually feels serious in the moment. Together, over a year, they are most of what actually turns into a late filing, a failed assurance question, or an animal that cannot move on the day it was meant to. A calendar that runs on its own, from the farm's own data, is a fairly unglamorous way to close that gap, but it is the one that matches how a busy farm actually operates.
No. It calculates and reminds, it does not submit. Every government filing or record submission still goes through the normal draft-and-confirm step, the same as any other entry in FarmHQ.
The deadline is recalculated from the actual event as soon as it's recorded, so a late-entered birth still gets a correctly calculated passport deadline from its real date, not from whenever it happened to be typed in.
Yes. Because the reminder is generated and sent from FarmHQ's own systems rather than triggered by opening the app, it still reaches you even if the app itself has been untouched since the underlying record was created.
Yes, in two ways. It's calculated automatically from the farm's own recorded events rather than typed in by hand, and it's delivered from FarmHQ's own systems rather than depending on the app being opened to check what's due.