Skip to content
DutyHub

What it does

Statutory clocks

A subject access request, a breach assessment, a complaint with a deadline. The clock starts when it arrives and the record shows what you decided along the way.

Deadlines are calculated properly. One calendar month from receipt is not thirty days and is not twenty working days, and a deadline calculated the convenient way is a deadline you will miss or over-serve.

An extension is declared, capped, and recorded as an extension. It is not a paused clock, because pausing puts time into the record that nobody actually waited and makes every later report wrong.

Decisions — a redaction, an exemption, a decision not to report a breach — are written through the audit trail as they are made and sealed, so what you knew and when is a record rather than a recollection.

A statutory clock, and where an extension fitsThe period runs from the date the request was received, not from when somebody noticed it. A subject access request is due within one calendar month. Where an extension applies it adds two further months, and the requester must be told within the first month and told why. Received The clock starts here, not when it was noticed One calendar month Due. A month, not 30 days — 31 January falls due in February + two months Only where an extension applies, and only if you said so in month one An extension is declared and capped. It is not a paused clock.
A statutory clock, and where an extension fits

What it does not do

The boundary, stated plainly, because you will find it eventually and it is better to find it now.

  • DutyHub calculates the deadline from the rules configured for the case type. Those rules are our reading of published guidance, reviewed by a retained practitioner and versioned so a past decision replays — but they are not a legal opinion on your case.
  • It does not decide whether an exemption applies. It records that you decided, when, and why.