NDA Checklist Before Sharing An Idea

You might be about to pitch a new app, speak with a manufacturer, outsource your branding, or bring in a potential co-founder. It makes sense to pause and ask: should I get an NDA signed first?

An NDA can be a very useful business tool, but only if it matches what you're actually sharing and how the other person will use it. A vague document that tries to protect everything forever can be harder to rely on when it really matters.

Here is a practical NDA checklist for Australia, with the key clauses to think about before you send your idea, deck, prototype, customer list or business plan to someone else.

Do I Need An NDA Before Sharing A Business Idea?

Yes, an NDA can help before sharing a business idea, but it usually protects the confidential details around the idea rather than the broad idea itself.

In Australia, an NDA is a contract. It can also sit alongside the general law of confidential information, sometimes called breach of confidence. The practical point is simple: if you share valuable information in circumstances where it's clearly confidential, you have a better chance of stopping misuse or seeking a remedy if things go wrong.

An NDA is especially useful when you're sharing:

• Business plans, pitch decks or financial forecasts
• Product designs, technical specifications, recipes, formulas or processes
• Customer lists, supplier details or pricing models
• Marketing strategies, launch plans or unpublished content
• Software code, wireframes, prototypes or AI model details
• Unregistered IP, such as a name you plan to apply to register as a trade mark with IP Australia

An NDA won't magically protect every idea. If you tell someone only that you want to create a marketplace for pet services, that concept may be too general. If you share your supplier list, commission structure, customer acquisition model and launch plan, that's much more likely to be the kind of information an NDA should cover.

There are also times when asking for an NDA may not be realistic. Many investors, accelerators and large corporates won't sign NDAs at the early pitch stage because they see lots of similar ideas. In that case, you can still protect yourself by sharing a teaser deck first, keeping the most sensitive information back until later, and recording what you disclosed and when.

What Information Should An NDA Cover?

An NDA should cover the specific confidential information you're actually sharing, not just use broad labels like "all business information" and hope that's enough.

A good confidentiality agreement usually defines confidential information clearly, then gives examples that match your business. This makes the document easier to understand and easier to point to later if there's a dispute.

Think about your information in categories:

• Commercial information: pricing, margins, budgets, business models, funding plans and sales strategy
• Technical information: code, algorithms, product roadmaps, technical drawings, specifications and testing data
• Creative information: designs, scripts, brand concepts, artwork, campaign ideas and unpublished content
• Operational information: supplier arrangements, internal processes, manuals and workflows
• Customer information: customer lists, lead lists, customer preferences and contact details

If your information includes personal information or sensitive information, you also need to think about privacy. The Privacy Act 1988 and the Australian Privacy Principles may apply to your business if, for example, you have an annual turnover of more than $3 million or you fall into a category that's covered regardless of turnover, such as some health service providers. Even where the Privacy Act doesn't apply, it's still good practice to limit what personal information you share and require secure information handling.

Say Priya runs a Brisbane cafe and is developing a bottled sauce range. She is speaking with a manufacturer and shares her recipe, expected first order of 2,000 bottles, target wholesale price of $6.50 per bottle and list of five retailers she is negotiating with. Her NDA should name recipes, production methods, pricing, forecasts and retailer details as confidential information. A generic NDA that only says "business information" may still help, but it gives Priya less certainty.

Should I Use A One-Way Or Mutual NDA?

It depends on who is sharing confidential information. Use a one-way NDA if only you're disclosing sensitive information, and a mutual NDA if both sides are sharing it.

A one-way NDA is common where you're pitching to a contractor, supplier, agency, consultant or potential manufacturer. You disclose information, and they agree to keep it confidential and use it only for the agreed purpose.

A mutual NDA is common where both sides are exploring a collaboration, joint venture, partnership, software integration, business sale discussion or early co-founder arrangement. Each side protects the other side's confidential information on similar terms.

Example: A Startup And A Developer

Mike is building a booking platform for tradies. He speaks with three software developers and shares wireframes, a product roadmap, sample customer data and his expected build budget of $80,000, so any data sharing should be tightly controlled. The developers only share standard capability statements and pricing.

For the first conversations, a one-way NDA is likely to make sense because Mike is the one disclosing the sensitive information. If Mike later chooses one developer and they start exchanging technical architecture, code libraries and confidential delivery methods, a mutual NDA or a broader development agreement may be more suitable.

The key is to match the document to the relationship. A mutual NDA isn't automatically better. If it creates obligations for your business when you aren't receiving anything sensitive, it can add unnecessary risk and admin.

You should also check whether the NDA is enough on its own. Once the relationship moves from "let's discuss" to "please build this", you'll usually need a proper services agreement, contractor agreement, software development agreement or manufacturing agreement as well. That contract should deal with ownership of IP, payment, milestones, warranties and what happens if the project ends.

What Should I Include In An NDA?

Your NDA should clearly say what is confidential, why the information is being shared, how it can be used, how long the obligations last, and what happens when the discussions end.

Here is a fill-in outline you can use as a planning checklist. It isn't a finished legal document, and a lawyer should tailor the final version before you use it.

1. Parties: Write the full legal names, ABNs or ACNs, and contact details of each party.
2. Purpose: State the reason for disclosure, such as assessing a manufacturing arrangement, preparing a quote or discussing a possible collaboration.
3. Definition Of Confidential Information: List the types of information covered, including oral, written, electronic and visual disclosures if relevant.
4. Exclusions: Carve out information that's already public, already known, independently developed, or lawfully received from someone else.
5. Use Restrictions: Say the recipient can only use the information for the agreed purpose and not for any competing or personal purpose.
6. Disclosure Restrictions: Set out who the recipient can share confidential information with, such as employees or advisers who need to know and are bound by confidentiality obligations.
7. Security Requirements: Require reasonable steps to protect the information, such as secure storage, password protection and access limits.
8. Return Or Destruction: Explain what must happen to documents, files, samples and copies when you ask for them back or discussions end.
9. Time Period: Set the confidentiality period, and consider a longer period for trade secrets that should stay confidential until they become public.
10. IP Ownership: Make clear that sharing information doesn't transfer copyright, trade mark rights, patent rights or other IP ownership.
11. Remedies: State that misuse may cause serious harm and that you may seek available legal remedies.
12. Governing Law: Choose an Australian state or territory law, such as the laws of New South Wales or Victoria, where appropriate.

The time period should be realistic. Many commercial NDAs use 2 to 5 years for ordinary business information, while true trade secrets may need protection for as long as they remain confidential. The right period depends on what you're sharing and how quickly it loses value.

If you're sharing material that may be protected under the Copyright Act 1968, the Patents Act 1990, the Designs Act 2003 or the Trade Marks Act 1995, remember that an NDA is only one piece of the puzzle. You may also need registrations, assignments or licences to properly protect and commercialise your IP.

What Mistakes Make An NDA Hard To Enforce?

An NDA can become harder to rely on if it's vague, unrealistic, signed too late, or inconsistent with what actually happened between the parties.

Here are the common issues we see when businesses rush the process.

The NDA Is Signed After Disclosure

If you disclose your sensitive information first and send the NDA later, the other person may argue that the earlier disclosure wasn't covered. If you need to have an initial chat first, keep it high-level and send the NDA before you share the details that really matter.

The Purpose Is Too Broad

A purpose like "business discussions" may not give you much control. A more useful purpose might be "to assess whether the recipient can manufacture and quote on the discloser's bottled sauce product". This makes it clearer what the recipient can and can't do.

The Definition Of Confidential Information Is Too Vague

If everything is confidential, the other side may argue that nothing was identified clearly enough. Use categories and examples. For very sensitive information, mark documents "confidential" and keep a disclosure log.

The Obligations Are Unrealistic

A clause that says the recipient can never disclose anything to anyone may not work if they genuinely need to share information with employees, contractors or professional advisers to assess the opportunity. It's often better to allow limited disclosure to people who need to know, provided they're also bound to keep it confidential.

The Wrong Entity Signs

Check the legal name. If you're dealing with a company, use its company name and ACN, not just a trading name. If you sign with the wrong entity, it can create problems when you need to enforce the agreement.

You Share More Than You Need To

An NDA isn't a reason to hand over everything on day one. Share information in stages. For example, send a summary first, then detailed financials or source files only once the relationship is more serious and the right contracts are in place.

What Should I Do If Someone Misuses My Confidential Information?

If someone misuses your confidential information, act quickly, preserve evidence and get advice before you send threats or make accusations.

Start with the practical steps:

1. Collect the agreement: Find the signed NDA, any related emails, messages and versions of the document.
2. Record what you disclosed: Note the dates, files, meetings, attendees and the exact information shared.
3. Save evidence of misuse: Keep screenshots, website pages, social media posts, product listings, quotes or customer messages that show what happened.
4. Check the NDA terms: Look at the purpose, confidentiality period, permitted disclosures, return obligations and governing law.
5. Limit further damage: Stop sharing more information, remove access to shared folders and change passwords if needed.
6. Get tailored advice: Work out whether to send a formal notice, ask for undertakings, seek return or destruction of materials, or take another commercial step.

Be careful about posting publicly or contacting the other party's customers before you get advice. Even if you're upset, a rushed response can make the situation messier and distract from the real issue.

Sometimes the best outcome is a fast commercial fix. For example, if a contractor has kept access to a shared drive after the project ended, the first step may be to revoke access, request deletion confirmation and remind them of their NDA obligations. If they're actively using your confidential information to compete with you, the response may need to be firmer.

The right path depends on the wording of your NDA, the value of the information, the evidence you have and how urgent the harm is. Getting advice early can help you avoid spending time and money on a strategy that doesn't match the risk.

Key Takeaways

• An NDA can help before sharing an idea, but it works best when it protects specific confidential information rather than a broad concept.
• Your NDA should clearly cover what is confidential, why it's being shared, who can access it, how it must be protected and when it must be returned or deleted.
• Use a one-way NDA when only you're disclosing sensitive information, and a mutual NDA when both sides are sharing confidential material.
• Common mistakes include signing too late, using vague wording, choosing the wrong party name, and sharing too much information too early.
• An NDA is often only one part of your legal setup. You may also need IP registrations, contractor agreements, services agreements or privacy protections.

If you'd like help with your NDA, protecting your confidential information, choosing the right agreement for a pitch or collaboration, or tightening up your IP and contractor documents, you can reach us at 1800 730 617 or team@sprintlaw.com.au for a free, no-obligations chat.