Running a Farm with a Team: Tasks, Permissions and the Partner Report
Once the flock grows, the problem is no longer the animals — it is organising people. A practical guide to assigning tasks, setting permissions per role, and producing a clear monthly report for a partner or owner.
At 40 head you know everything because you see everything. At 400 head with three employees and a visiting vet, the problem changes completely: it is no longer the animals, it is how information moves between people. Who gave that treatment? Was the weighing done? Why does the partner not know what happened this month?
Rule one: an unwritten task was never assigned
"I told him to treat number 112" is not a task, it is a memory. A task needs four things: what (a clear description), who (a named person, not "one of you"), when (a due date), and priority (high, medium, low). And after execution: who completed it and when.
That single shift — from spoken to written tasks — solves most of the "I said it and it wasn't done" problem on its own.
Roles in a typical farm
Owner / manager: sees everything including finance, and makes buying, selling and culling decisions.
Barn supervisor: assigns daily tasks, follows up on execution, records events (births, deaths, injuries) — and does not necessarily need to see wages or profit.
Worker: executes and records — meals, weights, notes on animals. Needs a very simple screen and no financial data at all.
Veterinarian: sees health history and vaccinations, records diagnosis, treatment and the withdrawal period. Nothing to do with finance or sales.
Nutritionist: sees weights, feed conversion and feed stock, and adjusts rations.
Partner / investor: does not need daily access, but does need a clear monthly report.
The permission principle: the least that lets the job get done
The professional rule is least privilege: each person sees only what they need for their work. This is not distrust — it protects both sides. The employee does not carry responsibility for data that is not theirs, and the owner protects financial and commercial information. And when someone leaves, disabling their account closes the door immediately, instead of changing a password everyone knew.
In Throf, team members are added as sub-accounts with different roles (employee, vet, engineer), each seeing only the sections they are permitted, while finance stays owner-only.
The daily and weekly routine
Daily (10 minutes in the morning): review today's tasks, vaccination alerts and expected births, and any health note from yesterday.
Weekly (30 minutes): review tasks not completed and why, feed and medicine stock and anything close to running out or expiring, and the weights recorded this week.
Monthly (one hour): the full report — the next section.
The partner report: what it should contain
A partner does not want daily detail; they want to know whether things are on track. Five sections are enough:
- Flock status: current head count, additions (births and purchases), removals (sales and deaths).
- Production: lambs born, weaning rate, average weights or milk yield.
- Health: vaccinations completed, disease cases, deaths and their causes.
- Money: expenses by line, sales, and the month's net.
- What's next: what is expected next month (births, vaccinations, selling opportunities) and any decision needing approval.
Clarity here builds trust better than any conversation: a partner who sees the numbers every month does not need to call every week.
Common mistakes in team-run farms
- One shared account: you cannot tell who did what, and you cannot close access when someone leaves.
- Recording at the end of the day: anything not recorded as it happens is forgotten or recorded wrongly.
- A notebook per employee: three notebooks means three versions of the truth. There must be one source.
- Never reviewing uncompleted tasks: a task ignored once becomes a habit.
The short version
Running a farm with a team is not about strictness, it is about clarity: a written task for every job, the right permission for every person, one source of data, and a monthly report that shows the partner what you see. Start with the smallest step this week: turn three tasks you would have said out loud into written tasks with names and dates, and measure the difference.
FAQ
How many workers do I need per 100 head?
It depends on the system (pasture or barn), the level of mechanisation, and the type of production. The more important rule is not the number but the allocation: every recurring job needs one named person responsible for it.
Should employees see the farm's financial data?
Preferably not. Keep finance owner-only, while employees see the operational sections they work in.
How do I make sure workers actually record things?
Make recording easier than not recording: a simple phone screen, few fields, and a short weekly review that shows what is recorded is read and used.
General guidance only — it does not replace your veterinarian or the competent authority in your country.
