Tools/ Documents
Documents

Process documentation, on the board it describes

Write down how a board works on the board itself, and keep the rest of your process documentation in Document boards beside it. Every saved version is kept.

The problem

Instructions nobody can find are instructions nobody follows

A board with clear owners and deadlines still depends on people knowing how to work on it.

The how-to lives somewhere else

How to answer, what is due when and who to ask sit in an email or a shared drive, not on the board.

Every new site manager asks again

The answers are in someone’s head, so they are given one person at a time.

Nobody knows which copy is current

The instructions were edited twice last year. Which file has the change, and who made it?

How it works

The how-to sits first in the board’s menu

Every board people work on can have a Documentation page, right where the work is.

  1. 01

    Switch it on and name it

    A board admin switches on the Documentation page in Settings and calls it what fits, such as How we work. It comes first in the board’s menu.

  2. 02

    Write it like any text in 21RISK

    Headings, lists, links, tables and images. The headings become an On this page table of contents, and each has its own link to share.

  3. 03

    Every save is a version

    The history shows who saved what and when, compares any version with the one before, and brings back an earlier one.

Fire safety findings / How we work VERSION 6
How we work ◷

This board holds every fire safety finding from our site audits. Read this before you raise or close one.

Raising a finding

  1. Pick the site and the category.
  2. Add a photo of what you saw.
  3. Set the site manager as responsible.

Deadlines

Blocked exit or escape routeSame day
Sprinkler or alarm fault7 days
Everything else30 days
Document boards

A page for what is not about one board

A Document board is one page of text in the sidebar, next to the boards it describes. Write down how your organization handles an incident, what a new site manager should know in their first week, or put one at the top of a folder to say what its boards are for.

You choose who reads it and who edits it. Nothing changes for anyone else until you save, every save is a version, and the history highlights exactly what changed. A restore saves the old text as a new version, so nothing is ever lost.

Incident response / History 8 VERSIONS
v8 Maja Krogh 14 Nov 2026
v7 Peter Vind 2 Oct 2026
v6 Maja Krogh 18 Sep 2026
Version 7 compared with version 6 Who to call
Site manager · on site, day shift
Maintenance lead · +45 20 11 40 08
Maintenance lead · +45 20 11 40 18
On-call engineer · nights and weekends
Insurance broker · within 24 hours of any fire
Restore this version
Features

What you get with documents

EVERY BOARD

On the boards people work on

Compliance 2.0, findings, safety walks, insurance, claims and frameworks and controls. On from the start for new boards.

CONTENTS

A table of contents

The headings become On this page, so readers jump to the part they need. Every heading has a link to share.

HISTORY

Every version kept

See who saved what and when, compare a version with the one before, and restore an earlier one.

SAFE

No overwritten work

If a colleague saves while you edit, you are told who saved before anything is lost.

ACCESS

Clear roles

Everyone on a board reads its documentation; its admins write it. A Document board has readers, editors and admins.

AGENTS

Read by your AI assistant

Assistants connected to 21RISK read the documentation first, so they answer with your own instructions.

Read how board documentation and Document boards work. For policies that must be approved and reviewed, use policy management.

FAQ

Frequently asked questions

Which boards can have documentation?

Compliance 2.0, findings, safety walks, insurance, claims and frameworks and controls boards. New boards have the Documentation page switched on from the start. On a board created before it existed, a board admin switches it on under Settings › Documentation.

What is the difference between board documentation and a Document board?

Board documentation is about one board: how to work on it. A Document board is a page of its own in the sidebar, for text that is not about one board, such as how your organization handles an incident or what the boards in a folder are for. Both keep every version.

Who can read and who can edit?

Everyone who can open a board reads its documentation and the history. People who can manage the board’s settings edit it, name it and restore earlier versions. A Document board has its own access: readers read it, editors also edit it and restore versions, and admins also choose who has access.

What happens if two people edit at the same time?

If a colleague saves while you edit, your save is stopped and you are told who saved. Your text stays where it is: look at their version in the history, or save yours over it. Both versions stay in the history.

Is a Document board the place for our company policies?

No. Documents are working text, with no approval, review date or expiry. A policy that must be approved and reviewed every year, such as an Information Security Policy, belongs in policy management, which records who approved each version and when it is due for review.

Do AI assistants read the documentation?

Yes. AI assistants connected to 21RISK read a board’s documentation before they work on the board, so they answer how-to questions with your own instructions. With the right access an assistant can save a new version, which shows in the history like any other.

Put the how-to where the work is

See how a board’s own documentation gets new site managers working on day one.