CONTRACTPROG: Programme Submission
The CONTRACTPROG entity stores programme submissions. A contractor programme submission under an NEC or JCT contract. Tracks revision number, submission and acceptance dates, and acceptance status.
Default definition. This article describes the default
CONTRACTPROG 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 CONTRACTPROG.Entity properties
| Property | Value |
|---|---|
| Entity code | CONTRACTPROG |
| Display name | Programme Submission |
| Plural | Programme Submissions |
| Level | 71030 |
Use cases
Child entity of CONTRACT via SUB|CONTRACT comboKey. Under NEC clause 31/32 the contractor submits a programme for acceptance within 2 weeks.
Fields
Submission Details
| Field | Type | Required | Notes |
|---|---|---|---|
revisionNumber | text | Yes | Revision number. Example: e.g. Rev 0, Rev 1 |
status | enum | Yes | Status. Valid ids: submitted (Submitted), under_review (Under Review), accepted (Accepted), rejected (Rejected). |
name | text | Programme title | |
submissionDate | date | Yes | Submission date |
acceptanceDeadline | date | Submission date + 2 weeks (NEC clause 31.3) |
Review Outcome
| Field | Type | Required | Notes |
|---|---|---|---|
reviewDate | date | Review date | |
reviewedBy | reference → user | Reviewed by | |
rejectionReason | text (multi-line) | PM must state reasons per NEC clause 31.3 |
Programme Details
| Field | Type | Required | Notes |
|---|---|---|---|
plannedCompletion | date | Planned completion | |
totalFloat | text | Total float. Example: e.g. 4 weeks | |
commentary | text (multi-line) | Commentary |
Documents
| Field | Type | Required | Notes |
|---|---|---|---|
attachments | file | Programme Documents |
Relationships
- No declared relationships in the default definition.
Creating a Programme Submission via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "CONTRACTPROG",
"level": 71030,
"comboKey": "SUB:<your-sub-id>|ENT:",
"revisionNumber": "Example value",
"status": "submitted",
"submissionDate": "2025-01-15",
"name": "Example value"
}Listing Programme Submissions
GET /v1/entities/CONTRACTPROG/SUB