Skip to content
Demiton

Allocation

Who and what is rostered on which job, and when.

Part of Assets in the register catalog.

Register ID
allocationUse this name to ask for the register. The API calls it a shelf ID.
Each record is
An eventSomething that happened at a point in time.
Status
AvailableFilled today from connected systems, uploads or public data.
Data
OrganisationPrivate to each organisation's own workspace.
Version
v1Current version.

Standards

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

Connectors

Connected today

Demiton keeps this register current from these systems now.

On the roadmap

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

  • GeotabPartial
  • HammerTechPartial
  • MapTrackPartial
  • MYOB Acumatica
  • Procore

Fields

15 fields: 6 required, 8 optional, 1 defined by each organisation.

Required

Every record carries these fields.

external_idText

The source row's own identifier (id)

Example: ASGN-ALLOC-771201

source_systemText

Which bound system emitted the row.

Example: ASSIGNAR

projectText

The project/job the worker or asset is allocated to.

Example: BWG-2025-001

occurred_atDateYYYY-MM-DD

The resource date the allocation is for.

Example: 2026-06-15

financial_periodText

The period the allocation is attributed to.

Example: 2026-06

hoursDecimal numberUnit: hours

Hours allocated (the shelf's only measure)

Example: 9.5

Optional

Present when the source system records them.

workerText

The person the allocation places.

Example: 5501

assetText

The plant/equipment the allocation places.

Example: 9301

cost_codeText

Cost code / work activity the hours are coded to.

Example: EARTHWORKS

statusGroup of fields

The allocation's state.

starts_atDate and timeISO 8601, with time zone

Planned start of the assignment.

Example: 2026-06-15T06:30:00+10:00

ends_atDate and timeISO 8601, with time zone

Planned end of the assignment.

Example: 2026-06-15T16:00:00+10:00

checked_in_atDate and timeISO 8601, with time zone

Actual check-in on the allocated shift.

Example: 2026-06-15T06:28:00+10:00

checked_out_atDate and timeISO 8601, with time zone

Actual check-out from the allocated shift.

Example: 2026-06-15T16:05:00+10:00

Defined by each organisation

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

Example record

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

allocation.example.json
{
"asset": "9301",
"checked_in_at": "2026-06-15T06:28:00+10:00",
"checked_out_at": "2026-06-15T16:05:00+10:00",
"cost_code": "EARTHWORKS",
"ends_at": "2026-06-15T16:00:00+10:00",
"external_id": "ASGN-ALLOC-771201",
"financial_period": "2026-06",
"hours": 9.5,
"legal_entity": "Bridgeworks Group Pty Ltd",
"occurred_at": "2026-06-15",
"project": "BWG-2025-001",
"source_system": "ASSIGNAR",
"starts_at": "2026-06-15T06:30:00+10:00",
"worker": "5501"
}

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/allocation/v1.json
Show the full JSON Schema

Loading the schema…

Talk to the team

Tell us what you run - your ERP, field, payroll and document systems - and we will show you the registers Demiton would keep current from them, on your data, in a 30-minute call.

Book a 30-minute callStart free