Renew a certificate before it lapses, not after

Today, an expiry is a date somebody typed into a spreadsheet, or did not. The renewal starts when a customer, an auditor or a border asks for the current one.

In Engrama the date lives on the record itself, so what is expiring is a state on the list rather than a thing to remember.

This job finishes and then starts again. That is what makes it a job and not a standing worry: each renewal closes, and the next date is already on the record.

A renewal has an order, and every step of it happens before the expiry rather than after.

The date arrives on the record

Not in a calendar. It comes in with the document, from the document, so nobody has to transcribe it.

The request goes out early

Far enough ahead that the counterparty has time to get it, which is the whole difference between a renewal and a lapse.

What comes back is checked

A replacement that is already expired, or that covers the wrong scope, is refused before it reaches you.

The new one replaces the old

Filed against the record it renews, with both kept, so the history is the record’s rather than an inbox’s.

You write the checks into the request when it goes out. Engrama runs them on what comes back, before it reaches you.

Some of them are a detail a machine can read: the new expiry date, the issuing body, the period covered. Some of them are not. Whether the replacement covers the same scope as the one it replaces is a judgment.

You decide whether what arrived is what you needed.

Today, renewed means the new PDF is in an inbox and the spreadsheet has been updated, or it has not.

With Engrama, the replacement is filed against the record it renews, the old one is kept, and the next expiry is already on the list.

An auditor, a customer, a regulator, an insurer, the person you answer to: whoever asks, you open the record instead of building the answer.