MULTI TEAM OPERATIONS
Multiple installer teams, multiple regions, multiple DNO mixes, one set of standards. CLRD becomes the system of record for every DNO application across the whole operation.
THE PROBLEM AT SCALE
Four branches, four ways of producing the same DNO pack. Every variation is somewhere an error can enter, and at this volume errors don't stay small. They become resubmissions, delayed energisations, and jobs standing still while someone works out what was sent, by whom, and under which rule.
Throughput and accuracy are the same problem. Done by hand, going faster only produces mistakes faster.
EnlargeWHAT YOU GET OUT OF IT
Standardise the workflow across every team, while still letting each branch run its own jobs. And batch and multi premise submission automation no other UK platform offers.
One workflow, every team
Job templates codify your standard installs, so the same job produces the same pack whoever runs it and whichever branch they sit in. Each branch sees its own jobs and clients, so local work stays local.
Volume without headcount
Batch and multi premise jobs, CSV bulk import and a full API move work through at programme scale rather than one form at a time. The routing and the documents are generated, not typed.
Provable, not remembered
Every action stamped per team and per user, under the regulation version in force. When a DNO or an auditor asks what was sent and why, the answer is one click.
200
PACKS / MONTH
National throughput across multiple branches.
Group
GOVERNANCE
Team scoped access controls with per job checksums.
Multi
BRANCH ROLLOUT
One workspace, many teams, one source of truth.
WHAT'S IN THE BOX
01
One batch fans out into a standalone job per premises, each with its own site, MPAN and evidence chain, and the shared G98 Form A where the premises form one close geographic region. No other UK platform automates this.
02
Every action attributable to a named user and team, under the regulation version in force, with cryptographic checksums on every exported pack. Who did what, when, and under which rule.
03
A documented REST API covering the full device model: create jobs, read jobs, sites and clients, with signed webhooks and safe retries on every create, account wide across every team.
04
Bring clients and sites in at programme scale, with a preview and analysis of the file before a single record is created. No blind imports.
05
Sized for multi team operations running 45 to 50 submissions a week sustained across the group.
06
The same job produces the same route and the same documents in every branch, derived from the job data and the published rules rather than from local habit.
07
Separate branch teams — or a group of installation companies, each with its own MCS registration — under one account. Each branch runs its own work; head office manages them all.
08
Head office sees every branch's jobs and clients, manages the whole roster from one team page, and can start a job under any branch.
09
Encrypted in transit and at rest, two factor authentication and device sign out, with group and team scoped roles enforced at the data layer as well as the interface.
10
Account architecture, template build per team, API wiring, training, pilot, go live.
11
A dedicated account manager runs your account, with an escalation path, defined response SLAs and periodic account reviews.
12
Each branch files under its own name, accreditation and logo, so every pack looks like it came from the branch that did the work.
THE PLAN
Pick the plan that fits your volume, or we'll set you up on a tailored trial so you can see the difference in your own workflow before committing to anything.
HOW THIS STARTS
At this level how it gets set up matters as much as what it does, so you get a named contact from the first call rather than a support queue.
MULTI TEAM OPERATIONS
£379/ month
200 packs / month · multi team · dedicated support
For installer operators running multiple teams, branches or departments, where compliance needs to be standardised across the group without losing per team autonomy.
First pack free · No card to start
What's included
FAQ
We'll walk through a group architecture on a working call, with real teams and real volumes.