Risk Matrix & Register — free online tool

Prepare and review

Before entering data, define the decision, process or review that the project should support. Choose a title that identifies the context and record only the information needed for that purpose. Agree on field meanings with the people involved before assigning values or responsibilities. Verifiable descriptions are more useful than broad statements such as fix everything or improve performance. If a value is estimated, record that condition in the description or notes. A person receiving the report can then distinguish observations from assumptions and discuss the reasoning behind the result.

Start with the example button to explore the fields and visualization. Example data is fictional and illustrates the method; it is not a recommendation for your organization. Replacing current data requires confirmation. To preserve previous work, first download a JSON backup or save a copy in the browser. New starts an empty project, while Duplicate creates an independent copy in memory. Use Save in this browser to keep that copy in your local project list. Rename a project using the project name field, then save again to retain the new name.

Enter a few records and inspect the result before building an extensive list. Changes apply when you confirm or leave a field. Open advanced mode when you need owners, configuration or additional details. Move up and move down buttons reorder records without dragging with a mouse. On a phone, wide tables and diagrams have their own horizontal scrolling area. The whole document should remain fitted to the screen. Use field labels and the detailed table to review information that appears small in a chart. Keyboard users can reach the same controls by tabbing through the editor.

1. Load example
2. Edit data
3. Report preview
4. JSON backup

Method and limitations

Score = likelihood × impact. Default thresholds are examples, not certification. In 3×3 mode, levels 1–5 map through ceil(level × 3/5); original assessments are preserved.

Assess inherent and residual risks, configure a 3×3 or 5×5 matrix and export your risk register for free.

Practical example

The table in this guide uses the same source as the example button. Compare its records with the editor to understand how fields become a classification, table or diagram. Internal identifiers maintain relationships between records and do not indicate priority. Change one input at a time and observe its effect. In weighted calculations, check that a weight expresses the relative importance of a criterion rather than the unit of the measured value. When tracking targets, review the period and baseline before interpreting the progress shown on the dashboard.

After completing the project, ask someone who did not edit it to explain what they understand. This reading helps reveal ambiguous descriptions, missing steps and conclusions that depend on unrecorded information. Check units, dates, sources and scoring criteria. A classification or percentage summarizes the model used; it does not prove that the underlying assumptions are correct. Use notes and description fields to record important limitations. Compare scenarios when uncertainty matters, and avoid treating small differences as sufficient evidence for a definitive decision. Keep original observations available for later review.

Choose a file format suited to the purpose. JSON preserves editable fields and settings so work can continue. CSV lets you inspect the register or results in a spreadsheet. Excel retains numeric values as numbers and text as text, without executable formulas generated from entered content. PNG records a visualization for presentations and cannot restore editable fields. For PDF, use Print / PDF and inspect the browser preview. Select A4 or US Letter, keep landscape orientation and review every page before saving. Report headings follow the page language, while text entered by the user keeps its original language.

Files, privacy and review

Saving is optional and keeps up to 30 projects per tool in this browser, within a 5 MB limit and the available browser quota. There is no automatic saving: click Save in this browser after changes you want to keep. Clearing site data, switching profiles or changing devices can prevent access. Export JSON for each important project and keep your own copies. The saved project list is shared across languages of the same tool, allowing saved work to reopen after switching language.

Entered data is processed locally. Someone using the same browser profile or holding exported files may read that information. There is no cross-device synchronization, simultaneous collaboration or project recovery through a Quima account. JSON import validates format, tool, version, references and limits before replacing the open project. Incompatible files are rejected while preserving current work. The import limit is 5 MB; Pareto tables allow up to 500 data rows. Protected files, spreadsheet formulas and unsupported structures should be converted into simple values before import. If storage is blocked or full, use JSON export to preserve your work before closing the page.

Projects are processed in this browser. Local saving is optional and does not replace a JSON backup. Project data is not sent to Quima or AI services.