A workday is a focused capture session for a group of cattle.

Instead of opening each animal's record and editing fields one at a time, you set up a form ahead of time with just the inputs this session needs (a weight, a breeding entry, a status change, a label or two), then queue animals through that form as you work them. The result is a clean, contained dataset of what happened during the session, useful whenever you're working a group through a defined task: spring breeding day, fall preg-check, etc.

This guide covers the practical workflow: creating a workday, running it, and looking at what got done.

The Workdays overview

Click Workdays in the main menu. You'll see every workday you've created, grouped by month with the newest at the top. Each entry shows the title, date, and any description.

Creating a workday

Click Create a workday from the overview. The setup form has three jobs: tell the app what the workday is, what you want to see about each animal as you work, and what data you'll be capturing.

Basic info

• Workday Title (required): what you'll call this session. Spring breeding day, Fall preg-check, Branding 2026, whatever you'd say out loud.
• Workday Description (optional): notes for context. Conditions, who was on the crew, anything worth remembering when you look back at this workday a year from now.
• Workday Date (required): the date you're working.
• Workday Report: pick one or more existing reports to attach. Each becomes a tab on the workday summary, filtered to just the animals you worked. You can always add reports later.

What to show per animal

Under Included General Info, check the fields you want visible when an animal is on screen: Age, Sex, Status, Sire, Dam, Grafted Dam, Surrogate Dam. The idea is to surface only what matters for this workday's decisions, not every fact you ever recorded about the animal. If you've enabled genetics, Included Genetics Info lets you pick specific traits to display.

If you need to see or capture more for an animal during the workday, you'll still be able to drill down one level deeper to do so. This just streamlines the default workflow for rapid entry.

What to capture

Two sections govern what you're updating:

• Included Fields is for properties on the animal itself: Identifiers, Status, Sex, Labels. Check the ones you'll be updating and (where applicable) configure defaults. For identifiers you can preset which types of new IDs you'll be adding so the form is ready to go.
• Included Events & Details is for events: Note, Weight, Bred (breeding), Preg Status (pregnancy status), Sale. Check the events you'll record and set sensible defaults where you can. For instance, the default sire on a breeding event if you're using one bull all day.

The combined effect is a per-animal form with only the inputs this workday actually uses. No clutter from event types you're not touching.

Starting and running

From the workday's summary, click Start workday to kick it off by searching for the first animal to work, and the per-animal form opens.

The form shows the configured display info at the top so you can confirm you've got the right animal, then your capture fields below. Fill in what applies, click Save, and you're back at the search screen for the next animal.

Multi-device

Multiple devices can run the same workday in parallel. Each device gets its own line, a separate work stream within the workday. Every change you make is tagged with the device's line, the user who made it, and a timestamp.

There's no shared queue or animal assignment. Each device picks its own next animal. If two devices accidentally work the same animal, both sets of changes are recorded, and you can sort it out later from the History tab.

If your workday has multiple lines, the Save button shows which line you're saving to (e.g. Save to Line A).

Pausing and finishing

You don't have to formally end a workday. Click Stop to step away. The workday stays open, captured data sticks. Come back, click Start workday, and pick up where you left off.

This is intentional. A spring breeding day might span three weeks; a calving workday runs from February to April. Workdays don't need a hard close.

The workday summary

After (or during) a workday, the summary view collects what's been captured into a few tabs:

• Summary: high-level overview cards. Tasks (a recap of what you set up to capture), sex breakdown, label usage, plus breakdowns for pregnancy, breeding, and weights when those events were recorded.
• Worked Animals (or whatever you named your workday report): the report view, filtered to just the animals you worked. From here you can do everything reports normally do: bulk update, export, build off the result set.
• History: a table of every change made during the workday, with the animal, the user who made the change, and the timestamp. Useful when more than one device was running the workday.

Editing after the fact

Need to change the workday setup itself, like adding an event type or swapping a default? Open the workday and click Edit. Saved changes don't affect data already captured.

Need to fix a specific entry? From the History tab, click the animal's name to reopen the per-animal form for that workday and adjust.

If you missed an animal entirely, just start the workday up again, find the animal, and save changes. There's no separate "add missing animal" flow.

What's next

Workdays produce a lot of data quickly. Once you've worked one, Building reports covers turning that data into views worth keeping. And Using labels is worth a look if you're using labels to flag animals during a workday. The patterns there scale up to hundreds of animals fast.