DemandFlow Support Centre

BGCHECK: Background Check

ReferenceEntity Reference16/04/2026Updated 16/04/2026
A structured background / compliance check record attached to a candidate and optionally a placement.

BGCHECK: Background Check

A structured background / compliance check record attached to a candidate and optionally a placement.

Default definition. This article describes the default BGCHECK 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 BGCHECK.

Entity properties

PropertyValue
Entity codeBGCHECK
Display nameBackground Check
PluralBackground Checks
Level11020
Computed name{{checkType}} . {{candidate}}

Use cases

BGCHECK replaces the free-form compliance checkboxes previously held on PLACE (creditChecked, idLogged, referenceReceived) with a typed record per check. Each record captures the check type (DBS, credit, right-to-work, reference, qualification, etc.), provider, lifecycle status (requested → in progress → passed/failed/expired), dates and certificate reference. BGCHECK is a child of CANDIDATE via comboKey (SUB|CANDIDATE|ENT:), so checks live with the person and persist across placements.

Fields

General: Check

FieldTypeRequiredNotes
nametextRead-only. Auto-composed from check type and candidate
candidatereference → CANDIDATEYesCandidate.
placementreference → PLACEOptional. link this check to a specific placement
checkTypeenumYesCheck type. Valid ids: dbsBasic (DBS. Basic), dbsStandard (DBS. Standard), dbsEnhanced (DBS. Enhanced), credit (Credit), rightToWork (Right to Work), identity (Identity), reference (Reference), qualification (Qualification), profRegistration (Professional Registration), profIndemnity (Professional Indemnity), publicLiability (Public Liability), medical (Medical), other (Other).
statusenumYesStatus. Valid ids: notRequired (Not Required), requested (Requested), inProgress (In Progress), passed (Passed), failed (Failed), expired (Expired), cancelled (Cancelled).
providertextWho performed the check (e.g. DBS, Experian, referee name)
certificateReftextCertificate number or reference provided by the check provider

General: Dates

FieldTypeRequiredNotes
requestedDatedateRequested.
completedDatedateCompleted.
expiryDatedateDate the check expires and needs to be renewed
ownerreference → userOwner.

General: Notes

FieldTypeRequiredNotes
notestext (multi-line)Notes.

Attachments

FieldPanelAllowed typesMax files
checkDocumentsDocumentspdf, doc, docx, xls, xlsx, png, jpg, jpeg, msg, emlmultiple

Relationships

  • Lookups: candidate points at a CANDIDATE record; placement points at a PLACE record.
  • Activity: activity timeline panel attached.

Creating a Background Check via the API

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

{
  "entity":   "BGCHECK",
  "level":    11020,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "candidate": "",
  "checkType": "dbsBasic",
  "status": "notRequired",
  "name": "Reference"
}

Listing Background Checks records

GET /v1/entities/BGCHECK/SUB

See also

bgcheckbackground checkbackground checksbgchecks

Was this article helpful?

← Back to Knowledge Base