Response & resolution time log

Field record

When the call came in, when you got there, when it was done.

Three times, written down while they are known

Received, arrived, resolved. Reconstructed a week later they are guesses; written on the day they are a record.

The target is yours and nothing is measured against it

There is a header field for the target you are working to, copied from your own agreement. CompliMaint supplies no service level, no response or resolution time and no priority scale, and it fills nothing in.

No elapsed time is calculated, and no breach is concluded

The tool computes no duration, no average and no percentage, and it makes no determination that a target was met, missed or breached. Your agreement says what you owe; reading these times against it is your job.

Kept alongside: Technician route sheet · Service agreement register · Callback register

A log of call, arrival and resolution times, kept on your device, against a target you entered from your own agreement. CompliMaint supplies no service level, response or resolution time or priority scale; calculates no elapsed time, average or percentage; and makes no determination that any target was met, missed or breached. Everything runs on your device.

Questions people ask

Does it come with standard SLA targets?
No. CompliMaint supplies no service level, response time or resolution time, and fills nothing in. The target field is one you copy from your own agreement.
Does it calculate how long a call took?
No. It computes no elapsed time, average or percentage. It records the times somebody wrote down.
Does it tell me whether I breached the SLA?
No. It makes no determination that a target was met, missed or breached. Your agreement says what you owe; reading the times against it is your job.
Can I record why a call took longer?
Yes — the notes column and the block under the grid are for exactly that: access delays, parts, a second visit.
Is anything transmitted?
No. The log stays in this browser.