Purpose-built reminder types
Vaccination, treatment, pregnancy check, calving, and custom reminder types match the recurring work farms actually track.
Boma turns vaccinations, treatments, pregnancy checks, and custom follow-ups into tracked reminders with due dates and status, so the farm knows what is due, what is overdue, and who it is assigned to.
Typed reminders
Vaccination, treatment, pregnancy check, calving, and custom types built in.
Status-tracked
Pending, in progress, snoozed, and completed states, not a flat checklist.
Assignable
Reminders can be pointed at a specific team member, not left ambiguous.
Task Board
Reminders are organized by status and due date, with priority levels highlighting what needs attention first.
What This Feature Does
Reminders and Tasks turns time-sensitive farm work into something the system tracks, instead of something a manager has to hold in their head. A reminder has a type — vaccination, treatment, pregnancy check, calving, or a custom category — a due date, a priority, and a status that moves from pending through in progress to completed, with a snooze option for work that needs to shift without being lost.
Reminders can be tied to a specific animal, connecting the follow-up work directly to the record it concerns, and can be assigned to a specific team member so it is clear whose job it is to act. An overdue reminder is not just a missed deadline sitting quietly in a list — it surfaces in dashboards and alerts so it gets noticed.
Because reminders live in the same system as everything else, completing one — like logging a vaccination — can connect directly to the health record it was tracking, keeping the "what was supposed to happen" and "what actually happened" in the same place.
Key Capabilities
Each capability below is available today inside Boma, not a roadmap promise. Together they form the working core of this feature.
Vaccination, treatment, pregnancy check, calving, and custom reminder types match the recurring work farms actually track.
Every reminder carries a due date and a priority, so the farm can distinguish between urgent and routine follow-ups at a glance.
Reminders move through pending, in progress, snoozed, and completed states, giving a realistic picture of work in motion, not just a binary done or not-done.
A reminder tied to a specific animal connects the scheduled action directly to that animal’s record, so context is never lost.
Reminders can be assigned to a team member, removing the ambiguity of a shared task list nobody feels individually responsible for.
Overdue reminders surface across dashboards and alerts, so a missed follow-up gets noticed instead of quietly aging in a list.
A reminder that needs to shift can be snoozed to a new date rather than being deleted and recreated, preserving its history and context.
Why It Matters
Livestock work has a rhythm of recurring obligations — vaccinations on a schedule, pregnancy checks at the right window, treatments that need a follow-up. When that rhythm lives only in a manager’s memory or a paper calendar on the wall, it eventually breaks: someone is out sick, the calendar gets left in the truck, or the farm simply gets busy and something slips.
Boma’s reminders exist to make follow-through a property of the system, not a property of any one person’s memory or discipline. A reminder assigned to a specific person with a clear due date is dramatically more likely to get done than a mental note or a line on a whiteboard, and when it does slip, it is visible instead of silent.
Fewer missed vaccinations and treatments
Scheduled work with visible due dates is far less likely to be forgotten than a mental note.
Clear ownership of follow-up work
Assigning a reminder to a specific person removes the ambiguity of a shared, unowned task list.
Overdue work gets noticed
A missed deadline surfaces in dashboards instead of aging quietly in a forgotten list.
Continuity when staff are unavailable
Scheduled reminders do not depend on one person being present to remember them.
Use Cases By Role
Boma is built around real farm roles. Here is how this feature shows up differently depending on who is signed in.
An owner can review overdue reminders across every category — vaccinations, treatments, pregnancy checks — without asking the manager for a status update.
A manager scheduling a vaccination round creates reminders for the relevant animals, assigns them to specific workers, and tracks completion as entries come in.
A worker checks their assigned reminders for the day, completes each one from mobile, and the system reflects the update immediately for anyone else watching.
After treating an animal, a vet can create a follow-up reminder to check on the animal in a set number of days, ensuring the case does not quietly drop off.
A platform admin supporting a new tenant can check whether reminders are being created and completed, an early signal of whether the farm is getting real value from the feature.
How It Works
A reminder moves through a clear lifecycle from creation to completion.
A type, due date, priority, and optionally an animal and assignee are set, either manually or as part of a vaccination schedule.
The assigned team member sees the reminder in their task list on web and mobile.
The reminder moves to in progress, gets snoozed if needed, or is marked completed once the work is done.
If a due date passes without completion, the reminder is flagged as overdue across relevant dashboards.
Completing a reminder tied to an animal keeps that follow-through visible in the animal’s own history.
Reminders are scoped to the farm that created them, following the same farm-level isolation as every other record type, so reminder data never crosses tenant boundaries.
Creating and assigning reminders generally follows the farm’s role permissions, while completing an assigned reminder is available to the person it was assigned to, keeping ownership clear without making the system unnecessarily restrictive for day-to-day use.
Farm-level isolation
Reminder data is scoped to the farm that created it, like every other record type.
Assignment-based ownership
A reminder’s assignee is explicit, making responsibility for follow-through unambiguous.
Status history preserved
Snoozing or completing a reminder does not erase its prior state, keeping a usable history.
Role-appropriate creation
Who can create and assign reminders follows the farm’s configured role permissions.
Business Outcomes
These are the practical shifts farms describe once the feature is part of daily use, not a marketing estimate.
Higher follow-through on scheduled work
Assigned reminders with due dates get completed more reliably than informal reminders.
Fewer silent misses
Overdue work is visible in dashboards instead of quietly falling through the cracks.
Clear individual accountability
Assigning a reminder to a specific person removes ambiguity about whose job it is.
Less time spent tracking status manually
Managers can see reminder status directly instead of following up individually to ask.
Questions
Specific answers for teams evaluating whether this part of Boma fits how the farm actually runs.
Yes. Vaccination schedules generate related reminders so a recurring protocol turns into tracked follow-up work rather than something a manager has to remember to create manually each time.
The reminder is flagged as overdue and surfaces in relevant dashboards and alerts, rather than quietly remaining in a pending state unnoticed.
Reminders can be updated, including their assignee, by users with the appropriate role, so work can be reassigned if someone’s availability changes.
Yes. Snoozing moves a reminder’s due date forward while preserving it as still outstanding, while completing marks the work as done. Snoozed reminders remain visible rather than disappearing.
Visibility follows the farm’s configuration and role permissions, but assignment makes it clear whose responsibility a given reminder is, regardless of broader visibility.
Related Features
Ready To Try It
Start free and turn vaccinations, treatments, and follow-ups into reminders your team actually completes.