In-jurisdiction jobs created
Number of jobs created inside the jurisdiction of a public funder DURING the reporting period — a FLOW, not a stock. The figure public funding programmes actually require: SSBCI 2.0 requires annual jobs-created reporting per portfolio company, EU structural funds report "employment supported" as a period figure, and US state tax-credit programmes are written in created/retained language. CONVENTION: counts in-jurisdiction positions whose occupant's first day fell within the reporting period and who is still employed in-jurisdiction at period end — counted as-of the reporting date, so a job that existed for a week and ended before period end is not reported as created. Same FTE-equivalent, employees-only, primary-work-location test as `hr.in_jurisdiction_headcount`; contractors are excluded even when in-jurisdiction. NOT DERIVABLE FROM `hr.in_jurisdiction_headcount`: two snapshots of that stock give NET CHANGE, not jobs created. A company that hires 10 in-jurisdiction and loses 10 shows a net delta of 0 while having created 10 jobs — and 10 is the number the funder counts. This is REPORTED BY THE COMPANY (`production: "primary"`), never computed from the stock series. Distinct from `hr.new_hires`, which is company-wide and carries no jurisdiction scope, so it cannot be filtered to the funder's geography. Disjoint from `hr.in_jurisdiction_jobs_retained` by construction: a job is created OR retained in a given period, never both. — 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.in_jurisdiction_jobs_created
Type: Number
Domain: HR
Definition
Number of jobs created inside the jurisdiction of a public funder DURING the reporting period — a FLOW, not a stock. The figure public funding programmes actually require: SSBCI 2.0 requires annual jobs-created reporting per portfolio company, EU structural funds report "employment supported" as a period figure, and US state tax-credit programmes are written in created/retained language. CONVENTION: counts in-jurisdiction positions whose occupant's first day fell within the reporting period and who is still employed in-jurisdiction at period end — counted as-of the reporting date, so a job that existed for a week and ended before period end is not reported as created. Same FTE-equivalent, employees-only, primary-work-location test as hr.in_jurisdiction_headcount; contractors are excluded even when in-jurisdiction. NOT DERIVABLE FROM hr.in_jurisdiction_headcount: two snapshots of that stock give NET CHANGE, not jobs created. A company that hires 10 in-jurisdiction and loses 10 shows a net delta of 0 while having created 10 jobs — and 10 is the number the funder counts. This is REPORTED BY THE COMPANY (production: "primary"), never computed from the stock series. Distinct from hr.new_hires, which is company-wide and carries no jurisdiction scope, so it cannot be filtered to the funder's geography. Disjoint from hr.in_jurisdiction_jobs_retained by construction: a job is created OR retained in a given period, never both.
Formula
Count of in-jurisdiction positions whose occupant's first day fell within the reporting period and who remains employed in-jurisdiction at period end. NOT `hr.in_jurisdiction_headcount[t] - hr.in_jurisdiction_headcount[t-1]` — that is net change, which nets creations against losses and understates (or hides entirely) the jobs a funder counts.Why it matters
Jobs created in the jurisdiction is the number a publicly-funded investor is measured on and reports upward to its own funder — for SSBCI, ultimately to the US Treasury. It is the mandate stated as a rate rather than a level: a portfolio whose in-jurisdiction headcount is flat may still be creating the jobs the programme funded it to create, replacing attrition that would otherwise have shrunk the base. Reading only the stock makes that work invisible.
How to interpret
Read ALONGSIDE hr.in_jurisdiction_headcount, never instead of it: creation with a falling stock means attrition is outrunning hiring (the jobs are real but the base is eroding), while creation with a rising stock is compounding. Never reconstruct this from a change in the stock — the two answer different questions and will legitimately disagree. Because the count is as-of the reporting date, it is not comparable to a "total hires ever started" figure from an HRIS, which counts starts that did not survive the period.
Related KPIs
hr.in_jurisdiction_headcounthr.in_jurisdiction_jobs_retainedhr.new_hireshr.total_headcount
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 stage | Priority |
|---|---|
| Pre-Seed | Core |
| Seed | Core |
| Series A | Core |
| Series B | Core |
| Series C+ | Core |
| Public | Core |
Suggested for stages: Pre-Seed, Seed, Series A, Series B, Series C+, Public.
Default owning functions
- HR
Machine-readable
- This KPI as JSON:
/api/ontology/hr/in_jurisdiction_jobs_created.json - All HR KPIs:
/api/ontology/hr.json - Full catalog:
/api/ontology/index.json
In-jurisdiction headcount
Number of employees whose primary work location is inside the jurisdiction of a public funder at period end — the in-jurisdiction subset of `hr.total_headcount`. Reported by companies whose investor is accountable to a government mandate that is scoped to a geography: a US state fund (e.g. an SSBCI-funded state venture programme), a national programme, or an EU regional fund. For those funders, workforce inside the jurisdiction — not total headcount — is the figure the programme reports upward to its own funder. The jurisdiction itself is board-level context, not part of this definition: a board reporting to a Missouri fund labels this field "MO-based jobs", one reporting to an EU regional fund labels it for its region. STOCK, NOT FLOW: this is a point-in-time count, the in-jurisdiction analogue of `hr.total_headcount`, and it can never exceed it for the same period. It is NOT jobs created or retained over a period — those are separate flow metrics that a net change in this count cannot express (a company that hires 10 in-jurisdiction and loses 10 shows no change here while having created 10 jobs). Convention follows `hr.total_headcount` (FTE-equivalent, employees only, end-of-period) plus the primary-work-location test, which is the usual point of dispute: payroll-tax nexus, a registered address, and where a remote employee actually sits can all disagree. Fix the convention at the board level once and apply it consistently. — HR KPI, I'mBoard-authored (editorial tier).
In-jurisdiction jobs retained
Number of jobs inside a public funder's jurisdiction that were RETAINED across the reporting period — a FLOW, not a stock, and the second half of the created/retained pair SSBCI 2.0 and most US state incentive programmes require. CONVENTION (pinned deliberately — retention has genuinely contested definitions, and two boards reporting incomparable numbers into one portfolio total is the failure this pin exists to prevent): an in-jurisdiction position that was FILLED AT THE START of the reporting period AND is STILL FILLED BY THE SAME EMPLOYEE, in-jurisdiction, AT THE END. Three consequences follow, and they are the convention: (1) BACKFILLS DO NOT COUNT — same seat, new person is not a retained job (that person is `hr.in_jurisdiction_jobs_created` if their first day fell in the period); (2) it is ENDPOINT CONTINUITY, not continuous employment on every day of the period, because endpoints are what payroll records can actually evidence; (3) retained and `hr.in_jurisdiction_jobs_created` are DISJOINT — a job is one or the other in a period, never both, so the two are safe to add. The invariant this yields, which validates the pair against the stock series: retained employees are a subset of the in-jurisdiction workforce at BOTH endpoints, so `retained <= min(hr.in_jurisdiction_headcount[t-1], hr.in_jurisdiction_headcount[t])`. Same FTE-equivalent, employees-only, primary-work-location test as `hr.in_jurisdiction_headcount`; contractors excluded. REPORTED BY THE COMPANY (`production: "primary"`) — retention has no stock analogue and cannot be computed from headcount snapshots at all: it is a statement about continuity of specific roles across a period, not a count at an instant. — HR KPI, I'mBoard-authored (editorial tier).