Scope, deliverables and milestones
Identify included services, specifications, dependencies, delivery dates, milestones and work that sits outside the agreed scope.


Aletura reviews service, contractor, freelance and consulting agreements by connecting deliverables and acceptance with fees, changes, ownership, risk and termination.
A service agreement should explain what is included, who depends on whom, how work is accepted and what happens when requirements change or delivery is delayed.
Review scope, deliverables, milestones, acceptance, fees, changes, ownership, liability, subcontracting and termination.
Identify included services, specifications, dependencies, delivery dates, milestones and work that sits outside the agreed scope.
Check review periods, acceptance criteria, deemed acceptance, rejection rights and the process for approving changes in scope, cost or timing.
Review fixed, time-based or milestone fees, expenses, invoicing, payment deadlines, disputed invoices and late-payment consequences.
Clarify ownership of background materials, project deliverables, reusable components, licences and rights that depend on payment.
Examine service warranties, correction obligations, liability caps, excluded losses, indemnities and remedies for delay or defective work.
Review termination rights, work-in-progress payments, handover duties, transition support and whether subcontractors may be used.
Compare 2–3 service, contractor, freelance or consulting agreements across scope, price, acceptance, ownership, liability and exit obligations.
Start with the important terms, then check the source passages and the questions that still need an answer.
For this prototype, open the fictional example. Public private-document uploads and live analysis are disabled.
Explore costs, responsibilities and dates in everyday language, with the original passages and visible uncertainty.
Find specific questions about missing information. Aletura provides information, not professional legal advice.
Guest use requires no account and creates no saved analysis. Signed-in users may explicitly save an encrypted masked result or, where policy permits, separately choose to retain the original contract with it. Unmasked extracted text and temporary identifier mappings are never saved.
Personal identifiers are privacy-masked locally before Mistral calls. Aletura defaults to Mistral EU regional inference, but the active deployment must be verified and a regional endpoint alone does not establish unconditional end-to-end EU residency or compliance.
Aletura helps you understand contractual text and identify terms that deserve attention. It does not decide enforceability, determine which mandatory law applies or recommend a legal strategy.
English, German, French, Italian and Romanian are configured report-language and benchmark targets. Their current certification status is not yet validated. Other detected languages use English output where processing is technically possible and are also not yet validated. Evidence stays in its original source language.
Not yet validated
A contract analyzer reviews an agreement against predefined questions and organizes findings about commitments, costs, risks, rights and exit terms.
Aletura checks purpose, parties, duration, money, obligations, liability, unilateral powers, termination, missing provisions and referenced documents.
Aletura performs structured checks automatically. Follow-up questions come after analysis and operate only on validated findings in the returned result.
It checks for renewal, notice and termination terms and links findings to evidence. Incomplete checks remain unresolved rather than being treated as safe.
Yes. It compares 2–3 documents after checking compatibility. Full clause-level comparison is reserved for likely versions or agreements of the same type.
Configured frameworks cover rental, leasing, purchase, services, memberships, SaaS, employment, confidentiality, financing and insurance, with universal checks for uncertain types.
Guest contracts and analysis reports are not saved. Signed-in users explicitly choose whether to save only the encrypted masked result or, where permitted, retain the original contract with it. Unmasked extracted text and temporary identifier mappings are never saved.
EN, DE, FR, IT and RO are configured report-language and benchmark targets but are not yet validated by a complete benchmark. Source evidence is not translated.
Yes. You may ask up to five successfully processed follow-up questions. Answers use the validated result, not the original contract.
No. Aletura provides structured information and highlights questions, but it does not determine enforceability or provide legal advice.
Upload a contract for structured analysis of its commitments, risks and exit terms.