Sector stories for UK estates teams.
FM providers need SLA control. Housing and healthcare teams need statutory evidence. Public bodies need explainable automation. AJAEX keeps each workflow traceable without splitting the estate across separate tools.
Examples, not case studies. These scenarios are illustrative patterns, not customer deployments or named references.
Every request, document, and update becomes traceable work.
Demand arrives
Clients, tenants and staff enter through the desk, self service, document upload, or the public API.
Context decides the route
The service, the place, the customer's agreement and permissions decide what happens next. AI suggestions wait for a person.
Work and evidence stay connected
Work tasks, planned maintenance, compliance documents, comments, and status changes stay on one auditable operating model.
Facilities Management
Reactive repairs, planned maintenance, multi-contract operations.
- Operational pressure
- Every client contract has its own SLA model, service catalogue, contractor rules, and reporting expectation. The margin leak starts when the helpdesk has to remember all of it manually.
- AJAEX response
- AJAEX scopes requests by site, organisation, contract, service and asset, then puts that context on one queue, with its change history (in testing).
What flows in
Tenants and building managers report repairs through self service. Desk agents work the same requests on one queue.
What the product does
Requests are scoped by site, organisation, contract and service. The desk shortlists likely services; the agent confirms. Work stays on one queue. Change history (in testing).
What the example shows
- Contract and site context from intake.
- Designed for one change history across many client estates.
- Helpdesk confirms the route: the platform keeps the record.
Relevant capabilities: Self-Service Portal, Service catalogue, Workflows, Service agreements, Public API.
Illustrative scenario, not a delivered engagement.
UK Public Sector
Citizen and internal requests, AI you can explain, multi-channel updates.
- Operational pressure
- Public bodies need speed without losing defensibility. AI, data residency, change history (in testing), and supplier transparency all have to survive procurement and operational scrutiny.
- AJAEX response
- AJAEX keeps UK-hosted data and a traceable request-to-resolution record, built for teams who have to explain how work was handled.
What flows in
Staff submit through self service. Requests and documents sit on the same controlled record the helpdesk works from.
What the product does
UK-hosted records, change history (in testing), and human confirmation on the desk. Where AI assists later, it stays logged and reviewable, not a black box.
What the example shows
- Clear request history from intake to resolution.
- Human confirmation stays on the desk path.
- UK data residency and audit posture are explicit.
Relevant capabilities: Self-Service Portal, Service catalogue, Governed rules, Service agreements, Document handling.
Illustrative scenario, not a delivered engagement.
Housing & Property
Repairs, cyclical compliance, and void turnaround in one work record.
- Operational pressure
- Repairs, access notes, compliance programmes, contractors, and void stages often sit in different tools. That makes tenant updates slow and statutory evidence hard to assemble.
- AJAEX response
- AJAEX brings tenant requests, property context and compliance work onto one traceable housing record.
What flows in
Tenants report repairs through self service. Compliance documents sit on the same estate record.
What the product does
Tenant and property context travel with the request. Repairs and compliance documents share one estate record, so teams are not reconciling three systems.
What the example shows
- Repairs carry property context from intake.
- Compliance work sits on the same property record.
- Priorities and fix times come from the agreement.
Relevant capabilities: Self-Service Portal, Service catalogue, Workflows, Document compliance, Service agreements.
Illustrative scenario, not a delivered engagement.
Healthcare
Estates helpdesk with compliance context.
- Operational pressure
- A routine estates request can become safety-critical when it touches clinical space, fire systems, or regulated equipment. Context at intake matters.
- AJAEX response
- AJAEX keeps estates requests on one record, with the compliance position of each place beside the work.
What flows in
Clinical and non-clinical staff submit through self service. Compliance documents sit on the estate record beside the work.
What the product does
Requests carry the place and the service, and the compliance position of the place sits beside the work. Evidence stays available for review, without claiming automatic clinical escalation.
What the example shows
- Site and asset context are available at intake.
- The compliance position of each site is visible to the desk.
- Uploaded documents are read by AI and checked by a person.
Relevant capabilities: Self-Service Portal, Service catalogue, Workflows, Document handling.
Illustrative scenario, not a delivered engagement.
Education
Campus helpdesk, multi-site compliance, MAT-wide visibility.
- Operational pressure
- Schools, colleges, universities, and trusts need building-level control without losing estate-wide visibility. Fire, asbestos, legionella, and electrical work cannot live in side spreadsheets.
- AJAEX response
- AJAEX gives staff a scoped request portal and estates teams one queue across the campus estate.
What flows in
Staff and students raise requests through self service. Estates teams see one queue; compliance stays on the estate record.
What the product does
Staff raise requests through self service. Estates teams work one queue across sites. The compliance position of each building sits on the same estate record, not a side spreadsheet.
What the example shows
- Requests are scoped and queued for the estates team.
- One queue across sites, not a spreadsheet per school.
- Each site's compliance position stays visible to estates teams.
Relevant capabilities: Self-Service Portal, Service catalogue, Workflows, Configurable forms, Document compliance.
Illustrative scenario, not a delivered engagement.
Regulated Mid-Market
Audit, change control, and configurable process without legacy IWMS drag.
- Operational pressure
- Operational teams outgrow spreadsheets, but legacy IWMS projects are slow, expensive, and hard to adapt once the process changes.
- AJAEX response
- AJAEX gives teams configurable records and workflows, with change history (in testing), without forcing every small process change back through engineering.
What flows in
Operational requests, assets and evidence arrive through the desk, self service and document upload, onto one controlled record.
What the product does
Configurable records, workflows and permissions on the Engine, so process changes do not always wait on a development project.
What the example shows
- Configuration without a project for every small change.
- Revisions kept on every record.
- Pricing based on sites and modules, not per-user sprawl.
Relevant capabilities: Configurable records, Workflows, Governed rules, Report builder, Change history (in testing).
Illustrative scenario, not a delivered engagement.
See how the platform adapts to your operation.
Book a 30-minute demo and we will walk through the ingestion, routing, compliance, and facilities capabilities most relevant to your sector.
Everything above is illustrative, not a named customer case study.