Skip to content
ActualCo logo
Actual Core logo

Physical operations — configurable

One operational record for physical operations.

Actual Core connects assets, maintenance, vendors, compliance, approvals, incidents and evidence into one record across every site.

Experience Actual Core
Patchwork to configured operational record. Fragmented inputs (Assets, Maintenance, Vendors, Compliance, Approvals, Incidents & evidence) become One configured operational record.

Patchwork to configured operational record

AssetsMaintenanceVendorsComplianceApprovalsIncidents & evidence

One configured operational record

Assets, maintenance, vendors, compliance, approvals, incidents and evidence aligned in one record.

CaptureAssignTrackEvidenceLearn

Actual Core

Built for operations where the work is physical, distributed and hard to reconstruct.

Actual Core is for operating environments that do not fit a standard named vertical but still need one record for the work that shapes experience.

  • Asset-intensive teams

    For organisations managing buildings, equipment, sites, facilities or infrastructure with real maintenance and lifecycle obligations.

  • Multi-site operators

    For teams that need consistent operational control across locations, vendors, people and approval paths.

  • Compliance-heavy environments

    For operations where procedures, inspections, incidents, risks and evidence need to be visible when it matters.

  • Public-facing operations

    For venues, services and environments where operational failure quickly becomes customer, resident, visitor or stakeholder experience.

If your operation depends on assets, vendors, compliance and follow-through, it needs more than disconnected tools.

What’s happening

Your operations are not one workflow. Your tools usually are.

Maintenance sits in a CMMS. Assets in a register. Compliance in documents. Vendors in spreadsheets and inboxes. Approvals wherever the request happened. Each tool may do its job — but when something goes wrong, the question is rarely in one place.

Why it matters

If the answer has to be assembled, the record is broken.

What asset was involved? Who approved the work? Was the vendor compliant? Was there an incident? What evidence exists? If leadership or auditors have to reconstruct it, the operational record is broken.

What’s at stake

What the disconnected record costs

  • Operators chase answers across systems instead of one operational record.
  • Evidence sits in documents and inboxes instead of on the work.
  • Leadership reviews become reconstruction exercises.
  • Operational memory leaves when key people leave.

Point tools versus an operational record

Point tools show fragments. Actual Core connects the context.

A point tool can confirm that an activity happened. Actual Core keeps the operational context, decisions and evidence together.

ToolWhat it shows
A CMMSA job was closed
Actual CoreThe asset history, vendor record, approval trail, procedure, incident context and evidence behind the work
An asset registerWhat exists
Actual CoreHow that asset performs, what it costs, where it fails and what decisions depend on it
A compliance toolDocuments stored
Actual CoreCompliance connected to the operational activity that proves it happened

Actual Core as the guide

Configure the record around your operating layer.

Platform

One record across the operating layer.

Every capability writes to the same operational record, so follow-through does not depend on reconstruction.

  • Assets

    • Register and lifecycle
    • Location and condition
    • Service history
    • Linked to work and incidents

  • Maintenance

    • Work orders
    • Preventive maintenance
    • Audit trail
    • Vendor assignment

  • Vendors

    • Contracts
    • Compliance documents
    • Performance across sites
    • Accountability on every job

  • Compliance

    • Inspections
    • Certifications
    • Checklists
    • Evidenced activity

  • Approvals

    • Quotes and purchases
    • Variations
    • Routed sign-off
    • Full work context

  • Incidents & Evidence

    • Reports and close-outs
    • Photos and documents
    • Sign-offs on the record
    • Linked to assets and vendors

A simple plan

From Experience to first operational record

  1. 1Experience Actual Core against the operating work you need to connect
  2. 2Map the first workflow ActualCo would operationalise
  3. 3Configure signals, records, owners and evidence
  4. 4Stand up stakeholder views and operating rhythm

What we won't ask of you

  • No rip-and-replace of systems that already work.
  • Start with one critical workflow, not a full estate rollout.
  • Configure at the pace your teams can absorb.

What good looks like

What success looks like

The work your existing systems cannot see now sits on a connected record. Operations, executives and partners share one operational record even though no off-the-shelf vertical fits.

  • Configurable record for non-standard environments
  • One operational record across mixed teams
  • Evidence and memory on the work that matters
  • An operational record to scale from

Who Actual Core helps

  • Operations leaders

    Create one operational record for the work that sits between systems, sites and teams.

  • Facilities and asset teams

    Connect assets, maintenance, vendors and evidence without replacing every specialist tool.

  • Compliance and risk owners

    Keep procedures, inspections, incidents and evidence visible when leadership or auditors ask.

  • Executives and service owners

    See whether operational follow-through is protecting the customer, resident, visitor or stakeholder experience.

Next step

Experience Actual Core

Start with the guided Actual Core Experience. We will use it to understand the first operational record you need and the critical workflow to configure around it.

Experience Actual Core