Define: Per Se

What Per Se Means in a Contract

Per se is a Latin phrase meaning by itself or as such. When used in a contract, it signals that a particular fact, act, or condition is treated as satisfying a legal or contractual standard purely because of what it is, without needing further proof of surrounding circumstances or consequences. For example, a clause might state that a breach of a confidentiality obligation constitutes a material breach per se, meaning the parties agree in advance that no additional showing of harm is required.

This usage removes ambiguity by pre-classifying certain events. Instead of leaving a court or counterparty to debate whether an act was serious enough to trigger a remedy, the per se designation makes the classification automatic. It is a drafting shortcut that trades flexibility for certainty, which can be valuable in industries like finance where predictable triggers for default or termination matter greatly to risk allocation.

Because per se strips away contextual evaluation, it tends to appear where the parties want a bright-line rule rather than a case-by-case judgment call. This is different from language requiring a party to prove materiality, reasonableness, or intent, all of which invite interpretation.

How Per Se Is Defined or Measured

Per se is not measured numerically or by a formula. Instead, it functions as a legal classification tool. A contract will typically pair the term with a specific triggering event, such as a certain type of disclosure, a missed payment, or a breach of an exclusivity provision, and declare that event to be per se material, per se unreasonable, or per se a default.

The measurement, if any, lies in identifying whether the triggering event has occurred at all, not in weighing its severity. Once the event is confirmed, the per se label does the rest of the work, closing off arguments about degree or impact.

• Per se breach: automatically treated as breach without proving damage
• Per se default: triggers remedies immediately upon occurrence
• Per se unreasonable: bypasses a reasonableness balancing test

Where Per Se Appears in Agreements

The term commonly surfaces in confidentiality, non-compete, and termination clauses, where parties want certain violations to carry automatic consequences. It also appears in representations and warranties sections, where a false statement about a specific fact may be deemed a material misrepresentation per se.

Industries with heavily regulated obligations, such as healthcare and insurance, often use per se language to align contractual triggers with compliance thresholds that leave little room for interpretation. In these sectors, a per se violation clause can mirror regulatory definitions so that contractual and legal consequences move together.

Per se clauses can also appear in service level agreements, where missing a specified metric is deemed a per se failure of performance, triggering credits or termination rights without further debate about whether the shortfall actually harmed the customer.

Why the Exact Wording Matters

Because per se eliminates the need to prove context or consequence, the precision of the surrounding language becomes critical. If a clause states that late payment beyond a stated number of days is a breach per se, the drafter must be exact about the trigger, since ambiguity defeats the purpose of using the term in the first place.

Vague per se language can create disputes over whether the underlying condition was actually met, even though the classification itself is not in question. Courts applying the law governing the contract will look closely at how the triggering event is defined, so loose drafting can undermine the certainty the parties intended to create.

Drafting Considerations

Drafters should use per se sparingly and only where a bright-line rule genuinely serves the parties' interests. Overuse can create rigid outcomes that do not account for minor or technical violations that were never intended to carry severe consequences.

It helps to pair per se language with clearly defined terms elsewhere in the agreement, so the triggering condition is unambiguous. Teams responsible for reviewing risk allocation, such as Risk Management teams, often flag per se clauses for careful scrutiny since they remove the flexibility to argue proportionality after the fact.

Finally, drafters should consider whether a per se standard aligns with how similar terms are treated elsewhere in the agreement, avoiding inconsistent thresholds that could confuse enforcement or invite challenges to the clause's intended automatic effect.