Demand and supply

Everything in ProFinda is one of two things: demand (work needing people) or supply (people who could do work). Matching is where they meet.

Demand

Demand is held as resource requests. A request carries structured fields - skills, start date, duration, commitment, grade range, constraints - plus a free-text description for human context. Requests arrive three ways:

Route	Typical source	Watch for
Raised in ProFinda	Engagement managers, partners	Vague skills
Created from CRM	Opportunities passing a probability threshold	Placeholder dates
Entered by the resourcing team	Corridor conversations, email	Missing fields

Requests carry a status (new, in triage, ready to staff, filled, closed) which is how teams run their queue.

Supply

Supply is people: their skills profile (declared, inferred and verified skills), their availability from the staffing system, their location and grade, and their development goals. Supply data is mostly maintained by system feeds; the individually-owned part is the skills and preferences on the profile.

Where they meet

Both sides are expressed in the same skills ontology, which is what makes comparison possible. A match evaluates one request against all eligible supply and returns a ranked shortlist - see how matching works.

Reading the balance

The utilisation and pipeline dashboards show the two sides in aggregate: where supply is idle (bench building in a grade or skill area) and where demand is unmet (requests ageing without candidates). Persistent imbalance in either direction is a hiring, pricing or development conversation, and the dashboards give you the evidence to start it early.