Straight Answers, Before You Ask

Days rather than months. We create your workspace, then guide you through configuring it — your sites, your teams, your forms, your reporting rules. Most organisations run their first real reports within the first week and go live across teams shortly after.

The length depends on how much structure you want in place before people start using it, rather than on technical work at our end. A single site with three checklists is quick. A twelve-site operation with different procedures per location takes longer, because the thinking takes longer.

Bring what you already use — your existing forms, checklists, incident templates and reporting routines, in whatever state they're in. Spreadsheets and Word documents are fine. You'll also want a rough picture of your organisational structure: sites, departments, teams, and who should see what.

You need no technical preparation and no IT project. If your current process lives in a filing cabinet and a shared drive, that's a normal starting point.

We create your dedicated workspace and guide you through setting it up. You decide how your operation is structured and what your forms contain; we show you how to build it and stay with you while you do.

That arrangement is deliberate. The people who know how your operation runs are inside your organisation, and configuration is a matter of hours rather than a specialist skill. It also means changing something six months from now takes you minutes, rather than a support ticket and a wait.

They become your templates. Everything you use now is rebuilt as digital forms and checklists, keeping the fields, the wording and the logic your teams already recognise. Nobody has to learn a new vocabulary for work they've been doing for years.

Where a form has grown awkward over the years, that's a good moment to simplify it — though the choice stays yours. We adapt the platform to how your operation runs, rather than asking you to adopt someone else's process.

Very little. The mobile app is built so a new starter can file a report on their first shift without instruction — that's the whole design principle. Reporting an incident takes a few taps and speaks their language. When someone gets stuck, the AI assistant answers in plain words from your own material, so a question rarely needs to become a phone call.

Administrators get more: a live session with us covering configuration, permissions and reporting, plus written manuals to keep. They're the people building your forms and setting who sees what, so it's worth the hour.

Thirty days, no credit card, no limits. You get your own dedicated workspace with every module and every feature switched on, holding your own data — the real platform rather than a demo environment.

It works this way because a restricted trial answers the wrong question. You need to know whether this fits your operation, and a version with pieces missing is unable to tell you that.

Then you walk away, and we'd rather find that out during a trial than after a contract. If you decide against continuing, your trial workspace and everything in it is deleted immediately — nothing sits on our servers waiting to be sold back to you later.

You adapt it. That's the core of how we build: the platform fits the organisation rather than the other way around. Your forms, your terminology, your approval routes, your reporting periods, your organisational structure — all configured to match what you already do.

This is the clearest difference between us and the large platforms. They offer configuration within a fixed model designed around someone else's process. We start from yours.

Each part of your organisation gets what belongs to it. A checklist used only at one site stays there. A procedure that differs between your Oslo and Bergen operations exists as two documents, each connected to its own location, with no reconciliation needed.

Group-wide policies work the same way — written once, connected to every site that needs them. And when one location's procedure links to the group policy behind it, both travel together when someone asks a question.

Yes. Each person uses the platform in their own language — menus, labels, buttons, notifications — so a supervisor in Warsaw works in Polish while a manager in Oslo works in Norwegian, inside the same workspace.

We add languages as our clients need them, so if your teams work in a language we've yet to cover, ask us.

Reports stay in the language they were written in. An incident description is evidence, and evidence keeps its original wording.

Security, healthcare, manufacturing, transport, energy, facilities, logistics, retail, construction and hospitality — operations where people work away from a desk, where compliance matters, and where something going wrong has consequences.

What those sectors share is more useful than what separates them: frontline teams who need something simple, managers who need reliable evidence, and regulators who need records. The configuration differs by industry; the underlying need is the same.

It sits in the same platform as your reporting and checklists, so a shift, the people on it and the work completed during it are connected rather than living in separate systems. Planners build schedules from templates, staff see their shifts on their phones, and changes reach people without a phone chain.

The practical benefit is that your reporting knows who was working when — which turns "this keeps happening" into "this keeps happening on this shift".

Yes. Operational analytics pull from every module — incidents, checklists, tasks, shifts — and compare across sites, teams and time periods. Beyond the dashboards, the platform writes scheduled briefings in prose: what happened this period, what changed since last, and what looks worth attention.

Each person sees the part of the organisation they're responsible for, so a site manager gets their site and a group director gets everything.

Three plans, published prices, starting at €195 per month. You pay per workspace rather than per person, so the cost depends on the plan you choose rather than how many people file reports.

Everything in the platform foundation is included in every plan: hosting, updates, security, support, mobile apps, and data migration from whatever you use now. The differences between tiers are the number of administrators and handlers, and whether the AI automation tools are switched on.

No. Unlimited people can file reports, complete checklists and use the mobile apps at no extra cost — including subcontractors and external teams if you want them reporting into your system.

What's counted is your management layer: administrators who configure the platform, and handlers who receive and act on reports. Essentials includes 1 administrator and 5 handlers; Professional and Intelligence include 2 and 20.

This is deliberate. Charging per user punishes exactly the behaviour you want, which is everyone reporting everything.

Yes, and many organisations do. Start with Essentials to get reporting and checklists working, then move to Professional as your management team grows, or to Intelligence when you want the AI tools running.

Your configuration, data and history carry across. Changing plan needs no new setup.

Your data is yours. You can export it in standard formats at any point, and we provide a full handover if you leave.

You do. Your organisation is the data controller; we act as your data processor under a Data Processing Agreement between us. We access and use your operational data solely to deliver the service you're paying for.

It's built to. Personal data is encrypted at field level, access is limited to the people who need it, every view and change is logged, and retention rules remove records on schedule rather than letting them accumulate indefinitely.

With the AI tools switched on, the platform detects personal data automatically — a name typed into a free-text description, a face in a photograph, details that landed somewhere they were never meant to go. That gets flagged as it arrives, so it's handled while it's still one record rather than a discovery you make during an audit.

Anonymisation, applied across the record. When a person is removed, or when their retention period expires, their identifying details are stripped out while the operational record stays intact.

That distinction matters for compliance. The incident still happened, and your safety statistics, audit trail and trend analysis need it. What GDPR requires is that the person stops being identifiable — rather than that the event disappears from your records. Anonymisation satisfies the erasure request and keeps your reporting whole.

Never. Your data stays inside your workspace and is used to deliver your service, full stop. Our models are developed and run on our own infrastructure, and nothing your teams write is used to improve anything used by anyone else.

The reason this can be stated plainly is architectural. There's no external provider in the chain, so there's no third party's terms to read and no setting to check.

Three years from the date each record is created, and longer if your organisation needs it — some sectors have retention obligations that run well beyond that, and it's set in your agreement.

Our privacy policy sets out what we collect, why, and how long we keep it. The Data Processing Agreement covering your organisation's data forms part of your contract, and we're happy to review it with your legal or compliance team before you sign.

Most platforms encrypt the storage — one locked entrance, with open rooms inside. We encrypt each individual field. Names, scores, personal details and other sensitive values are encrypted inside the application before they reach the database, so the database only ever holds ciphertext. Even a direct database snapshot shows encrypted values rather than readable data. It's the difference between protecting the building and protecting every person inside it.

Your data is hosted on secure cloud infrastructure within the European Economic Area, under Norwegian and EU data protection law. Personal data stays inside the EEA unless adequate GDPR safeguards are in place. We can confirm the exact region for your contract before you sign.

Your data stays inside your environment. Every AI model in the platform is developed and run on our own dedicated infrastructure — the assistant, the summaries, the image analysis, the GDPR detection. Nothing is sent to external large language model providers or third parties for processing. The assistant answers only from your own material, and it retains nothing after answering.

This is a design decision rather than a policy promise. There's no external connection for your data to travel down.

Three options, and you choose what suits your organisation: passkeys (FIDO2), an authenticator app with a time-based code, or a password combined with a one-time code. For enterprise identity, we support single sign-on through Google and Microsoft, so platform access follows your existing directory. Removing someone from your directory removes their platform access.

Access is role-based and scoped to your organisational structure — by site, department, team, or however your operation is arranged. Each person sees the material belonging to their part of the organisation, and the AI assistant follows the same boundaries. Two people asking the assistant an identical question can receive different answers, because each answer is built only from what that person is already permitted to open.

Workspace data is isolated at tenant level across every module, so your organisation's data stays separate from every other customer's.

Yes. Every view and every change is logged with a name and a timestamp, and earlier versions can be restored. For particularly sensitive material, you can restrict it to read-on-screen only, with the reader's name displayed across the page. The most regulated material — contracts, salary policies, investigation findings, patient or customer personal data — can go into a separate encrypted area that even the AI is unable to read.

Access belongs to the account rather than the device. Revoke the account and that phone loses access at its next connection — the data lives in your workspace rather than on the handset, so nothing walks away with the phone.

Your data is backed up automatically on a continuous schedule, with monitoring running around the clock. Recovery procedures are tested regularly. Specific recovery time and uptime commitments are set out in your service agreement.

You'd hear from us directly and quickly. As your data processor, we notify you without undue delay so you can meet your own GDPR obligations as controller — which include reporting to your supervisory authority within 72 hours. With a team of three, that call comes from someone who understands what happened, rather than from a ticket queue.

Yes. When your organisation uses the platform, you are the data controller and Unified Analytics AS acts as your data processor, governed by a Data Processing Agreement between our organisations. We use a small number of trusted providers for cloud hosting and message delivery, each under contractual obligations matching our own commitments. The full sub-processor list is available on request and forms part of your agreement.

We're working towards NIS2, the EU standard covering the sectors most of our clients operate in. We chose it deliberately: NIS2 sets requirements for the operational security and incident reporting your organisation is accountable for, which makes it the standard that matters for the work you actually do.

What's already in place: field-level encryption so the database never holds readable personal data, role-based access scoped to your organisation, passkey and MFA sign-in, complete audit logging, and EU hosting under Norwegian and European law.

Ask us for the full security documentation — we'll send it to your IT team.

Yes. Data can be exported in standard formats at any time during your contract, and we provide a full handover at the end of it. Your data belongs to your organisation throughout.