---
id: KB-TZ-014
url: https://app.codecontract.io/help/traceability-and-compliance/the-certificate-that-expires-in-august
idioma: en
categoria: trazabilidad
audiencia: usuario
nivel: basico
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-CF-001, KB-TD-002]
citadoPor: [KB-LE-013, KB-PR-018, KB-PR-019]
---

# The certificate that expires in August

_The expiries that fall at the worst time of year, and how to stop suffering them._

**Responde a:** expiries during holidays · certificate expired in august · renewals during the holiday period · warnings with enough lead time

Some expiries take care of themselves and others always land badly: August ones, the week between Christmas and New Year, and the first day of the year. It is not bad luck: the warning arrives when whoever must renew is away, and so is whoever could cover for them.

## The three bad moments

| When | Why it fails | Recommended margin |
| --- | --- | --- |
| August | The third parties renewing are also on holiday | Two months |
| Year end | It collides with closing and everyone is stretched | Two months |
| Early January | The warning arrived at Christmas and nobody saw it | Three months |

> [!IMPORTANT]
> The margin does not depend on how long you take: it depends on how long whoever issues the document takes. A medical certificate, an official certificate or a policy renewed through a broker all depend on third parties with their own holidays.

## How to fix it, once

1. **Set the margin per document type, not one for everything** — Insurance does not take as long as an audited certification.
2. **And a larger margin for anything expiring in a bad period** — It is the only rule that ends the annual suffering.
3. **With a named owner, not "the department"** — And a deputy for the period when that owner is away.
4. **And review in June what expires in August** — One review a year at the right moment beats twelve warnings.

> [!WARNING]
> The classic error is setting "one month before" for everything. For a document renewed in an afternoon it is excessive; for one requiring an external audit it arrives late and guarantees a lapse — with the peculiarity that the warning worked perfectly.

## If it has already lapsed

**En corto**

- First, know what stops: sometimes nothing, sometimes everything.
- Communicate before you are asked, especially if a client is affected.
- And record the date it was detected and what was done.

That record matters: the difference between a managed lapse and an ignored one, before an inspector or a client, is precisely being able to show when you saw it and what you did from then on.

> [!NOTE]
> When the lapsed document belongs to a third party — a supplier, a subcontractor — the decision on whether they keep working is yours and is best written down, even when the answer is yes.

**Can several people be warned?**

Yes, and for critical items it helps: one person may be away.

**What if the third party does not renew in time?**

That is your decision, not an accident: block, escalate or accept the risk.

**How many warnings are reasonable?**

Two: one with margin and a final call. More get ignored.

## Ejemplos

**A company finds two or three lapsed certificates every August.**

- Sets a two-month margin for summer expiries and names a deputy
- Reviews in June what expires in August

→ Summer stops being the month of emergency renewals.

**A certificate expires in the middle of the holiday period.**

- Brings forward warnings for anything falling in August

→ Renewal happens before nobody is around.

**The warning arrives and whoever should act is away.**

- Also addresses the warning to a deputy

→ Renewal does not wait on one person.

**Renewal happens late and there is a gap in cover.**

- Adjusts the lead time to the process's real duration

→ No day is left uncovered.

**Nobody knows what expires in the coming months.**

- Checks expiries by date

→ The calendar gets planned.

**The provider takes longer than expected to renew.**

- Adds their response time to the lead time

→ The margin includes the wait.