Your organisation as it really is.

The work,
in time windows

Tasks that belong together are bundled into a stack with one time window: the opening round, the midday check, the closing round. Define it once, use it in forty branches.

• Recurrence rules that hold. Night shifts and the clocks going forward are worked out properly, so no day of work quietly disappears.
• Exceptions per recurrence. Skip a day, move it, or schedule something extra just once, without tearing up the whole rota.
• Flexible tasks with a long window. Getting the Easter decorations ready and dressing the seasonal display can happen anywhere in the three weeks before Easter. Doing it early scores better, and in the last three days it stops being optional.

The fixed rhythm is the starting point, not a straitjacket. Alongside the recurrence rules, Brikx moves with the way your team actually divides up the day: a busy delivery day, building work, a seasonal peak or a colleague off sick.

The score
and the daily report

After the last task the daily report is recorded and emailed: the score, what worked, what did not, and for what reason. As an email, as a PDF, and available in the system whenever you want it.

Every zone gets its own report, covering all the zones beneath it. A shift leader reads their shift, a site manager reads their whole site, a regional manager reads their region. Always the same build-up: a short summary at the top, then the figures you can check it against, then what held the work up with the reason the employee wrote down.

That saves chasing. Instead of ringing each layer separately you see where the outliers are, which blockers are still open, and where your attention should go today. If a zone was still running its day when the report was drawn up, it says so in as many words, so you do not mistake an incomplete total for a finding.

The measure is yours. A task finished late counts for half by default; if that strikes you as too strict or too lenient you set it yourself, and it can differ per zone. A reported blocker counts in full, because somebody who reports a broken till instead of signing the task off has done their job.

Change that rule later and old scores are not quietly recalculated. Last month’s score stays tied to the rules that applied then, so you can move the measure without rewriting your own history.

What is recorded stays recorded. Once a task has been signed off, nobody can change or delete it afterwards. That possibility is not in the product. The page on data sets out exactly what that means, including for us.