Demand triage check

Five questions on demand intake and triage.

demand, intake, triage, resource requests

Checks the course Demand intake and triage. No pass mark — it is here so you can check yourself.

Question 1

Question 1 of 5

What should a request contain before it is handed to fulfilment?

Only the client nameSkills required, dates, location or remote expectation, and an accountable requesterA completed staffing decisionThe utilisation report for the practice

A clean handoff needs the skills, dates, location expectation, and someone accountable for clarifications.

Question 2

Question 2 of 5

A request arrives marked urgent but with vague requirements. What is the recommended first move?

Staff it immediately with whoever is freeGo back to the requester for the missing specifics before anything is promisedPark it until the requester complainsEscalate it straight to the practice lead

Vague and urgent is the riskiest combination; clarify first so effort is not wasted staffing the wrong thing.

Question 3

Question 3 of 5

Why keep every request in the intake queue rather than accepting some by email or corridor conversation?

The queue enforces a single source of truth, so priority calls are made across all demand, not just the loudestEmail requests are automatically rejected by ProFindaIt reduces the number of requestsPartners prefer it

Side channels fragment demand; triage only works when everything competing for people is visible in one place.

Question 4

Question 4 of 5

What does triage primarily decide?

Which individual is staffed on each requestThe order and urgency in which requests move to fulfilment, and which need clarification firstThe fee for the engagementWho attends the weekly meeting

Triage sorts and sequences demand; the actual staffing decision comes later in fulfilment.

Question 5

Question 5 of 5

A request has sat unclarified for two weeks because the requester has not replied. What is good practice?

Delete itStaff it with assumptionsApply an agreed ageing rule - chase, then close or downgrade it visibly so the queue reflects real demandLeave it in the queue indefinitely

Stale requests distort the picture of demand; an explicit ageing rule keeps the queue honest.

ProFinda learning and documentation portal

How this portal works Styleguide

Internal · 2026