DemandFlow Support Centre

CONTRACTDEF: Defect

ReferenceEntity Reference16/04/2026Updated 16/04/2026
The CONTRACTDEF entity stores defects. A defect identified under an NEC or JCT contract. Tracks notification, correction deadline, rectification date, and status.

CONTRACTDEF: Defect

The CONTRACTDEF entity stores defects. A defect identified under an NEC or JCT contract. Tracks notification, correction deadline, rectification date, and status.

Default definition. This article describes the default CONTRACTDEF definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches CONTRACTDEF.

Entity properties

PropertyValue
Entity codeCONTRACTDEF
Display nameDefect
PluralDefects
Level71040

Use cases

Child entity of CONTRACT via SUB|CONTRACT comboKey. Under NEC clause 43 the Supervisor notifies defects.

Fields

Defect Details

FieldTypeRequiredNotes
defectReftextDefect reference. Example: e.g. DEF-001
statusenumYesStatus. Valid ids: open (Open), rectified (Rectified), disputed (Disputed), accepted (Accepted (not rectified)).
nametext (multi-line)YesDescription
locationtextLocation / area
notifiedByenumNotified by. Valid ids: supervisor (Supervisor), contractor (Contractor), pm (Project Manager).
assigned_toreference → userOwner

Dates

FieldTypeRequiredNotes
dateNotifieddateYesDate notified
correctionDeadlinedateDate notified + defects correction period from contract
rectifiedDatedateRectified date

Resolution

FieldTypeRequiredNotes
remedialActiontext (multi-line)Remedial action taken
costOfRectificationnumberCost of rectification

Documents

FieldTypeRequiredNotes
attachmentsfileDefect Evidence

Relationships

  • No declared relationships in the default definition.

Creating a Defect via the API

POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json

{
  "entity":   "CONTRACTDEF",
  "level":    71040,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "status":      "open",
  "name":        "Example value",
  "dateNotified": "2025-01-15"
}

Listing Defects

GET /v1/entities/CONTRACTDEF/SUB

See also

contractdefdefectdefectscontract

Was this article helpful?

← Back to Knowledge Base