AI for Scheduling in Professional Services: Staffing an Engagement Before the Plan Moves Again
This is the resourcing desk. One person, or a small team, deciding who is staffed on which engagement, with partners asking for named individuals, engagement managers asserting availability they have not checked, and a forecast that stopped being true between being built and presented. Scheduling in a consultancy, advisory practice, audit firm or engineering consultancy is not a calendar problem but constrained allocation, where the constraints are careers, client relationships and regulatory eligibility, and where the current state sits in a planning tool, a leave system, a pipeline, hundreds of calendars and last week's timesheets.
A resourcing request is a paragraph in someone's inbox
Almost no request arrives structured. It arrives as a message from a partner reading "we have probably won the operating model piece, need a senior analyst who has done regulated utilities work, 3 days a week from the 4th, through to the year end, plus someone junior who can actually handle the data". Sometimes it is a verbal aside in a pipeline review.
An agent is useful at the front of this. It reads the prose and produces a structured requirement: grade, skill, sector experience, start, duration, intensity, location, and critically the confidence that the work exists at all. Then it writes back the few questions that change the answer, rather than a form. Most requests are conditional on an unsigned proposal, and a request record that does not carry that conditionality corrupts every downstream plan.
Nobody actually knows who is free next month
Availability in most firms is asserted. A manager says they are nearly fully committed and the plan agrees, because the plan was written when the engagement was scoped. In fact fieldwork finished early, a workstream was deferred, and that manager has had most of a fortnight free. Meanwhile someone recorded as available is quietly absorbed by a remediation that never got a code.
The agent behaviour that matters is continuous reconciliation. Compare planned commitment against recorded hours, engagement status, milestone completion and remaining budget on the code. Where plan and evidence disagree, do not guess and do not silently adjust the plan. Put the specific question to the named engagement manager: this allocation says most of their week, the hours say otherwise, is it still real. That loop removes more phantom capacity than an optimiser.
Clearances, independence and sector experience narrow the pool first
Before preference, development or cost, eligibility removes most of the firm. Independence restrictions block anyone with a personal or family financial interest in an audit client. Rotation rules take a partner or key team member off an engagement served long enough. Conflicts block anyone who worked the other side. Security clearance, a licence for a reserved activity, signing rights, a client's approved personnel list, language, visa status and travel tolerance cut further, and part-time patterns are hard constraints, not preferences.
This is where structure pays. Hold the eligibility rules in machine-readable form, then have the agent show not only who qualifies but who was removed and by which rule. A shortlist without its exclusions is unreviewable, and the lead's skill is knowing which exclusion is worth a conversation.
Partner and director hours are the input everything else waits on
The scarcest resource is rarely the delivery team. It is review time, the technical sign-off, the difficult client conversation and the hours a director spends before a deliverable goes out. That time is usually absent from the plan, because it lives in calendars and in the expectation that seniors absorb it anyway.
An agent can make it visible. Map each engagement's review and sign-off milestones against the responsible partner's and director's committed weeks, and surface the collisions: three engagements expecting the same signing partner inside one fortnight, a clearance meeting planned into a week already full of pitch work. Finding that a month out beats any improvement in junior utilisation.
Chargeability, the bench and the pressure to staff the nearest body
Resourcing sits between two incentives pulling against each other. Unassigned people are a cost, so there is pressure to staff whoever is free rather than whoever fits. Equally, engagement leaders hoard good people on codes that no longer need them, because releasing someone means competing to get them back.
Agents make both visible without accusation. Who is unassigned next fortnight. Who is assigned below their recorded capacity. Who is held on an engagement whose remaining budget and milestones do not support the allocation. That last view, the quiet hoard, is the most valuable report the function does not currently have, and it is reconciliation rather than judgement.
Holiday, training and internal commitments nobody treats as bookings
Client work competes with approved leave, mandatory training weeks, methodology updates, exam and study leave, recruitment interviews and internal practice development. These sit in different systems, approved by different people, and carry very different authority. Exam leave and approved holiday are fixed. An internal workstream is not.
An agent should pull all of it into one commitment view and label each item with its source and how negotiable it is. The failure mode to design against is an agent treating approved leave as slack because it sits somewhere the planner never looks.
A staffing option is only useful if it shows what it cost
Proposing names is the easy half. A proposal a reviewer can act on carries its consequences: who is suggested, what they come off and whether that engagement absorbs the loss, which constraint was relaxed, and what must be asked of whom before it is real.
Give the lead a short ordered set of feasible options with that reasoning attached, plus the near misses and why they fail. The decision stays with a person who knows one of those names is already having a difficult year.
An engagement slips a fortnight and three other plans shatter
The client's year end close runs late, data arrives incomplete, or a phase gate is deferred. The engagement moves a fortnight, and the team carefully booked onto their next codes is now double-committed, with a gap where the deferred work used to be.
This is the strongest case for agents in resourcing, because the work is detection and recomputation at a cadence no person sustains. Watch milestone dates, status updates, timesheet burn against plan and the correspondence that signals a slip before anyone replans. Then compute the knock-on and draft the re-plan as a difference list: these allocations move, these break, these people now have a gap, this engagement needs a client conversation about sequencing. The draft is reviewed, not committed automatically.
The rolling forecast is out of date before it is circulated
The forecast is usually one spreadsheet, maintained by one person, for one weekly meeting. It blends signed with probable work, carries assumptions nobody wrote down, and is stale by the time it is on screen.
An agent can maintain it continuously instead. Keep committed and probable demand separated, show which parts of the plan depend on wins that have not happened, and carry a dated record of what changed since the last meeting. The point is not a prettier forecast. It is that the meeting argues about decisions rather than whose numbers are right.
Cohorts, secondments and borrowing from another office
Graduate intakes arrive in cohorts: uniform availability, a fixed training calendar, limited eligibility, and a need to be spread across engagements for development and supervision ratios rather than concentrated where demand happens to be. A different problem from the single experienced hire.
Borrowing is different again: a secondment into a client, a specialist lent from another office, a shared service team with its own priorities. Each carries a cost rate, an internal recharge, an approval from someone else's resourcing lead and a return date everyone forgets. Agents handle that administration well: the request, the agreed terms, the recharge record, the dated return and the reminder before the person is assumed back.
What the timesheets recorded instead of the plan
The plan is a hypothesis. Timesheets are the record. Very few firms compare them systematically, which is why duration and mix estimates for similar engagements stay wrong in the same direction for years.
An agent can build that comparison as a standing output: planned team against actual, planned effort against recorded, by engagement type, sector and phase, then feed the estimate into the next request of the same shape. It should also flag engagements where planned and delivered teams barely overlap, because that is usually a scoping problem rather than a data problem.
Where AI fails here
Development judgement does not transfer. Whether someone is ready to lead a workstream, whether a stretch assignment is the right risk this year, whether a person needs a quieter quarter: these are decisions made by people who know the individual, and an agent optimising for fit and utilisation will reliably propose the safe, proven name. That is how a practice stops growing its own seniors.
Client continuity is similar. The reason a particular manager stays on an account is often unwritten, and usually worth more than the efficiency of moving them. Fairness is also not an objective function. Who gets the travel, the unglamorous remediation, the weekend before a filing: that distribution is a leadership responsibility, and visibly delegating it to a system damages trust quickly.
Anything touching independence or confidentiality stays with its named owner. An agent can apply a restriction list and show its working, but that data goes stale and group structures change, so a clean eligibility result means no conflict was found, never that none exists. Information barriers limit what the resourcing view should expose: a staffing option revealing an engagement to someone walled off from it is a real breach, not a user experience issue.
Data quality sets the ceiling. Where timesheets are late and status is updated at month end, an agent's live view is a confident picture of last fortnight.
Begin with the Monday morning staffing meeting
Point the first build at that meeting's pack rather than at automated allocation. One reconciled view of commitments with its exceptions flagged, every open request parsed from prose into a structured requirement with its conditionality shown, and the next fortnight's conflicts listed with partner and director collisions first. That is useful immediately and requires no authority to commit anything.
Run it alongside the existing spreadsheet for a quarter and compare them on conflicts caught before they became escalations, not on utilisation. Once the commitment view is trusted, add the re-plan drafting, because by then the firm knows whether the underlying picture is accurate enough to act on it.
If it would help to talk through how this maps onto your own planning and timesheet data, Adopt AI Partners can be reached at hello@adoptaipartners.com.