What runs on nimmy

One connected platform for risk, compliance, regulatory change, projects and workflows. Switch on the modules you need today and add more when you are ready.

How teams use nimmy
Regulatory change
Compliance and obligations
Your own registers
Risk and controls
Projects and programmes
Workflows
Across the organisation
Across every module

Select a module to see what it connects to.

Risk · Controls · Assurance · Issues · Incidents · Actions

Risk and controls

A risk register that shows where each risk sits now, and controls that show whether they are working.

  • Exposure against appetite, from the score and every signal since
  • Indicators with thresholds, bow-ties and treatment decisions
  • Controls read as operating, degraded, failed or not observed
  • Tests signed off by someone other than the tester
  • Assurance by all three lines, with a coverage view
  • Issues from any source, and incidents through to regulatory notification
Obligations · Policies

Compliance and obligations

One register of every requirement the organisation carries, and the policies and controls that cover it.

  • Requirements from law, contracts, licences and your own policies
  • Applicability, owner and coverage for each legal entity
  • Gaps raised as issues, or accepted with a second signature
  • Policies with versions, approval routes and review cycles
  • An existing policy library imported in force
  • A requirement followed when the rule it cites is amended
Queue · Implementation · Calendar · Research · Enforcement · Engagement · Communications · Annotations

Regulatory change

Regulators, standards bodies, courts and legislatures, matched to your business and worked through a team queue from triage to close.

  • One item per change, however many sources report it
  • Applicability decided per entity, with a rationale
  • Redlines between versions of the same document
  • Implementation plans, or a project, from the change itself
  • A calendar of consultation, effective and transition dates
  • Closure on two signatures

Every publication is kept, versioned and searchable in Research. A body that is not yet in the catalogue can be requested.

Projects · Portfolio · Benefits

Projects and programmes

Plans, milestones tied to regulator dates, governance and benefits, for any project from an office move to a multi-year programme.

  • Workstreams, milestones and dependencies, with the critical path on business days
  • Status declared by the manager beside status computed from the plan
  • Milestones anchored to a regulator’s date
  • Risks and issues on the enterprise registers
  • Gates, baselines and change requests Teams and Enterprise
  • Budgets, timesheets, capacity, portfolios and benefits Teams and Enterprise

A regulatory change can be planned as a project from its Plan tab. Plans import from Microsoft Project or a spreadsheet.

Workflows

Workflows

Teams and Enterprise

Approvals, tasks, attestations and notifications across every module, built, tested and versioned.

  • Triggers on records, fields, dates, schedules and scheduled checks
  • A simple builder and a canvas on the same definition
  • Tested against a real record before it is published
  • Separation of duties on every approval
  • Runs act with their author’s permissions, never more
  • An evidence pack for every run, as a PDF

Events from outside and data fetched from your own systems can start or feed a workflow on Enterprise.

Custom registers

Your own registers

Asset registers, records of processing, delegations of authority: registers you build that behave like the built-in ones.

  • Fields from a library, published as versions
  • Links to risks, controls, people, teams and entities
  • Sharing by person, team or role, field by field
  • Forms in your brand, reviewed before a response lands
  • Form links and published views for people outside Teams and Enterprise
  • Imported from a spreadsheet in one step

Across the organisation

Modules for what the organisation does, who it depends on and who answers for it. Each is a register like the others, with owners, a queue of what needs attention, and history.

Operations and critical services

Capabilities, value chains and impact tolerances, read from the health of the controls and risks attached.

Third parties

Tiering, assessments by domain, and concentration across suppliers.

Accountability

Accountable people, prescribed responsibilities, and a record of the steps each person took.

Licences and permits

Every authorisation, its holder and renewal date, with its conditions on the obligation register.

Declarations

Conflicts, gifts, hospitality, outside work and personal trading, decided by someone other than the person declaring.

Complaints

Acknowledgement, response and remediation tracked against your own standards, and recurring causes found.

Product approvals

New products and changes through the gates they need, with a review after launch.

Committees

Meetings, papers, minutes and decisions, with registers as they stood on the day.

Scenario testing

Exercises run and read against the impact tolerance in force at the time.

Model governance

What each model decides, its validation, drift and human oversight.

Training

Requirements by audience, and completions on the current version.

Switch on the modules you need today and add more when you are ready.

Request access

AI that cites its sources

Teams and Enterprise

AI drafts, summarises, extracts obligations, assesses impact and answers questions. Every answer cites the paragraph it came from.

  • Answers grounded in nimmy’s own corpus, never the open web
  • Suggestions shown as suggestions: accept, edit or dismiss
  • Nothing sent, published or written to a register until a person approves it
  • Each function switched on or off by your administrator

Reports

One view over every register and module, filtered, saved and exported.

  • Saved views, shared with colleagues as a link
  • Export to Excel, PDF, Word or CSV
  • Reports scheduled weekly, monthly or quarterly
  • Each register’s history kept daily, for trends and committee packs
  • The audit trail, reportable and exportable like everything else

Integrations

Send work to the systems your teams already use.

  • Jira, ServiceNow, Archer, Confluence and Microsoft Teams
  • API keys that expire, and webhooks
  • Calendar subscriptions for Outlook and Google Calendar
  • Single sign-on and SCIM through your identity provider

nimmy pushes to these systems and does not take records from them: each register stays the source of truth.

Security

Single sign-on and SCIM, a second factor for passwords, tenant isolation enforced in the database, a tamper-evident audit trail, and encryption in transit and at rest.

  • Row-level security separating every organisation’s data
  • A hash-chained audit trail, verified from Settings
  • Connector credentials sealed in the database
  • Rate limits on everything that faces the internet
  • Uploads checked against their own content
Security

nimmy is in pilot

We are working with a small group of early customers. Request access and tell us about your organisation.

Or write to [email protected]