Overstaffing verdict (instances)

Per-project instances of the overstaffing verdict.

Part of Opportunities in the register catalog.

Register ID

overstaffing_verdict:overstaffing_verdictUse this name to ask for the register. The API calls it a shelf ID.

Each record is

A stateThe current value of something, replaced when it changes.

Status

DeclaredDefined, and fills when a source produces its first record.

Data

OrganisationPrivate to each organisation's own workspace.

Version

v1Current version.

Download JSON SchemaSee an example record

Standards

This register holds records these standards and laws ask for. Holding them does not by itself certify compliance.

• ISO 30414Human capital reportingInternational

Connectors

Connected today

Demiton keeps this register current from these systems now.

No system fills this register yet.

On the roadmap

Systems in the planned connector rollout that can fill this register. Partial means the system holds only some of its fields.

None planned yet.

Fields

12 fields: 8 required, 3 optional, 1 defined by each organisation.

Required

Every record carries these fields.

verdictText

The outcome: OVERSTAFFED, ON_TRACK or UNDERSTAFFED. BUDGET_ONLY is *not* a stored value — the writer returns without writing.

Example: OVERSTAFFED

assessed_atDate and timeISO 8601, with time zoneUnit: UTC

When the judgement was taken.

Example: 2026-08-20T04:00:00Z

project_refText

The Demiton project the verdict is about (the project_code the writer keys on).

Example: BWG-2025-002

actual_hoursNumberUnit: hours

Labour hours actually charged to the project at assessment time.

Example: 1120

burn_pctNumberUnit: ratio (0–1+)

actual_hours / budget_hours.

Example: 0.72

run_rate_pctNumberUnit: ratio

burn_pct / elapsed_pct — headcount run-rate against expected pace; the value the verdict thresholds are applied to.

Example: 1.18

elapsed_pctNumberUnit: fraction (0–1)

Fraction of project duration elapsed at assessment time.

Example: 0.61

budget_hoursNumberUnit: hours

Tendered labour hours the actual is measured against (parsed schedule total or override).

Example: 1550

Optional

Present when the source system records them.

confidenceNumberUnit: 0–1

Producer confidence in the judgement.

Example: 0.82

source_fileText

Name of the resource-schedule workbook the budget side came from.

source_uriText

Canonical URI of the verdict fact (demiton://project/{code}/overstaffing-verdict).

Defined by each organisation

Their contents come from the organisation's own forms or systems, so they differ between organisations.

verdict_thresholdsGroup of fields

The overstaffed_at / understaffed_at cut-offs used for this assessment.

Example record

A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.

overstaffing_verdict:overstaffing_verdict.example.json

{
  "actual_hours": 1120,
  "assessed_at": "2026-08-20T04:00:00Z",
  "budget_hours": 1550,
  "burn_pct": 0.72,
  "confidence": 0.82,
  "elapsed_pct": 0.61,
  "project_ref": "BWG-2025-002",
  "run_rate_pct": 1.18,
  "verdict": "OVERSTAFFED"
}

Use this contract

The contract is a standard JSON Schema (draft 2020-12) document, so any JSON Schema validator can check a record against it. Keywords starting with x-demiton- add Demiton's own meaning, such as units and requiredness, and validators ignore them.

Schema URL

https://docs.demiton.io/registers/overstaffing_verdict--overstaffing_verdict/v1.json

Show the full JSON Schema

Loading the schema…