Watchtower QA Guide

Watchtower Q2 KPI Flow

This guide documents the exact local QA flow for the new Watchtower Q2 weekly KPI setup. Notes are short on purpose, but each role now has a more detailed click path and more granular screenshots.

Flow To Run First

This is the order used before capturing any screenshots.

Reset local stack, seed all data, and keep Metabase running.
Login as Tuan Le and create objective `C4` in Q2 2026.
Create two new weekly project KPIs: one for Nam Hoang and one for Nishith Murab.
Return to Planning, create `C4-KR1`, and link both KPIs in two screens.
Set KPI allocation to `50% / 50%`.
Set client access to `Visible to client` for the Nam KPI and `Client can update` for the Nishith KPI.
Login as Director and add rollout for both KPIs.
Login as Nam Hoang and submit the internal weekly report.
Login as Nishith Murab, walk Summary, burnout, Evidence & History, and KPI detail first, then submit the client weekly report.
Login as Tuan Le, jump from the OKR back into KPI detail, review the internal submission, and verify the client lane.

Local Prep

Baseline verified before running the role flow.

App: https://seta.quickdemo.site/login
Metabase: https://bi.seta.quickdemo.site
Quarter used in this guide: Q2 2026
Watchtower note: Nam Hoang is given PM membership on WT so the project weekly manual KPI can stay assigned to him.

Scope Created

Objective: C4
KR: C4-KR1
Internal KPI: WT-C4-NAM
Client KPI: WT-C4-NISHITH

Access Split

Nam KPI: client access VIEW
Nishith KPI: client access INPUT
Allocation split: 50 / 50
Quarter: Q2 2026

Generated

Generated at: 30 Mar 2026, 11:19
Output: docs/guide/watchtower-q2-kpi-flow.html
Assets: docs/guide/assets
Metabase health: {"status":"ok"}

1. Tuan Le Builds The Q2 OKR And KPI Setup

Tuan creates the new objective, creates both weekly project KPIs, then returns to the OKR tree to add the KR and link both KPIs in two screens.

Step 1

Fill the new objective dialog

Create objective `C4` for the Watchtower Q2 weekly reporting flow.

Step 2

Confirm the new objective in Planning

Check that `C4` is visible in the Planning tree before adding KPI coverage.

Step 3

Create the Nam internal weekly KPI

This KPI is a project weekly manual KPI for Nam Hoang.

Step 4

Review the Nam KPI detail page

Confirm the KPI detail page is created correctly before rollout.

Step 5

Create the Nishith client weekly KPI

This KPI is a project weekly manual KPI for Nishith Murab.

Step 6

Review the Nishith KPI detail page

Confirm the second KPI is ready to be linked back into the KR.

Step 7

Return to Planning before adding the KR

Open the newly created `C4` objective and start the KR flow from the objective card.

Step 8

KR step 1: fill the KR details

Create `C4-KR1` with the Q2 target and status.

Step 9

KR step 1: select the two supporting KPIs

Choose both new KPIs before moving to the configuration screen.

Step 10

KR step 2: open KPI link configuration

Review the selected KPI list and allocation summary.

Step 11

KR step 2: set 50/50 split and client access

Nam KPI is `Visible to client`; Nishith KPI is `Client can update`.

Step 12

Confirm the linked KPIs back in the OKR tree

The KR should now show both linked KPI cards under `C4`.

2. Director Rolls Out Both KPIs

Rollout is completed from the Director account because coverage management is Director-only in the current RBAC.

Step 1

Roll out the Nam KPI

Assign Watchtower and override ownership so Nam submits and Tuan reviews.

Step 2

Land on the Nam tracking detail after rollout

The redirect confirms the assignment was created.

Step 3

Roll out the Nishith KPI

Assign the client KPI to the Watchtower project for Q2.

Step 4

Land on the Nishith tracking detail after rollout

The second redirect confirms the client KPI assignment is live.

3. Nam Hoang Submits The Internal Report

Nam enters the internal weekly report from Tracking and submits it for Tuan review.

Step 1

Open the Nam tracking page

Start from the live assignment detail before filling the weekly report.

Step 2

Fill the weekly report

Complete the checkboxes, evidence note, and review notes before submitting.

Step 3

Confirm the submitted state

The page should move into the submitted handoff for review.

4. Nishith Murab Walks The Client Pages And Submits

Nishith goes through the client-facing Summary, burnout, Evidence & History, and KPI detail views first, then returns to Needs Input to submit the weekly report.

Step 1