Review and complete daily farm work

What this workflow achieves

This workflow helps a team turn due work into verified farm records. It connects five different views without confusing their purpose:

View	What it is for
Dashboard	A selected-farm snapshot and links to source work.
Work	Current due, overdue, upcoming and unscheduled jobs derived from farm records.
Execution mode	A stable local working round containing the jobs present when it began.
Calendar	Dated planned/due/completed events across a six-week view.
Alerts / Notifications	Conditions requiring attention and messages delivered about them.

A reminder, alert acknowledgement, calendar event or local session state is not the underlying treatment, vaccination, milk, breeding or lifecycle record. Complete the source form and verify its saved result.

1. Confirm the farm and farm-local day

Before starting, check Current Farm in the left navigation and the farm-local date/time in the header. Work, overdue status, calendar days and alert timing use the farm’s timezone even when the user is elsewhere.

If an expected number is a dash, loading, partial or failed, do not treat it as zero. Retry the source and inspect its error/coverage message.

2. Read the dashboard as a starting point

Open Today → Dashboard.

The headline indicators can include:

• Conception rate over the last 90 days;
• Average daily yield per cow over the last 30 days;
• weighted herd SCC over the last 30 days; and
• Calving interval over a rolling 24 months.

Dairy-only cards are hidden on beef-only farms. A missing value can mean insufficient data, not poor performance.

Use:

• Start Today’s Work or Today’s Work cards to open the actionable queue;
• Compliance & exceptions for withdrawals, low stock and pending registry work;
• Next actions for upcoming calendar items;
• Farm pulse for active animals, watch list, do-not-breed and lifecycle composition; and
• the routine/economic sections to open their source reports.

Opening a dashboard action does not save the work. Follow it to the source form.

3. Filter the Work board

Open Today → Work.

Control	How to use it
Find or scan animal	Search tag, national ID or name and select the correct animal. / focuses the search.
Area	All, Farm, Animals, Health, Breeding, Milk, Lifecycle, Feed, Inventory, Compliance or Beef. Changing area clears an incompatible task filter.
Timing: All	Includes overdue, due, upcoming and unscheduled work.
Due now	Overdue plus due today.
Overdue	Missed farm-local due dates.
Due today	Due on the current farm day only.
Upcoming	Future-dated work.
Unscheduled	Work without a due date; it is not completed history.
Task card	Restricts the list to one work type; All work/Clear removes it.
Refresh work	Requests current derived work; it does not create/complete records.

The list is paged at 25 rows. Read each job’s due state, animal identity, title and instruction before acting. A disabled action can reflect missing permission or an invalid current state; selecting a row does not grant authority.

If the page says Partial or a count ends with +, one or more work sources are incomplete. The displayed total can understate the farm workload. Retry the named source before relying on it.

4. Record one job

Select the action on the correct row. Enter what actually happened using the source form, including farm-local occurrence date/time, animal, result, product/dose/quantity and notes/evidence as applicable.

Review validation and save. Then confirm:

1. the source module shows the new record;
2. stock/withdrawal/lifecycle effects are correct where relevant;
3. the work item disappears or changes state after refresh; and
4. no duplicate was created while waiting for an asynchronous refresh.

Simply opening and closing a form does not complete a job. A reminder can remain briefly while its source projection or alert evaluation catches up.

5. Record a compatible batch from Work

Use batch recording only when the same supported operation applies to several animals.

1. Choose Area, Timing and task.
2. Tick one eligible job; that first row establishes the batch action/type.
3. Select further compatible rows. Different actions, protocol/vaccine variants or incompatible states cannot join.
4. Use Select all … compatible on this page for eligible rows on the visible page.
5. Where available, use Select all … matching for matching rows beyond the page; a limited action instead offers Select first N of total.
6. Check the selected count, animals and batch maximum.
7. Choose Run batch, complete required shared and per-animal fields, then save.
8. Review saved, skipped and failed outcomes. Retry only failed animals after checking current records.

Clear changes only the selection. Filter changes clear it, while ordinary paging can retain it; always recheck the selected count before Run batch. For vaccination, select the intended vaccine/protocol before building its compatible batch.

6. Start an execution-mode round

Choose Start Work → Start session after reviewing the available jobs. Execution mode freezes a stable starting list for this browser round, so newly derived work does not continually reorder the session.

Control	Meaning
N remaining of N	Remaining excludes recorded and deferred jobs; starting total remains fixed.
Started	Local browser-session start time.
Area buttons	Filter remaining jobs and show remaining counts by area. Changing area clears batch selection.
Search session	Searches tag, name, national ID or work type inside this session. / focuses it.
Record action	Opens the source form for one job.
Defer	Skips this job for the local round only. It does not change due date, snooze an alert or save work.
Summary / Finish session	Ends the work view and displays Recorded, Deferred and Unresolved counts.
Exit	Confirms discarding the local session. Already saved farm records remain.

Batch inside execution mode

Tick one job to establish the type, then use Select all … compatible visible jobs for the current area/search view up to the action maximum. Searching hides rows but does not clear an existing selection; choose Clear explicitly when starting another batch.

A partially successful batch records only successful animals. Failed animals remain unfinished even if the batch panel closes.

7. Finish, defer or leave a round

The summary means:

• Recorded — its source recording action was accepted; dependent alert effects may still be processing;
• Deferred — skipped in this local round and still needs work/review; and
• Unresolved — neither recorded nor deferred.

Finishing a session does not complete unresolved jobs. A later round is rebuilt from current farm records and can include deferred work again. Exiting/discarding a session never undoes saved treatments, milk, breeding or other records.

An unfinished session can be restored in the same browser tab. Treat it as a convenience list, not shared work-allocation evidence for other devices.

8. Use Calendar for dated work

Open Today → Calendar.

Control	Effect
Previous / Next	Moves between six-week Monday-to-Sunday windows and closes selected-day detail.
Today	Returns to the farm’s current month.
Work	Outstanding planned/due events; default.
All	Outstanding plus completed records.
Completed	Recorded/completed events only.
All types / type chips	Toggle Calving, Dry off, Vaccination, Treatment, Follow-up, PD check, Vet visit and Feed plan. At least one remains selected.

Counts cover the loaded six-week grid, including adjacent-month days, after type filtering. Select a day to open all visible entries. Read status:

• Planned is expected work, not a recorded event;
• Overdue has a date before farm today;
• Due today is due on farm today; and
• Done is recorded/completed.

Grouped vaccination or pregnancy-check events offer batch action only when compatible. Enter actual results; calendar date alone is not evidence. Calendar is not a free-form appointment diary—create/edit work in its owning module.

9. Investigate an alert

Open Today → Alerts. Use status, severity and category filters; pages contain up to 20 alerts. Active includes acknowledged alerts, while Snoozed/Resolved/Dismissed are lifecycle states, not source records.

Open alert detail and inspect alert type, animal/farm scope, created/due/escalation times, acknowledgement/resolution/snooze/dismiss evidence, auto-resolvable flag and any linked delivery/source action.

Choose the action that matches your intention:

Action	What it records
Acknowledge	Someone has seen and is handling the alert. Bulk heading selection affects the current page only.
Snooze	Temporarily postpones this alert for 1, 4, 8 or 24 hours, 3 or 7 days, or a custom future farm-local time.
Resolve	Closes the alert, optionally with useful resolution notes.
Dismiss	Suppresses this occurrence after confirmation.
Recording action	Opens the underlying form that records what happened.

None of the first four actions creates the underlying clinical/stock/milk/lifecycle record. Group snooze or batch follow-up can return partial success; review the result.

10. Understand and tune alert generation

Farmlync raises alerts from record changes and scheduled checks. It applies the selected farm’s enabled rule, thresholds, severity, auto-resolution and escalation. Continuing conditions are evaluated repeatedly without intentionally producing a duplicate every minute; a cleared condition that later returns can create another occurrence.

Scheduled evaluation wakes roughly every minute for farms needing a pass, while escalation checks periodically (about every 15 minutes). These are processing intervals, not exact delivery guarantees.

An Owner/Manager opens Alerts → Alert Rules:

Control	Effect
Enabled	Saves immediately; there is no page-level draft Save.
Edit Severity	Critical, High, Medium, Low or Info.
Auto-resolve	Allows supported conditions to close when cleared.
Escalation Hours	Optional positive whole hours. Current escalation applies to Active High/Critical alerts.
Threshold Parameters (JSON)	Rule-specific settings only. Preserve exact supported names and numeric value types.
Re-evaluate Now	Queues a new evaluation; it is not a synchronous result.
Reset to Defaults	Replaces custom settings after confirmation.

Changing a JSON key to an invented/misspelled name can save yet have no intended effect because evaluators can fall back to defaults. Use the rule guide’s threshold catalogue, change one supported value and verify an affected source record/alert after re-evaluation.

11. Check notifications and delivery preferences

Open the bell or Notifications for this selected farm. Use Unread Only/Show All, paging, individual Mark read and Mark All Read. Failed/Suppressed rows explain delivery state where available. Inbox presence or absence does not prove work completion.

In Preferences, configure:

• In-App Notifications;
• Email Notifications;
• Push Notifications;
• Daily alert digest at 07:00 farm-local (requires Email); and
• Quiet Hours with both Start and End plus timezone. Non-critical notifications are suppressed during quiet hours; critical alerts can still deliver.

Choose Save Preferences and wait for success. Browser/phone push also needs an enabled device subscription and browser permission. Use Send test push after enabling the device.

Per-alert-type channel chips save immediately and are separate from the main preferences Save. Reset an override to inherit general choices. Delivery channel settings do not disable the farm alert rule itself.

Completion checklist

• Current farm and farm-local day were confirmed.
• Partial, unavailable and failed counts were not treated as zero.
• Each completed job has a saved source record.
• Batch selections contain only compatible jobs and outcomes were reviewed per animal.
• Deferred/unresolved execution items remain visible for follow-up.
• Calendar planned events were not mistaken for completed records.
• Alert acknowledgement/snooze/resolve was not used instead of recording work.
• Rule changes use supported parameters and were re-evaluated/verified.
• Notification preferences and device push subscription were checked separately.

For control-level references, see Dashboard, Work board, Execution mode, Calendar, Alerts, Alert Rules and Notifications.