Transformative —
Intelligence from Your Data

What is Transformative?

Transformative is a compliance intelligence platform. It connects to the databases, form systems, and telematics platforms your organisation already uses — and gives you a single place to see, question, and act on all of that data together.

Think of it as the layer that sits above your existing systems. Your route data lives in SQL Server. Your field forms come in via DoForms. Your vehicle GPS streams through Geotab. Transformative ingests all of it, stores a complete bi-temporal history, and puts a powerful analytical interface on top.

You don't need to change anything about how you operate. The platform reads your data as it already exists, tracks every change over time, and lets you interrogate what happened, when it happened, and what's likely to happen next.

Your Dashboard

When you log in, you land on your data source dashboard. Each connected data source appears as a named panel — your fleet management system, your forms data, your telematics feed. Select one to open it.

Once inside a data source, the interface divides into three areas:

Exploring Your Data

Records in the main grid represent the current state of each entity. Clicking a record reveals everything attached to it — not just the fields, but the full connected graph.

Drill-Down Navigation

For data with natural parent-child relationships — routes containing stops, stops with students assigned — the right panel shows a linked hierarchy. Click through from a route to see its stops. From a stop, see which students board there. From a student, see their care needs and medical requirements. Each level loads the next without leaving the page.

The Toolbar

Above the main grid, a compact toolbar gives you three controls that work together:

Asking Questions in Plain English

The AI query bar sits between the toolbar and the data grid. It's the most powerful way to work with your data — type a question or instruction in plain English and the platform figures out exactly what to query, which table to look in, and how to surface the result.

There are three distinct modes. You switch between them using the mode selector on the left of the bar.

Maps and GPS Intelligence

For data sources with geospatial content — vehicle GPS, route stop coordinates, trip logs — Transformative renders an interactive map directly in the right panel when you select a record. No configuration needed; the platform reads latitude, longitude, and sequence information from the registry and draws the map automatically.

Route Maps

Select a route record and the map draws the actual GPS breadcrumb trail for that route — the path vehicles travelled, timestamped at the intervals your telematics system captured. The track is drawn in time order so you can see exactly how the journey unfolded.

Stop Markers

Where a route has planned stop data registered, numbered amber markers are overlaid on the GPS track — each marker showing the stop sequence number and stop name on hover. This lets you compare the planned stop sequence against the actual path travelled at a glance.

Geotab Trip View

For Geotab-connected data sources, selecting a vehicle record shows a trip strip — each trip card displaying start time, end time, distance, and maximum speed. Click any trip card to isolate its GPS track on the map. This lets you drill into a specific journey without losing the context of the full day's activity.

Viewing Your Data at Any Point in Time

One of the most distinctive things about Transformative is that it never overwrites historical data. Every time a record changes in your source system — a route is reassigned, a vehicle changes status, a timesheet is amended — the platform stores both the new version and the old one, with a precise timestamp for each.

This means you can see your operation not just as it is today, but exactly as it was on any date in the past.

The Time Scrubber

At the top of each data source view, a date/time control lets you set the "as at" date. Move it to last Tuesday and every table, every grid, every record refreshes to show the state of your data as it existed on that day. The header shows a persistent amber banner reminding you you're viewing historical state, with a "Return to Present" button.

Version History

Selecting a record and opening the Version History panel shows every version of that record across time — each change listed with its timestamp and the values that changed. This is your complete audit trail, available for every record, with no extra configuration.

Bi-Temporal Gap Detection

Transformative tracks two time dimensions for every record: when it was true in the real world (application time) and when the platform recorded it (system time). When these are significantly different — meaning data arrived late — the gap detection panel flags it. This is particularly useful for compliance: if a record needed to exist on a certain date but was only entered later, the gap is visible and measurable.

Forecasting and Divergence Alerts

The Predict mode in the AI bar doesn't just show you what happened — it projects what's likely to happen next, based on the historical patterns in your data. And once a forecast is running, the platform monitors incoming actuals and alerts you if reality starts to diverge from the projection.

Running a Forecast

Switch the AI bar to Predict mode and type what you want to forecast. The platform identifies the relevant metric, analyses the historical trend, and generates a weekly projection for the period you specify. The forecast is stored against your tenant so you can return to it later.

What-If Scenarios

Scenarios let you model a proposed change to your operation and see what the data would look like if that change had happened — without touching the live record. You're creating a branch of reality that exists alongside your actual data, not instead of it.

A scenario has a branch point — the date from which the hypothetical diverges from history. Everything before the branch point is your real operational data. Everything after is the modelled version.

Creating a Scenario

From the Scenario panel (below the main data grid), create a new scenario and give it a name and hypothesis. Then make the proposed changes — reassigning a route, adding a vehicle, moving a resource. The scenario tracks those changes as a separate set of records branching from your chosen date.

Private and Published

New scenarios are private by default — visible only to you. When you're ready to share the analysis with others in your organisation, you can publish it. Publishing is permanent: a published scenario becomes visible to all authenticated users on your tenant. It cannot be unpublished, which ensures the integrity of any analysis that others have reviewed or relied on.

What Feeds Transformative

Transformative is source-agnostic. It connects to the systems your organisation already runs. The provisioning of a new data source is handled by your platform administrator or reseller — as an end user, you see the data after it's been connected and ingested. This section is a brief overview of the types of sources the platform supports.

How Your Data Is Protected

Transformative is built for regulated industries where personal data carries legal weight. The platform supports GDPR Article 17 (Right to Erasure) and CCPA Right to Delete requirements through a cryptographic approach that is fully compatible with its immutable, bi-temporal data store.

How PII Fields Are Encrypted

When your administrator connects a data source, they can mark individual fields as containing personal information during the field mapping step. Each marked field is assigned a PII category:

Once marked, the raw value of that field is never stored in plain text. Instead, the platform encrypts it with a unique AES-256 key generated specifically for that individual before writing the record into the database. The encrypted value can only be read back by the platform while that key exists. When you view a record in the platform, the decryption is automatic and invisible to you — the field appears exactly as it would otherwise.

The Right to Be Forgotten

When a data subject requests erasure under GDPR Article 17 or CCPA, your administrator processes the request through the Erasure Management section of the Authority. The process works in two stages to protect against accidental or mistaken erasures:

What Happens to Historical Records

The platform's bi-temporal records are never deleted. After a hard purge, the rows still exist in the database — you can see that a student was on a route, that a care recipient had a schedule, that an employee had shifts. The count, the dates, the relationships between records are all intact. Only the personal content of encrypted fields is gone.

In the platform UI, erased fields display as [Data Erased] rather than a blank, making it clear that the value existed but has been legally removed rather than that it was simply empty.

Blocked Re-Introduction

Once an erasure is scheduled (even during the grace period), the platform immediately blocks any attempt to re-ingest data for that individual from a source system. If the source system still holds the record and a poll cycle runs, the row is silently rejected and logged. This log is available to your administrator as proof that re-introduction was actively prevented — relevant documentation for regulatory compliance.

Erasure History & Audit Trail

Every erasure request — scheduled, recovered, or completed — is recorded permanently in an immutable audit log. This log cannot be edited or deleted. It records who requested the erasure, the legal basis, any verification reference provided by the regulator, and when each stage completed. Your administrator can view the full history at any time from the Erasure Management page in the Authority.

Key Concepts

A short reference for the terms you'll encounter across the platform.