Alex is Sprintlaw’s co-founder and principal lawyer. Alex previously worked at a top-tier firm as a lawyer specialising in technology and media contracts, and founded a digital agency which he sold in 2015.
Hiring your first team or scaling your workforce is exciting - but the way you set pay and conditions can get confusing quickly.
Two terms you’ll hear a lot are “common law contract” and “enterprise agreement”. Both are lawful ways to set employment terms in Australia, but they work very differently and have very different implications for small businesses.
In this guide, we walk through what each option is, how they interact with the National Employment Standards (NES) and awards, the pros and cons for small employers, and a practical roadmap to decide which approach suits your business today - and as you grow.
What’s The Difference Between A Common Law Contract And An Enterprise Agreement?
At a high level:
- A common law contract is the individual employment agreement you give each employee. It sets role-specific terms like duties, pay, confidentiality and notice. It can’t undercut legal minimums such as the NES or any applicable modern award.
- An enterprise agreement (EA) is a collective agreement made between an employer (or group) and its employees. It must be bargained in good faith, pass the Better Off Overall Test (BOOT) against any relevant award, and be approved by the Fair Work Commission (FWC). Once approved, it becomes the primary instrument setting terms for the covered employees.
Both sit within the Fair Work framework. No matter which path you choose, the NES always applies and you need to check any relevant Modern Awards for minimum entitlements that can’t be undercut.
How Do Awards And The NES Fit Into This?
Think of the NES as the non‑negotiable floor for all employees covered by the Fair Work Act 2009 (Cth). This includes things like annual leave, parental leave, personal/carer’s leave, public holidays and maximum weekly hours.
On top of that, many roles are award-covered. Awards set occupation or industry-specific minimums like base rates, loadings, penalty rates, allowances, rostering rules and overtime. If a role is award-covered, any common law contract must at least match (or exceed) these terms.
An enterprise agreement can replace the award, but only if each employee is better off overall compared to the award (the BOOT). The FWC will test this before approving the agreement.
If you rely on contracts only, you’ll still need to ensure things like maximum weekly hours, penalty rates and overtime/allowances meet or exceed the relevant award and the NES.
When Does A Common Law Contract Make Sense For Small Businesses?
For most small businesses, starting with well-drafted individual contracts is the simplest and lowest-cost pathway to compliance. You can tailor terms to the role and scale without launching into a formal bargaining process.
Key advantages of contracts
- Simplicity and speed: You can onboard quickly using an appropriate Employment Contract or Casual Employment Contract template tailored to your business and award coverage.
- Flexibility: Easy to adapt role-by-role (e.g. commission structures, bonus clauses, remote work terms) provided you don’t undercut legal minimums.
- Lower cost and admin: No formal bargaining or FWC approval is required. You manage compliance through contracts, payroll settings and policies.
What to watch
- Award compliance: If your roles are award-covered, you must keep on top of minimum rates, allowances and penalties. Build them into your contract and payroll settings so you’re not underpaying.
- Clarity and consistency: Good contracts should clearly address duties, hours, overtime or TOIL, confidentiality, IP ownership, post-employment restraints and notice periods. It’s wise to align these with your Workplace Policies and a central Staff Handbook so managers apply them consistently.
- Ongoing updates: Awards and minimum wage rates are reviewed annually. You’ll need to adjust pay and conditions when changes take effect to remain compliant.
When Would An Enterprise Agreement Be Better?
An enterprise agreement can be useful once you have a larger workforce with similar roles, complex rostering, or a need for tailored conditions across a whole site or business.
Potential benefits of an EA
- Customisation at scale: You can set tailored hours, classifications, allowances and rostering rules that work for your operation and workforce, rather than juggling multiple awards.
- Industrial certainty: A well-designed EA can reduce ambiguity and provide stability for several years (until its nominal expiry), which can help with budgeting and workforce planning.
- Clear internal processes: EAs typically include procedures for consultation, dispute resolution and flexibility requests, which can streamline HR management.
Consider the costs and obligations
- Time and process: You must follow the bargaining rules, communicate with employees, provide access to the proposed agreement, and ensure it passes the BOOT. The FWC must approve it before it takes effect.
- Rigour and record-keeping: You’ll need strong HR systems to apply classifications correctly, monitor rosters and entitlements and manage consultation obligations.
- Less agility: Changing an EA mid-term is not simple. If your business model is evolving, a contract-and-award approach can be easier to adjust in the short term.
For many small businesses, an EA becomes attractive once headcount grows and you’re managing a consistent workforce where the efficiencies of one tailored instrument outweigh the setup effort.
Can You Use Both? How They Interact In Practice
Yes - most businesses with an EA also issue a written employment contract. The EA sets the collective baseline for covered employees, while the contract covers things the EA doesn’t, like confidentiality, IP ownership, conflict of interest, restraints and any non‑monetary benefits.
In the event of a conflict, the hierarchy generally looks like this for covered employees: NES (top) → EA (must pass BOOT) → individual contract (cannot undercut the EA or NES). Your contracts should be drafted to “work with” the EA and avoid inconsistency.
For employees not covered by the EA (for example, management or non-covered roles), your individual contract plus any applicable award and the NES will govern.
What’s Involved In Moving To An Enterprise Agreement?
If you’re weighing up an EA, here’s an overview of how it typically works. This is a general guide - the details matter, so get tailored advice early.
1) Decide scope and objectives
Identify which employees you want covered, what awards currently apply, and what you want to achieve (for example, a simplified classification structure, a flexible rostering model, or consolidated allowances). Consider how your business will look in 2-3 years so the EA supports growth.
2) Prepare a draft and BOOT analysis
Draft an agreement that is easy to read and operationally workable. Model pay and conditions so that each employee would be better off overall than under the relevant award. Build examples to evidence the BOOT across typical patterns including weekend work, overtime and allowances.
3) Bargain in good faith
Notify employees of the bargaining process and provide a copy of the draft. Keep clear records of discussions and changes. Ensure employees have a genuine opportunity to understand and consider the proposal.
4) Employee vote
After a proper access period, employees cast a vote. If a majority of the employees who cast a valid vote approve, you may apply to the FWC for approval.
5) FWC approval
The FWC will assess the agreement, including the BOOT, proper explanation to employees, and compliance with required terms (NES interaction, flexibility, consultation, dispute resolution). If approved, the EA takes effect from the specified start date.
Once your EA is in place, keep your payroll and rostering systems aligned and train your managers. Make sure your contracts for covered employees are consistent with the EA.
If You Stick With Contracts, How Do You Stay Compliant?
The contract-and-award route is very workable for small teams. To do it confidently, focus on these pillars:
Pay and classification accuracy
Confirm which award (if any) applies to each role and the correct classification. Build award rates, overtime, allowances and loadings into your payroll rules. Many employers also sanity‑check pay outcomes using a pay calculator and periodic audits.
Clear written contracts
Use role-appropriate agreements - for example, a Employment Contract for permanent staff and a Casual Employment Contract for genuine casuals. Your contracts should cover duties, hours, overtime arrangements, leave, probation, notice, confidentiality, IP and post‑employment restraints where appropriate.
Aligned policies and handbooks
Policies turn your contractual framework into day-to-day guidance for managers. Code of conduct, leave, WHS, performance management and grievance processes are standard inclusions in a central Staff Handbook, supported by any role or site-specific Workplace Policies.
Manage rosters, hours and leave
Set rosters and breaks in line with the award and NES. Watch trigger points for overtime, meal breaks and weekend or public holiday work so the right rates and notice periods are applied. If you use time off in lieu (TOIL), make sure it’s permitted and documented.
Common Legal Questions Small Employers Ask
Do I need an enterprise agreement to pay all‑inclusive salaries?
No. You can use contracts with annualised salaries provided the salaries are sufficient and you meet any award requirements for annualised wage arrangements (such as record‑keeping, pay reconciliation and ensuring employees are better off than if they were paid strictly per the award). Some employers prefer an EA for certainty across a workforce, but it’s not mandatory just to pay salaries.
Can a contract “contract out” of an award?
No. A contract cannot undercut an award or the NES. If you offer different arrangements, the total package must still leave the employee better off than the award would have.
Can I include post-employment restraints in an EA?
Generally, restraint clauses (like non‑solicit or non‑compete) are included in individual contracts rather than the EA. If restraints are important to your business model, ensure they are appropriately drafted in the contract and supported by your IP and confidentiality terms.
What happens when our EA expires?
An EA has a nominal expiry date, but it continues to operate until it’s terminated or replaced. Employers often start bargaining for a replacement well before the nominal expiry to avoid gaps and to reflect changes in the business, law and pay rates.
How To Decide: A Practical Framework For Small Businesses
There isn’t a one-size-fits-all answer. Use these questions to guide your decision:
- Headcount and growth: Are you a small, agile team or moving toward a larger, stable workforce with similar roles and rosters?
- Operational complexity: Do you need tailored rostering/allowance rules across many staff, or can award rules plus good contracts and policies manage your needs?
- Compliance capability: Do you have the systems and HR resources to bargain, model the BOOT and manage EA obligations - or would you prefer a leaner compliance setup early on?
- Change horizon: Is your business likely to pivot in the next 1-2 years? If so, contracts may provide easier short-term flexibility while you find your operating rhythm.
- Industrial certainty: Would a multi‑year, business‑specific instrument help with budgeting and engagement, or is the cost and time of bargaining not justified yet?
For many small businesses, the staged approach works best: start with robust contracts, policies and award compliance; then explore an EA once your workforce is large and consistent enough to benefit from a tailored, business‑wide instrument.
Implementation Tips So Your Approach Works Day-To-Day
Keep documentation aligned
Make sure your contracts, EA (if you have one), policies, payroll rules and manager training all point in the same direction. Conflicts between documents are a common source of disputes and underpayments.
Build compliance into systems
Set award rules in your time-and-attendance and payroll systems so penalty rates, overtime and allowances calculate automatically. Manual workarounds are where errors creep in.
Audit regularly
Spot-check classifications and pay outcomes, particularly when awards are updated. Consider periodic reviews of overtime, breaks and rostering patterns against your instrument (contract/award or EA).
Communicate clearly
Whether you rely on contracts or an EA, invest in training for managers and accessible policies for staff. Clear expectations and prompt issue resolution reduce risk and improve culture.
Key Takeaways
- A common law contract is an individual agreement; an enterprise agreement is a collective instrument approved by the FWC - the NES and any applicable award still set the floor for both.
- Contracts are fast, flexible and low-cost to implement, but you must stay on top of award rates, allowances, penalties and rostering rules to avoid underpayment.
- An EA can simplify complex workforce arrangements and provide stability, but it requires careful bargaining, BOOT modelling and ongoing HR discipline.
- Most small businesses start with strong written agreements, clear Workplace Policies and award-compliant payroll settings before considering an EA as the team grows.
- Whatever you choose, align your contracts, policies and systems, and review pay outcomes regularly to ensure compliance with the NES, awards and any enterprise agreement.
- Getting tailored advice early will help you choose the right path for your current size and set you up to scale confidently.
If you’d like a consultation on choosing between common law contracts and an enterprise agreement for your business, you can reach us at 1800 730 617 or team@sprintlaw.com.au for a free, no-obligations chat.








