# MEGA™ v1.8 — Guided Workshop Experience

## Purpose
The assessment workflow now follows the familiar Excel risk-register sequence. A Risk Officer should not have to discover separate unrelated pages to identify, assess, and report a risk.

## Risk Officer sequence
1. Select **Assessment workshops** from the sidebar.
2. Click **Prepare / Start** on a scheduled workshop, or **Continue live workshop** on a live workshop.
3. Under **Step 01: Identify risks**, select **Add applicable risk**. The department and workshop are preselected. Choose an SDBIP operational objective, then a risk category and its risk title; enter consequences and root causes.
4. Save. The new risk opens directly at the voting stage.
5. On the workshop workspace, click **Start live workshop**. When the workshop is Live, open an individual risk and click **Open voting for this risk**. Share the participant link. Click **Refresh results** as needed, then **Close voting & calculate** to adopt average impact × average likelihood.
6. Continue down the same risk page: enter current controls and control effectiveness; review automatically calculated residual risk.
7. Correct any draft control-factor entries before approval if needed (the correction is audit-logged). Record the risk owner, improvement actions, action owners, due dates, and budget status.
8. Submit complete risks and ask an authorised manager to approve. Approved risks appear in the consolidated register.
9. Once all voting rounds are closed, click **End workshop**. Workshop status moves to Completed. Records remain available for control monitoring and approval.

## Workshop status behaviour
- **Scheduled:** Prepare risks; voting is disabled.
- **Live:** Voting rounds can be opened; participants can vote using the existing no-account voting page.
- **Completed:** New risks and voting are disabled. Existing risks can be monitored, reviewed, and approved.
- Only the assigned workshop Risk Officer or an administrator may start or complete a workshop.

## Upgrade existing Afrihost site
1. Backup files and database.
2. Extract the complete ZIP. It is a full application, not a patch.
3. Upload application source files. **Do not overwrite `app/config.php` on the hosting server.** The packaged copy has been preserved unchanged from the prior version, but your live configuration takes precedence.
4. Keep the existing database. **Do not rerun `install.php`**. No new tables or migrations are required for these UI changes.
5. Open **Assessment workshops** in the sidebar. Hard refresh the browser to load CSS/JS v1.8.
6. Test on a staging database with fictional data before using the live workshop with officials.

## Known test limits
PHP lint, JS syntax, static navigation checks, HTML mock rendering, existing scoring tests and ZIP integrity are verified locally. A MySQL-backed end-to-end test, on-server visual review, voting concurrency, and participant identity integrity have **not** been verified. Anonymous voting still relies on browser-level duplicate protection and should be supervised.