Be clear about what is confidential before you share it.
You have an idea and need help developing it. The first conversation does not always need the secret formula, customer database or complete technical design. Start with the problem, the intended user and the kind of help you need.
An NDA can work in one direction or both
A non-disclosure agreement sets obligations around confidential information. NDAs can be one-way or mutual. “Mutual confidentiality agreement” is not a separate guarantee of stronger protection: read what the agreement actually requires. The UK Intellectual Property Office's overview explains the one-way and mutual distinction.
Which form is appropriate depends on what each party will disclose. If both sides will share confidential material, discuss whether the agreement covers both sides.
Define the information and the purpose
IP Australia's NDA guidance is a useful starting point for understanding confidentiality agreements. For an actual agreement, get advice from a lawyer qualified in the relevant jurisdiction, including New Zealand or Australia where applicable. This article is general information, not legal advice.
Useful questions for that discussion include: what information is covered, what it can be used for, who can access it, how long obligations last, and what happens when discussions end. If the parties are in different countries, ask which law and dispute arrangements apply.
Discuss ownership separately
Confidentiality and ownership are different questions. Do not assume an NDA settles who owns designs, code or other work created during a project. Australia's contractor agreement guidance explains why intellectual property terms need attention in the contract.
Make that discussion part of the scope before commissioning work. Your agreement should address the actual materials and rights involved.
Share only what is needed
Our practical recommendation is to use a brief that explains the job without exposing sensitive details unnecessarily. A sample or anonymised example may be enough to discuss a workflow.
Keep track of what you share and who receives it. Do not treat a signed document as a reason to send every file, or to upload private information into an AI tool whose handling you have not checked.
You can start a useful conversation without presenting every detail of the invention. Tell us the problem you want to solve, and flag any confidentiality requirements before sending sensitive material.