A custom applicator who shows up twice a season with their own rig, and a seasonal picker who works alongside the regular crew under a supervisor’s direction, are obviously different kinds of working relationships. The trouble starts in the wide territory between those two clear cases — a driver who works most weeks of the season, a mechanic who is on the property often enough to feel like staff, a harvest crew brought on through a labor contractor rather than hired directly. The label attached to the arrangement and the reality of it can quietly drift apart, and the records are usually the only evidence of which one was actually true.
Contractor and employee are not two names for the same relationship. They carry different tax treatment, different protections, and different obligations, and a misclassification is not a paperwork error to fix later — it is a finding that can reach back across every week the arrangement existed. The records kept for each need to be different in kind, not just in label.
This page is about what those records look like, and why the difference between the two categories is a distinction with consequences, evidenced by paper rather than declared by intent.
This is not legal or tax advice. Whether a given worker is properly classified as a contractor or an employee is determined by tests set by tax authorities, labour regulators, and courts, and those tests vary by jurisdiction and by which agency is applying them. Nothing on this page tells you how to classify any specific worker. What follows is about the kind of record that supports whichever classification is actually correct. For the classification itself, consult your labour authority, your tax authority, and a lawyer or accountant.
The label on the arrangement is not the classification
Calling a worker a contractor on an invoice does not make them one, in the same way that calling a treatment “preventive maintenance” does not change what a regulator sees when they look at what actually happened. Classification tests look past the label to the substance of the relationship — who directs the work, who supplies the tools, whether the work is a defined project or open-ended availability, whether the person works for others or exclusively for you.
This means the records that matter are not the ones that state the classification, but the ones that document the facts a regulator would actually examine. A written agreement that says “independent contractor” at the top is worth little if every other record shows the person clocking in daily, supervised hour by hour, using tools you provided.
What a contractor's record should actually show
A genuine contractor relationship tends to leave a different paper trail than employment, and the records worth keeping are the ones that reflect that difference honestly rather than papering over its absence.
- A defined scope of work, not open-ended availability — a specific job, with a start and an end, rather than ongoing hours logged the same way an employee’s would be.
- Invoices, not wage stubs — payment tied to completed work or milestones, evidencing a business relationship rather than a pay period.
- Evidence the contractor operates independently — their own equipment, their own insurance, work performed for other clients, a business registration in their own name.
- The written agreement itself, describing the scope and the relationship, kept alongside the invoices and evidence above rather than standing alone.
None of this guarantees a classification will withstand a challenge — that outcome depends on the actual facts, tested against rules this page cannot state. What it does is make the honest version of events demonstrable, which is the most any record can do.
What an employee's record needs that a contractor's does not
Where a contractor’s record centers on scope and invoices, an employee’s centers on hours, supervision, and the obligations that come with direct employment: an onboarding record completed on the first day, hours logged against the enterprise they worked, and training or certification records tied to their name where the role requires it. The shape of the record follows from the shape of the relationship — direction, dependency, and an ongoing wage — rather than from a label chosen for convenience, and it is the same set of obligations described in farm labor recordkeeping for anyone the farm employs directly.
A farm that keeps identical records for both categories — the same hourly logging, the same supervision pattern, the same ongoing weekly arrangement — is keeping records that describe one relationship while calling half of it something else. The paperwork will not resolve that contradiction; only changing the underlying arrangement, or the label, will.
Where the two categories blur, and why the record has to resolve it
The hard cases are rarely the clean ones. A worker who starts as an occasional contractor and gradually becomes a near-permanent fixture, working the same hours as staff under the same supervision, is the pattern that draws scrutiny — not because the arrangement started wrong, but because it drifted without anyone updating the paperwork to match. The records, read honestly over time, are what would reveal that drift, whether or not anyone intended it.
The practical discipline is periodic review: does this relationship, as it actually operates today, still match the category it was assigned when it began. If the answer is no, the record — and the classification — should change to match the reality, not the other way around.
Keeping the two records genuinely separate
The safest practice is keeping contractor and employee records in visibly different forms from the start — different documentation, different payment structures, different logging — rather than running both through the same system with a label swapped. A system that treats every worker identically, regardless of category, produces records that look the same whichever label was chosen, which is the opposite of what a classification challenge needs to see.
Farm40 records employees and their hours against the enterprise they worked, alongside training and certification history where relevant — the employee side of this distinction. It has no separate contractor-invoicing workflow, and it does not determine or validate a worker’s classification; that stays a legal and factual question outside what any record-keeping tool can answer. What it can do is keep the employee-side records honest and complete, so if a classification is ever challenged, at least that half of the picture is not the weak point.
The label costs nothing to write down. The facts behind it are what get examined, and the records either support them or expose the gap between the label and the reality.