Outsourcing Battery Testing: How to Protect Your IP

To protect your IP when outsourcing battery testing, combine three layers: a contract that covers more than confidentiality, samples that reveal as little as possible, and clear rules on who owns and keeps the data. An NDA alone does not stop a lab from learning your chemistry, because the tests themselves expose it. This guide shows what each test reveals and which controls to put in place before you ship anything.

It is written for R&D leads at cell makers, materials startups and EV or energy storage teams. It is practical guidance, not legal advice: have your own counsel review any contract.

Quick answer 1. Sign an NDA that defines confidential information, sample destruction and how long the duty lasts. 2. Add IP assignment for results, a no-reverse-engineering clause and a ban on unapproved subcontractors. 3. Send blind-coded samples with only the information the test needs. 4. Agree who owns raw data, how it is transferred and when it is deleted. 5. Ask for written proof that leftover samples and files were returned or destroyed.

 

Why an NDA alone is not enough for battery samples

A software vendor sees your code only if you hand it over. A battery lab is different: the physical sample is the secret. Once a powder or electrode is in another lab, analysis can reveal elements, ratios, particle design and coating choices. An NDA makes misuse a breach of contract, but it does not limit what the lab learns while doing the work, and it does not control samples left on a shelf after the project ends.

So protection has to start before the contract, with a decision about what you send, and continue after the report, with a decision about what happens to leftovers and files.

What each battery test reveals about your chemistry

Different tests expose different parts of your know-how. Use this table to decide what a lab really needs to see. For a deeper look at the methods, see our comparison of EDS, XRF, ICP-OES and XPS.

Test	What an outsider can learn	How to limit exposure
ICP-OES / ICP-MS	Elemental composition, dopant levels	Order it only when composition is the question; split elements across labs if needed
XRD	Crystal phase and structure	Send only the sample being judged, not precursors
SEM-EDS	Particle size, shape, coating, surface elements	Share images under the same confidentiality terms as raw data
Electrochemical cycling	Capacity, rate and life of your material	Share only targets the test needs (voltage window, rate), not your formulation
Cell teardown	Electrode design, loading, separator and electrolyte choices	Agree who may open cells and that all parts are returned or destroyed

 

Contract clauses to require before you ship

Start with an NDA, then add the clauses that cover physical samples and results. A good NDA defines what counts as confidential, sets out how material is destroyed and states how long the duty lasts after the project ends, as this IP protection outsourcing checklist also recommends.

• Confidentiality scope: samples, data, reports, photos and your specifications, not just documents marked “confidential”.
• IP assignment: results, data and any improvements made using your material belong to you.
• No reverse engineering: the lab may test only what the order describes.
• Return or destruction: leftover samples, cells and files are returned or destroyed, with a written certificate.
• Subcontracting: no third party sees samples or data without your written approval.
• Publication: nothing is presented or published without your consent.
• Survival: confidentiality continues for a set period after the project closes.

Ask your counsel to check these terms against your own risk, especially if the lab is in a different country.

Sample-side controls: send less, label smarter

The safest information is the information you never send. Before shipping, strip everything that is not needed for the test.

1. Replace product names with blind codes, and keep the code key in-house.
2. Remove supplier names, lot numbers and formulation sheets from labels and paperwork.
3. Send the smallest quantity the test needs, and ask the lab how much that is.
4. For sensitive projects, split work between labs so no single lab sees the whole picture.
5. Keep a log of every sample sent, its code, quantity and return or destruction date.

When you are planning confidential material evaluation projects, ask the lab to describe its intake process in writing: who receives samples, where they are stored and who can access them. Our confidential material evaluation projects page explains what we test.

Data-side controls: who owns the results?

Raw data can be as revealing as the sample. Agree these points before testing starts:

Question	What to agree
Who owns raw data and reports?	You do, including raw instrument files, not just the PDF report
How is data transferred?	Through an encrypted channel you approve; no personal email accounts
Who receives the report?	A named distribution list on your side
How long does the lab keep files?	A fixed period, then deletion with written confirmation
How is lab security checked?	Ask whether the lab holds a data-security certification such as ISO 27001 or a SOC 2 Type II report, or how it controls access instead

 

University labs vs commercial labs

University labs often offer specialist equipment and expertise, but they work under different rules. Students and visiting researchers may handle samples, and publishing is part of the job. If you work with a university, settle publication rights and student access in writing before samples arrive, and ask who exactly will run the tests.

Commercial labs usually accept stricter confidentiality terms by default, but they may use subcontractors for some techniques. Ask which tests are done in-house and which are sent on.

How to protect IP when outsourcing battery testing: questions to ask before you ship

• Will the NDA cover samples, data, photos and specifications?
• Do we own all results and raw data?
• Which tests are done in-house, and who are the subcontractors?
• Who will handle our samples, and where are they stored?
• How will leftovers be returned or destroyed, and will we get a certificate?
• Can anything be published or presented, and on what terms?

Many of the same questions apply when you choose a materials partner. See our list of questions to ask a battery material supplier.

When to keep testing in-house

Some work is too sensitive to send out, whatever the contract says. Keep testing in-house when one sample would reveal your core formulation, when the test is a teardown of a cell design you have not yet patented, or when you cannot get written terms you are comfortable with. Outsourcing makes sense when the lab offers equipment you do not have and the sample reveals less than the result is worth.

This guide is written by the engineering team at Canrd Technology Co., Ltd., which supplies battery research materials and runs R&D testing services. It cannot replace advice from a lawyer, and no set of controls removes all risk.

Frequently asked questions

Is an NDA enough to protect my battery formulation?

No. An NDA makes misuse a breach of contract, but the lab still learns from the sample while testing it. Add IP assignment, a no-reverse-engineering clause, sample return or destruction, and blind-coded samples that carry only the information the test needs. Have your own counsel review the final terms.

Who owns the test data from an outsourced lab?

Whoever the contract says. Write in that you own all results, reports and raw instrument files, and that the lab keeps them only for a fixed period before deleting them. Ask for written confirmation of deletion when the period ends, and name who on your side receives reports.

Can a lab reverse-engineer my material from a sample?

Analysis such as ICP, XRD and electron microscopy can reveal elements, crystal structure and particle design, so a skilled lab can learn a lot. That is why you should send only what each test needs, ban testing beyond the order and split sensitive work between labs.

Should test samples be returned or destroyed?

Yes, one or the other, and in writing. Agree in the contract that leftover powders, electrodes and cells are returned to you or destroyed when the project ends, and ask for a certificate. Keep your own log of every sample code sent and its final status.

Can university labs publish results from my samples?

They may expect to, because publishing is part of academic work. Settle publication rights before samples arrive: what can be published, after how long, and whether you approve the text first. Also agree which students or visitors may handle your material.

 

Planning to send samples out? Talk to us about scope and confidential handling before you ship: contact our team.