Expression Of Interest For A Project: Legal Checklist For Australian Businesses

Submitting an expression of interest (EOI) for a project can be a great way to win new work, enter new industries, or become an approved supplier for government and large corporate buyers.

But an EOI isn’t just a “marketing document” - it can also create legal and commercial risk if you overstate capability, share confidential information without adequate protections, or rely on unclear procurement terms.

If you’re a small business owner, it’s worth treating an EOI as a structured process: understand what the buyer is asking for, respond clearly, and make sure you’re legally protecting your business while you compete for the work.

Below is a practical guide to preparing an expression of interest for project submissions in Australia, with a legal checklist you can apply whether the project is private sector, government, construction, professional services, or tech. This guide is general information only and isn’t legal advice.

What Is An Expression Of Interest (EOI) For A Project?

An expression of interest (EOI) for a project is typically the first stage in a procurement or sourcing process. It’s a document (or form response) where you explain who you are, what you can deliver, and why you should be considered for the next stage.

EOIs are common when a buyer:

• doesn’t yet have a final scope and wants to test the market
• wants to shortlist capable suppliers before requesting detailed pricing
• needs to create a panel of suppliers for future work
• is looking for innovative solutions and wants ideas upfront

Depending on the buyer, the next stage after an EOI might be:

• a Request for Proposal (RFP) or Request for Tender (RFT)
• a pricing request or quote stage
• a negotiation stage
• a direct award or limited-quote process (less common, and usually only in specific circumstances)

Is An EOI Legally Binding In Australia?

Usually, an EOI is not intended to be a binding contract for the project itself. However, parts of the process can become binding depending on what you submit and what the buyer’s terms say (including any procurement conditions, portal terms, and declarations).

Common “binding-adjacent” risks include:

• misleading statements about your experience, pricing, availability, certifications, or subcontractors
• confidentiality obligations in the buyer’s procurement rules (even at EOI stage)
• IP ownership clauses that may give the buyer rights to use your ideas or proposal materials
• exclusivity or non-solicitation clauses (less common, but worth watching for)

Even where the EOI itself isn’t a contract, your business can still be exposed if you make promises you can’t keep or if you rely on informal communications rather than clear written terms.

When Should Your Business Submit An Expression Of Interest For Project Work?

EOIs take time, and time is a real cost for small businesses. So it’s worth being selective.

Submitting an expression of interest for a project tends to be worthwhile when:

• the buyer is a repeat purchaser (panel arrangements and long-term pipelines can pay off)
• your capability is a strong match even if you’re not the biggest supplier
• there’s a clear pathway to a paid contract (RFP, tender shortlist, supplier onboarding)
• you can differentiate (unique method, niche expertise, specialist team, faster delivery)

It may be less worthwhile if:

• the EOI is extremely broad with no clear selection criteria
• the process asks for extensive unpaid design/spec work at the EOI stage
• the buyer terms require you to give away IP or accept unreasonable liability too early

That doesn’t mean you should never proceed - it just means you should proceed with your eyes open, and with your legal risk controlled.

How To Write A Strong Expression Of Interest For Project Submissions (Practical Structure)

Every buyer formats EOIs differently, but a strong response usually answers the same core questions: Can you do the job, will you do it safely and reliably, and are you low-risk to engage?

Here’s a practical structure you can adapt.

1. Cover Page And Business Snapshot

• legal entity name and ABN/ACN (as applicable)
• trading name (if different)
• registered address and contact person
• brief “what we do” summary (2–3 sentences)

If you operate through multiple entities (e.g. a trading entity and an IP holding entity), make sure the contracting entity is clear upfront to avoid confusion later.

2. Understanding Of The Project (And Assumptions)

This section is often where EOIs win or lose. Buyers want to see you understand the problem, not just that you have a standard pitch deck.

Include:

• a plain-English summary of what you think the buyer needs
• assumptions you’re relying on (timelines, access, dependencies)
• what information you still need (so you can price accurately later)

Be careful about certainty here. It’s fine to be confident, but you don’t want to accidentally promise you can deliver something without seeing key project constraints.

3. Capability, Team And Resourcing

• relevant experience (projects similar in scope/industry)
• key personnel and roles
• subcontractors or partners (if any)
• capacity and availability (realistic start dates)

Only list people and partners you can actually commit. If you’re still exploring subcontractors, say so clearly.

4. Methodology And High-Level Project Plan

Even if you’re not pricing yet, outline how you would deliver:

• phases and milestones
• quality assurance approach
• risk management approach
• reporting and stakeholder communication

This also helps you later when you’re negotiating the contract scope and deliverables.

5. Relevant Compliance And Governance

Depending on the industry, you might include:

• WHS approach (especially construction and onsite services)
• security policies (for IT, government, or sensitive sites)
• privacy and data handling practices (if personal information is involved)
• licenses, insurances, certifications, and registrations

If the project involves collecting or handling personal information, it’s also a good time to check whether you have a fit-for-purpose Privacy Policy and internal processes to match what you’re promising in the EOI.

6. Commercials (If Requested)

Sometimes EOIs request pricing ranges, day rates, or an indicative budget. If so:

• state what’s included and excluded
• identify assumptions (scope, volumes, timing)
• be clear if figures are estimates only

If you plan to rely on your standard terms when you quote, it’s worth aligning early with your Terms Of Trade or service terms so you’re not scrambling later when the buyer pushes their own template contract.

Legal Risks To Watch For In An Expression Of Interest For Project Opportunities

EOIs can feel preliminary, but they can still contain legal “tripwires” in the background documents (procurement conditions, supplier rules, portal terms, attachments).

Here are the big risk areas to actively check.

Misleading Or Deceptive Conduct

In Australia, businesses need to be careful not to mislead buyers (even unintentionally). Your EOI should be accurate, evidence-based, and not overstate outcomes.

Common risk statements include:

• claiming you have certain certifications or insurance when you don’t
• implying you have done similar projects when you haven’t
• guaranteeing timeframes without acknowledging dependencies
• using case studies without permission or with confidential details

If you’re unsure whether a claim crosses the line, it’s safer to qualify it and explain the basis for the statement.

Confidentiality And Information Sharing

EOIs often require you to share:

• pricing approaches
• delivery methods
• unique processes and templates
• commercial relationships (suppliers, subcontractors)

If you’re sharing non-public information, consider what protections already apply under the procurement conditions. In some cases, you may be able to request additional confidentiality protections (such as an NDA) before sharing sensitive attachments - but buyers won’t always agree, particularly in government procurement. Where appropriate for early-stage discussions, a Mutual NDA is often a practical starting point.

Intellectual Property (IP) Ownership In Your Proposal

Some procurement documents include clauses that give the buyer rights to use, reproduce, or (in some cases) own parts of your proposal materials. That can be a serious issue if your EOI contains:

• original designs
• technical solution architecture
• software concepts
• unique methodologies

If you want to protect your IP, you may need to:

• mark parts of the submission as confidential and proprietary
• exclude detailed designs until later (once contract terms are agreed)
• negotiate IP terms at RFP/contract stage

If your project delivery involves creating custom software or digital assets, the contract stage is also where an appropriate Software Development Agreement (or similar services agreement) can protect your ownership, licensing, and payment milestones.

Liability And Risk Allocation Too Early

Some procurement processes try to lock in liability positions before you’ve even priced the job, including:

• uncapped indemnities
• liquidated damages
• fitness-for-purpose obligations that are broader than your offer
• insurance requirements that don’t match the project risk

Where possible, you want those terms to be negotiated at contract stage - and you want your scope and pricing to reflect the risk you’re being asked to accept.

Probity, Conflicts, And Supplier Declarations

Government and large corporate projects often require declarations about:

• conflicts of interest
• gifts and hospitality
• anti-bribery compliance
• modern slavery reporting (where relevant)

If you’re growing into bigger procurement opportunities, it can help to formalise internal governance early. Depending on your setup, a Conflict Of Interest Policy can be useful, particularly where you have contractors or advisors who may also work across the same industry.

A Legal Checklist Before You Lodge Your Expression Of Interest For Project Work

Before you hit “submit”, it’s worth running through a simple legal checklist. This can save you from signing up to obligations you didn’t intend, or creating unnecessary risk for your business.

1. Confirm Your Contracting Entity (And Authority)

• Are you submitting under the correct legal entity name?
• Is the person signing/accepting declarations authorised to do so?
• Do you need board/director approval for the submission (for companies)?

It’s also worth being clear internally about who can sign what, particularly if a portal requires a declaration on behalf of the business. If you have a team member handling submissions, an Letter Of Authority can help clarify permissions and reduce confusion.

2. Check The EOI Conditions And Any Attached Buyer Terms

• Are there confidentiality requirements?
• Is there an IP assignment or licence over your materials?
• Are you agreeing to exclusivity or restrictive conditions?
• Are there unusual insurance or liability terms?

If the buyer has provided a draft contract, try to review it early - not after you’ve invested weeks into a proposal and feel “locked in”.

3. Validate Every Claim You Make

• Do you have evidence for your past performance statements?
• Are case studies approved for use (and not breaching confidentiality)?
• Are your timeframes and resourcing realistic?

Where something depends on third parties (suppliers, subcontractors, access), say that.

4. Protect Your Confidential Information

• Have you clearly marked confidential sections?
• Have you limited the “secret sauce” details where possible?
• Do you need to request additional confidentiality protections before sharing sensitive attachments?

5. Check Your Internal Documents Are Ready If You’re Shortlisted

EOI success can move fast. If you’re shortlisted, you may be asked for contracts, policies, onboarding documentation, or proof of compliance.

Depending on your industry, this may include:

• Service agreement / customer contract: sets scope, fees, deliverables, change control, warranties, and limitations of liability
• Website terms: if your project involves a portal or platform, your Website Terms And Conditions may need updating
• Privacy documentation: if you’re collecting personal information during delivery, your Privacy Policy and collection notices should match your data practices
• Employment contracts: if you’ll hire staff to deliver the work, a tailored Employment Contract can help set expectations, IP ownership, confidentiality, and notice requirements
• Subcontractor agreements: essential if delivery relies on contractors, particularly for confidentiality, IP, and customer flow-down obligations

The key idea is to avoid winning the project and then scrambling through legal paperwork under deadline pressure.

Key Takeaways

• An expression of interest submission is often a gateway to larger contracts, supplier panels, and repeat work - but it’s worth approaching it with a plan, not just a pitch.
• Even when an EOI isn’t a binding contract, you can still face risk through misleading statements, confidentiality issues, and IP clauses in procurement conditions.
• A strong EOI clearly explains your understanding of the project, your capability and resourcing, your delivery approach, and any key assumptions.
• Before lodging, check the buyer’s terms carefully for IP ownership or usage rights, confidentiality, liability, and declarations (especially for government or regulated industries).
• Having your core documents ready (service terms, Privacy Policy, employment and contractor agreements) helps you move quickly if you’re shortlisted and protects you when negotiations begin.

If you’d like help reviewing an expression of interest for a project submission or preparing the right contracts for the next stage, you can reach us at 1800 730 617 or team@sprintlaw.com.au for a free, no-obligations chat.