Ask most livestock farms who could find last month's medicine book entries, the VAT figures and the passport applications without the farmer, and the honest answer is usually nobody.
A workable setup gives at least the farmer and one other person, usually a spouse, a member of staff or a farm secretary, real access to the farm's compliance and financial records, not just a shared folder nobody opens. An accountant needs read access to the records at year end, not the job of re-entering everything from scratch. Staff and contractors generally only need access to their own timesheets, not the full compliance file.
Most livestock farms run compliance and bookkeeping through one person's head and one person's login, usually the farmer's. That works fine every ordinary week. It stops working the moment that person is in hospital, stuck on a course, or simply too buried in calving to open a laptop, and a BCMS deadline or a VAT return does not pause to wait for them.
The risk is not dramatic most of the time. It shows up as small delays: a passport application filed two days late because nobody else knew a calf had been born, or a receipt going unrecorded for weeks because it sat in a jacket pocket rather than being logged by whoever was actually at the merchant's counter. Individually, none of it looks serious. Over a year, it adds up to exactly the kind of missed deadline and messy record that causes real cost.
The person doing the paperwork on a UK livestock farm is frequently not the person whose name is on the holding. A farmer's spouse or a part-time farm secretary is often the one actually filling in forms, chasing invoices and keeping the medicine book current, working around the farmer's own hours in the yard rather than instead of them.
Software and processes built around the assumption that the farmer personally does every piece of admin tend to fit this reality badly. If the system only really works for one named user, the person who actually does most of the typing ends up working through someone else's login, or keeping a shadow set of notes that never quite matches the official record.
In most cases, the person doing day to day admin needs real access to the compliance side (births, movements, deaths, the medicine book) and the money side (receipts, invoices, VAT records), because that is the actual content of the job. What they do not automatically need is unrestricted control over things like bank transfers or account settings, which are a different kind of risk from typing up a passport application.
The useful distinction is between access to enter and view records, and authority to take an irreversible step, such as submitting to a government system or moving money. A well set up multi-user farm system lets more than one person draft and prepare, while keeping the final submission or payment as a deliberate action, ideally still confirmed by whoever holds ultimate responsibility for the holding.
An accountant genuinely needs to see the farm's financial records at year end: income, expenses, VAT filings, and enough detail behind each to prepare accounts and a tax return properly. What they should not have to do is re-enter a year's worth of receipts from a carrier bag, which is still how a lot of farm bookkeeping reaches an accountant in practice.
The better shape is read access to records that are already in a usable state, with the accountant able to query and export rather than retype. That single change, going from re-entry to review, is usually where the biggest chunk of an annual accountancy bill actually goes on a small farm, and it is entirely a records access problem rather than an accounting one.
Staff and contractors are a different case again. Most of them only need access to log their own hours, which then feeds into the wage records covered in our guide to farm wage records. They do not generally need to see the farm's medicine book, its VAT position or its full compliance history, and giving them that access tends to be an oversight rather than a deliberate decision.
Where a contractor does need visibility into something specific, such as a vet needing to see recent treatment history for a herd they are called out to, the more useful pattern is scoped access to that particular record, not a general login shared informally because it was easier at the time.
The practical risk in giving more than one person access is not usually dishonesty, it is losing track of who entered what, and ending up unable to explain a record if it is ever questioned. A system that logs who drafted an entry and who confirmed it solves this without requiring anyone to trust blindly or check constantly.
This is the shape FarmHQ's multi-user access is built around: the farmer, a spouse or farm secretary, staff, and an accountant can each have their own login and their own scope, while every entry still carries a record of who drafted it and who confirmed it before it went anywhere. Nobody has to share a password to get their part of the job done, and nobody outside the farm gets more access than the specific job actually needs.
Not automatically. A sensible multi-user setup separates drafting and preparing a record from the final submission, so someone can enter a movement or a death without that action alone triggering a government filing. Whether the final submitter is the farmer or someone else is a decision you make deliberately, not a side effect of giving access.
In practice, either nothing gets done until they are available again, or someone works around the system entirely, using informal notes or a shared password that defeats the point of having proper records in the first place. Both outcomes are worse than setting up a second, properly scoped account in advance.
A dedicated accountant login with read access to the records is generally better than sharing your own credentials. It lets the accountant see what they need without also holding the ability to change compliance records or approve submissions that are not theirs to make.
For most family farms, two working logins (the farmer and one other person doing day to day admin) plus a limited accountant login covers it. Larger operations with staff add scoped logins for each employee, generally limited to their own timesheets and relevant records rather than the whole farm file.
Access should be removed as soon as the working relationship ends, the same as you would with any other system. A record of what that person entered while they had access should still remain in the farm's history, since removing their access should not mean losing the records they created.