Forms Legal

Posted on Jul 9

Cascading Clauses: Your Secret Weapon Against Bogus Employment Contracts as a Freelance Developer

#legal #startup #contracts

TL;DR: Standard employment contracts often ban you from all similar work for years, but a cascading clause breaks it into fallback options. Courts enforce the first reasonable tier, so you keep working. I now demand these in every contract.

Signed an employment contract without blinking at the restraint clause? Yeah, I did too, until my weekend side project got flagged as 'competition' by HR. Turns out, one overbroad sentence could legally ban you from React jobs for years. But here's the indie dev lifehack: cascading clauses turn legal landmines into safety nets. Your next contract needs this tweak.

Why Devs Get Nailed by Restraint Clauses

You shipped a tiny Shopify plugin for Client A. Their contract tried banning all e-commerce work for 18 months. Meanwhile, a junior dev I mentored got slapped with "no React work" clauses. Courts won't enforce that for someone without trade secrets. Yet these clauses still scare developers away from side gigs or open-source contributions.

Restraints fail when they're too broad. A junior dev building basic UI components shouldn't be banned from the entire frontend ecosystem. But standard contracts don't care about your actual role. They copy-paste corporate legalese designed for sales VPs with confidential client lists.

Your freelance gigs are especially vulnerable. If your contract says "no competing work," does that include building WordPress sites while your day job uses React? Most boilerplate says yes. One vague phrase could kill your side income for years.

Cascading Clauses Demystified: The Dev-Friendly Version

Cascading clauses are like conditional statements for contracts. Instead of one massive restraint, you get tiered options. Courts enforce the first reasonable tier. Think of it as defensive coding for your career.

Here's a real example I negotiated last month:

The Developer shall not:
(a) provide services to Shopify competitors for 12 months globally;
(b) if (a) unenforceable, provide services to Client A's adjacent e-commerce tools for 6 months in Australia;
(c) if (b) unenforceable, solicit Client A's merchants for 3 months.

If a court voids (a) as too broad, it jumps to (b). If (b) fails, it enforces (c). No total void. You keep working.

Compare this to typical contracts: single-duration, single-geography restraints. Fail one point, lose everything. My first contract had "no tech work for 24 months Australia-wide." For a junior role? Impossible to enforce. But without fallbacks, I'd have zero protection.

Non-Solicit vs. Non-Compete: Freelancer Reality Check

Non-compete clauses ban entire industries. Non-solicit clauses target specific clients or colleagues. As a freelancer, non-solicits matter way more.

Imagine building fintech apps. A non-compete might say "no financial software for 12 months." Courts often void this, it's too broad for most devs. But a non-solicit saying "don't poach Client B's customers you directly served" usually sticks.

Here's what actually impacts your freelance hustle:

Non-compete: Ban on similar work (e.g., "no React development"). Rarely enforceable for devs without trade secrets.
Non-solicit: Ban on contacting specific clients/staff. Much easier to prove reasonable.

My rule: Never sign a non-compete without cascading fallbacks. For non-solicits, narrow the scope to only clients you touched directly. "All clients in the past 3 years" is a red flag. "Clients you engaged with in the last 6 months" is defensible.

Your 3-Minute Contract Audit Checklist

Skip the legalese panic. Scan contracts in minutes with this checklist:

Spot dangerous boilerplate:

Search for "restraint period" or "geographical scope." If duration >12 months or geography >your actual work region, red alert. Junior dev banned from "all AI work Australia-wide"? Hard no.
Demand fallback tiers:

Add cascading language like:

"If unenforceable, [shorter duration] in [smaller region] → else [non-solicit only]."

Example: "No Shopify work 12mo → else no Client A adjacent tools 6mo → else no poaching merchants."
Document your actual value:

Write this in the contract appendix:

"Protectable interests: Proprietary component library X, not standard React skills."

Prevents them banning your entire tech stack. Courts only protect what you actually accessed.

I keep this checklist in my contract template repo. Saved me twice last year when contracts tried to ban all cloud work after I built one AWS Lambda function.

NSW Quirk vs. Real-World Safety

New South Wales has a loophole: the Restraints of Trade Act 1976. Section 4 lets courts trim unreasonable clauses instead of voiding them. Sounds great, until you learn the catch.

In NSW, a judge might read down "24 months Australia-wide" to "6 months Sydney." But this isn't automatic. You still lose months of income while waiting for court. And outside NSW? Total void. No fallback. Victoria, WA, Queensland, zero safety net.

Cascading clauses work everywhere. No waiting for judges. No gambling on "read-downs." The clause self-adjusts to what's reasonable for your role.

Remote workers: Don't assume NSW rules apply because the company's HQ is there. Courts look at where you worked. If you're in Melbourne, NSW law probably doesn't save you. Cascading drafting is your universal insurance.

Why This Matters for Your Side Hustle

Last year, a client tried banning me from all e-commerce after I built their Shopify plugin. Standard clause: "no competing work 18 months." Impossible for a freelancer. I pushed back with cascading tiers:

"No direct Shopify competitors for 12 months → else no Client A-specific integrations 6 months → else no soliciting their merchants."

They agreed. When I later joined another e-commerce project (non-Shopify), no one blinked. The cascade made the restraint reasonable for my actual work, not some fictional sales exec role.

Contrast this with a junior dev I advised. Her contract said "no React work 12 months." Generic and unenforceable. But without fallbacks, she feared taking any frontend gig. We renegotiated it down to "no copying proprietary component library Y." Suddenly, she could take React jobs again.

Stop Signing Nuclear Options

Most devs treat contracts like EULAs, we click "I agree" to get paid. But restraint clauses are landmines disguised as standard terms. One overbroad phrase can nuke your side income for years.

Cascading clauses fix this. They're not magic, they won't save obviously unreasonable bans. But they force contracts to match reality. Courts enforce the first tier that fits your actual role and access.

Next time you sign:

Reject single-tier restraints immediately
Insert "if unenforceable, [fallback]" language
Tie restrictions to your specific confidential knowledge

I've added cascading clauses to all my contracts since 2022. Zero legal fights. Zero lost gigs. Just clean work without career grenades ticking in the background.

Check templates at forms-legal.com/australia to see cascading structures in action, but always customize for your actual role. Your career's too important to gamble on boilerplate.

DEV Community