Software audits are run with letter templates, and the way to answer one is with an inventory and a position rather than reassurance.
What a software license notice is
A software licence notice deals with unauthorised installation, over-deployment, redistribution, reverse engineering or use beyond a licence metric. It is issued both by vendors pursuing licence compliance and by licensees where a supplier has failed to honour support, escrow or source-code obligations.
When to send a software license notice
After a reconciliation of entitlements against deployment, or immediately after a discovery of unauthorised use. Compliance programmes frequently come with a short deadline and a settlement window.
What a software license notice must contain
- The licence agreement, the entitlement metric and the deployed count
- The specific unauthorised use, with evidence rather than assertion
- The remedy: true-up, reinstallation control, removal or remediation of source use
- Any claimed fees, with a calculation rather than a lump figure
- A deadline, and whether the vendor is offering discounted compliance settlement
- A reservation of rights, and a request for certification of compliance on completion
Each of those elements exists to close a specific argument the recipient could otherwise make. A notice that omits the basis of the claim invites a dispute about whether the obligation existed at all; one that omits the deadline invites a dispute about whether it was ever due.
How to serve it so it cannot be denied
Service is the part of the process that fails most often. Use the method the contract or the statute names first, and only then the method the parties actually use. Registered post with a tracking record, a courier with a signature, or a process server for a formal statutory notice are the reliable routes; ordinary email is not, unless the agreement expressly permits electronic service or the parties have conducted themselves that way for long enough to establish it.
Send the same document to every address in play — the registered office, the contractual notice address, and the address used in ordinary correspondence — and keep the receipt, the tracking record and an exact copy of what was sent. Where the notice matters, a certificate of posting costs almost nothing and removes the argument entirely.
How long to give the recipient
Fourteen to thirty days, though vendor compliance programmes may impose their own shorter window. Express the deadline as a calendar date rather than a number of days, and make clear which time zone or jurisdiction's calendar governs where the parties are in different countries.
Where this notice applies
The same document has to satisfy different procedural rules in every jurisdiction. These pages set out the local requirements for this notice type:
- Software License Notice in India
- Software License Notice in United States
- Software License Notice in United Kingdom
- Software License Notice in Canada
- Software License Notice in Australia
- Software License Notice in United Arab Emirates
- Software License Notice in Singapore
- Software License Notice in Germany
- Software License Notice in France
- Software License Notice in South Africa
- Software License Notice in Nigeria
- Software License Notice in Kenya
See the full software license notice guide for the template structure, or start from the list of all 103 jurisdictions we support.
Checklist before you send
- The obligation is identified by clause, statute or invoice — not described in general terms.
- The amount or the action required is stated exactly, with a calculation behind any figure.
- The deadline is a calendar date, and you intend to act on it.
- The document the recipient needs in order to comply is enclosed or named.
- Service method matches the contract or the statute, and the proof of delivery is ready.
- A dated copy of the notice is kept in the case file, together with everything you relied on.
If the recipient ignores it
Escalation is either a compliance settlement or licence litigation, and both turn on the audit trail: licence certificates, deployment logs, purchase orders and the metric definition in the agreement.
Common mistakes to avoid
- Stating a deadline you do not intend to enforce — a deadline that passes without consequence trains the recipient to ignore the next one.
- Leaving out the document that creates the obligation. Quote the clause, the statute or the invoice, and the notice stops being an opinion.
- Sending it to the wrong address. Use the address the contract or the statute names, and keep the proof of delivery.
- Mixing the demand with negotiation. Ask for the remedy and set the deadline in one letter; settle in a separate one.
Draft yours with the generator
The generator produces a first draft of a software license notice in minutes, applying the local terminology, the correct compliance window and the escalation route for the country you choose. Edit the wording, check the details against your own documents, and serve it by a method you can prove.