Software choice
Service level guarantees (SLAs) of condominium software
Cloud condominium software is reachable as long as the service is running: if it is not available when needed, the manager cannot generate a statement, send a notice of meeting or consult a condominium's data. Service level guarantees, often referred to by the acronym SLA, are the commitments through which the vendor describes service availability, maintenance windows and intervention times in case of problems. Understanding how to read them is part of an informed choice, because they distinguish a vendor that formalises its commitments from one that leaves everything implicit. This guide explains what a service level guarantee covers, how to interpret its main points and what to check before subscribing.
What to check in service level guarantees
- A service availability level is stated, with a verifiable value.
- Scheduled maintenance windows are communicated in advance and at low-impact times.
- Intervention times for outages are distinguished from ordinary support times.
- A page or channel exists that communicates service status and any outages.
- The commitments are documented in writing and do not remain a generic promise.
- Continuity and recovery measures in case of a significant failure are described.
- It is clear how unplanned interruptions are handled and communicated.
What service level guarantees are
A service level guarantee is the set of commitments through which the vendor describes the quality of the service it offers: how available the software is over time, how it handles maintenance, how quickly it intervenes in case of an outage and how it communicates the system's status. It is not a technical detail reserved for specialists, but an element that directly affects the firm's operational continuity.
The difference between a vendor that formalises these commitments and one that leaves them implicit is substantial. Written, verifiable commitments let the manager know what to expect and plan critical moments with greater confidence. In the absence of explicit guarantees, service quality is left to the vendor's goodwill, without an objective reference.
Service availability and maintenance windows
The most visible point of a guarantee is service availability, that is, the percentage of time the software is reachable. A stated, verifiable value is preferable to generic formulas such as always available, which offer no concrete reference. It is useful to understand whether the value includes or excludes scheduled maintenance, because the distinction changes the meaning of the figure.
Scheduled maintenance windows are normal in any cloud service: they serve to update and secure the system. What matters is that they are communicated in advance and placed at low-impact times, for example at night, so as not to interfere with the manager's daily activities. A vendor that plans and announces maintenance shows respect for users' work.
Outage intervention times and service status
Service level guarantees distinguish outage intervention times from ordinary support times. Answering an operational question is one thing; restoring the service when it is down for all users is another. A serious vendor describes how it handles interruptions, with what priority it intervenes and how it keeps users informed during recovery.
A useful tool is the page or channel that communicates service status, where users can check in real time whether a problem is widespread or affects only their own workstation. This transparency avoids uncertainty during outages and lets the manager understand at once whether to wait for recovery or look for an alternative.
Continuity, recovery and written commitments
A complete guarantee also describes continuity and recovery measures in case of a significant failure: how data is protected, how often it is saved and how the service can be restored after an incident. For a manager who holds accounting data and meeting documents, this dimension is as central as day-to-day availability.
The value of a guarantee also lies in its formalisation. Commitments documented in writing are more reliable than verbal statements, because they offer an objective reference. Before subscribing it is worth checking whether the vendor puts its service commitments in writing. AmministraPro describes its features and plans on the /funzioni and /prezzi pages, useful for assessing, alongside the product, the quality of service offered before subscribing.
Frequently asked questions
What does a service level guarantee indicate?
It indicates the commitments through which the vendor describes service quality: how available the software is over time, how it handles maintenance, how quickly it intervenes in case of an outage and how it communicates the system's status. For cloud software these commitments directly affect the firm's operational continuity, because they determine what the manager can expect when the service is not reachable at the moment it is needed.
Does the stated availability include scheduled maintenance?
It depends on the vendor, which is precisely why it should be clarified. An availability value can be calculated including or excluding scheduled maintenance windows, and the distinction changes the meaning of the figure. It is useful to ask explicitly how availability is measured and to check that maintenance is communicated in advance and placed at low-impact times, so as not to interfere with daily activities.
Why are maintenance windows normal?
Because every cloud service needs periodic maintenance to update and secure itself. Scheduled maintenance is not a defect but a necessity. What distinguishes a serious vendor is the handling: communicating maintenance in advance and placing it at low-impact times, for example at night, avoids interfering with the manager's work and shows attention to users.
What use is a service status page?
It serves to check in real time whether an outage is widespread or affects only your own workstation. When the software does not respond, this transparency avoids uncertainty and lets the manager understand at once whether to wait for recovery or look for an alternative. A page or channel communicating service status and any problems is a concrete sign of transparency on the vendor's part.
Should service level commitments be in writing?
Where possible, yes, because commitments documented in writing offer an objective reference and are more reliable than verbal statements. Not all vendors formalise service parameters, but the mere willingness to put commitments on availability, maintenance and recovery in writing is already an indicator of seriousness. Without explicit commitments, service quality is left to the vendor's goodwill, with no verifiable guarantees.
Try AmministraPro
Accounting, thousandths-based cost splitting, meetings, communications and artificial intelligence in a single Italian software, compliant with UNI 10801 and GDPR.