Complex information
Because accessibility and accountability obligations that apply to every page and every form, this one compounds rather than staying still.
Education, public and social impact / Institutions
Digital systems for public utility authority businesses
For a public utility authority, most of the work sits between the systems. Operloom designs that layer deliberately, builds it, connects it and documents who owns what.
Large enterpriseInstitutionsScheduled workOnline payment
What earns the work is transparency, accessibility and services that work without help. What loses it is a system that cannot keep up with the interest it creates.
Primary conversion: Application, service request, registration, donation, membership or stakeholder enquiry
01Enterprise
The business reality
Before any of this is a technology question, it is an operating question. These are the conditions a public utility authority works inside, and the ones the build has to answer.
Inaccessible journeys
Fixing it is rarely a tooling decision. It is a question of where the work is supposed to stop and who picks it up next.
Manual forms
It lands on the digital director / communications director / CIO first, well before it shows up in any number.
Departmental silos
Left alone it becomes a reporting problem too: the record of what happened gets assembled afterwards, from memory.
Weak service measurement
The cost is rarely dramatic. It is a small amount of lost time and lost context on every service request, repeated all year.
02Enterprise
Target architecture
This is the shape the system takes for a public utility authority. The connections matter more than the boxes: most of the failures happen between systems rather than inside them.
- 01Discovery
Where a resident first finds the business.
- 02Website
The pages a resident reads before deciding to make contact.
- 03Forms
Qualifying questions asked once, at the point of enquiry.
- 04CRM
Every resident, every service request and who owns it.
- 05Calendar
Real availability for a service request, with the preparation time it needs.
- 06Invoicing
Estimates and invoices raised from the agreed scope.
- 07Payments
Payment taken and reconciled against the record.
- 08Email
Operational and lifecycle messages that arrive and are logged.
- 09Automation
The rules that move work between systems, with human review where it matters.
- 10Portal
What a resident can see and do without contacting anyone.
- 11Advertising
Campaigns tracked through to the record they produced.
- 12Analytics
The measures a public utility authority is actually run on.
- 13Internal alerts
Who is told, when, and what they are expected to do about it.
03Enterprise
CRM architecture, identity and permissions
The CRM and customer data platform holds citizens, members, donors, partners, applicants, stakeholders, cases and engagement history. Configured around how the work is actually run, rather than around the default pipeline the platform ships with.
Records
No duplicates, and no separate spreadsheet holding the version people actually trust.
Lifecycle
The stages a resident actually moves through here, named the way the team already names them.
Pipeline
Open service requests with a realistic value and a next action, so the forecast means something.
Lead source
Source captured on the first touch, because reconstructing it later is guesswork.
Ownership
One accountable owner at every stage. Unowned records are treated as a fault, not a backlog.
Tasks and follow up
Follow up scheduled when the service request is created, not when someone remembers.
Reporting
Reporting out of the working system, so the numbers and the work cannot disagree.
Permissions
Role-based access, reviewed when people join and when they leave.
04Enterprise
Customer and service journeys
This is the route a resident takes. Each step is a place where the system either holds the context or drops it.
- 01
Discovery
A resident finds the business from the public, members and partner organisations at once.
- 02
Evaluation
They check whether this is the right organisation for them. This is what transparency, accessibility and services that work without help is for.
- 03
Enquiry
They send an application or service request. The form asks the questions that decide whether it can be scoped, and nothing else.
- 04
Qualification
The application or service request is routed and qualified against the criteria that actually predict a good service request.
- 05
Onboarding
The resident is set up with access, expectations and a first result worth having.
- 06
Delivery
The service request is delivered. What happened is recorded against the resident, not in a separate note.
- 07
Invoice
An invoice is raised from the same record, so what was agreed and what was billed cannot drift apart.
- 08
Renewal
Renewal is worked before it is due, from usage rather than from the date alone.
05Enterprise
Digital estate and component governance
What the site has to do here is specific: accessible institutional information and digital service platform, structured so a resident can get from arriving to application, service request, registration, donation, membership or stakeholder enquiry without a detour.
ServicesProgrammesDepartmentsLocationsResourcesFormsEventsConsultationsPublications and portals
06Enterprise
Automation
These are the workflows that carry the repeatable parts of a service request. Every one of them has a human review point, because the useful automations are the ones people trust.
01Enquiry capture and routing
TriggerA resident submits an application or service request on any page of the site
ConditionsThe submission passes validation and spam checks, and carries the page, campaign and referral it came from
ActionsCreate or match the resident record, attach the source, apply the qualifying answers, assign an owner and start the response clock
Human reviewA person reads every application or service request before it is answered. Routing decides who, not what they say
DestinationCRM and customer data platform, with an internal notification to the assigned owner
Why it helpsNo application or service request sits unowned, and the source that produced it survives into the reporting
02Response and follow up
TriggerAn application or service request has been owned for longer than the agreed response window
ConditionsNo reply has been logged and the record is still open
ActionsEscalate to a second owner, raise a task and flag it on the daily view
Human reviewEscalation notifies a person. It never sends anything to the resident on its own
DestinationTask queue and internal alert
Why it helpsSlow replies surface the same day rather than at the end of the month
03Reporting refresh
TriggerThe reporting period rolls over
ConditionsSource data has loaded and reconciled
ActionsRefresh the dashboard, recalculate the measures that matter to a public utility authority, and flag anything that moved beyond its usual range
Human reviewCommentary is written by a person. The numbers are not
DestinationDashboard and scheduled summary
Why it helpsThe same numbers every time, assembled the same way, so a change means something
04Confirmation and reminder sequence
TriggerA appointment is booked or rescheduled
ConditionsThe resident has a valid contact method and has not opted out of operational messages
ActionsSend confirmation immediately, then reminders on the schedule this kind of appointment needs, each with reschedule and cancel links
Human reviewTemplates are approved once. Individual sends are automatic
DestinationEmail and messaging, logged against the resident record
Why it helpsFewer missed appointments, and a cancellation that arrives early enough for the slot to be refilled
05Payment and receipt
TriggerA payment succeeds or fails
ConditionsThe payment is matched to an open service request or order
ActionsUpdate the status, issue the receipt, release the next step and raise a task on failure
Human reviewFailed payments are worked by a person, not retried silently
DestinationPayment platform, finance system and CRM and customer data platform
Why it helpsPayment status is on the record rather than in a separate inbox
06Quote to invoice
TriggerA quote is approved by the resident
ConditionsScope and price are agreed and recorded on the service request
ActionsRaise the invoice from the agreed scope, set the payment terms, send it and track its status against the same record
Human reviewAnything outside the standard scope or discount range goes to a person first
DestinationFinance system and CRM and customer data platform
Why it helpsWhat was agreed and what was billed stay the same document
07Review request
TriggerA service request is marked complete
ConditionsThe service request completed without an open complaint, and the resident has not been asked recently
ActionsWait the interval that suits this kind of work, then send a single request with a direct link
Human reviewSuppression rules are set by a person and applied automatically
DestinationReview platform and resident record
Why it helpsReviews are requested consistently rather than when somebody remembers
07Enterprise
Integration surface
The categories this operating model usually has to connect. Naming a category is not a claim of partnership, certification or reseller status.
Case systemsCRMPaymentsDocumentsIdentityEmailAnalytics and data platforms
08Enterprise
Data platform and analytics
Reporting is built around the decisions the business actually makes. For a public utility authority that is a short list, which is the point.
Service use
Measured from the record rather than reconstructed at month end.
Applications
Broken down by source, so the number leads somewhere.
Registrations
Tracked as a trend, because a single period rarely means anything.
Engagement
Defined once and written down, so it means the same thing next quarter.
Accessibility and campaign outcomes
Reviewed alongside the stage it depends on, not in isolation.
09Enterprise
Email and communication
Email only works when it arrives. Authentication and list hygiene come before anything creative, because a message in spam is worse than no message.
Service updatesStakeholder communicationCampaignsAlerts and newsletters
10Enterprise
Discovery and marketing
Discovery for a public utility authority runs from the public, members and partner organisations at once. The channels below are the ones that follow from that, and nothing is included because it is fashionable.
Technical SEO
The foundations: crawlability, speed, structure and the markup that describes what this business is
Service search
Service, programme, location, publication and question led information architecture
Local search
Location management for campuses, offices, facilities and public services
Content
Answering what a resident needs to know before they will make contact
Social
Public information, research, advocacy, events and community engagement
Paid media
Selective public information, recruitment, fundraising or programme campaigns
Reviews
Feedback, consultation, issue management and institutional trust
Landing pages
Campaign pages built from the same components, so they are fast to ship and consistent to measure
11Enterprise
Quotes, invoicing and payments
Quoting, invoicing and payment are built as one path rather than three tools, because the gaps between them are where revenue goes missing.
Request a quote
A resident asks for pricing with enough detail attached to answer properly.
Approve an estimate
Approval is recorded against the scope it approved.
Pay a deposit
Where a deposit is how the work is committed, it is taken at that point.
Receive an invoice
Raised from the agreed scope, not retyped from it.
Pay online
Without a phone call, and reconciled automatically.
Access receipts
Available to the resident rather than requested from you.
View payment status
Visible on the record, so chasing is informed.
12Enterprise
Booking and scheduling
Scheduling for a public utility authority is where most of the avoidable loss sits. appointments, consultations, facilities, events or service access.
Availability
Read from the real calendar, so double booking is not possible rather than unlikely.
Buffers
Preparation and turnaround built into the slot, because a appointment is not only the time with the resident.
Qualification
The questions that decide whether the slot is right, asked before it is taken.
Reminders
On the interval this kind of work needs, each one carrying a reschedule link.
Rescheduling
A resident can move a appointment without a phone call, which is how you find out early.
Cancellation
A clear policy applied consistently, with the slot released for rebooking.
Routing
To the right person and the right location, using rules rather than judgement.
Time zones
Handled properly wherever the work crosses them.
13Enterprise
What Operloom builds
Scope is decided by what the operating model requires, not by what is available. Core is structural for a public utility authority. Recommended follows shortly after. Optional depends on the year you are having.
19Core services
9Recommended
6Optional
Digital presence
- Website build or redesigncore
Website build or redesign supports public utility authority businesses by helping to improve access to services
- Service and landing pagescore
Service and landing pages supports public utility authority businesses by helping to improve access to services
Revenue operations
- CRM setup and data modelcore
CRM setup and data model supports public utility authority businesses by helping to improve access to services
- Pipeline and lifecycle designcore
Pipeline and lifecycle design supports public utility authority businesses by helping to improve access to services
- Lead routing, scoring and follow upoptional
- Email infrastructure and deliverabilitycore
Email infrastructure and deliverability supports public utility authority businesses by helping to improve access to services
- Email campaigns, nurture and reminderscore
Email campaigns, nurture and reminders supports public utility authority businesses by helping to improve access to services
Measurement
- Analytics and conversion trackingcore
Analytics and conversion tracking supports public utility authority businesses by helping to improve access to services
- Dashboards and attributioncore
Dashboards and attribution supports public utility authority businesses by helping to improve access to services
Customer experience
- Client, patient or customer portalcore
Client, patient or customer portal supports public utility authority businesses by helping to improve access to services
- Help desk and service workflowscore
Help desk and service workflows supports public utility authority businesses by helping to improve access to services
- Live chat, WhatsApp and messagingrecommended
Technology
- Platform integrations and APIscore
Platform integrations and APIs supports public utility authority businesses by helping to improve access to services
- Security, privacy and maintenancecore
Security, privacy and maintenance supports public utility authority businesses by helping to improve access to services
Scale
- Multi location and franchise managementcore
Multi location and franchise management supports public utility authority businesses by helping to improve access to services
- Enterprise governance and data architecturecore
Enterprise governance and data architecture supports public utility authority businesses by helping to improve access to services
Brand
- Brand identity systemcore
Brand identity system supports public utility authority businesses by helping to improve access to services
- Sales and marketing materialsrecommended
Discovery
- Technical and on page SEOcore
Technical and on page SEO supports public utility authority businesses by helping to improve access to services
- Local SEO and Google Business Profileoptional
Content
- Content strategy and copywritingcore
Content strategy and copywriting supports public utility authority businesses by helping to improve access to services
Operations
- Documents, forms and e signaturecore
Documents, forms and e signature supports public utility authority businesses by helping to improve access to services
- Booking and appointment systemrecommended
Automation
- Workflow automationcore
Workflow automation supports public utility authority businesses by helping to improve access to services
- Practical AI assistants and workflowsrecommended
Social
- Social profile setuprecommended
- Social media operationsrecommended
Acquisition
- Paid search campaignsrecommended
- Paid social campaignsoptional
Commerce
- Online payments and depositsrecommended
- Memberships and subscriptionsoptional
Finance operations
- Quotes, estimates and invoicingoptional
Trust
- Reviews and reputation managementoptional
Events
- Event, ticketing and registration systemrecommended
14Enterprise
Where better systems change something
The honest claim is narrow: a well built system makes certain failures much less likely and makes the rest visible. For a public utility authority the areas below are where that shows up first, each with the measure that would prove it.
Customer experience
Giving residents the confirmations, reminders and status information they would otherwise have to ask for.
Measure: Service useRetention
Making the second service request as deliberate as the first, rather than leaving it to whoever remembers.
Measure: ApplicationsOperational control
Being able to change how the work runs without needing the person who originally set it up.
Measure: RegistrationsRevenue visibility
Knowing what is committed, what is quoted and what is at risk, without rebuilding the picture by hand each month.
Measure: EngagementConversion
Removing the steps between interest and a committed service request, and making the next action obvious at every point.
Measure: Accessibility and campaign outcomesAdministrative efficiency
Taking the repeatable parts of the service request out of somebody's head and putting them into a workflow that runs whether or not it is a busy week.
Measure: Service use15Enterprise
How Operloom works
- 01
Assess
Mapping the real process, which is rarely the documented one, and pricing what the gaps cost.
- 02
Design
How an application or service request should become a service request, agreed and written down before anything is configured.
- 03
Implement
Delivered in stages that each stand up on their own, rather than one launch that has to go perfectly.
- 04
Connect
Integrate the platforms so Case systems, CRM, payments, documents, identity, email, analytics and data platforms behave as one system.
- 05
Document
Documentation aimed at whoever runs this next year, which may not be whoever commissioned it.
- 06
Measure
Tracking, dashboards and definitions, so the effect is checkable rather than asserted.
- 07
Improve
A review cadence with a short list of changes, run against the same measures each time.
16Enterprise
Deliverables and operational ownership
Concrete deliverables, not projected commercial results. What each one achieves depends on how it is used after handover.
Accessible institutional information and digital service platformBrand and component system as requiredCRM and customer data platform configuration, pipeline and field definitionsBooking workflows, availability rules and reminder sequencesQuote and invoice templates linked to the recordPayment configuration and reconciliationAuthenticated email setup and lifecycle templatesAutomation workflows with documented review pointsTracking plan, event taxonomy and dashboardsSelf service area scoped to what is genuinely usefulIntegration configuration and failure handlingDocumentation, workflow maps and handover trainingLaunch support and an agreed review cadence
17Enterprise
Recommended package
Recommended starting scope
Institutional Digital Service and Engagement
A starting scope rather than a fixed package. The plan page sets out who it is for, the core deliverables, the modules, the integrations and the measures.
Core measures
- Service use
- Applications
- Registrations
- Engagement
- Accessibility and campaign outcomes
Custom scope
Scope varies with what already exists, so we do not publish a figure. Tell us what you have and you will get a scoped proposal with the assumptions written down.
- Support level
- Agreed per engagement
- Contract term
- Agreed per engagement
- Implementation
- Agreed after scoping
18Enterprise
Governance, security and accessibility
Accessibility, public records, privacy, procurement, safeguarding and governance obligations.
That is a factual summary of the areas that tend to apply, not advice. Requirements vary by jurisdiction and change. We build to what your advisers confirm applies, and we implement it properly: consent capture, retention, access control, audit trails and secure handling.
19Enterprise
Frequently asked questions
Question: How long does an implementation take?
Operloom replies:
It depends on how much already exists and how clean it is. A build is sequenced so that something useful goes live early rather than everything landing at once: the CRM and customer data platform and application or service request capture first, because that is where work is lost today, then the site, then the automation, then reporting. We give a timeline after a scoping conversation, not before one.
Question: Can we keep the website and CRM we already have?
Operloom replies:
Often, yes, and it usually makes the project smaller. A maintainable site is better connected than replaced: application or service request capture that carries its source, tracking that survives, and a clean handover into the CRM and customer data platform. The CRM question is whether it can hold citizens, members, donors, partners, applicants, stakeholders, cases and engagement history without being fought. If it can, we configure it properly. If it cannot, we say so and explain what migrating would actually cost you in time and disruption.
Question: How does booking connect to everything else?
Operloom replies:
Availability comes from the real calendar, not a copy of it, so a service request cannot be booked into a slot that is already gone. Appointments, consultations, facilities, events or service access. Every booking writes back to the resident record, so the diary and the pipeline are the same story.
Question: How do you handle the regulatory side?
Operloom replies:
Carefully, and within our lane. Accessibility, public records, privacy, procurement, safeguarding and governance obligations. We build to what your advisers tell us applies: consent capture, retention rules, access control, audit trails and secure handling. We implement requirements. We do not interpret them for you, and we will say so rather than guess.
Question: What happens after launch?
Operloom replies:
You get the documentation, the workflow map and the training, because the point is that you own it. Ongoing support is a separate arrangement rather than an assumption: some businesses take a maintenance and improvement retainer, others take the handover and run it themselves. Both are fine, and we will tell you which one we think fits.
Question: What does Operloom actually build for a public utility authority?
Operloom replies:
The scope starts from how this kind of business runs rather than from a package. In practice that means accessible institutional information and digital service platform, a CRM and customer data platform holding citizens, members, donors, partners, applicants, stakeholders, cases and engagement history, and the booking and follow up around it. The nearest starting point in our catalogue is Institutional Digital Service and Engagement, which is a scope to argue with rather than a fixed list.
Question: What do you need from us?
Operloom replies:
Less than most people expect, but not nothing. Access to the platforms, a decision maker who can settle scope questions in the same week they are asked, and someone who knows how the work really runs, which is rarely the same as how it is written down. Content and assets where you have them. We write what you do not.
Question: How does this work across several brands, markets and teams?
Operloom replies:
Through a shared data model and explicit ownership rather than a single template imposed on everyone. Common definitions, governed components and one measurement layer, with local teams able to move inside agreed boundaries. Accessibility, security and documentation are part of the build rather than a later phase.
Start with the part that is losing work today
The first conversation is a scoping one: what exists, what it costs to run, and what would have to be true for application, service request, registration, donation, membership or stakeholder enquiry to happen more often. No obligation and no prepared deck.