12 screens covering the full Phase 2 functional surface · rendered in the PRIMA application design system
How to read these wireframes. They follow the PRIMA application design system — the same
layout shell, left navigation, primary colour (#2563eb), grid/table styling, badges, controls and spacing
as the live product — so they confirm layout, content and behaviour in the real look-and-feel.
Numbered markers 1 map each on-screen element back to your decision in the
Requirements Q&A (e.g. Q24). A short scope confirmation follows
each screen — items still needing a decision are marked in amber.
The commercial proposal (phasing, timeline & quote) is issued as a separate document once this scope is agreed.
5Plan-edit authority: the Manager edits the whole plan; the Team Leader may edit only the activities assigned to them.
6 Team is planned by designation first, then specific people are assigned.
What each element does
1Q5 — Named-role team: Engagement Partner, EQCR, Engagement Manager, Team Leader, Team Members.
2Q6 — Role defaults from designation but is overridable (here a Sr Staff acts as Team Leader).
3Q5 — EQCR is optional, applicable to listed / public-interest entities only.
4Q10 — Optional from/to date ranges per member feed availability calculations.
5Q7 — Manager edits whole plan; Team Leader edits only their sections.
6Q8/Q9 — Plan by designation then assign people; no new designations — rates from timesheet rates.
Scope confirmation — Team
Q5
Named-role team (EQCR optional).
Q6
Designation-default roles, overridable per engagement.
Q7
Manager + Team Leader edit authority (scoped).
Q8/Q9
Designation-first planning; existing designations & timesheet rates (no new master).
Q10
Optional per-member date ranges.
Module 3 · Stages & Workflow
Engagement Stages & History
8-stage lifecycle + 60-day lockdown, semi-automatic transitions with condition checks, and a full audit trail.
2 Or enter a date range + total hours; the system distributes evenly across working days.
Capacity check — Priya S.
Capacity (this range)
120 hrs
Already allocated
90 hrs
This allocation
100 hrs
Result
−70 over
34 Over-allocation & cross-team assignments require approval before they take effect.
CancelRequest Approval →
What each element does
1Q19 — Allocation at activity level with a weekly hours breakdown (the firm's chosen granularity).
2Q20 — Alternatively date-range + total hours, distributed evenly across working days.
3Q21 — Over-allocation is permitted but must be approved by Partner/Manager.
4Q22 — Cross-team allocations require the employee's own Manager's approval.
Scope confirmation — Allocation
Q19
Activity-level + weekly breakdown.
Q20
Date range + total hours, even distribution.
Q21/22
Over-allocation & cross-team allocation are approval-gated.
Open
Activity-level + weekly is the most storage-heavy option. Date-range-with-distribution gives ~90% of the value at ~30% of the build — worth a quick re-confirm before committing.
Module 6 · Resource Availability & Capacity
Resource Availability & Allocation View
Who is free, who is overloaded, who is idle — across Botswana & India offices, at any point in time.
Office All ▾Designation All ▾Manager / Team My team ▾Date 06-Jan → 03-Feb ▾
Resource 1
W1 · 06 Jan
W2 · 13 Jan
W3 · 20 Jan
W4 · 27 Jan
Utilisation 4
Botswana · Audit – DP
John · Mgr
ABC · Fieldwk 40
ABC · Fieldwk 40
XYZ · Review 28
+
108% over
Priya · Sr
ABC 24
ABC · Fieldwk 40
DEF · Fieldwk 40
DEF 18
100%
India · Audit – SK
Sam · Staff
+
XYZ 18
+
+
25% idle
Maya · Staff
+
+
+
+
8% idle
Unallocated demand 2
Planned hours not yet staffed — drag onto a person/week
ABC · Revenue testing
Sr Staff · 40h left · by 20-Jan
GHI · Stock count
Staff · 60h · by 31-Jan
DEF · Cash & bank
Staff · 30h · by 28-Jan
+ 3 more…
▾ Quick-assign · Sam · W3 3
GHI · Tax Audit ▾
Stock count ▾
30
CancelAssign
5 Drag a demand card onto a cell, or click + to quick-assign; multi-select people to assign in bulk and “copy last week” for recurring patterns.
6 Over-allocation and cross-team assignments still route to approval (Q21/Q22) — fast, but governed.
What each element does
1Points to Note — Resource-centric board (people as rows, weeks across) so a Manager staffs the whole team from one screen, not per engagement.
2Q15/Q19 — “Unallocated demand” = planned activity-hours not yet staffed; drag onto a person to allocate.
3Q19/Q20 — Inline quick-assign popover (engagement + activity + hours) — no need to open the engagement.
4Q21 · Notes — Live utilisation per person; over-allocated and idle both flagged for re-balancing.
5Notes — Drag, bulk multi-assign and “copy last week” make large-team scheduling fast.
6Q21/Q22 — Speed without losing control: over-allocation / cross-team still go through the Approval Inbox.
Dropdown shows only engagements you're allocated to, and only planned activities.
3Unplanned activity is blocked. If the work isn't in the plan, you can't book it —
Ask Manager to add activity ▸ sends a request to the Engagement Manager.
What each element does
1Q42 — Dropdowns show only allocated engagements and only planned activities.
2Q42 — Live remaining-budget chip (Budget / Used / Remaining) with over-budget warning.
3Q43 — Unplanned activity is blocked; employee requests the Manager to add it to the plan.
2 Multiple invoices per engagement (fee, disbursements, supplementary, credit note).
Payment tracking & GL posting live in the accounting application — PRIMA holds engagement-side invoice records only.
What each element does
1Q38 — Milestone-based invoicing aligned to engagement stages.
2Q39 — Multiple invoices per engagement via an Invoice Register.
3Q40 — Draft generation from WIP / milestone / completion-%, then Manager-adjustable.
4Q41 — Partner approval before an invoice is issued.
Scope confirmation — Invoicing
Q38
Milestone-based.
Q39
Multiple invoices + register.
Q40
Draft from WIP / milestone / completion-%.
Q41
Partner approval.
Open
Confirm the Invoice Register does not duplicate the accounting/billing app — define the canonical invoice record & hand-off contract.
Cross-cutting · One reusable approval surface
Approval Inbox
Every approval-gated action in Phase 2 surfaces in one role-routed inbox — not six separate flows.
1 Each request records the approver, decision, comment and timestamp.
The same surface serves over-allocation (Q21), cross-team allocation (Q22), budget revision (Q29), budget overrun (Q31), invoice (Q41) and timesheet (Q44) approvals.
Why a single inbox
1Across Q21, Q22, Q29, Q31, Q41 and Q44 the firm chose approval-gated overrides. These share one shape — a gated action awaiting a role-holder's decision — so they are built once as a reusable approval capability and surfaced in this inbox, rather than as six bespoke flows. (Implementation approach — reuse vs build — is a technical decision for the proposal stage.)
Cross-cutting · Practice management
Manager / Partner Portfolio Dashboard
Utilisation, idle vs overloaded, budget health across the book, and the basis for performance review.
1Q33 — Budget vs Actual rolled up by Manager and by Partner (portfolio profitability).
2Points to Note — Idle vs overloaded detection so work can be re-balanced equitably.
3Points to Note — Budget-overrun traceability to the responsible individual.
4Points to Note — Utilisation + on-time/within-budget metrics designed in as the appraisal basis.
Scope confirmation — Portfolio
Q33
By Manager / by Partner first; client-group / firm-wide to follow.
Notes
Utilisation, idle/overloaded, overrun attribution, appraisal metrics designed into the model.
Open
Dashboards & Reports are scoped separately after core features (per the client doc) — this screen previews the intent.
Out of scope / handled by other products
Capability
Owner
PRIMA's role
Blockers, PBC list, auto-escalation (Q34–Q37)
Signals platform
Integration contract only — push blocker-linked-to-activity, pull blocker-resolved. No PRIMA UI.
Payment tracking & GL posting (Q38 note)
Accounting app
PRIMA holds engagement-side invoice records; canonical billing/GL lives in accounting.
Detailed risk scoring beyond H/M/L (Q1)
KYC/AML app
PRIMA stores H/M/L; integration is post-Phase-2.
Open items to close before / during build
Lockdown semantics (Q11): during the 60-day window — late timesheets/invoices/corrections allowed, or read-only except Partner reopen?
Allocation storage shape (Q19): confirm activity-level + weekly vs date-range-with-distribution (the simpler option delivers most of the value for a fraction of the effort).
Plan template ownership (Q16): seeded system templates vs firm-authored; single vs multiple; who may edit.