Reporting for portfolio-based education · Now onboarding pilot institutions

The reporting layer your portfolio system should have shipped with.

Deighta sits on top of the tools you already use, starting with PebblePad, and extending to API-based systems like TargetConnect and Studiosity. Secure, UK-hosted, and quietly doing the transformation, dashboards, and engagement flags your team has been asking for.

~4 weeks from kick-off to live
UK-hosted GDPR-compliant · DPIA-supportive
Hourly automatic data refresh
northfield.deighta.app /overview
Students tracked
722
Live · 3 cohorts · 11 tutors
Submissions · 7d
312
Check-in recommended
41
+14 this week · pattern-based
The gap · starting with PebblePad

PebblePad holds the data. We make it readable.

We chose PebblePad as our first integration because it's the reflective-practice backbone of dozens of UK HEIs, and because the last mile, turning exported data into something a programme team can read at a glance, is exactly the job we're built for.

01
From CSV to clarity
Exported data arrives as structured CSVs, great for portability but not for reading. We translate those files into live dashboards, refreshed on a schedule you set. No more stale manual reports.
02
Every workbook, absorbed
Because PebblePad is flexible by design, every institution's workbooks are configured differently. We map your specific structure into a standard schema once, during onboarding, then maintain it quietly.
03
Humans, not spreadsheets
Native exports come out wide, with cryptic column headers and binary-coded fields that only make sense to the person who built the workbook. We turn those into human-readable dashboards that a busy tutor can scan in seconds.
What Deighta does

A reporting layer built for how HEIs actually work.

Not a generic BI tool with a PebblePad skin on. A domain-specific transformation layer and dashboard suite, shaped by real programme operations.

Whether your data comes by file or API.
For PebblePad, it's a secure drop zone for structured exports. For TargetConnect and Studiosity, it's a live API connection. Either way: UK-hosted, tenant-isolated, audit-logged, and all of it hidden from your dashboards' end users.
Transformation logic you don't maintain.
Every PebblePad configuration is different. We build a bespoke mapping once, during onboarding. After that, the pipeline just runs.
Auto-refreshed hourly.
Upload exports on your schedule. Dashboards update in the background.
Check-in recommendations.
Pattern-based flags designed around support, not surveillance. Tutors see who might benefit from an early conversation, not a risk score.
Terminology baked in.
"Lower engagement" not "at risk". "Check-in recommended" not "alert". Your governance framework is literally coded into the product.
Role-based tutor views with row-level security.
Tutors see only their tutees. Programme leads see cohort views. Strategic leadership gets KPIs and demographic splits. No one sees more than they should.
On the horizon: qualitative insight.
Reflection entries and case reports are rich but unstructured. We're researching how to surface themes and patterns responsibly, with bias testing and tutor oversight at the centre. Not shipping yet, and not until we're confident it helps rather than harms. Early design partners welcome.
Systems we plug into

PebblePad first. More as we go.

Deighta is designed as a reporting layer that absorbs the awkwardness of whatever portfolio, engagement, or learning-support system you already use. Some we talk to via API; others via structured file exports. The end result looks the same: a clean, trusted dashboard layer.

Available now · Flagship
PebblePad
CSV export pipeline · Bespoke transformation per workbook
Portfolio workbooks, SRAs, case reports, placement reflections, capability frameworks. Whatever structure your institution has built, we absorb it during onboarding and maintain it thereafter, so your programme teams never have to think about the shape of an export again.
● Available now
TargetConnect
Live API connection
Careers and employability engagement data, linked through to programme and cohort views. Lower-friction integration because the API is well-behaved.
● Available now
Studiosity
Live API connection
Writing-support engagement data. Useful for understanding which students use academic support services, and correlating with outcomes.
On the roadmap
More to come
Mahara · OneFile · Canvas
Use any of these? Become a design partner for the next integration. Pilot institutions get preferential pricing and direct influence over the data model.
Bring your own
Something else?
Custom integration · Scoped in discovery
If your system exports structured files or has an API, we can probably absorb it. We'll confirm in the discovery call, and price the integration into your setup fee.
Under the hood

Four steps, then it just works.

Designed to be boring to operate. Once the pipeline is set up and signed off, your role is to drop files in and read the output.

01 / INGEST
Data flows in
Exports from systems like PebblePad land in your secure workspace. API-based sources like TargetConnect and Studiosity connect automatically on a schedule.
02 / TRANSFORM
We clean & structure
Our bespoke transformation layer maps your workbooks into a standard schema. Handles quirks, missing fields, encoding issues.
03 / MODEL
Dashboards refresh
Dashboards update automatically. Engagement bands, check-in recommendations, and cohort views all regenerate in the background.
04 / ACT
Your team acts
Tutors reach out. Programme leads plan. Strategic leadership reports. All from a single, trusted source.
See it in motion

Three short videos, no sales pitch.

The fastest way to understand what Deighta does is to watch the product do it. Each clip is under three minutes.

Pipeline
From CSV chaos to clean data.
How Deighta ingests exports and standardises them.
01:48
Engagement
Check-in recommendations, explained.
The logic, safeguards, and governance behind flagging.
02:52
Onboarding

A proper set-up, not a scramble.

We use an onboarding model borrowed from clinical eCOA deployments: a one-time set-up with a proper spec, then a predictable monthly service. Setup fees are fixed; there are no surprise invoices for dashboards you didn't ask for.

01
Discovery call
30 MIN · FREE
02
Requirements workshop
½ DAY
03
Data Transfer Spec
SIGNED OFF
04
Functional Spec
WIREFRAMED
05
Build sprint
2–4 WEEKS
06
Go-live & handover
ONGOING
Security & governance

Built to pass a DPIA.

Student data is the whole job. Deighta is UK-hosted, tenant-isolated, audit-logged, and designed so your data protection officer can trace every byte. Our privacy framework was shaped directly by the student-data ethics work done at pilot HEIs.

UK-hosted GDPR-compliant UK GDPR Encryption at rest Encryption in transit Tenant isolation Role-based access Row-level security Pseudonymised by default Audit logging DPIA support
Let's talk

Tell us about your workbooks.

Book a 30-minute discovery call. We'll ask about your PebblePad setup, the questions your team can't currently answer, and the constraints you're working within. No pitch, no sales funnel.

Free discovery call, lasting around 30 minutes.
You'll leave with a written scope estimate, whether you proceed or not.
We work with UK HEIs using PebblePad for portfolio-based programmes.

By sending this, you consent to Clemfield Digital contacting you once. No list, no drip, no nonsense.
FAQ

Questions we keep getting.

Does this only work with PebblePad?
PebblePad is our flagship integration because that's where we've seen the most acute reporting gap, but Deighta is designed as a portfolio-and-engagement reporting layer, not a PebblePad tool. We also support live API connections to TargetConnect and Studiosity today, and Mahara, OneFile, and other systems are on the near-term roadmap. If you've got a system that exports structured files or has a decent API, there's a path for it.
How long does setup actually take?
Typically 4 to 6 weeks end-to-end, from signed Statement of Work to dashboards live with real users. Discovery and spec phases take 1 to 2 weeks, the build itself 2 to 4 weeks depending on workbook complexity, with a week for UAT and training. API-based integrations like TargetConnect and Studiosity are faster because we skip the transformation-mapping work.
What does the admin on our side need to do?
For API integrations, effectively nothing after initial setup: the connection runs automatically. For PebblePad, the designated admin runs a scheduled set of exports on an agreed cadence (typically weekly) and drops the files into your Deighta workspace. We provide a short video, a one-page SOP, and a structured folder template. Most admins find it faster than their current reporting process.
What if our workbooks or configurations change mid-year?
Small changes (added fields, renamed columns) are absorbed without contract changes, we just update the transformation profile. Major structural changes (new workbooks, fundamentally new logic) are handled as change requests with fixed-scope quotes. Nothing is ever "we'll figure out the cost later".
What data actually leaves our institution?
Only what your designated integrations send: for PebblePad, only the CSV exports your admin chooses to upload; for API integrations, only the fields and records the scope agreement covers. We don't connect to your student system, we don't pull data we haven't agreed to, and every transfer is logged. You can revoke access at any time.
Can we get row-level security so tutors only see their tutees?
Yes, and it's the default. Tutor accounts are scoped to their tutee list. Programme leads see their programme. Strategic leadership sees aggregated views. Row-level security is enforced at the database layer, not just the UI, so it's not bypassable.
Is it built on Power BI, or is it a custom product?
Both, depending on the view. We use Power BI embedded (app-owns-data) where it earns its place, and custom React dashboards where we need to go beyond what BI tools can do comfortably, particularly for the engagement recommendations and future qualitative-insight features. Clients see a single branded product; we make the architecture decisions behind the scenes.
How is this priced?
A one-time setup fee, scoped against your data sources and complexity, plus a monthly SaaS subscription that covers hosting, maintenance, minor iterations, and support. API-based integrations are typically cheaper than file-based ones because there's less bespoke transformation work. We share detailed pricing during the discovery call once we understand your specific scope.