Staffing should show margin and capacity before it shows a name
Before assigning a person to a project, you should see what it does to the project's planned margin and to that person's remaining capacity this week. One matrix, three workflows.
A staffing decision is two decisions at the same time, and most firms make it as one.
A delivery lead needs a senior consultant on a project. The candidate is named in a Slack message. The PM agrees in the next message. The assignment lands in the project tool by Tuesday. Nobody on either side of the conversation has seen what the assignment does to the project’s planned margin, and nobody has seen what it does to the candidate’s remaining capacity for the week. The decision is made on memory, on relationship, and on the assumption that the senior consultant will absorb it.
A week later the senior consultant is at one hundred and twenty percent. A different project’s margin has slipped because the candidate the lead actually needed was the junior who could not be staffed in time. The two facts never met before the assignment was made.
The two numbers the assignment changes
Every staffing change moves two numbers, and both belong on the same screen as the assignment itself.
The first is the project’s margin. A senior consultant at a higher cost rate compresses the margin. A junior at a lower cost rate, if the work fits, opens it. The right answer is not always senior. The right answer is the one that fits the work and the price, and the lead cannot read “fit” without the math in front of them. Margin impact is not an after-the-fact reconciliation. It is the input to the decision.
The second is the person’s remaining capacity. Capacity is a real number, derived from time already booked against other work that week. It is not a guess. A senior consultant at ninety percent has ten points left this week, and an assignment that needs fifteen breaks something. Either the assignment slips. Or the senior consultant takes the hit. Or another project loses time it was counting on. Each of those is a real cost, and the lead should pay it knowingly or not at all.
The matrix shows both. Margin impact in one column. Capacity impact in the other. The name comes after, not before, the math.
Three workflows, one matrix
Staffing happens in three shapes, and most firms run them through three different surfaces.
Project-level staffing is the largest move. A new project lands, and a team gets assigned across the engagement. The decision is multiple people, multiple weeks, against a planned margin the deal team already wrote down. The matrix shows the assignment block, the cumulative margin impact, and each person’s capacity through the engagement window.
Single-task staffing is the day-to-day move. A discrete piece of work needs a name on it. A backlog item, an expansion line, a one-week build. The matrix shows the same two numbers, scoped to the task, against the people who carry the right skill.
Batch staffing is the planning move. Multiple assignments, multiple people, considered together. A quarterly resourcing review. A re-balance across two practices. The matrix accepts a batch, runs the margin and capacity math against every change at once, and lets the lead commit the batch or roll it back.
The three workflows share one matrix because the inputs are the same. Skill. Capacity. Cost rate. Project margin. The shape of the assignment changes. The math does not.
Where memory beats data and where data beats memory
A lead with twenty years of relationships knows things the matrix does not. Who works well together. Who is overdue for harder work. Who is two weeks from burnout, even though their capacity number reads fine. That judgment is real. The matrix does not replace it.
What the matrix replaces is the easier thing memory keeps getting wrong. Capacity by Friday is a number, not a recall. Margin against the planned engagement is a calculation, not an instinct. The lead’s judgment about who fits the team and the work belongs on top of the matrix, not in place of it.
The mistake firms make is the opposite. They use memory for the calculable parts and discover, at the end of a quarter, that the senior consultant was overbooked by twenty percent and the junior was idle by thirty. Both facts were knowable in advance. Neither was visible at the moment of decision.
What PartnerView ships
PartnerView’s staffing surface is one matrix. Project-level assignments, single-task assignments, and batch assignments flow through the same view. Each candidate row shows the skills that match, the remaining capacity for the engagement window, and the margin impact of the assignment on the project’s planned margin. Cost rate is sourced from the same record finance reads against, so the margin math is not a separate calculation.
Capacity is derived from actual time booked against other work, not from a self-reported number. The skills matrix carries real proficiency levels, not yes-no checkboxes, so “find a monday.com advanced consultant with healthcare experience” is a filter on the matrix, not a Slack question.
The lead’s judgment lands on top of the math. The matrix does not assign people. The lead does. The matrix makes sure the lead is reading the right two numbers when they decide.