SLA penalties in Portugal: how to write, cap and enforce them

An SLA penalty is a pre-agreed consequence for missing a service level, such as a response time, a restoration time or an availability target. In Portugal, a penalty between two businesses is valid when the contract defines the breach clearly, ties the amount to the likely harm and keeps it from being grossly excessive. Beyond that, the penalty only works if you can prove the breach with records. This guide covers the legal frame, the calculation methods, a real Portuguese public-tender example and the evidence trail that makes a penalty enforceable.

Fullyops

fullyops.com

Make SLA Breaches Easier to Prove

Fullyops records work orders, interventions and hours, helping maintenance teams document service activity relevant to SLA measurement.

Solicite una demostración

TL;DR

A penalty can be a service credit (a fee reduction on a later invoice) or a cláusula penal (a pre-agreed compensation under the Civil Code). They are not the same instrument, so name which one you mean.
Portuguese courts can reduce a manifestly excessive penalty clause, and in standard-form contracts between businesses a disproportionate one can be void.
Penalties should scale with the severity and recurrence of the breach and sit under a clear cap. One public Portuguese tender uses 1‰ of the contract price per day of delay and a 10% cap per infraction.
Vague indicators cannot be enforced. Define the baseline, target, measurement method, owner, frequency and reporting window for each one.
Time-stamped work order records are what turn a breach into a provable fact, for both supplier and customer.

Índice

What an SLA penalty is, and what it is not
The Portuguese legal frame in plain terms
Which breaches should carry a penalty
A Portuguese example: the IMPIC tender specification
How to calculate a penalty that holds up
Exclusions, notice and cure periods
Evidence: the part that decides disputes
Contesting a penalty and escalating a dispute
When breaches keep happening
Put the measurement in place before the penalty applies
PREGUNTAS FRECUENTES
Fuentes

What an SLA penalty is, and what it is not

People use “penalty” for several different mechanisms. Mixing them up is the most common drafting mistake, so separate them before you write a number.

Service credits. A service credit is normally a reduction of the fee, or a credit applied to a future billing period, when the service falls below the SLA benchmark. UNCITRAL’s notes on cloud computing contracts describe it as a deduction in the next measurement period, often on a sliding scale according to how far the service missed the target, with an overall cap (UNCITRAL, remedies). Credits are common in recurring-service contracts because they are simple to apply and do not require anyone to prove loss.

Penalty clauses (cláusulas penais). In Portugal, a penalty clause is the parties’ advance fixing of the compensation owed for non-performance, under article 810(1) of the Civil Code, as summarised by the Supreme Court of Justice (Supremo Tribunal de Justiça, 2010). It is a liquidated-damages mechanism, so the Civil Code rules on its limits apply.

Ordinary damages. If the contract has no penalty clause, the customer would need to prove actual loss in the usual way. A penalty clause exists to avoid that burden.

A good SLA says in one sentence which of these applies to which breach. For example: “Missed response times generate a service credit; repeated or definitive non-performance gives rise to a contractual penalty under the clause below.”

The Portuguese legal frame in plain terms

This section summarises the rules that matter most for B2B maintenance and facilities contracts. It is general information, not legal advice: for a specific contract, have a Portuguese lawyer (advogado) review the clause.

Article 811: no double recovery

Under article 811 of the Civil Code, the creditor generally cannot demand both performance of the main obligation and the penalty, except where the penalty is for delay. It also bars compensation above the penalty unless the parties agreed otherwise, and the compensation cannot exceed the loss resulting from the non-performance (Código Civil, art. 811). In practice, a supplier who is late can be both required to perform and charged a delay penalty, but a definitive failure should not produce both full performance and a full compensatory penalty.

Article 812: courts can reduce an excessive penalty

Article 812 lets the court equitably reduce a penalty clause that is manifestly excessive, including because of a later change in circumstances. Any stipulation that excludes that reduction is void (Código Civil, art. 812). So you cannot draft your way around the court’s power with a “no reduction” clause.

The threshold is high. Portuguese case law treats the relevant excess as a substantial, glaring or shocking disproportion, not any gap between the penalty and the actual loss. The party seeking reduction must plead and prove the relevant facts, and the court does not normally reduce on its own initiative (Supremo Tribunal de Justiça, 2018). The same judgment says a clause is illegitimate only where there is a shocking disproportion between the foreseeable damage and the compensation it provides.

Standard-form contracts between businesses

Most SaaS and maintenance providers use standard terms. For relations between businesses, article 19© of Decree-Law 446/85 (the general contractual clauses regime) prohibits penalty clauses that are disproportionate to the damage to be compensated (Diário da República, consolidated text). The Supreme Court has noted a practical difference: under this rule the consequence is nullity, whereas under article 812 the consequence is reduction (Supremo Tribunal de Justiça, 2022).

The drafting lesson is the same for both parties. A penalty that is proportionate, tiered and capped is far more likely to stand than a single flat figure that ignores how serious the breach was.

Which breaches should carry a penalty

Not every missed target deserves a financial consequence. Attach penalties to the indicators that damage the customer’s operation, and leave minor ones to reporting and corrective action plans.

In maintenance and facilities contracts, the usual candidates are:

Response time: how long from the fault being logged to a technician acknowledging or arriving.
Restoration time: how long until the asset is back in at least operational condition.
Final resolution time: how long until a permanent fix, where the first restoration was only temporary.
Equipment availability: the share of time that critical assets are in service.
Preventive maintenance compliance: planned tasks completed within the agreed window.
Coverage: staffed posts or on-call cover delivered against what the contract requires.

Facilities guidance lists indicators of this kind, such as response times, equipment availability, preventive maintenance and post coverage, and recommends fixing a baseline, target, method, frequency and measurement window for each (OHUB facilities guide). The same guidance warns that loose wording such as “adequate cleaning” is hard to apply and invites disputes.

Define each indicator so it can be measured

For every indicator that carries a penalty, write down:

Baseline: the current level, so the target is realistic.
Target: the number the supplier commits to.
Method: what counts as the start and the end of the clock.
Owner: who records the measurement.
Frequency: how often it is calculated.
Reporting window: the period over which compliance is judged, such as a calendar month.

Objective, physical checks help here. A checklist such as measurable rooftop unit checks shows how a maintenance task can be defined as a yes-or-no item rather than an opinion, which is exactly what a penalty trigger needs.

A Portuguese example: the IMPIC tender specification

Public procurement documents are a useful reference because they are published and specific. The IMPIC (the Portuguese construction and real estate institute) set out service levels and penalties in a 2022 tender specification (IMPIC, caderno de encargos). This is a public-sector example, not a market standard, but it shows how the pieces fit together.

Service levels by priority

Prioridad	Response	Restoration	Final resolution
Maximum	Within 4 hours	Within 10 hours	Up to 15 days where the first restoration was only operational
Medio	Within 12 hours	Within 1 day	Up to 20 days where applicable
Minimum	1 working day	Not separately stated	Solution within 30 days

The useful idea is the priority ladder: the more critical the fault, the shorter the clock, and the clock is split into response, restoration and permanent fix. A single “resolve within X hours” target cannot capture that.

Penalties and caps

The same document provides for:

a penalty of 1‰ of the contract price for each day of delay;
5% of the contract price for defective performance notified in writing;
10% for definitive non-performance;
severity assessed by duration, repetition, degree of fault and consequences;
a cap of 10% of the contract price per infraction and 20% in aggregate, which can rise to 30% in specific circumstances where the contract is not terminated.

Three design choices stand out. The amount grows with the type of failure. The severity test looks at recurrence and consequences, not just minutes. And there are two caps, one per event and one overall, so that exposure is predictable for the supplier and the penalty stays defensible against the proportionality tests described above.

A worked illustration

Take a hypothetical annual facilities maintenance contract worth €120,000, using the IMPIC percentages purely as an example. A delay of three days would give 3 × 1‰ × €120,000 = €360. Defective performance notified in writing would give 5% = €6,000. Definitive non-performance would reach the 10% per-infraction cap, €12,000. Accumulated penalties would stop at 20%, €24,000, unless the contract provides otherwise. The figures are illustrative: your own numbers should reflect the harm a breach actually causes your operation.

How to calculate a penalty that holds up

There are four common structures. Many contracts combine them.

Flat amount per breach. Easy to administer, but it ignores severity and is the structure most exposed to a proportionality challenge when the sums are large.

Amount per unit of delay. A percentage of the contract price, or of the monthly fee, per hour or day late. It follows the harm as it grows and fits delay breaches well.

Sliding-scale service credit. A percentage of the monthly fee that rises as performance falls further below target, with an overall cap, as described in the UNCITRAL notes above. It suits availability and uptime indicators.

Tiered by severity and recurrence. Higher tiers for repeated or serious breaches, as in the IMPIC model. This is the most defensible because it links the amount to the seriousness of what happened.

Drafting checklist for the amount

Express the penalty as a percentage of a defined base (monthly fee, annual price or affected scope), not an unexplained figure.
Set a cap per event and an overall cap per period.
Say whether the penalty is exclusive or whether the customer may also claim proven damages above it. Under article 811, damages beyond the penalty require the parties’ agreement.
Say whether the penalty is paid, credited or set off against invoices.
Keep the amount in proportion to the foreseeable damage. If a short outage on a non-critical asset carries the same penalty as a plant stoppage, one of the two is mispriced.

Exclusions, notice and cure periods

A penalty is only fair if the supplier controlled the outcome. Most disputes come from what the contract leaves unsaid, so cover these points:

Exclusions: customer-caused delay (no site access, missing approvals), planned maintenance windows agreed in advance and events outside either party’s control.
Notice: how and when the customer must flag a breach, and in what form. The IMPIC model, for instance, ties its 5% penalty to defects notified in writing.
Cure period: whether the supplier has a short window to fix the problem before the penalty applies, and for which priorities.
Clock rules: whether the clock runs during nights, weekends and public holidays, and whether it stops while waiting for the customer.
Root cause: a requirement to document the cause and the corrective action after serious incidents.

One Portuguese IT services provider describes a sound incident record as covering opening, priority, assignment, documented resolution and closure, with a report and root cause (Impulso Tecnológico). That is a company’s description of its own process rather than a rule, but the five-step trail is a sensible minimum for any maintenance contract.

Evidence: the part that decides disputes

A penalty clause is worth what the records behind it are worth. When a customer says a response took six hours and the supplier says two, the contract needs a single agreed source of truth.

At a minimum, each work order should hold:

the time the request was logged and its priority;
the time of assignment and of the technician’s arrival or first action;
the time of restoration and of final closure;
the technician’s notes, parts used and any photos or sign-off;
a note of any pause with its reason, such as waiting for site access.

If these live in spreadsheets, emails and phone calls, neither side can prove much. If they live in a work order system with automatic time stamps, the monthly SLA report becomes a by-product of the daily work. Our guide to the five-stage work order workflow shows how the stages map to those time stamps, and our piece on maintenance compliance records for inspections and tenders covers the documentation Portuguese clients typically expect.

Contesting a penalty and escalating a dispute

A contract should say whether a measurement can be contested, within what period and with what evidence. Facilities guidance suggests a monthly governance committee that reviews results, causes and action plans, with minutes and follow-up (OHUB facilities guide).

A workable escalation ladder looks like this:

Monthly SLA report issued by a set day, with the underlying work order data available to both sides.
Contestation window, for example a fixed number of working days, in which the other party submits its evidence.
Operational review meeting between the account manager and the customer’s maintenance lead, with minutes.
Senior escalation to named managers on each side if the meeting does not resolve it.
Formal dispute route chosen in the contract, such as mediation, arbitration or the courts.

If a penalty ends up in court, remember the position described earlier: the party arguing that it is manifestly excessive must plead and prove the facts. Good records protect whichever side is right.

When breaches keep happening

Repeated breaches should change the response, not only the amount. A well-drafted SLA moves from credits to a formal improvement plan, and from there to the higher penalty tiers described above. It should also state what counts as a persistent breach, for example the same indicator missed in a set number of consecutive reporting periods, and what rights follow. Whether and how a contract can be terminated for repeated failure depends on its wording and on Portuguese law, so have this clause reviewed by a lawyer before signing.

Our perspective

We see the same pattern in maintenance contracts again and again: the penalty clause is negotiated for weeks, and the measurement method is left to the last page. Then the first dispute arrives and neither side can show when a ticket was opened, when the technician arrived or when the asset was handed back.

That is why we built FullyOps around the work order as the unit of record. Asset history, work order control, field data collection and operational analytics sit in one platform, so the time stamps that decide an SLA are captured as the work happens, not reconstructed at the end of the month. Our plans are designed for different roles, with technicians, administrators and managers each seeing what they need.

Our advice to operations managers is to write the SLA around what your system can measure, and to choose a system that measures what your SLA promises. When the two match, penalties become rare, because problems surface before they become breaches, and disputes become short, because both sides read the same record.

Pedro

Put the measurement in place before the penalty applies

If your contracts carry response, restoration or preventive maintenance targets, FullyOps gives your team work order management, preventive maintenance scheduling, inventory tracking, reporting and performance analytics in one cloud platform, with integrations to your other systems. You can see the Basic, Professional and Advanced plans on the FullyOps website, and compare tools in our guide to the best SLA maintenance software in Portugal. For the contract side, see our article on five clauses that prove maintenance KPIs and our overview of SLA management for operations teams.

PREGUNTAS FRECUENTES

Is an SLA penalty the same as a service credit?

No. A service credit is usually a fee reduction applied to a later billing period, often on a sliding scale with a cap. A penalty clause under the Portuguese Civil Code is a pre-agreed compensation for non-performance. A contract can use one, the other or both, but it should say which applies to which breach.

Can a Portuguese court reduce an SLA penalty?

Yes, if the penalty is manifestly excessive. Article 812 of the Civil Code allows equitable reduction, and case law requires a substantial, glaring disproportion. The party asking for reduction must plead and prove the relevant facts. In standard-form contracts between businesses, a disproportionate penalty can instead be void under Decree-Law 446/85.

What is a reasonable cap on SLA penalties?

There is no single legal figure. A published Portuguese public tender from the IMPIC caps each infraction at 10% of the contract price and the total at 20%, with a possible increase to 30% in specific circumstances. Treat that as an example and set your own cap in proportion to the harm a breach would cause.

What evidence do I need to apply a penalty?

You need time-stamped records of the request, priority, assignment, arrival, restoration and closure, plus notes on any pauses and the cause. The contract should also say who produces the monthly report and how long the other side has to contest it. Records kept in a work order system are easier to defend than emails and phone logs.