Daily Operations Log

The Daily Operations Log is the narrative layer for a batch, or a farm site, on a given day. It records what actually happened: feeding, cleaning, environmental readings, incidents, and more, then goes through a submit-and-approve workflow before it becomes part of the permanent record.

What a Daily Log is for

A Daily Log is not where you record mortality, health events, vaccinations, or feed consumption directly, those are recorded in their own modules, scoped to the batch. Instead, the Daily Log links to them automatically: opening today's log shows the operation entries you added, alongside a read-only rollup of mortality, health, vaccination, and feed activity recorded elsewhere for that batch on that day.

Think of it as the coordination layer for the day, everything that happened, in one place, even though specialised records live in their specialised modules.

Operation entry types

Each entry has an operation type, a timestamp, and the person who recorded it. Twelve types are available:

Quantifiable types (feeding, water change, harvest, and others) capture a quantity and unit. Environmental Check entries capture temperature, humidity, pH, and dissolved oxygen. Incident entries capture a severity level (low, medium, or high) alongside a description and optional evidence photos.

Creating a Daily Log

1. 1

   Navigate to Operations > Daily Logs

   Click "Daily Logs" in the left sidebar under Operations. You can also open today's log directly from a batch's Overview tab.

2. 2

   Choose a batch, a site, or both

   A Daily Log can be scoped to a specific batch, an entire farm site, or both. At least one of the two is required.

3. 3

   Add operation entries as they happen

   Click "Add Entry" and choose an operation type: feeding, cleaning, water change, stocking, transfer, inspection, environmental check, maintenance, treatment, harvest, sanitation, or incident. Fill in quantity and unit where relevant, plus notes.

4. 4

   Attach evidence where it matters

   Evidence photos can be attached to an incident entry, and general documents can be attached to the log as a whole, from the Attachments tab.

5. 5

   Save as draft

   Entries save as you go. The log stays editable in Draft status until it is submitted.

Submitting for approval

When the day's recording is complete, submit the log for review. A submitted log is locked from further entries; if something was missed, it must be rejected back to draft by an approver before it can be edited again.

Approving a Daily Log

Users with the daily-log.approve permission can approve or reject a submitted log. Approving a log with linked feed entries confirms that feed consumption and deducts it from inventory.

A rejected log returns to the submitter with a required rejection reason, visible in the log's Workflow History tab alongside every other status change.

Daily Operations Coverage score

Every Daily Log shows a Coverage score from 0-100%, a quick signal of how complete the day's record is. It's computed from three factors: whether entries were recorded, whether a feed log is linked, and how far the workflow has progressed.

A low score triggers a warning banner directly on the log, calling out specifically what's missing, no feed log linked, or no entries recorded, so gaps are visible before month-end, not after.

Best practices

• Log as it happens, not at the end of the day. Each entry has its own timestamp; recording in the moment keeps the timeline accurate and makes incidents visible sooner.
• Attach evidence to incidents. A photo attached at the time of an incident is far more useful during review than a description alone.
• Review the Coverage score before submitting. A score below 100% usually means a feed log isn't linked yet, check before submitting for approval.
• Approve promptly, but carefully. Approval deducts inventory immediately and cannot be reversed; review the linked feed quantities before confirming.