📊 Capacity Scan — a real-time picture of who is available right now

Before STAFFY proposes a single assignment, it needs to know the landscape. Capacity Scan reads all active Klient PSA resources and their current task assignments to build a real-time picture: who is available, who is at capacity, and who is already over-allocated. This is the foundation every staffing decision is built on — and it is always live data, never a stale export.

STAFFY focuses on In Progress projects only. Resources assigned exclusively to completed, cancelled, or on-hold projects are surfaced as available bench capacity — ready to be matched to open work.

📊 STAFFY · Capacity Scan — Week of May 26, 2026
ResourceRoleUtilizationStatus
Sarah ChenSr. Consultant72%Available
James OkaforProject Manager95%At capacity
Priya NairConsultant60%Available
Mike TorresSr. Consultant112%Over-allocated
Aisha DialloBusiness Analyst40%Available

🔍 Staffing Gaps — every task that needs a resource, in one view

Staffing Gaps is STAFFY's demand-side picture. It scans all tasks across In Progress projects and surfaces the ones that need attention: tasks with no assignee, tasks with insufficient hours relative to their deadline, and tasks where the current assignee is over-allocated and delivery is at risk. This is sourced entirely from Klient PSA — no spreadsheets, no manual triage.

STAFFY prioritizes by deadline proximity and project criticality. The resource manager sees the most urgent gaps first — not an undifferentiated list of every open task in the org.

🔍 STAFFY · Staffing Gaps — In Progress Projects
TaskProjectDeadlineGap
Data migration reviewAcme OnboardingMay 29No assignee
Integration testingProject SolsticeJun 3Under-staffed
Requirements workshopApex RolloutJun 5No assignee
UAT coordinationAcme OnboardingJun 10At risk
Go-live checklistProject SolsticeJun 15No assignee

🎯 Match — the right resource for every open task, with reasoning

With capacity and demand both visible, STAFFY proposes the best-fit resource for each open task. The match is based on available hours, utilization against target, role alignment, and — where defined in Klient PSA — skill and project history. STAFFY shows the reasoning, not just the name. The resource manager can see exactly why each proposal was made before deciding to accept, swap, or reject it.

STAFFY never considers resources who are already over-allocated. If no suitable match exists in the current resource pool, it flags the gap rather than proposing a poor fit.

🎯 STAFFY · Match Proposals
Data migration review — Acme Onboarding
Deadline May 29 · No assignee · Sr. Consultant role
Sarah Chen
72% util · 8h available
Match reason: lowest utilization among Sr. Consultants with availability before May 29
Requirements workshop — Apex Rollout
Deadline Jun 5 · No assignee · Business Analyst role
Aisha Diallo
40% util · 16h available
Match reason: only BA on bench with sufficient capacity before Jun 5
Integration testing — Project Solstice
Deadline Jun 3 · Under-staffed · Consultant role
Priya Nair
60% util · 12h available
Match reason: already assigned to Project Solstice — extension is lowest disruption

⚠️ Conflict Alert — surfaces problems before they become project failures

Conflict Alert is STAFFY's proactive surfacing engine. Before any proposal is finalized, and independently as a standing check, STAFFY identifies three categories of risk across all In Progress projects: over-allocations that already exist and need resolution, deadline risks where tasks have no assignee or insufficient coverage with a deadline approaching, and cascading gaps where assigning a resource to one task would create a coverage problem on another active project.

These are surfaced to the resource manager as alerts — not buried in a report. The intent is to get ahead of project failures, not document them after the fact.

⚠️ STAFFY · Conflict Alert — May 26, 2026
🔴 Over-allocation — Mike Torres at 112%
2 active task assignments overlap this week on Acme Onboarding and Apex Rollout. Recommend reassigning one task before adding more work.
🟡 Deadline risk — Data migration review, Acme Onboarding
Deadline May 29 · No assignee · 3 days to deadline. Immediate action required.
🟡 Cascading gap — if Sarah Chen takes Acme task
Assigning Sarah to Data migration review would bring her to 95% util, leaving UAT coordination on Acme Onboarding (Jun 10) without a feasible backup. STAFFY will not propose this without flagging it.
✅ 3 tasks on Project Solstice — on track, no conflicts detected

➕ Action 5 — coming soon

This fifth STAFFY action is being finalized. It will slot in here, ahead of the You Decide · You Assign approval gate — keeping STAFFY consistent with the rest of the PSA Squad's six-step flow.

👁️ You Review — You Approve

STAFFY proposes. You decide. Once you have reviewed the capacity picture, the staffing gaps, the match proposals, and the conflict alerts, you reach the review screen. Every proposed assignment is listed with its reasoning. You can accept a proposal, swap the resource, adjust the hours, or reject and leave a task unassigned. When you approve, STAFFY creates the task assignments in Klient PSA as standard records. Nothing is written until you say so.

The assignments STAFFY creates follow your existing Klient PSA workflow — visible in resource reports, reflected in utilization dashboards, and available to TIMEY1 as the schedule foundation for timesheet pre-fill. The two agents are designed to work together.

🤖 STAFFY · Proposed Assignments — Ready for Review
3 proposals · 2 conflicts resolved · May 26, 2026
Sarah Chen → Data migration review
Acme Onboarding · 8h · Deadline May 29
8h
Aisha Diallo → Requirements workshop
Apex Rollout · 12h · Deadline Jun 5
12h
Priya Nair → Integration testing
Project Solstice · 10h · Deadline Jun 3
10h