# ESM Strategy Hub: Software Requirements Specification

Oct 23, 2026 · @Khalid Muhammad

ESM Group will build an in-house strategy and OKR platform, working name **ESM Strategy Hub**, to replace Cascade from FY28 (Sep 2027), with an MVP live for the FY28 strategy-setting cycle in June to August 2027.

## 1. Document control

| Item | Detail |
| --- | --- |
| Document | Software Requirements Specification (SRS) and wireframe brief |
| Version | 0.1 draft for IT review |
| Business owner | Khalid Muhammad, Finance & Strategy Director |
| Build owner | ESM IT (IT Head to confirm technical lead) |
| Audience | ESM IT developers, solution architect, QA, and department heads as reviewers |
| Companion artefact | Clickable wireframe (published separately, linked in section 10) |
| Review cadence | Revised after each IT sprint review until sign-off |

Requirement IDs use the pattern `FR-<module>-<nn>` (functional) and `NFR-<nn>` (non-functional). Priority uses MoSCoW: **M** must have for MVP, **S** should have, **C** could have, **W** won't have this release. Terms: *focus area* = the top layer (Cascade calls it a focus area or theme); *objective* = strategic objective; *KPI* = the measurable result Cascade calls a measure or key result; *action* = an action point or project that drives the KPI.

## 2. Background and goals

ESM Group runs its Group and department strategies in Cascade today; an in-house build lets ESM fit the tool to its own hierarchy, review rhythm and data, and remove per-seat licence cost.

**Current state.** The FY25 Corporate Strategy in Cascade (screenshots provided) shows the shape ESM uses: a focus area (*Safety*), objectives under it (*Security of Information, no loss of data*), department-level objectives linked from other plans (*ESM Solution Strategy FY25*, owned by IT), KPIs (*Non Successful Cyberattacks*, *No Loss of Data*) and actions (*Secure Development Practices*, *Back-ups on all platforms*). Each row carries a date range, owner, status (Achieved, At Risk, Behind) and % complete, with a Planner list view and a Timeline (Gantt) view.

**Pain points to solve.**

- KPI values are captured manually in Cascade; most source data (finance, enrolments, HR, facility bookings) already sits in ESM systems and the data warehouse.
- Cascade terminology and layout are generic; ESM wants its own four-layer model, ESM statuses and ESM fiscal calendar (Sep to Aug) as first-class concepts.
- The monthly leadership report and the GEMS governance pack are built by hand from Cascade exports.
- Licence cost scales with users, which limits how far down the organisation ESM can push ownership.

**Goals of the build.**

1. One place for the Group strategy and every department strategy, linked so that department work rolls up to Group objectives.
2. Owners update KPIs and actions in under five minutes a month, with Excel import for bulk updates.
3. Live dashboards replace the strategy pages of the leadership monthly pack and feed the GEMS governance pack.
4. Full history across fiscal years, including objectives that run over more than one year.
5. A platform ESM IT owns and can extend (risks, AI summaries, performance reviews) without vendor dependency.

**Success measures (first 12 months live).** 100% of FY28 Group and department strategies held in the Hub; at least 90% of KPIs updated by the monthly deadline; leadership strategy pages produced from the Hub with no manual rework; Cascade licence ended.

## 3. The ESM strategy model

The Hub must model ESM's strategy as four fixed layers (focus area, objective, KPI, action) inside fiscal-year plans that run 1 September to 31 August, with department plans linking up to the Group plan.

### 3.1 Plans and the cascade

- **Group plan.** One per fiscal year, e.g. *Corporate Strategy FY25* (01 Sep 2024 to 31 Aug 2025). Owned by the Finance & Strategy Director. Holds the four Group focus areas and the Group objectives.
- **Department plans.** One per department per fiscal year, e.g. *ESM Solution Strategy FY25* (IT). Departments include Operations, Marketing, Sales, Finance, HR/People, IT and each brand team (Hamilton Aquatics, AIS, Ellevate, Beyond Basketball, Hamilton Training, ESMLive, ESMcreate). Department plans reuse the four Group focus areas so every item maps to the Group structure.
- **Linking.** A department objective is *aligned to* one or more Group objectives. In the Group plan it appears nested under the Group objective with a link marker and the source plan name, exactly as *Enhance the security of information...* appears under *Security of Information* in the FY25 screenshot.

&#91;embedded content: strategy model · Group and department plans, four layers\]

Both plans use the same four layers; the alignment link joins a department objective to the Group objective it serves, so department progress can roll up.

### 3.2 The four layers

| Layer | Lives in | Example from FY25 | Has progress from | Typical count |
| --- | --- | --- | --- | --- |
| Focus area | Plan | Safety | Roll-up of its objectives | 4 per plan |
| Objective | Focus area | Security of Information, no loss of data | Roll-up of its KPIs and linked child objectives | 3 to 6 per focus area |
| KPI | Objective | No Loss of Data; Non Successful Cyberattacks | Actual vs target | 2 to 4 per objective |
| Action | KPI (or objective) | Back-ups on all platforms; Secure Development Practices | % complete or milestones | 2 to 5 per KPI |

The layer names are configurable labels, but the depth is fixed at four for MVP. Actions may also sit directly under an objective where no KPI applies.

### 3.3 ESM-specific rules

1. **Shared objectives.** One objective can have several owning departments (e.g. Operations, Marketing and Sales share *Grow new enrolments*). It is stored once and appears in each owning department's plan view; each department can attach its own KPIs and actions beneath it.
2. **Multi-year objectives.** An objective can span fiscal years (e.g. KSA expansion, FY27 to FY29). It is stored once with a start and end date and appears in each fiscal-year plan it touches, with KPIs and targets set per year. Progress shows both *this year* and *whole life*.
3. **Flexible ownership.** Any item can be assigned to one or more individuals, a team, or a whole department, plus collaborators who can update but do not own.
4. **Fiscal calendar.** All periods, phasing and YTD figures use the ESM year: Q1 = Sep to Nov, Q2 = Dec to Feb, Q3 = Mar to May, Q4 = Jun to Aug. Term views (Term 1, 2, 3) are an optional overlay for academy KPIs.
5. **Year-end carry-forward.** At year end, unfinished objectives, KPIs and actions can be closed, carried into the next fiscal year's plan, or converted to multi-year, keeping their history.

## 4. Benchmark: what to take from Cascade and other OKR tools

The MVP should match Cascade's core (planner, timeline, alignment, measures, dashboards) and borrow two ideas from other tools, a visual strategy map and structured monthly check-ins; AI features and bi-directional integrations come later.

| Capability | Seen in | ESM decision | Priority |
| --- | --- | --- | --- |
| Planner list view with nested focus area, objective, KPI, action rows | [Cascade](https://www.cascade.app/features/planner) | Adopt; primary screen | M |
| Timeline (Gantt) view of the same tree | Cascade (FY25 screenshot) | Adopt | M |
| Configurable structure, terminology, custom fields and tags | [Cascade](https://www.cascade.app/features/planner) | Adopt, with ESM's four layers fixed | M |
| Time horizons per item (monthly, quarterly, annual) | [Cascade](https://www.cascade.app/features/planner) | Adopt, on the Sep to Aug calendar | M |
| Alignment across plans and drill-down to owners and dependencies | [Cascade](https://www.cascade.app/) | Adopt (linked objectives + alignment map) | M |
| Metrics connected to strategy from business data (Excel, Xero, SAP, Salesforce) | [Cascade](https://www.cascade.app/) | Adopt via Excel/CSV import (warehouse feed out of scope for now) | S |
| Strategy map showing pillars down to department and individual goals | [Perdoo](https://perdoo.com/) | Adopt as the Alignment Map screen | S |
| KPI boards tracking month-over-month performance and future targets | [Perdoo](https://platform.softwareone.com/product/perdoo/PCP-1007-4918) | Adopt as KPI scorecard with monthly phasing | M |
| Structured check-ins on progress, wins and challenges | [Perdoo](https://perdoo.com/) | Adopt as monthly KPI check-in (ESM rhythm, not weekly) | M |
| Projects and tasks rolling progress up to the objective | [Profit.co](https://www.profit.co/?p=118490) | Adopt for actions with milestones | M |
| Check-ins and notifications in Slack and Microsoft Teams | [Profit.co](https://www.profit.co/?p=118490) | Teams and email notifications | S |
| AI health scores, risk flags and executive summaries | [Cascade](https://www.cascade.app/features/planner) | Phase 3, using ESM's own AI bot work | C |
| Import strategy from PPT, Word or PDF using AI | [Cascade](https://www.cascade.app/features/planner) | Phase 3 | C |
| Kudos, pulse surveys, 1:1s | Perdoo | Not needed; HR systems cover this | W |

**Avoid.** Seat-based permissions that stop collaborators updating; weekly check-in pressure that does not fit ESM's monthly leadership rhythm; deep generic hierarchies that hide the four ESM layers.

## 5. Users, roles and permissions

Access is role-based plus item-based: a global role sets the ceiling, and ownership or collaboration on an item grants edit rights on that item and its children.

| Role | Who at ESM | Create plans | Edit Group plan | Edit dept plan | Update KPI actuals | Approve targets | View | Admin settings |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| System Admin | IT | Yes | Yes | Yes | Yes | No | All | Yes |
| Strategy Admin | Finance & Strategy Director, delegate | Yes | Yes | Yes | Yes | Yes | All | Strategy settings only |
| Executive Viewer | MD, leadership team, GEMS reviewers | No | No | No | No | No | All published plans | No |
| Department Head | Head of each department or brand | Own dept | Comment | Own dept | Own dept | Own dept, then Strategy Admin | All published plans | No |
| Owner | Named owner of an item | No | Own items | Own items | Own items | No | All published plans | No |
| Collaborator | Added to an item | No | Update only | Update only | Own items | No | All published plans | No |
| Contributor | All other staff | No | No | No | Assigned actions only | No | Own department, Group summary | No |

Rules:

1. Ownership can be a person, a team or a department (`owner_type` = user, team, department). For a team or department, every member inherits Owner rights; the department head is the accountable owner shown on the card.
2. An item can have several owners and any number of collaborators (the FY25 shared objectives need this).
3. Plans and items can be marked *Private* (as the FY25 Group plan is today); private items are visible only to owners, collaborators and Strategy Admin.
4. Plans move through Draft, In review, Approved (published) and Closed. Only Strategy Admin approves the Group plan and approves department plans after the department head submits them.
5. Users, their department and reporting line are created and maintained by the Strategy Admin in the Hub or imported from Excel; nothing syncs from Entra ID or the HR system (see section 11).

## 6. Data model

The core is one `strategy_item` tree per plan, with many-to-many tables for ownership, cross-plan alignment and fiscal-year membership so shared and multi-year objectives are stored once.

### 6.1 Entities

| Entity | Purpose | Key fields |
| --- | --- | --- |
| `fiscal_year` | ESM year | id, label (FY25), start\_date (01 Sep), end\_date (31 Aug), status (open, closed) |
| `period` | Months, quarters, terms within a year | id, fiscal\_year\_id, type (month, quarter, term), label, start\_date, end\_date |
| `org_unit` | Group, entity, brand, department, team | id, name, type, parent\_id, head\_user\_id, country (UAE, Qatar, KSA), active |
| `user` | Staff | id, name, email, password\_hash (nullable), auth\_method (password, microsoft, both), entra\_id (nullable), job\_title, org\_unit\_id, manager\_id, role, active |
| `plan` | Group or department strategy | id, name, type (group, department), org\_unit\_id, fiscal\_year\_id, status (draft, in\_review, approved, closed), visibility (private, org), approved\_by, approved\_at |
| `strategy_item` | Focus area, objective, KPI or action | id, plan\_id, parent\_id, item\_type, title, description, start\_date, end\_date, is\_multi\_year, sort\_order, status\_override, progress\_cached, health\_cached, created\_by, archived |
| `item_fiscal_year` | Which years a multi-year item appears in | item\_id, fiscal\_year\_id, carried\_from\_item\_id |
| `item_owner` | Ownership and collaboration | item\_id, owner\_type (user, team, department), owner\_id, role (owner, collaborator), is\_accountable |
| `item_alignment` | Department objective supports Group objective | child\_item\_id, parent\_item\_id, weight (default 1) |
| `kpi_definition` | Measure settings for a KPI item | item\_id, unit (AED, %, count, days), direction (increase, decrease, maintain, achieve), baseline, target, frequency (monthly, quarterly, termly, annual), aggregation (sum, average, latest), thresholds (on\_track\_pct, at\_risk\_pct), data\_source (manual, import) |
| `kpi_target` | Phased targets | item\_id, period\_id, target\_value |
| `kpi_actual` | Captured or synced values | item\_id, period\_id, actual\_value, source, entered\_by, entered\_at, comment, evidence\_file\_id |
| `action_detail` | Action and project settings | item\_id, progress\_method (manual\_pct, milestones, checklist), budget\_aed, priority |
| `milestone` | Steps inside an action | id, item\_id, title, due\_date, done, done\_at |
| `check_in` | Monthly owner update | id, item\_id, period\_id, status, progress\_pct, narrative, wins, issues, next\_steps, submitted\_by, submitted\_at |
| `comment` | Threads on any item | id, item\_id, author\_id, body, mentions, parent\_comment\_id |
| `attachment` | Evidence files | id, item\_id, file\_url, uploaded\_by |
| `tag`, `custom_field` | Classification | id, name, type, options |
| `review_meeting` | Leadership or department review | id, type (monthly, quarterly, annual), date, plan\_ids, minutes, decisions |
| `audit_log` | Every change | id, entity, entity\_id, field, old\_value, new\_value, user\_id, at |

### 6.2 Integrity rules

- `item_type` hierarchy is enforced: focus area parent = null; objective parent = focus area; KPI parent = objective; action parent = KPI or objective.
- `item_alignment` may only link an objective to an objective in a plan of a higher `org_unit` level in the same or overlapping fiscal year.
- A KPI must have a `kpi_definition` before the plan can be submitted.
- Deleting is soft (`archived = true`) and blocked where actuals exist; history is never lost.
- Values are stored in the KPI's own unit and currency (AED, QAR, SAR); Group roll-ups convert at the Finance-set rate for the period.

## 7. Functional requirements

The Hub has ten modules; 44 of the 59 requirements below are MVP (M).

### 7.1 Plans and fiscal years (PLN)

| ID | Requirement | Pri |
| --- | --- | --- |
| FR-PLN-01 | Strategy Admin creates a fiscal year (label, 01 Sep to 31 Aug); months, quarters (Q1 Sep to Nov) and terms are generated automatically. | M |
| FR-PLN-02 | Create a Group plan or department plan for an org unit and fiscal year. One Group plan per year. | M |
| FR-PLN-03 | Copy a plan from the prior year as a starting draft, choosing which items to carry. | M |
| FR-PLN-04 | Plan header shows name, star/favourite, private flag, owners and collaborators, assigned team, Share, and a fiscal-year switcher (as in Cascade). | M |
| FR-PLN-05 | Plan workflow: Draft, In review, Approved, Closed, with submit, approve and return-with-comments actions and an approval log. | M |
| FR-PLN-06 | Plan directory lists all plans, filterable by year, type, org unit, owner, status. | M |
| FR-PLN-07 | Plan templates (e.g. standard department plan with the four focus areas pre-loaded). | S |

### 7.2 Planner view (PLR)

| ID | Requirement | Pri |
| --- | --- | --- |
| FR-PLR-01 | Collapsible tree: focus area band, objective cards, KPI and action rows, with type icons matching section 3.2. | M |
| FR-PLR-02 | Each row shows title, date range, owner avatars (initials fallback), status chip, progress bar and % complete, and a row menu. | M |
| FR-PLR-03 | Inline "+" to add a child of the valid type at any level. | M |
| FR-PLR-04 | Aligned department objectives appear nested under the Group objective with a link marker and a source-plan chip; clicking opens the source. | M |
| FR-PLR-05 | Drag to reorder within a parent; drag to re-parent where the type rule allows. | S |
| FR-PLR-06 | Filters: owner, department, status, item type, tag; search by title. Expand all / collapse all. | M |
| FR-PLR-07 | Toggle "Show linked department items" on the Group plan. | M |
| FR-PLR-08 | Bulk edit owner, dates and tags for selected rows. | C |

### 7.3 Item detail panel (ITM)

| ID | Requirement | Pri |
| --- | --- | --- |
| FR-ITM-01 | Side panel opens on row click with tabs: Overview, Progress (KPI chart or milestones), Check-ins, Alignment, Comments, Files, History. | M |
| FR-ITM-02 | Edit title, description, dates, owners (user, team, department), collaborators, tags, custom fields. | M |
| FR-ITM-03 | Mark an objective as multi-year and choose the fiscal years it spans. | M |
| FR-ITM-04 | Add several owning departments to a shared objective. | M |
| FR-ITM-05 | Manual status override with mandatory reason; override shown with a marker. | M |
| FR-ITM-06 | Comments with @mentions and email/Teams notification. | M |
| FR-ITM-07 | Full change history from `audit_log`. | M |

### 7.4 KPIs and data capture (KPI)

| ID | Requirement | Pri |
| --- | --- | --- |
| FR-KPI-01 | Define unit, direction, baseline, annual target, frequency, aggregation and RAG thresholds. | M |
| FR-KPI-02 | Phase targets by month, quarter or term (even split, copy last year's shape, or manual). | M |
| FR-KPI-03 | "Capture data" grid: owner enters actuals for all their KPIs for a period on one screen, with comment and evidence upload. | M |
| FR-KPI-04 | KPI chart: actual vs target by period, YTD line, last-year comparison. | M |
| FR-KPI-05 | Excel/CSV import of actuals with a validation preview. | M |
| FR-KPI-06 | Automatic actuals from the ESM data warehouse (out of scope for now; no warehouse integration). | W |
| FR-KPI-07 | Lock actuals for a period once the monthly review closes; Strategy Admin can reopen. | M |
| FR-KPI-08 | KPI library: reuse a KPI definition across department plans; a Group KPI can sum department KPIs. | S |
| FR-KPI-09 | Multi-currency KPIs (AED, QAR, SAR) with conversion for Group roll-up. | S |

### 7.5 Actions (ACT)

| ID | Requirement | Pri |
| --- | --- | --- |
| FR-ACT-01 | Action with owner, start and due date, priority, budget (AED), progress method (manual %, milestones, checklist). | M |
| FR-ACT-02 | Milestones with due dates; progress = completed milestones / total. | M |
| FR-ACT-03 | Overdue flag and reminder when due date passes and progress < 100%. | M |
| FR-ACT-04 | Dependencies between actions (finish-to-start), shown on the timeline. | C |

### 7.6 Timeline view (TML)

| ID | Requirement | Pri |
| --- | --- | --- |
| FR-TML-01 | Grid of Name, Start date, Owner, with a Gantt bar per row coloured by status (as in the FY25 Timeline tab). | M |
| FR-TML-02 | Month columns on the ESM fiscal year; Today button; zoom month, quarter, year. | M |
| FR-TML-03 | Columns picker (end date, status, % complete, department) and View menu (group by focus area, department or owner). | M |
| FR-TML-04 | Bar fill shows % complete inside the date span; multi-year items extend across years. | M |
| FR-TML-05 | Drag bar ends to change dates, with permission check. | S |

### 7.7 Alignment map (ALN)

| ID | Requirement | Pri |
| --- | --- | --- |
| FR-ALN-01 | Visual tree from Group focus areas to Group objectives to aligned department objectives, coloured by status. | S |
| FR-ALN-02 | Gap check: list Group objectives with no aligned department objective, and department objectives aligned to nothing. | M |
| FR-ALN-03 | Department contribution view: which departments support each Group objective. | S |

### 7.8 Check-ins and reviews (REV)

| ID | Requirement | Pri |
| --- | --- | --- |
| FR-REV-01 | Monthly check-in per objective: status, narrative, wins, issues, next steps; pre-filled with KPI and action data. | M |
| FR-REV-02 | Check-in window opens on day 1 and closes on a configurable working day (default day 5) for the prior month. | M |
| FR-REV-03 | Review pack view for a meeting: selected plans, filtered to At Risk and Behind, with check-in narratives. Export to PDF and PowerPoint. | M |
| FR-REV-04 | Record meeting decisions and new actions against items. | S |
| FR-REV-05 | Quarterly and year-end review templates with target re-baselining (with approval). | S |

### 7.9 Dashboards and reports (DSH)

| ID | Requirement | Pri |
| --- | --- | --- |
| FR-DSH-01 | Home: my items, my overdue updates, my KPIs needing data, recent activity. | M |
| FR-DSH-02 | Group dashboard: status count by focus area, progress by department, top risks, update compliance. | M |
| FR-DSH-03 | Department dashboard: same, filtered to one department. | M |
| FR-DSH-04 | Leadership monthly strategy pages and GEMS governance strategy page as fixed report layouts, exportable to PDF/PPTX. | M |
| FR-DSH-05 | Year-on-year comparison of objectives and KPIs. | S |
| FR-DSH-06 | Export any list to Excel. | M |

### 7.10 Notifications and admin (ADM)

| ID | Requirement | Pri |
| --- | --- | --- |
| FR-ADM-01 | Email and Microsoft Teams notifications: assigned, mentioned, check-in due, check-in overdue, status changed to At Risk, plan submitted or approved. | M |
| FR-ADM-02 | User preferences for notification channels and a weekly digest. | S |
| FR-ADM-03 | Admin: org units, users and roles, fiscal years, status thresholds, layer labels, tags, custom fields, review calendar. | M |
| FR-ADM-04 | Year-end close wizard: close, carry forward or convert each open item (section 9.4). | M |
| FR-ADM-05 | AI monthly summary per plan and draft check-in narratives from KPI movements. | C |

## 8. Status, progress and roll-up rules

Progress is calculated bottom-up from KPI actuals and action completion, and status is derived from progress against time elapsed, so a manual status is the exception, not the norm.

### 8.1 KPI progress

For an *increase* KPI, progress = (actual − baseline) / (target − baseline), capped at 0% and 120%. For a *decrease* KPI the sign flips. *Maintain* KPIs score 100% when the actual is within tolerance, else 0%. *Achieve* (yes/no) KPIs score 0% or 100%.

```latex
\text{KPI progress} = \min\left(1.2,\ \max\left(0,\ \frac{\text{actual}_{\text{YTD}} - \text{baseline}}{\text{target}_{\text{YTD}} - \text{baseline}}\right)\right)
```

YTD actual uses the KPI's aggregation (sum, average or latest). Status compares progress to the YTD phased target, not the annual target, so a KPI is not shown Behind in September for missing a full-year number.

### 8.2 Action progress

Manual % entered by the owner, or completed milestones ÷ total milestones, or ticked checklist items ÷ total.

### 8.3 Roll-up

- Objective progress = weighted average of its KPIs (default equal weights), plus aligned department objectives when "include linked items" is on for the plan.
- Where an objective has no KPIs, it rolls up its actions.
- Focus area progress = average of its objectives; plan progress = average of focus areas.
- Weights are editable per child (0 to 100, normalised) by the item owner.

### 8.4 Status

| Status | Rule (default thresholds, editable in Admin) | Colour |
| --- | --- | --- |
| Not started | Start date in the future, no actuals | Grey |
| On track | Progress ≥ 95% of expected YTD | Green |
| Behind | Progress 80% to 94% of expected YTD | Amber |
| At risk | Progress < 80% of expected YTD, or an action overdue > 30 days | Red |
| Achieved | Progress ≥ 100% of the annual target, or action complete | Purple |
| Missed | Period ended below target | Dark red |
| Paused / Cancelled | Set manually with reason | Grey outline |

A parent's status comes from its own rolled-up progress, and the parent card also shows a red marker with a count when any child is At risk, so a red item is never hidden. Manual overrides need a reason and expire at the next check-in. The FY25 screenshot shows this: *Safety* objectives sit at 100%, 77% and 82%, an average of 86%, so Safety is Behind with one At risk child flagged. Every status chip has a "why this status" tooltip showing the calculation.

## 9. Strategy setting and review workflows

The Hub runs one annual cycle: Group strategy set and approved before 1 September, department plans aligned to it, monthly check-ins feeding the leadership meeting, quarterly reviews, and a year-end close in August.

&#91;embedded content: annual strategy cycle · 6 steps, May to 1 Sep\]

### 9.1 Annual strategy setting (system steps)

1. **Open the new fiscal year** (Strategy Admin, by May). Copy last year's Group plan as Draft; multi-year objectives appear automatically; other items are carried forward at year-end close (9.4).
2. **Set Group focus areas and objectives** (Strategy Admin with MD and leadership team, May to June). Assign accountable owners; mark shared and multi-year objectives.
3. **Approve the Group plan** (MD, by end of June). Status moves to Approved and is published to all staff.
4. **Department planning** (department heads, July). Each head creates the department plan from the template, aligns every objective to a Group objective, adds KPIs with targets phased by month, and actions with owners. The gap check (FR-ALN-02) must show no unaligned items before submit.
5. **Review and approve department plans** (Strategy Admin, by mid August). Return with comments or approve. KPI targets are cross-checked with the FY budget.
6. **Go live** (1 September). All approved plans lock their structure; changes after go-live need a change request logged in the item history.

### 9.2 Monthly cycle

| When | Who | What the Hub does |
| --- | --- | --- |
| Day 1 | System | Opens the check-in window for last month; notifies KPI owners to enter last month's actuals |
| Days 1 to 5 | KPI and action owners | Enter actuals, update action progress, submit objective check-ins |
| Day 6 | System | Reminds and escalates missing updates to the department head; locks the period at the end of day 7 |
| Days 6 to 8 | Department heads | Review department dashboard, confirm statuses |
| Days 8 to 10 | Strategy Admin | Generates leadership strategy pages and GEMS governance strategy page |
| Leadership meeting | Leadership team | Reviews At risk and Behind items; decisions and new actions recorded in the Hub |

### 9.3 Quarterly review

At the end of each quarter (November, February, May) the Strategy Admin runs a deeper review: target re-phasing requests (with approval), new or retired KPIs, ownership changes, and a quarterly report per focus area. This lines up with the three-monthly review of the ESM Reporting, Meeting & Governance Framework.

### 9.4 Year-end close and carry-forward

In August the close wizard lists every open item in each plan. For each, the owner proposes and the Strategy Admin confirms one of: **Close as achieved**, **Close as missed** (with a lessons-learned note), **Carry forward** (copied into next year's plan, linked to the original), or **Convert to multi-year** (same item, extended end date, new annual targets). The closed year becomes read-only but stays fully searchable and reportable.

## 10. Screen inventory and wireframes

Nine wireframe screens cover the MVP; they are published as a clickable canvas, [ESM Strategy Hub Wireframes](https://claude.ai/artifact/2nsd3bZ4ocij9i4K7YagCe), using the FY25 Safety data from the Cascade screenshots and `[placeholders]` where ESM data is not yet defined.

| # | Screen | Purpose | Main components | Requirements covered |
| --- | --- | --- | --- | --- |
| 01 | Home: My strategy | Personal landing page | Search, fiscal-year switcher, Capture data button, four counters, my items table, monthly rhythm, activity feed | FR-DSH-01 |
| 02 | Planner | Edit and read a plan | Plan header (private, status, owners, team, share), tabs, filters, linked-items toggle, focus area bands, nested objective, KPI and action rows with status and progress, inline add | FR-PLN-04, FR-PLR-01 to 07 |
| 03 | Timeline | Gantt of the same tree | Name, start, owner columns; Sep to Aug months; bars coloured by status with % fill; multi-year striping; Today, Zoom, Group by, Columns, View | FR-TML-01 to 05 |
| 04 | Item detail panel | Full detail of one item | Status and progress, why-this-status, override, tabs (Overview, Progress, Check-ins, Alignment, Comments, Files, History), multi-department owners, multi-year toggle, KPI cards with weights, latest check-in | FR-ITM-01 to 07 |
| 05 | Capture data | Monthly owner update in one place | Period and plan selectors, Excel import, KPI actuals grid with auto-feed markers, action progress cards, objective check-in form | FR-KPI-03, 05, 06; FR-REV-01 |
| 06 | Alignment map | See and fix the cascade | Focus area to Group objective to department objectives lanes, status colours, gap state, gap check counters, unaligned list | FR-ALN-01 to 03 |
| 07 | Group dashboard | Health of the whole strategy | KPI tiles, status by focus area, department table, needs-leadership-attention list, PDF and PPTX export | FR-DSH-02, 03, 06 |
| 08 | Leadership review pack | Run the monthly meeting | Agenda by focus area, exception cards with check-in and driving KPIs, decision capture, new action, re-phase request, GEMS export | FR-REV-03, 04; FR-DSH-04 |
| 09 | Admin: year-end close | Close a year and carry forward | Four-step wizard, open-items table with owner proposal and admin decision | FR-ADM-03, 04 |

**Screens still to wireframe (phase 2):** plan directory, plan approval workflow, KPI definition and phasing editor, user and org admin, notification settings, mobile capture view.

**Design notes for build.** Use ESM navy (#1C244F) for navigation and primary buttons and ESM teal (#60C4BD) for selection and accents; status colours are fixed system-wide (purple Achieved, green On track, amber Behind, red At risk, grey Not started) and every status also carries a text label, never colour alone. All screens must work at tablet width; Capture data and Home must work on a phone.

## 11. Integrations, migration and non-functional requirements

The MVP needs three integrations (email notifications through Microsoft 365, optional Microsoft sign-in, Excel import and export), plus a one-off migration of Cascade history before go-live. There is no integration with the ESM data warehouse, the HR system or Power BI for now: users, departments and KPI actuals are maintained in the Hub or imported from Excel.

### 11.1 Integrations

| Integration | Direction | Use | Priority |
| --- | --- | --- | --- |
| Microsoft Entra ID | In | Optional single sign-on (OpenID Connect via Laravel Socialite); no directory sync | M |
| Microsoft Outlook / Exchange email | Out | Notifications, reminders, weekly digest | M |
| Excel / CSV | In and out | Bulk import of users, plans and KPI actuals; export of any list | M |
| Microsoft Teams | Out | Notifications and deep links to items | C |
| SharePoint | Out | Store generated leadership and GEMS packs in the leadership SharePoint | C |

### 11.2 Migration from Cascade

1. Export FY25, FY26 and FY27 plans from Cascade (focus areas, objectives, KPIs, actions, owners, dates, statuses, % complete, measure history, comments where available).
2. Map Cascade types to Hub types; map Cascade users to Entra IDs; flag unmatched users for manual assignment.
3. Load into a staging environment; Strategy Admin reconciles counts and statuses plan by plan against Cascade.
4. Run Cascade and the Hub in parallel for one monthly cycle; switch off Cascade after leadership sign-off.
5. Closed years load as read-only.

### 11.3 Non-functional requirements

| ID | Requirement |
| --- | --- |
| NFR-01 | Planner with 500 items loads in under 2 seconds; dashboards in under 3 seconds at the 95th percentile. |
| NFR-02 | Supports 600 named users and 100 concurrent users without degradation (headroom for KSA growth). |
| NFR-03 | Availability 99.5% in UAE working hours (Sun to Fri 07:00 to 20:00 GST); planned maintenance outside these hours. |
| NFR-04 | Password or optional Microsoft SSO sign-in; role-based access enforced server-side on every request, not just in the UI; private items never returned to unauthorised users. |
| NFR-05 | Data hosted in the UAE region of the chosen cloud; meets UAE PDPL; Saudi PDPL to be confirmed by Legal before KSA staff onboard. |
| NFR-06 | Encryption in transit (TLS 1.2+) and at rest; daily backups kept 35 days; restore tested quarterly; RPO 24 hours, RTO 8 hours. |
| NFR-07 | Full audit log of every create, update, delete, status override and approval, retained for 7 years. |
| NFR-08 | Responsive: desktop and tablet for all screens; phone for Home, Capture data, Item detail and notifications. |
| NFR-09 | Accessibility to WCAG 2.1 AA; status never shown by colour alone. |
| NFR-10 | British English UI; dates DD/MM/YYYY; numbers with thousand separators; currency labelled (AED, QAR, SAR). Arabic UI is a phase 3 option. |
| NFR-11 | All business rules (thresholds, check-in window, layer labels, fiscal year start) configurable in Admin without code change. |
| NFR-12 | Automated test coverage of 80% on the calculation engine (section 8), with fixtures matching the FY25 screenshots. |

## 12. Technical architecture

The build is a single Laravel (PHP) web application with a Vue 3 front end served through Inertia.js, so there is no separate API layer, one MySQL database and Laravel queues for background work, hosted in Azure UAE North. Users sign in with an email and password or, where enabled, Microsoft single sign-on.

&#91;embedded content: architecture · Laravel + Vue app, MySQL, files, jobs, 2 Microsoft services\]

### 12.1 Recommended stack

| Layer | Recommendation | Why |
| --- | --- | --- |
| Front end | Vue 3 (Composition API) pages rendered through Inertia.js inside the Laravel app; a Vue tree grid and Gantt component for Planner and Timeline | One codebase: pages get their data from Laravel controllers, so there is no separate API to build or secure |
| Back end | Laravel (current supported release, PHP 8.3+): controllers, Eloquent ORM, policies and form requests | Built-in authentication, validation, queues, scheduler and ORM |
| Database | MySQL 8 (Azure Database for MySQL flexible server) | Relational model in section 6; recursive CTEs for the tree |
| Background jobs | Laravel queues (database or Redis driver) + Laravel scheduler | Roll-up recalculation, reminders, period lock, pack generation |
| Files | Laravel filesystem with a configurable disk: local server storage or Azure Blob Storage, chosen by `FILESYSTEM_DISK` | Evidence attachments and generated packs; storage can be switched without code change |
| Auth | Laravel email and password login, plus optional Microsoft single sign-on (Entra ID, OpenID Connect) via Laravel Socialite | Every user can sign in; SSO can be switched on for staff with Microsoft 365 accounts |
| Notifications | Laravel notifications by email through Microsoft 365 (Graph or SMTP) | Reminders and digests reach Outlook; Teams can be added later |
| Exports | Server-side PDF (Browsershot) and PPTX (PhpPresentation) using ESM templates; Excel via Laravel Excel | Leadership pack and GEMS page match the house style |
| Hosting | Azure App Service (Linux, PHP) or a VM in UAE North; separate dev, test and production | Data residency and safe release |

### 12.2 Sign-in: password and Microsoft SSO

Users sign in with an email and password by default; Microsoft SSO is an option the Strategy Admin can switch on, and both methods can run side by side.

1. **Password login.** Laravel's built-in authentication: hashed passwords (bcrypt or Argon2), password reset by email, and login throttling after repeated failures. Accounts are created by the Strategy Admin in Admin > Users or imported from Excel.
2. **Microsoft SSO (optional).** A "Sign in with Microsoft" button appears when SSO is enabled in Admin. Laravel Socialite with the Microsoft provider runs the OpenID Connect flow against ESM's Entra tenant; scopes `openid profile email User.Read`.
3. **App registration.** One single-tenant Entra app registration per environment (dev, test, production), redirect URI `https://<host>/auth/microsoft/callback`; the client secret is kept in server configuration, not in code.
4. **Matching.** On callback the Hub matches the Entra object ID to `user.entra_id`, or on a user's first SSO sign-in links by email to their existing Hub account. No matching user means access is refused; SSO never creates accounts on its own.
5. **Per-user method.** Each user's `auth_method` is password, Microsoft or both. The Strategy Admin can set staff to Microsoft only, which disables their password.
6. **Roles.** Hub roles (section 5) are assigned in Admin, not read from Entra groups.
7. **Sessions and sign-out.** Laravel session cookie (HttpOnly, Secure, SameSite=Lax). Sign-out ends the session and, for SSO users, also redirects to the Entra logout endpoint.

### 12.3 Calculation engine

Progress and status (section 8) are calculated server-side only, by one module, and cached on `strategy_item` (`progress_cached`, `health_cached`). Recalculation runs on every actual, milestone or structure change, walking up the tree and across `item_alignment` links. The UI never calculates status, so dashboards and exports always agree.

### 12.4 Route outline

| Method and path | Purpose |
| --- | --- |
| `GET /fiscal-years`, `POST /fiscal-years` | List and create years |
| `GET /plans?year=&type=&orgUnit=` | Plan directory |
| `POST /plans`, `POST /plans/{id}/copy` | Create plan, copy from prior year |
| `POST /plans/{id}/submit` · `/approve` · `/return` | Approval workflow |
| `GET /plans/{id}/tree?includeLinked=true` | Full planner tree with cached progress and status |
| `POST /items`, `PATCH /items/{id}`, `DELETE /items/{id}` | Create, edit, archive any layer |
| `PUT /items/{id}/owners` | Set owners and collaborators |
| `POST /items/{id}/alignments` | Link to a Group objective |
| `PUT /kpis/{id}/definition`, `PUT /kpis/{id}/targets` | KPI settings and phasing |
| `GET /me/capture?period=`, `POST /actuals/bulk` | Capture data screen |
| `POST /imports/actuals` (multipart) | Excel or CSV import with validation report |
| `POST /items/{id}/check-ins` | Monthly check-in |
| `GET /dashboards/group?period=`, `GET /dashboards/department/{id}` | Dashboard data |
| `POST /reviews`, `POST /reviews/{id}/decisions` | Review meetings and decisions |
| `POST /exports/slt-pack?period=`, `POST /exports/gems-pack?period=` | Generate packs |
| `POST /years/{id}/close` | Year-end close wizard |
| `GET /audit?entity=&id=` | Change history |

## 13. Delivery plan

The Hub is delivered in three phases, with the MVP live for FY28 strategy setting in June 2027 and Cascade switched off after the September 2027 monthly cycle.

### 13.1 Phases

| Phase | Window | Scope | Exit gate |
| --- | --- | --- | --- |
| 0. Discovery | Nov to Dec 2026 | Set up the Laravel and Vue project and environments, finalise data model, clickable prototype from the wireframes, Cascade export test | Spec v1.0 signed by Finance & Strategy Director and IT Head |
| 1. MVP build | Jan to Apr 2027 | All M requirements: plans, planner, item panel, KPIs and capture, actions, timeline, gap check, check-ins, review pack, dashboards, notifications, admin, year-end close | Feature complete in test |
| 1b. UAT and migration | May to Jun 2027 | UAT with Strategy Admin and 3 department heads; migrate FY25 to FY27 from Cascade | UAT sign-off; migrated counts reconcile |
| Go-live for planning | Jun to Aug 2027 | FY28 Group and department plans built and approved in the Hub | All FY28 plans approved by 31 Aug 2027 |
| Run and parallel | Sep to Oct 2027 | First monthly cycle in the Hub; Cascade read-only | Leadership accepts Hub-generated pack; Cascade licence ended |
| 2. Enhance | Sep to Dec 2027 | Teams notifications, alignment map, KPI library, multi-currency | Phase 2 features accepted by Strategy Admin |
| 3. Intelligence | 2028 | AI monthly summaries, draft check-ins, risk flags, AI import of strategy documents, Arabic UI | Business case approved |

### 13.2 Team and capacity

The build needs a product owner (Finance & Strategy Director or delegate, about 1 day a week), a technical lead, two full-stack developers and part-time QA. The FY27 IT plan already commits the in-house app developer for most of the year, so the build needs either a dedicated new developer or an external provider for phase 1; IT to confirm before discovery ends.

### 13.3 MVP acceptance criteria

- [ ] The FY25 Safety focus area, loaded from Cascade, shows the same objectives, owners, dates, statuses and % complete as the screenshots (100%, 77%, 82%; Safety Behind).
- [ ] A department objective aligned to a Group objective appears nested under it in the Group planner, with the source plan chip.
- [ ] One objective owned by three departments appears in all three department views and is stored once.
- [ ] A multi-year objective appears in two consecutive fiscal-year plans with separate annual targets and a whole-life progress figure.
- [ ] An owner can enter all monthly actuals and one check-in from the Capture data screen in under 5 minutes.
- [ ] The period locks on day 7 and the leadership pack exports to PPTX and PDF in ESM format with no manual edits.
- [ ] A Contributor cannot see a Private plan through any page, export or direct URL.
- [ ] The year-end wizard closes FY27 and carries selected items into FY28 with history linked.

### 13.4 Open questions

- [ ] Names and definitions of the other three Group focus areas.
- [ ] Final list of departments and brands that get their own plans, and whether brands in Qatar and KSA have separate plans.
- [ ] Status thresholds: confirm 95% and 80% or set ESM's own.
- [ ] Check-in deadline: working day 5 or 7, and the leadership meeting date each month.
- [ ] Whether KPI weights are allowed or all KPIs count equally.
- [ ] Azure hosting option for the Laravel stack (App Service or containers), and whether an external provider builds phase 1.
- [ ] Whether Microsoft SSO is switched on at launch, and whether staff with Microsoft 365 accounts are set to Microsoft only.
- [ ] Default file storage for production: local server disk or Azure Blob.
- [ ] Cascade contract end date, which sets the latest safe go-live.
- [ ] GEMS governance page format: confirm the strategy section layout GEMS expects.
