You are putting together the paperwork for a new hire, and two documents sit in front of you: the employment agreement and the employee handbook. It would be easy to treat them as one combined mass of text and split the terms between them by instinct. The placement decision deserves more thought than that, because the two documents carry very different legal weight. A term that must bind an employee for years after they leave only works in one of them, and a handbook that looks like a flexible set of rules can quietly turn into part of the employment contract.
Two documents, one placement decision
An employment agreement is a contract between you and one employee. Australian law does not require it to be in writing: the Fair Work Ombudsman notes that an employment contract can be verbal or written, and can be called an agreement, terms and conditions, or a workplace contract. Because it is a contract, both sides can enforce it. If either party breaches a term, the other can ultimately take the dispute to court and seek damages or an order compelling performance.
An employee handbook is different. It is a collection of policies, which in practice are written directions to your workforce about expected conduct, processes and standards. A policy is not itself a contract. If an employee ignores a policy, your response is disciplinary, not a court claim for breach of contract. That distinction drives everything else in this article.
The real question you are answering is narrower than "which document do I need". It is: for each individual term, which document should carry it? The answer depends on five factors: what each document can enforce, which terms only a contract can protect, what the handbook is actually for, how easily each document can change, and the minimum standards that sit beneath both of them. There is also a warning hidden in the question. The two documents are not as cleanly separate as they look, because a handbook can become contractually binding if your agreement incorporates it by reference, or if employees reasonably rely on it as a promise. Once that happens, the flexibility you thought you had disappears.
Five factors that decide where a term belongs
What each document can actually enforce
The starting point is legal status. A contract creates binding obligations on both parties. If you breach the agreement, the employee can sue you. If the employee breaches it, you can take disciplinary action, terminate for serious breach, and in some cases recover damages. That is why the terms you genuinely need to enforce go in the agreement.
A policy creates obligations in a looser sense. It is a direction, and an employee who ignores it faces warnings and, ultimately, termination. But you cannot take an employee to court simply because they breached a policy, any more than they can sue you for not following one. Unless the policy has been incorporated into the contract, it sits outside the enforceable bargain.
The catch is incorporation. If your agreement says the employee "must comply with the company policies as amended from time to time", that sentence can pull the whole handbook into the contract. The same can happen through a consistent course of conduct, such as paying employees according to a policy promise until one day you stop. What looked like a flexible handbook can become a set of enforceable terms that you cannot change unilaterally.
Which terms only a contract can protect
Some terms are commercially important precisely because they need to bind after the employment ends, or because they protect assets the employee creates. These have no home in a handbook.
- Notice of termination: The National Employment Standards (NES) in s 117 of the Fair Work Act 2009 (Cth) set minimum notice periods: one week for up to a year of service, two weeks for one to three years, three weeks for three to five years, and four weeks beyond five years, with an extra week for employees over 45 with at least two years of service. A clause in the agreement sets the notice you and the employee have actually agreed on, usually at or above those minimums. If the agreement is silent, the NES still apply, but you can end up arguing about what reasonable notice at common law would have required, and that ambiguity is where disputes start.
- Intellectual property: For copyright, there is a default rule in your favour. Under s 35 of the Copyright Act 1968 (Cth), an employer owns the copyright in literary, dramatic, musical and artistic works made by an employee under a contract of service, unless the parties agree otherwise. That default does not extend to patents, designs, trade secrets and other confidential know-how. An assignment clause in the agreement is what captures those, and it is also the mechanism for varying the statutory copyright default where you want a different result.
- Confidential information: A confidentiality clause binds an employee during employment and, properly drafted, continues to bind them after termination. A handbook policy simply cannot do that.
- Restraints: Post-employment restraints on soliciting clients, poaching staff or competing are enforceable only to the extent they are reasonable and protect a legitimate business interest, as the Federal Court confirmed in Pearson v HRX Holdings Pty Ltd [2012] FCAFC 111. If there is no restraint clause, no court will invent one for you. This is the clearest example of a term with no possible home in a handbook.
What the handbook is actually for
The handbook is the right home for standards that apply to everyone in the business and that change as the business changes. Two broad categories cover most of it.
- Core policies that touch liability: A work health and safety policy, an anti-discrimination and anti-bullying policy, and an IT use policy. These matter because an employer can be held liable for discriminatory or harassing conduct by staff in the course of employment, and a clear policy that is actually trained on and enforced is part of the picture a court or tribunal weighs when deciding whether you took reasonable steps.
- Operational policies that keep the business running: How to apply for leave, complete timesheets, claim expenses, dress, and behave in the office. These are the details that evolve, and they belong in a document you can update.
There is no rule that every operational detail must live in the handbook. If a direction matters to the whole company, a policy is the practical way to communicate it. If it matters to one employee's bargain, it belongs in the agreement.
How easily each document can change
This factor is where employers most often trip up. An employment agreement cannot be changed unilaterally. Varying a term of the contract requires the employee's agreement, usually recorded in a signed letter of variation or a new agreement. A unilateral change to a significant term is a breach of contract and can amount to a repudiation that entitles the employee to treat the employment as over and claim damages.
A handbook, by contrast, is designed to change. You can update an expenses process or a dress standard and document the new version without each employee's signature, as long as you notify staff of the change and, ideally, have them acknowledge it.
But compare the two scenarios:
- Agreement incorporates the handbook: If your agreement says the employee must comply with policies as amended from time to time, every future handbook change becomes a change to the contract. The flexibility you wanted is gone, and an employee who is worse off after an update has a genuine argument that you breached their contract.
- Agreement stays silent on policies: The handbook remains a set of directions you can update freely, and employees are disciplined for non-compliance rather than for breaching the contract. This is the cleaner structure for a business that expects its operations to evolve.
Drafting an express incorporation clause is not always wrong. It gives you a contractual hook to enforce policy compliance, and some businesses value that more than flexibility. The point is that the choice is real, and it is made by one line in the agreement, often without anyone noticing.
The minimum standards floor beneath both documents
Neither document creates your employees' core entitlements. They sit on top of a statutory floor that neither can undercut. Section 61 of the Fair Work Act 2009 (Cth) makes the NES minimum standards that cannot be displaced, and the Fair Work Ombudsman states that an employment contract cannot remove or provide for less than an employee's minimum entitlements. Where a modern award or enterprise agreement also applies, those minimums operate alongside the NES and the contract.
This matters in two ways. First, a term that tries to contract out of a minimum, whether in the agreement or in a policy, is ineffective to the extent it is less beneficial to the employee. Writing "no annual leave in the first year" into either document does not make it lawful. Second, it means the documents' job is to add certainty and commercially useful obligations above the floor, not to substitute for it. A notice clause sets your agreed notice above the NES minimum. An IP clause assigns rights the statute does not already give you. An anti-discrimination policy demonstrates the reasonable steps that reduce liability. None of them replace the entitlements themselves.
How an Artificer Legal employment lawyer gets the split right
Working out where each term belongs is a drafting exercise, and it is one where small choices create large differences. An employment lawyer at Artificer Legal can audit the agreement and handbook you already use and map each term to the document that can actually enforce it. That means stress-testing the assumptions behind the placement, such as the belief that a restraint in the handbook will hold up, or that a policy change is always safe because it is "just a policy".
The drafting itself is where the value concentrates. A restraint that courts will enforce needs to be scoped to the legitimate interest it protects, which is a judgement call about your actual client base and the employee's role. An IP clause needs to assign what the statute does not already cover. An incorporation clause, or the deliberate absence of one, should be a decision you make rather than an accident of an old template. A practitioner can also model the downside of each choice, such as a client poached by a former employee because the restraint was unenforceable, or a handbook you cannot update because it was pulled into the contract. Getting the split reviewed costs a fraction of what either failure costs.
The handbook line that quietly becomes a contract
The point that most often gets missed is the interaction between the two documents. Every term you will one day need a court to enforce, a restraint, a confidentiality obligation, an IP assignment, has to live in the agreement, because that is the only document with contractual force. But the handbook's great virtue, its flexibility, survives only while it stays outside the contract. A single sentence in the agreement incorporating policies as amended from time to time can hand that flexibility away without anyone intending it.
The practical version of this article is short. Put the enforceable terms in the agreement, put the changeable standards in the handbook, and decide consciously whether any part of the handbook should be contractual. An employment agreement and an employee handbook are separate documents doing separate jobs. The agreement is the enforceable bargain between you and one employee, it can only be varied by mutual agreement, and it carries the terms that must bind before, during and after employment. The handbook is your set of directions to the workforce, it can be updated as the business changes, and it carries the core policies that protect you from liability and the operational details that keep things running. Neither can displace the NES or award minimums that sit beneath them. If you are drafting either document for the first time, or inheriting a pair that were never designed together, it is worth having a lawyer check the line between them before an employee or a court does.