I'mBoardDocs
Board OntologyHR

Total Contractors

Count of active 1099 contractors, consultants, agencies-of-record, and similar non-employee labor at period end. Tracked separately from `hr.total_headcount` because the cost structure, retention dynamics, and classification risk are different. Common pitfall: under-counting agencies that bill on a project basis without per-head visibility — these often slip out of HR systems and surface only in finance AP detail. A contractor-to-FTE ratio above ~30% sustained typically warrants a classification audit and a deliberate "build vs rent" board conversation. — HR KPI, I'mBoard-authored (editorial tier).

I'mBoard-authored (editorial tier)

No public third-party standard anchors this KPI yet, so I'mBoard authors and maintains the definition — transparently labeled as editorial tier. See the ontology methodology for the published vs editorial tier system and the back-attribution workstream.

Rogue ID: hr.total_contractors Type: Number Domain: HR

Definition

Count of active 1099 contractors, consultants, agencies-of-record, and similar non-employee labor at period end. Tracked separately from hr.total_headcount because the cost structure, retention dynamics, and classification risk are different. Common pitfall: under-counting agencies that bill on a project basis without per-head visibility — these often slip out of HR systems and surface only in finance AP detail. A contractor-to-FTE ratio above ~30% sustained typically warrants a classification audit and a deliberate "build vs rent" board conversation.

Formula

Count of active non-employee workers (1099 contractors, agency contractors, consultants) with engagement status = active at period end. Convert to FTE-equivalent in `hr.fte_metrics` using a contractor-to-FTE factor (e.g., 0.8) if applying to capacity math.

Why it matters

Hidden capacity and hidden cost — contractors expand effective capacity without going through the headcount-approval gate, but they carry classification risk and tend to convert into permanent cost without explicit board approval. Surfacing the count counters that quiet expansion.

How to interpret

Contractor share of total workforce above ~30% sustained signals either a hiring-gate workaround or a deliberate flex-staffing strategy — both warrant a narrative explanation. Under US IRS rules and similar in other jurisdictions, sustained "contractors" working full-time under direction risk reclassification (industry folk-wisdom on the 30% threshold, not citation-grade).

Calculation policy

How an AI agent should compute this KPI from messy company data. Free-text rules consumed at reasoning time — not a deterministic DSL. The most common ways to get this wrong are listed under Common miscomputations.

Inclusion rules

  • Count of active non-employee workers — 1099 contractors, consultants, and agencies-of-record — with engagement status = active AS OF the period-end date (point-in-time, same snapshot date as hr.total_headcount).
  • Count the people actually delivering work, including agency staff billing on a project basis; estimate per-head equivalents for agencies that only bill a lump sum so the count is not silently understated.
  • Keep this number strictly parallel to, and separate from, hr.total_headcount so the contractor-to-FTE ratio is readable.

Exclusion rules

  • W-2 / direct employees — those are hr.total_headcount. The whole point of this KPI is to keep the two cost structures and classification-risk profiles distinct.
  • One-off vendors and SaaS subscriptions that are not labor (hosting, software, professional fees) — this is a count of contracted PEOPLE, not a spend line.
  • Contractors whose engagement ended on or before the snapshot date.

Required inputs

  • Active contractor / consultant roster at period end with engagement status and, where possible, FTE-equivalent effort.
  • Finance AP / vendor ledger to surface agency engagements that never reached the HRIS (the classic blind spot).
  • Engagement type (individual 1099 vs agency-of-record) for the classification-risk read.

Data-source priority

  • Contractor-management / AP system of record for active engagements.
  • Finance AP detail as the catch-all for project-billed agencies invisible to HR systems.
  • Department leads as a last-resort reconciliation for embedded contractors.

Edge cases

  • Project-billed agencies with no per-head visibility: estimate the effective head count from the contract scope rather than recording zero — under-counting here defeats the metric.
  • Contractor converting to employee mid-period: drop from this count and pick up in hr.total_headcount / hr.new_hires on the conversion date; never double-count in the same period.
  • Full-time, long-tenured "contractors" working under company direction: flag for the classification-risk (IRS reclassification) conversation even though they still count here.

Validation checks

  • Contractor share = contractors ÷ (headcount + contractors); sustained above ~30% warrants a narrative on classification risk or a deliberate flex-staffing strategy.
  • Reconcile the count against contractor spend in finance — a rising spend with flat count usually means agency heads are uncounted.

Common miscomputations

  • Under-counting lump-sum agency engagements because they lack per-head records — the metric exists precisely to surface this hidden capacity.
  • Sweeping contractors into hr.total_headcount (or vice versa) — corrupts both counts and the contractor-ratio read.
  • Counting terminated / expired engagements still open in the vendor system as active.
  • hr.total_headcount
  • hr.fte_metrics
  • hr.hiring_plan
  • hr.payroll_run_rate

Source

I'mBoard editorial — authored and maintained by I'mBoard, first published 2026-04-01. No third-party standard is cited for this KPI; when one emerges, the definition is back-attributed and promoted to the published tier (a minor version bump). Read the ontology methodology for the published vs editorial tier system, attribution rules, and dispute process.

Stage relevance

Company stagePriority
Series ARecommended
Series BRecommended
Series C+Recommended
PublicRecommended

Suggested for stages: Series A, Series B, Series C+, Public.

Default owning functions

  • HR

Machine-readable

Terminations

Count of company-initiated employee separations during the period — performance-management exits, layoffs, redundancies, and for-cause terminations. The numerator of `hr.involuntary_turnover_rate` and the inverse of `hr.voluntary_exits` on the attrition page. Common pitfall: bundling layoff events (often one-time, board-known) with normal performance-management churn (steady-state, manager-driven). Best practice is to break out layoffs in `hr.talent_challenges` narrative and reserve this number for the recurring stream. — HR KPI, I'mBoard-authored (editorial tier).

Total Headcount

Total number of employees (W-2 / direct-employment equivalents) across all departments at period end. The base denominator for nearly every other HR ratio — turnover rate, revenue per FTE, payroll as % of burn — so getting the snapshot date and the FTE-vs-headcount convention right matters. CANONICAL HEADCOUNT (#2056): this single KPI carries BOTH the plan and the reported figure via the scenario axis (#2019) — scenario=`budget` is the board-approved headcount plan (formerly the separate, now-deprecated `hr.approved_headcount_budget`), and scenario=`actual` is the reported end-of-period count. Budget-vs-actual variance is read off the two scenarios of this one definition. Common pitfall: mixing headcount (people) with FTE (capacity) — they diverge whenever part-time, contractor, or shared-services arrangements exist. Document the convention (typically "FTE-equivalent, employees only, end-of-period") at the board level once and apply consistently. — HR KPI, I'mBoard-authored (editorial tier).

On this page