
A SELA, or software evaluation licence agreement, is a short contract that lets a business try software for a limited time, only to decide whether to buy it. It gives the evaluator just enough rights to test the software, and protects the owner's code, confidential information and liability while the trial runs.
In short:
- Use a SELA when you let a prospective customer trial, pilot or beta test your software before they sign a full licence.
- The core terms are: what the software is, how long the evaluation lasts, what the evaluator can and can't do, confidentiality, feedback, liability and what happens at the end.
- Some restrictions can't be enforced. In the UK, a term is void in so far as it stops a lawful user making a back-up copy they need, decompiling the program for interoperability where strict conditions are met, or observing and testing how it works while using it as permitted.
- The legal points below are based on UK law, with liability rules for England and Wales (and Northern Ireland where stated). If your agreement is governed by another country's or state's law, the same clauses apply, but the detailed rules can differ.
What does SELA stand for?
SELA stands for software evaluation licence agreement (often spelt "license" in the US). People also call it an evaluation licence, a trial licence or a "sela agreement".
A licence is needed because software is protected by copyright. In the UK, copyright protects software automatically, without registration, and stops others copying, adapting or distributing it without permission (GOV.UK: how copyright protects your work). Installing and running a program involves copying it, so the evaluator needs your permission, and the SELA sets the limits of that permission.
When do you need a SELA?
A SELA is useful whenever software leaves your control before a customer has paid or signed a full licence. Typical situations include:
- Business trials. A prospective customer wants a few weeks to test your product with its own data before committing.
- Pilots and proofs of concept. A limited deployment, often with one team or site, to show the software does what you say.
- Beta testing. Sharing pre-release software with selected users in return for feedback on bugs and features.
SELAs are most common in business-to-business deals for software installed on the customer's systems. For hosted products, trial terms often sit in a SaaS agreement instead, but the same issues still need covering.
SELA vs NDA, software licence and SaaS agreement
- NDA. A non-disclosure agreement protects confidential information, but it doesn't give anyone the right to use your software. A SELA usually includes its own confidentiality clause, so you may not need a separate NDA unless talks started earlier.
- Software licence agreement. A full software licence agreement grants paid, longer-term rights to use the software in the business, usually with warranties, support and service levels. A SELA is the short, limited version that comes first.
- SaaS agreement. A SaaS agreement covers access to software hosted by the provider rather than installed by the customer.
What a SELA should include
- The parties. The full legal names and addresses of the software owner (the licensor) and the evaluator, and who signs for each.
- The software. Exactly what is being evaluated: product name, version, modules, documentation and any test data you supply.
- The licence grant. A limited, non-exclusive, non-transferable right to install and use the software only to evaluate it. Say how many users or devices are allowed, and whether use is limited to a test environment.
- The evaluation period. A clear start and end date, and whether it can be extended in writing.
- Restrictions. For example, no production use, no copying beyond what's needed, no sharing with third parties, and no use to build a competing product. See the next section for limits on what UK law allows you to restrict.
- Fees. Most evaluations are unpaid, but say so. If there is a pilot fee, set out the amount and when it's due.
- Confidentiality. What counts as confidential (the software, documentation, pricing and roadmap), how it must be protected and how long the duty lasts after the trial.
- Feedback and ownership. Whether you can use the evaluator's feedback without restriction, and confirmation that the evaluator gets no ownership of the software or any improvements.
- Warranties and liability. Software for evaluation is usually provided "as is", with liability capped. See below for the UK rules.
- Data. If the evaluator will load personal data into software you host or support, how that data is handled.
- End of the evaluation. What the evaluator must do when the period ends or the agreement is terminated: stop using, uninstall and return or delete the software, or sign a full licence.
- General terms. Termination rights, which clauses survive termination (confidentiality, liability, ownership), governing law and where disputes are decided.
Restrictions UK law won't let you impose
Owners often want to ban everything except simple testing. That's usually fine, but in the UK some limited rights of a lawful user of a computer program (broadly, someone entitled to use it, for example under the SELA) can't be removed by contract. Each right applies only within its conditions. Under the Copyright, Designs and Patents Act 1988:
- Back-up copies. A lawful user may make a back-up copy where it is necessary for the purposes of their lawful use. This doesn't allow general copying (section 50A).
- Decompiling for interoperability. A lawful user may decompile a program only where it's necessary to get the information needed to create an independent program that can operate with it (or with another program). The conditions are strict: the information mustn't already be readily available, the decompiling must go no further than needed, and the information can't be used for any other purpose, passed on unnecessarily, or used to create a program substantially similar in its expression (section 50B).
- Observing, studying and testing. A lawful user may observe, study or test how the program functions, to work out the ideas and principles behind it, but only while doing things they are entitled to do, such as loading, displaying, running or storing it (section 50BA).
A term in the agreement is void in so far as it tries to prohibit or restrict these acts (for decompiling, only where the section 50B conditions are met) (section 296A). By contrast, other copying or adapting that's necessary for lawful use, such as fixing errors, can be restricted by the agreement (section 50C).
In practice, this means a well-drafted UK SELA bans reverse engineering "except to the extent permitted by law" rather than outright. These rights don't let an evaluator use the software for anything beyond the evaluation, or share it.
Warranties and liability: the "as is" clause
Because the evaluator usually pays nothing, the owner normally gives no promises about performance and limits its liability, for example to a fixed amount or to any fees paid, with no liability for indirect loss. That is a sensible starting point, but in England, Wales and Northern Ireland the Unfair Contract Terms Act 1977 (UCTA) sets limits on exclusion and limitation clauses in business-to-business contracts (consumer contracts are covered by the Consumer Rights Act 2015 instead):
- You can't exclude or restrict liability for death or personal injury caused by negligence (UCTA section 2(1)).
- For other loss caused by negligence, an exclusion or limit is valid only if it is reasonable (section 2(2)). Reasonableness means the term was fair and reasonable to include, given what the parties knew or should have known when the contract was made (section 11), with further guidelines in Schedule 2.
- If one party deals on the other's written standard terms of business, the reasonableness test also applies to terms limiting liability for breach of contract (section 3).
- A term limiting liability for misrepresentations made before the contract must also be reasonable (Misrepresentation Act 1967, section 3, which applies in England and Wales; Northern Ireland has its own equivalent). Reasonableness is judged under UCTA section 11(1).
Two caveats. First, UCTA sections 2 to 4 don't apply to a contract "so far as it relates to" the creation or transfer of a right or interest in copyright, technical or commercial information or other intellectual property (Schedule 1, paragraph 1(c)). It isn't settled how far that covers the liability terms in a software licence or evaluation agreement, so it's safest to draft liability limits as if UCTA applies. Second, the relevant UCTA sections apply to business liability (section 1(3)). If your evaluators are consumers rather than businesses, the Consumer Rights Act 2015 applies instead and is stricter, so get the terms checked.
Confidentiality, feedback and data
Confidentiality. Your code, documentation and roadmap may be trade secrets. In the UK, acquiring, using or disclosing a trade secret is unlawful where it amounts to a breach of confidence in confidential information (Trade Secrets (Enforcement, etc.) Regulations 2018, regulation 3). A clear confidentiality clause makes it easier to show what was confidential.
Feedback. If you want to use evaluators' suggestions without paying for or crediting them, say so in the SELA. If you want to own anything the evaluator creates (rather than just use it), remember that in the UK an assignment of copyright is only effective if it's in writing and signed by or on behalf of the person assigning it (CDPA section 90(3)).
Personal data. If the evaluator loads personal data into a system you run, you may be acting as their processor. Under the UK GDPR, a controller using a processor must have a written contract that includes certain required terms. The ICO's guidance on contracts between controllers and processors explains what to include. Where possible, ask evaluators to use test or anonymised data instead.
Ending the evaluation
A common problem is an evaluator who keeps using the software after the trial. A good SELA deals with this by:
- setting a fixed end date, and saying the licence ends automatically on that date unless extended in writing;
- requiring the evaluator to stop using, uninstall and return or delete the software and confidential information, and confirm this in writing if asked;
- saying that any continued use needs a full licence, so the next step is a signed software licence or SaaS agreement.
Signing a SELA
Both parties should sign before the software is made available. In the UK, electronic signatures are admissible as evidence of a document's authenticity and integrity (Electronic Communications Act 2000, section 7), so e-signing is common for this kind of agreement. Simple e-signatures are generally fine for contracts like this; documents that must be executed as a deed have extra formalities.
Get your SELA drafted and checked
Robot Lawyer's Software Evaluation Licence Agreement asks about the software, the parties, the evaluation period and the restrictions you need, then drafts a complete agreement for the law of the country or state you choose. On the Verified plan, a solicitor (or, for customers outside the UK, a lawyer qualified in England and Wales) checks your agreement within 24 hours and makes amendments where needed, and you can send it for e-signature. When the trial turns into a sale, move on to a Software Licence Agreement or a SaaS Agreement.
FAQs
Is a SELA legally binding if the evaluator doesn't pay?
It can be, but it depends on the circumstances. In England and Wales a contract generally needs consideration, which doesn't have to be money: the evaluator's promises, such as keeping information confidential, providing feedback or accepting restrictions, may be enough. Alternatively, the agreement can be executed as a deed, which doesn't need consideration. Whether a particular SELA is enforceable depends on its terms and how it was agreed, so if you're unsure, get it checked.
How long should an evaluation period be?
There's no legal minimum or maximum. It depends on the software and what needs testing, but evaluations often run for a few weeks to a few months, with a written extension if both sides agree.
Do I need an NDA as well as a SELA?
Usually not, if the SELA has a proper confidentiality clause. A separate NDA is useful if you shared confidential information before the evaluation started, or if the discussions go wider than the software trial.
Solution
Software Evaluation License Agreement (SELA)