Risk Management

Use the Risk Management template to track risks, incidents, and improvement requests through a simple submission and approval flow.

To use this template, open it here.

What this template includes

The template is built for three submission types:

• Risks
• Incidents
• Improvements

It provides:

• Role-based submission and review workflows
• Status tracking for submitted records
• Approval and rejection actions
• Email notifications for key workflow events
• A project table for approved work

Roles and access

The app uses three role groups:

• App Users create submissions and manage their own records
• Power Users review all submissions and apply approvals or rejections
• App Admins manage the full dataset and app configuration

Keep role permissions aligned with the workflow. Each role should only see the records and actions it needs.

Data model

The template uses five internal tables plus Budibase’s Users table.

Table relationships

The main relationships are:

• Improvement Projects links to Risks
• Improvement Projects links to Incidents
• Improvement Projects links to Improvements
• Each submission table links to Users for ownership and auditing

Use Single User fields for ownership, creator, or reviewer tracking, and Relationship fields for the links between tables.

Workflow

The submission flow is:

1. A user creates a risk, incident, or improvement.
2. The record is assigned a submission status.
3. A power user reviews the record.
4. The record is approved, rejected, or canceled.
5. Email notifications are sent at the relevant step.

Approved items can be linked to an Improvement Projects record for follow-up work.

Screens

The template uses a mix of autogenerated and custom screens.

• App users use submission forms and personal status views
• Power users use review screens for approvals and rejections
• Admins use management screens for monitoring and reporting

Keep these screens role-specific. That makes the workflow easier to scan and reduces unnecessary branching in the UI.

Automations

The main automations cover:

• Submission notifications
• Approval and rejection updates
• Cancellation handling
• Scheduled email summaries for power users

If you change the statuses or add a new workflow stage, update the related automations at the same time.

Customising the template

Start by adjusting:

1. Role names and permissions
2. Status values
3. Submission fields
4. Review actions
5. Email notification content

If you replace the internal tables with your own data model, update the views and automations together.

Related guides

• Budibase DB
• Working with screens
• Working with email automations
• Working with data in design