Every facility that runs more than a handful of calls for expertise faces the same quiet problem. The expert who delivered an excellent assignment last year exists somewhere in the record — a CV attached to an email, a name in a spreadsheet, a paper file in a cabinet — but when a new call opens, the search begins again almost from scratch. The expertise is real. The institution's knowledge of it has evaporated.
A reusable roster is the solution to this problem. Not a database of names, but a structured, maintained, connected record of expertise that compounds in value with every assignment run.
What makes a profile reusable
The distinction between a one-off CV and a reusable profile is not one of content — it is one of structure. A CV is designed to be read. A reusable profile is designed to be searched, compared, filtered and updated.
Practically, this means capturing fields consistently rather than free-form: education and qualifications, fields of expertise (mapped to a controlled vocabulary, not free text), language competencies, employment history, references, and — critically — the assignments the expert has completed within the facility itself, with the working and mission days associated to each.
That last element is what transforms a static record into a living one. A profile linked to actual delivery history tells you not just what an expert claims to offer, but what they have done, for whom, and how it was assessed. A CV never tells you that.
The problem with rebuilding each cycle
Facilities that manage their rosters in spreadsheets often rebuild them, or substantially refresh them, at the start of each call. Partly this is because the spreadsheet from the last cycle is out of date. Partly it is because it never captured the right fields in the first place. Partly it is simply because no one trusts it enough to rely on it.
The cost of this is higher than it appears. The time spent re-sourcing experts who were already in the system — reaching back to them, collecting CVs again, reconstructing availability — is real work that adds no value. Worse, the facility loses the institutional knowledge accumulated across assignments: who performed well, who was available and flexible, who should be considered first for the next similar call.
When that knowledge lives only in the heads of the staff who ran the previous cycle, it leaves when they do.
What a connected roster makes possible
When the roster is a structured database connected to the facility's operational records, the call for expertise changes character. It becomes a search, not a scout.
- You publish a call and the roster responds, because subscribed experts receive notifications of open assignments matching their profile.
- Applications come in against defined fields — matched to the profile data you already hold — so you are comparing like with like from the first review.
- When a candidate is selected, their profile updates automatically with the assignment, the working days and, eventually, the performance evaluation.
Each cycle leaves the roster better than it found it. The facility's knowledge of its expert community compounds rather than resets.
The bottom line
The expert roster is a Technical Assistance Facility's most valuable operational asset. It represents accumulated knowledge of who can do what, at what level of quality, under what conditions. That asset is only realised if the roster is structured, maintained and connected to delivery. Left in a spreadsheet, it evaporates between cycles. Built as a connected database, it is the foundation on which every future call runs faster and better than the last.