CLRD

MULTI TEAM OPERATIONS

One DNO compliance backbone
across every branch.

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.

Book a demo Sign up

THE PROBLEM AT SCALE

Every branch invents its own compliance process.

Branch A uses one template, branch B uses another, the South West team prefers a different SLD format, and head office has no consistent way to see how many packs went out last month, by whom, for which DNO, with what error rate. When a DNO audit lands, the evidence is scattered across spreadsheets, inboxes and someone's hard drive.

At multi team scale, the cost of compliance variance compounds into rework, missed energisations and reputational risk.

Admin · DNO directoryLive
CLRD admin DNO directory: every UK DNO with its market ID, contacts and job counts, across the whole operationEnlarge

WHAT YOU GET OUT OF IT

Governance at the group level.
Autonomy at the team level.

Standardise the workflow across every team, while still letting each branch run its own jobs.

Standardise without homogenising

One enforced compliance workflow, applied across every team and branch, with team scoped pipelines so branches still see their own work.

Make the operation legible

Group level reporting on throughput, route mix, DNO breakdown and rejection rates. Head office finally sees the whole picture.

Make audits boring

Every submission, every change, every export, audit stamped per team. When a DNO query lands, the answer is one click, not a week of digging.

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

Designed for installer groups running compliance as infrastructure.

01

200 packs per month

Sized for multi team operations doing 45 to 50 submissions a week sustained across the group.

02

Multi team usage

Teams, branches and departments as first class entities. Team scoped pipelines, group level oversight.

03

Group + team reporting

Throughput, route mix, DNO breakdown and submission status, by team and rolled up to the group.

04

Audit log with checksums

Every action stamped per team, per user, with cryptographic checksums on exported packs. Defensible at audit.

05

Custom branding per group

Group wide branding on exported packs, with optional team level overrides where the operation demands it.

06

Included API access

Programmatic job creation, status sync, pack retrieval and webhooks, account wide across every team.

07

Enterprise onboarding

Structured rollout: account architecture, template build per team, API wiring, training, pilot, go live.

08

Enterprise support structure

Named account contact, escalation path, defined response SLAs, periodic account reviews.

09

Role based access control

Group and team scoped roles, so each person sees only the work their role allows, across every team and branch.

THE PLAN

Ready when you are. Curious? Look first.

Pick the plan, or take a closer look at the product before you commit. No signup needed.

MULTI TEAM OPERATIONS

£379/ month

200 packs / month · multi team · enterprise support

For installer operators running multiple teams, branches or departments, where compliance needs to be standardised across the group without losing per team autonomy.

Sign up See all plans

First pack free · No card to start

What's included

  • ✓200 submission packs per month
  • ✓Multi team usage with team scoped pipelines
  • ✓Group + team reporting
  • ✓Audit log with checksums
  • ✓Custom branding (group wide, optional per team)
  • ✓Included API access and webhooks
  • ✓Role based access control
  • ✓Enterprise onboarding
  • ✓Named account contact and priority SLA
  • ✓Quarterly account reviews
  • ✓Annual billing available (~17% cheaper than monthly)

FAQ

Common questions, answered.

How are teams modelled?
Teams are first class entities under a group account. Users belong to one or more teams; jobs belong to a team; reporting rolls up cleanly from team to group. Branches, regions, departments, framework lots, model whichever maps to your operation.
Can different teams have different DNO mixes and templates?
Yes. Team scoped templates, team scoped pipelines and team level reporting. Each team runs its own work; the group sees the whole picture.
What does 'audit log with checksums' actually mean?
Every state change on a job, every export, and every regenerated pack is recorded with timestamp, user, team and a cryptographic hash of the output. If a DNO asks 'what did you send us on this job', the answer is provable.
How is access controlled across teams?
Role based access control, scoped by team and branch. Each person sees only the work their role allows, group admins get oversight across everything, and access maps to your team and branch structure.
What's the onboarding model at this tier?
Structured: a discovery session, account and team architecture, template build per team, API integration if needed, training, a pilot team go live, then phased rollout across remaining teams. Typically four to eight weeks end to end.
What happens if a team needs to burst over the cap?
Burst usage above 200/month is accommodated. If burst becomes the new normal, Custom moves you to a volume that fits and resets the commercial shape around it.
Is there a free trial or pilot?
Yes, matched to your scale. We size a trial to your operation so your teams can run real jobs and see CLRD properly before committing. We scope the right starting point on the first call.
Is data segregated per team?
Yes. Team scoped access controls and reporting boundaries are enforced at the data layer as well as the UI.

Make compliance the same across every team.

We'll walk through an enterprise architecture for your group on a working call, with real teams and real volumes.

Book a demo