Engineering guides / Software consulting and technical discovery
By Arte Soft engineering · 24 October 2026
Software maintenance contract: scope, authorisation and exit clauses
Before commissioning software maintenance, turn expectations into an agreed responsibility schedule. This procurement guide concerns the contract’s scope, authorisation and exit arrangements across applications and infrastructure. For day-to-day native iOS maintenance work, use the separate iOS retainer guide.
Establish the supported baseline
List the applications, versions, environments and external services included. Confirm that source code, build instructions and release access are available and that the current production revision can be identified. Record known defects and unsupported components before the agreement starts. Otherwise an old issue can become an argument about whether it is a new failure. Decide whether data recovery, store submissions and infrastructure changes are included. If taking over an unfamiliar system, a preliminary assessment may be necessary before committing to response obligations. That assessment should have its own scope and output rather than an undefined onboarding period.
Prepare an authorisation and change schedule
Attach a table that identifies who may request a change, approve its cost, accept its result and authorise production deployment. A support contact is not necessarily a purchasing authority. Specify how an urgent fix is approved when the ordinary decision maker is unavailable, and how that approval is recorded afterwards. Include the route for rejecting a change or postponing work without implying acceptance. This is a procurement checklist for discussion with appropriate advisers, not a ready-made legal agreement. The signed terms should describe payment, intellectual property, access, liability and termination in language suitable for the parties and jurisdiction. Engineering scope alone does not settle those commercial and legal obligations.
Specify release and acceptance responsibilities
Decide who approves changes, performs acceptance checks and authorizes production deployment. Keep environments and customer data protected during diagnosis. Deliverables can include a maintained issue register, change records, release notes and periodic dependency review, according to the agreement. Acceptance for an individual fix should reproduce the original problem and verify the affected journey after the change. Describe exclusions such as major features, legal assurance or unrelated vendor support. A maintenance arrangement works better when both parties can distinguish a defect correction from a commercial change request without reopening the whole contract each time.
Keep a record of service boundaries when a new feature is added. A maintenance agreement written for one website should not silently expand to cover a newly connected mobile app, payment provider or overnight processing job without an explicit review.
Plan continuity and exit
Keep documentation and credentials under the client’s appropriate ownership, with controlled access for the maintainer. Define how open issues and release knowledge transfer if the arrangement ends. Arte Soft’s public products demonstrate ongoing software ownership, not a guarantee of immediate support capacity for every system or a particular service level. Bring the system inventory, current operational problems and the coverage you need. We can assess a maintenance scope and identify any baseline repairs needed first. The goal is a sustainable agreement that makes responsibility clear, rather than an attractive promise that cannot be met when several failures occur together.
Relevant Arte Soft work
Cloud Calendars — our own product is our own product or engineering project. It provides context for the work we discuss here; it is not a claim of identical results for every client deployment.
Sources and further reading
Need help with Maintenance scope assessment?
Send the current app, system or brief, the behaviour you need and your constraints. We can agree a discovery, implementation or repair scope with concrete acceptance criteria.
Discuss this with Arte Soft