Spec: Weekly Summary
Spec: Weekly Summary
Section titled “Spec: Weekly Summary”| Field | Value |
|---|---|
| Module | Gospl Platform (People) |
| Source | v1.0 Draft — June 2026 |
| Status | Draft — Claude added build status, data model, clarifications. Awaiting owner sign-off. |
| Owner | TBD (People Team) |
| Contract | /contracts/people/weekly-summary.yaml |
| Design link | TBD |
| Related | weekly-goals.md (post-submit flow links to goal-setting), _platform/identity-and-access.md (permissions), _platform/notifications.md (planned — heavy dependency) |
Processed like the others. Note the cross-cutting dependencies in §C — this spec is the strongest pull yet for a shared notifications layer and a shared week definition.
1. Overview
Section titled “1. Overview”Employees reflect on the week just passed — achievements, obstacles, learnings, priorities — plus three 1–5 scores (Quality of Work, Personal Wellbeing, Professional Wellbeing). Redesign reduces friction, tightens the employee↔manager feedback loop, and adds an AI-driven trend layer for senior leadership.
2–4. Functional summary
Section titled “2–4. Functional summary”- List page (§4.1): prominent in nav (1 click). Table: week covered, date added, the three scores. Month/year filter. Rename ‘sessions’ → ‘summaries’ throughout. A Response column (doc icon when the manager has responded; click reveals text). ‘Add Summary’ top-right. Rows clickable to full submission.
- Add/Edit form (§4.2): week defaults to most-recently-uncompleted week (Mon–Thu → current; Fri–Sun/Mon-morning → previous if missing), editable but pre-populated. Three 1–5 scores with tooltips. Four open-text questions (proud-of / obstacles / learned / most-important-next), each with guidance note, rich text. Cancel always available.
- Post-submit (§4.3): minimal confirmation + prominent CTA to weekly goal-setting (the joined-up end-of-week flow), plus dismiss option.
- Notifications (§4.4): consolidate the two reminders into one end-of-week prompt (summary → goals). On submit, line manager emailed the content/link with a Respond link → manager enters free-text feedback in Gospl → logged + shown in the Response column → employee emailed the response.
- Monday email (§4.5): managers get previous-week scores for direct reports; senior managers get the full chain; missing submissions flagged; click-through links. v2: suppress absence gaps via Scoro/HomeRun leave (FR-28).
- AI trends (§4.6): detect statistically notable score changes per user (not just low absolutes — e.g. consistent 5 → 3), surface individual changes to that user’s manager (FR-30), operate at department level (FR-31), and expose an AI insights dashboard in the admin area for senior leadership / People Team (FR-32), complementing standard reporting. Flag both concerning and positive shifts.
- Permissions (§4.7): own only (employee) → direct reports (manager) → full chain (senior manager) → org-wide (Senior Leadership / People Team). Configurable via role management, no hardcoded users (FR-39).
§A. Acceptance Criteria & Build Status
Section titled “§A. Acceptance Criteria & Build Status”| Ref | Criterion | Status |
|---|---|---|
| FR-02,03,04,06,07 | List shows week/date/3 scores; month-year filter works; label is ‘summaries’; Add-Summary top-right; rows open the full submission. | buildable now |
| FR-05 | Response column shows a doc icon only where a manager response exists; clicking reveals the response text. | buildable now |
| FR-08,09 | Opening a new summary pre-selects the most-recently-uncompleted week per the Mon–Thu/Fri–Sun rule; the field is editable; no active selection required. | blocked: G1 (week definition) |
| FR-10,11,12,13 | Three 1–5 scores with tooltips; the four simplified questions with guidance notes. | buildable now |
| FR-14 | Open-text fields support rich text (bold, lists). | buildable now |
| FR-15,16,17 | Cancel exits without saving; post-submit shows minimal confirmation + goal-setting CTA + dismiss. | buildable now (CTA links to Weekly Goals) |
| FR-19,20,21,22 | On submit, manager is emailed with content/link + Respond link → manager submits feedback in Gospl → logged + reflected in Response column. | blocked: N (notifications layer) |
| FR-23 | On manager response, the employee is emailed the response. | blocked: N |
| FR-18 | The two reminders are consolidated into one end-of-week notification. | blocked: N, Q4 (audit existing comms) |
| FR-24,25,26,27 | Monday email: scores scoped to recipient (direct reports / full chain), missing flagged, click-through links. | blocked: N, G1 |
| FR-29,30,31 | Detect statistically notable per-user score shifts; surface to the manager; detect department-level shifts. | blocked: Q3 (significance threshold) |
| FR-32,33,34 | AI insights dashboard in admin for senior leadership/People Team; complements standard reporting; flags concerning + positive. | blocked: Q3 (+ admin AI-insights surface, see §C) |
| FR-35,36,37,38,39 | Visibility ladder enforced server-side; configurable via role management, no hardcoded users. | buildable now (uses _platform access — PR-06) |
| FR-28 | v2: suppress absence-related missing-submission gaps via Scoro/HomeRun. | out of scope (v2) |
§B. Data Model Stub
Section titled “§B. Data Model Stub”| Entity | Owner | Fields (indicative) | Notes |
|---|---|---|---|
| WeeklySummary | Gospl | id, tenantId, userId, weekStart, qualityOfWork(1-5), personalWellbeing(1-5), professionalWellbeing(1-5), proud, obstacles, learned, important, createdAt | Scores feed FR-29 trend analysis. weekStart shares the week definition (G1). |
| SummaryResponse | Gospl | id, summaryId, managerId, body(rich text), createdAt | Manager feedback (FR-21/22). Visibility per Q2. |
| Week definition | Gospl (shared) | weekStartDay, timezone | Same concept as Weekly Goals G2 — define once, both consume. |
| Score trend / flag | Gospl | derived | Statistical analysis over a user’s score history (FR-29-31). Numeric stats, not embeddings — no pgvector needed. |
Tenancy/permission: tenant-scoped; visibility uses the _platform ladder (PR-06).
Adds the senior_leadership functional role (org-wide read, alongside people_team)
— added to the platform role model this round. Rich-text fields stored sanitised.
§C. Clarifications Needed
Section titled “§C. Clarifications Needed”Blocking:
- G1 — Week definition (shared with Weekly Goals G2). Canonical week-start/timezone now
live in
admin/tenant-settings(defaultEurope/London, Monday). Remaining: the Mon–Thu/Fri–Sun “most-recently-uncompleted” rule + the rejoin-after-leave edge (Q1) compute against tenant settings. - N — Notifications/email layer. This spec needs: manager-email-on-submit, employee-
email-on-response, the consolidated end-of-week reminder, and the Monday digest. That’s
a shared notifications service (in-app + email) — also needed by Weekly Goals
(OQ-04). Strongest demand yet; recommend stubbing
_platform/notifications.mdnext. - Q3 — “Statistically notable” threshold for AI flagging (X below personal average? % change?). Configurable threshold recommended. Gates FR-29/30/31.
- Q2 — Manager-response visibility — employee + manager only, or also senior leadership? Likely “anyone with access to that user’s record.” Confirm; drives the Response read rule.
Non-blocking / noted:
- Q4 — Audit existing email comms before consolidating (FR-18) — risk of removing valued comms. → Sarah.
- Q5 — Role model — RESOLVED by
_platform/identity-and-access.md+ PR-06; this spec references it (no per-spec role logic). - Q6 / FR-28 — Scoro/HomeRun leave integration — v2; flagged as an early dependency to avoid rework.
Cross-cutting pattern (worth a decision): this is the third feature wanting an AI insights surface in the admin area (MVP Phase 2, Weekly Goals flags, now Weekly Summary FR-32). Consider a shared admin AI-insights area rather than per-feature dashboards.
Out of Scope (this version)
Section titled “Out of Scope (this version)”Scoro/HomeRun holiday integration for suppressing missing-submission alerts (v2).