Consultant Associate Network Tracker
Three documents and three sheets that compute each associate's own recheck cadence, so a stale confirmation gets flagged before you call someone already booked elsewhere.
Free download · No account needed
Associate Register · Halworth Advisory · 6 associates, 5 specialisms · audited 24 Aug
Six associates, checked two ways
| Associate | Own cadence | Days since | Fixed 30-day check | Own-cadence status |
|---|---|---|---|---|
| Tobias Marchetti | 15 days | 20 | Current | Stale |
| Elias Vandenberg | 38 days | 10 | Current | Available |
| Simone Auerbach | 9 days | 22 | Current | Stale |
| Soren Kjeldsen | 24 days | 31 | Stale | Stale |
| Meera Chandrasekaran | 33 days | 19 | Current | Booked |
| Nadia Petrosyan | 41 days | 28 | Current | Available |
A fixed thirty-day check catches one of the three actually stale. Tobias and Simone both read Current under a schedule set for the whole bench, because 20 and 22 days both sit inside 30, even though their own patterns say 15 and 9.
Page one for building a consultant associate network is a bench template: name, specialism, rate, and a current availability flag, the same columns everywhere. The most detailed version found, a prompt-driven associate bench, automates one monthly check across the whole roster, on the stated premise that a monthly cadence is frequent enough without becoming an irritation. None of them ask the question that actually decides whether the flag can be trusted. How fast does this specific person's own availability go stale, and has it already happened since the roster was last touched?
This pack computes a recheck cadence per associate instead of one schedule for the whole bench. It averages, in days, the gap between when someone last said they were about to be free and when the practice actually learned somebody else had booked them first. Halworth Advisory, audited for this pack on 24 August 2026, carries six associates across five specialisms. Three are past their own cadence that day, but a fixed thirty-day check catches only one of them, because two others have their own cadences of fifteen and nine days.
The cost is dated rather than abstract. One associate was last confirmed available on 2 August and, matching her own nine-day pattern, was booked by another firm eight days later; Halworth called her eighteen days after that confirmation still believing her current. Rolled up by specialism, two of Halworth's five have no associate whose availability can currently be trusted at all, a gap a six-person headcount hides completely. The same register feeds a specific assignment into the subcontract and margin pack, and runs alongside the past-client pipeline the practice also has to keep fed.
What's in the pack
Network Strategy
Names every specialism the practice needs covered, when a second associate is worth carrying, and the cadence rule that decides whether a name on the register can actually be trusted, checked against the practice's own forward capacity.
Engagement Standard
The baseline terms every associate engagement runs under before a specific contract gets drafted. Control and profit-or-loss line up with the two factors the Department of Labor's proposed 2026 classification rule weighs most heavily, plus confidentiality flow-down, IP, and insurance.
Quality Protocol
The delivery bar every associate's work gets checked against before it reaches a client: cited, consistent, reviewed, and on the client's own template. Whether a specific deliverable is later safe to reuse elsewhere is a separate check.
Associate Register
Every associate worth calling, with specialism, rate, their own computed recheck cadence, and a status that reads Stale the moment a confirmation runs past that person's own pattern, regardless of what it last said.
Collaboration History
The raw log: every engagement's outcome against the Quality Protocol, and every time an associate said they were about to be free, dated against when the practice actually learned someone else had booked them first.
Capacity View
Coverage rolled up by specialism rather than by headcount, naming any specialism where every associate covering it has gone stale at once, since that is invisible in a register that only counts names.
Stale Availability Is Not Availability
The standing rule behind every status on the register. A confirmation older than that associate's own cadence is not staffed against until it is refreshed, no matter how recently the relationship still feels current.
How to use it
- 1
Open in River, or take it blank
Install the pack and send who you'd actually call, their specialism and rate, and whatever history exists, or download the Word documents and CSV sheets and build the register yourself.
- 2
Log every associate and their history
Every associate gets a specialism, a rate, and whatever is known about their last confirmed availability, plus any past rebooking gaps logged on Collaboration History.
- 3
Let the cadence compute
Once an associate has two or more logged gaps, their own recheck cadence averages out, and any confirmation older than that cadence reads as Stale on the register.
- 4
Recheck, then roll up by specialism
Draft the recheck for anyone flagged Stale, log what comes back, then roll the register up by specialism to see which ones currently have no trustworthy coverage at all.
Frequently asked questions
Is this template free?
Yes. The zip is Word documents and CSV sheets, no account and no card required. Edit with AI is the optional half: the agent reads your associate contacts and whatever collaboration history exists, then builds the register and computes every cadence it has enough data for. The rest of the packs sit in the template library.
What format are the downloaded files?
Three Word documents and three CSV sheets in one zip. The Associate Register and Collaboration History carry the columns that do the work: specialism, rate, last confirmed date, days since, and computed status. Excel, Numbers, and Google Sheets all open them with nothing to convert.
What does Edit with AI actually do?
It reads the associates you'd actually call, their specialism and rate, and whatever rebooking history exists, then starts the Associate Register. Once an associate has at least two logged gaps on Collaboration History it averages them into that person's own cadence, and flags any confirmation older than that cadence as Stale.
How is an associate's own recheck cadence actually computed?
From their own logged history, not a fixed number applied to everyone. Every time an associate has said they were about to be free and the practice later learned they were booked elsewhere, the gap in days gets logged on Collaboration History. The average of those gaps becomes that person's cadence; below two logged gaps it stays provisional.
Does this replace a subcontractor agreement?
No. This pack decides who to call and whether their availability can be trusted right now; the subcontract and margin pack prices and contracts a specific associate once an actual engagement needs staffing. The two run in sequence, this register first, that contract once a name is chosen.
Should I check anything else before staffing an associate on a client engagement?
Yes, the engagement itself might already be restricted. A cleared opportunity is not automatically staffable by anyone: check any live restriction the client relationship carries before assigning an associate, since a non-solicit or confidentiality term binds the work regardless of who actually delivers it.
Know who's actually free before you call them
Take the Word documents and CSV sheets blank, or send River your associates and their history and get every recheck cadence computed back.
Edit with AI