Make the intake specific
Supply the parties, document kind, jurisdiction, obligations, dates and reference material. Review imported content and retain its source identity before using it in a new matter.
Lex · worked guide
Software license agreement template: define the permission precisely
A software license agreement sets the permissions and conditions for using software. A useful template starts with the licensed software and the people, purposes and environments covered by the proposed grant. It then separates those permissions from ownership, service commitments and matters that require jurisdiction-specific legal review.
Choose License Agreement drafting →Lex · real output
Read the matter facts and the resulting draft together.
This is a real Lex export for invented parties. Inspect the input and clauses as a worked example, with professional review kept separate from automated drafting and checks.
Master Services Agreement: analytics services (worked example)
A master services agreement of 17 numbered parts: definitions, scope of services, service levels and change orders, fees, intellectual property, confidentiality, data protection, warranties, indemnification, limitation of liability, force majeure, term and termination, transition assistance, governing law, general provisions and schedules. Its first page says it is a worked example, not a legal document.
Inspect the source brief or data
Draft a Master Services Agreement: analytics services between Larkfield Analytics Ltd (Supplier) and Harbourside Housing Association (Customer). Governing law: England and Wales. Effective date: 2027-02-01. Term: Two years from the effective date, renewable by written agreement. Confidentiality: Five years after the agreement ends. The Supplier provides survey design, data engineering and dashboard services to the Customer under statements of work agreed in writing. Excluded: any service not set out in a signed statement of work. Dependencies: the Customer provides access to its systems and a named contact for each statement of work. State on the first page that the parties, people and addresses in this agreement are invented and that it is a worked example, not a legal document. The notice email address of Larkfield Analytics Ltd is notices@larkfield-analytics.example and of Harbourside Housing Association is notices@harbourside-housing.example (both invented).
Read the sample review notes
Read mechanically against the intake, not by a lawyer: 10 of the 12 facts the intake gave are in the draft (the two registration numbers are not printed), nothing is left as a placeholder, and it states two terms the intake did not give, 30 days and 10 Business Days, which Lex chose.
Inspect clauses and changes
Use the legal workspace's permitted structural tools, Draft Checks and review paths. Compare proposed changes with the saved draft and original material; unsupported Word edits must be handled explicitly.
Approve the exact version
Have qualified counsel review enforceability, local requirements and the actual commercial intent. Check the current approval state and the downloaded document after a change.
Structured clause proposals and permitted changes
Select the target clause and give Ask Lex a bounded instruction. Missing facts remain visible for review. Inspect the before-and-after proposal, required clause checks and any explicit outside-matrix or mandatory-clause override before versioned application. Use the legal workspace's structural allowlist rather than assuming every general content-editor block is available.
Playbooks, source evidence and obligations
Inspect immutable playbook versions, anchored findings, provenance and precedent variants before staging a change. Matters retain original sources, quotation findings and source-version comparisons. Review extracted obligations for timing, ownership and source revision; negotiation turns and agreement-pack review cells have their own decisions and current-version requirements.
Original Word, redlines and the delivery receipt
Original-format Word export, tracked changes against an original and saved-version redlines are separate paths. Unsupported edits must be surfaced rather than silently claimed as preserved. Inspect the layout, validator notes and downloaded file, then retain its delivery receipt. Counsel's review applies to the actual matter and version.
Lex does not provide legal advice or certify compliance. The public specimen is not a universally reusable legal template. Word fidelity depends on the supported original-document and saved-version path; unrestricted Power Edit and image insertion are not legal editing features.
Filled license-scope planning example
This filled example is an editorial explanation of the structure. The related real product output above is separately identified.
| Part | Example and review point |
|---|---|
| Parties and software | Invented licensor Alder Software Ltd and licensee Birch Studio Ltd; the named software release and documentation must be identified. |
| Permitted use | Illustrative instruction: internal business use by the named team. Decide separately whether affiliates, contractors or additional environments are included. |
| Restrictions and ownership | Record the proposed copying, distribution, modification and transfer terms for counsel to assess; identify retained IP ownership. |
| Commercial and service terms | Supply the actual fees, term, support scope and any separately agreed service levels. |
| End of permission | Specify the proposed termination triggers and what should happen to access, copies and data afterwards. |
A filled license-scope excerpt
Hand-authored educational illustration. The parties and proposed transaction are invented. This is not a generated Lex result, a complete agreement or an actual obligation.
For this fictional planning example, Alder Software Ltd proposes to permit Birch Studio Ltd to use ExampleApp version 1 internally during the evaluation period from 15 January to 14 February 2027, solely through its named evaluation team. Ownership would remain with the licensor; the proposed permission would not include distribution or transfer of source code.
- The software, release, permitted users, purpose and evaluation period are identified.
- The proposed grant is separated from ownership and from distribution rights.
- Fees, support, data handling, warranties, remedies and termination need separate instructions and qualified review.
Keep licensing, services and compliance review distinct
A license grant is not an assignment of ownership. Do not assume that a service agreement, privacy notice or open-source compliance policy answers the same question. Confirm the actual deployment model, third-party components, data handling and contracting entities before drafting. Lex includes a License Agreement type and can prepare a matter-specific first draft from supplied facts. Qualified counsel must review local enforceability, exclusions, remedies and the intended rights. This page does not perform a software-license compliance audit.
Reference: WIPO explanation of licensing agreements. Checked 20 October 2026.
Updated
More from Gixo