# Five Whys

The Five Whys technique asks "why" repeatedly to trace a problem back to its root cause. Each response becomes the basis for the next question until an underlying issue is uncovered.

## Opening the Manager

Load the **Five Whys Manager** from the dashboard to view existing analyses. The manager is defined as a modal stored in the `ui_modals` table and rendered with `ModuleLoader`.

## Adding and Editing Entries

1. Click **Add Whys** in the manager header to open the Five Whys form. Select the related incident and enter up to five responses.
2. Use **Edit** from the table row actions to update an existing entry.
3. Entries are stored locally via `LocalSyncManager` in the `ohs_five_whys` table. Use the manager buttons to push changes and call `syncNow()` when finished.

`SyncController` exposes generic bulk endpoints so no extra API controller is needed when using `LocalSyncManager`.

## Relationship to Root Causes

Root cause investigations saved in `ohs_root_causes` reference a Five Whys record through the `five_whys_id` column. Link the analysis to a root cause entry by storing the resulting ID in this field.