Prompt 07 — Individual user workspace

Required context

• Product shell and design system
• Individual routes and permissions
• Current subject home, import, result/PDP, and account screens
• External user documentation

Prompt

Build a coherent, mobile-first individual workspace centered on due work, understandable feedback, and development action.

1. Today page

Replace the four equal prototype cards with:

• Greeting and active tenant/scope
• Priority task list ordered by due date and urgency
• Each task shows type, subject/context, estimated time, due date, save/resume state, and privacy cue
• Current program participation progress
• Latest released result or imported report summary
• Next PDP action/check-in
• Notifications or announcements only when actionable
• First-use and all-done empty states

Do not show admin links inside the task hierarchy; the workspace switcher provides role access.

2. Tasks and feedback requests

Create a filterable list for:

• Feedback to give
• Self surveys
• Rater nominations/approvals assigned to the user
• PDP follow-ups
• Optional feedback requests

Support start/resume, declined/not-observed policy where allowed, due/overdue, completion confirmation, and contextual help.

3. Survey experience

Implement a focused, accessible survey flow:

• Intro: purpose, subject, observation period, anonymity/visibility, estimated time
• Logical grouping with one question or a small bundle per step
• Persistent progress and autosave
• Scale labels and keyboard operation
• Separate Not Observed and Not Applicable when configured
• Optional comment guidance
• Review before submit where policy requires
• Confirmation and next action

Do not allow users to navigate into another tenant or subject by editing URLs.

4. Results overview

List periods and evidence sources with:

• Native campaign/imported external distinction
• Status: processing, awaiting threshold, ready, released, archived
• Observation period and source
• Last viewed/shared state
• Clear action to open, continue PDP, or resolve import problem

Detailed analytics are implemented in prompt 14; create stable route and summary contracts now.

5. Imports

Upgrade PDF import to:

• Drag/drop and file picker
• File type/size/source validation
• Period and subject confirmation
• Upload and processing progress
• Parsing preview and mapping confirmation
• Duplicate and mismatch handling
• Human review for low-confidence extraction
• Import history, source lineage, errors, retry, and delete/archive policy

Never imply that imported scores are directly comparable to native trends.

6. Account and privacy

Link to the account/security center from prompt 06. Add a clear “Who can see my data?” view based on tenant policy and current sharing.

7. Tests and documentation

• Mobile, tablet, desktop
• Keyboard and screen-reader survey flow
• Autosave/offline interruption behavior according to architecture
• Cross-tenant negative tests
• Task-state and retry tests
• No sensitive answers in analytics/logging
• Update user docs and result/import external wiki pages

Acceptance gates

• A user can understand and complete the next task without knowing product architecture.
• Every task explains why it exists and who can see the result.
• Survey completion works on a narrow mobile viewport and keyboard only.
• Imports provide preview and lineage rather than a blind upload.
• Role workspaces remain separate from individual navigation.