One register
Each risk is written as an event with its causes and impacts. One shared register replaces one spreadsheet per department.
// Pliris Intelligence PlatformRisk Management
Risk management a small team can actually run
Most organizations keep their risks in a spreadsheet that one person understands. Pliris Risk Management gives every risk a home, an owner, a review date, and a place in the report your board or council reads.
Early accessIn development now. Early participants shape the roadmap.
- Low
- Medium
- High
- Extreme
// 01The product
What it does
Impact by category
Rate people, property, environment, service delivery, finances, and reputation on one grid. The score follows the highest impact, so nothing hides inside an average.
A heat map that stays current
Likelihood against consequence, drawn from the register itself. Click a cell to see the risks inside it.
Treatments with a name on them
Every action has an owner, a deliverable, and a due date. Overdue actions reach the owner's inbox and the dashboard.
An acceptance workflow
Owners submit, the risk manager reviews, and the discussion stays on the record. Extreme risks cannot be submitted without a treatment summary.
A timeline of what is due
Review dates, treatment deadlines, and plan renewals on one calendar and one timeline, found automatically from your data.
History that is never deleted
Closing a risk keeps it. Changes are logged with who and when, which is what an auditor will ask for.
Help in plain language
What a risk is and how the process runs, written for staff who were handed this on top of their real job.
// 02Starter packages
Start from a package, not a blank page
The engine is the same for everyone. A starter package loads the categories, scales, roles, dashboards, reports, and help that fit your sector, so day one is reviewing risks instead of configuring software. Everything a package sets up stays editable.
BC Local Government
First packageFor municipalities and regional districts in British Columbia.
- Compliance tracker for the three Emergency and Disaster Management Act documents, each with its own review clock
- Likelihood and consequence scales with rating bands that follow the BC public sector risk guideline
- Six impact categories, hazard categories, and treatment types
- Risk owner, risk manager, and executive roles
- Council report and quarterly risk report templates
- Help topics on the Act and the process, in plain language
1 January 2027
Sign up with this package →From this date the Act asks every BC local authority for a hazard risk assessment, an emergency management plan, and a business continuity plan. Plans written under the old Emergency Program Act do not carry over.
Standard register
IncludedFor any organization that wants a sound register without a sector overlay.
- Strategic, operational, financial, compliance, and hazard categories
- Five by five likelihood and consequence matrix
- Treatments, acceptance workflow, and review dates
- Board report template
Your framework
On requestAlready have a policy, a taxonomy, or a scoring method? We load it as your package.
- Your categories, scales, and rating bands
- Your roles and approval steps
- Your report layouts
The summary of the Act above is not legal advice. Check the Act and regulation for your authority.
// 03The process
How a risk moves
The same five steps every time, with the software keeping the discipline a small team cannot spare a person for.
- 01
Identify
Risk ownerWrite the event, its causes, and its impacts.
- 02
Assess
Risk ownerLikelihood one to five, impact by category. The band is worked out for you.
- 03
Accept
Risk managerReview, ask questions on the record, accept, and set the next review date.
- 04
Treat
Action ownersNamed actions with due dates. Late ones surface on their own.
- 05
Review
EveryoneWhen the review date arrives the risk returns to assessment. Executives read the dashboards.
// 04Reports
Reports that look written, not exported
A board does not want a screenshot of a dashboard. Build a report the way you would lay out a document: choose the paper, add a cover, place charts and tables beside your own words, and print a clean PDF.
- Portrait or landscape, Letter, Legal, or A4, with a running header and page numbers
- A fit check that warns you before a table is too wide for its column
- A reporting period and an as-of date that every chart and table follows
- A table of contents and a sign-off block for the report of record
- Each reader sees only the rows their role allows, on screen and on paper
// 05Trust
Compliance first, for organizations that answer to the public
- Sovereign by design
- The service is designed to run in a Canadian data centre, with your workspace kept separate from every other customer's and your data yours to take out at any time.
- Built around FOIPPA
- Reasonable security, need-to-know access, retained history, and an activity log, so your privacy officer has evidence to point to.
- Roles that mean something
- Risk owners see their own risks. Managers see the register. Executives read. Access is enforced on every screen, export, and printout.
- Sign-in you can defend
- Multi-factor sign-in, account lockout, and single sign-on with your Microsoft 365 tenant.
- Tested like an attacker would
- An adversarial test suite runs against every change, trying to reach another person's records by every door.
- No IT project
- It runs in the browser. Your package arrives set up, and your existing spreadsheet can be imported.
// 06People
Who uses it
Executives and boards
One current picture of what could go wrong, what it would cost, and who is dealing with it.
The risk lead
The register, the reviews, and the board report, without rebuilding them each quarter. Often this is a finance or corporate officer, not a risk manager.
Department owners
A short form, a clear scale, and reminders. Their risks, their actions, nothing else in the way.
// 07Questions
Before you ask
Is this only for BC municipalities?
No. The product is a general risk management platform. BC local government is the first starter package because the Emergency and Disaster Management Act gives those organizations a date to meet.
What exactly is a starter package?
A saved setup: categories, scales, rating bands, roles, dashboards, report templates, and help topics. It is loaded when your workspace is created. After that it is yours to edit.
We already have a spreadsheet. Do we start again?
No. Import it, map the columns once, and carry on.
How many people do we need to run it?
It is designed for an organization where nobody has risk in their job title. Mandatory review dates, overdue reminders, and ready-made reports do the work a risk office would do.
Can we change the scoring?
Yes. Likelihood and consequence scales, the rating bands, and the impact categories are configuration, not code.
When can we use it?
The platform is in development and the early access program is open. Sign up and we will arrange a walkthrough with sample data.
// Early access
See it with sample data
Thirty minutes, a fictional organization, and the questions your board will ask. Early access participants help decide what gets built next.