DemandFlow Support Centre

INI: Initiative

A strategic initiative with financial planning, milestones, KPIs, and benefits realisation tracking.

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

Entity properties

Property	Value
Entity code	`INI`
Display name	Initiative
Plural	Initiatives
Level	12000

Use cases

INI represents strategic initiatives that sit above projects in the organisational hierarchy. Initiatives are broader than projects - they define strategic goals and link to one or more projects (PJ via link relationship) for execution. The default list view is dataview (card layout) with a custom template showing type icon, name, description, and value section, providing an executive-friendly visual overview.

Fields

Basic Information

Field	Type	Required	Notes
`name`	text	Yes	Initiative Name.
`color`	color		Card colour.
`code`	text		Initiative Code.
`type`	enum	Yes	Valid ids: `Generic` (Generic), `Cost Saving` (Cost Saving), `Revenue Generation` (Revenue Generation), `growth` (Growth & Expansion), `efficiency` (Operational Efficiency), `innovation` (Innovation & Technology), `customer` (Customer Experience), `talent` (Talent & Culture), `sustainability` (Sustainability), `compliance` (Risk & Compliance), `financial` (Financial Performance).
`status`	enum		Valid ids: `draft` (Draft), `proposed` (Proposed), `approved` (Approved), `in_progress` (In Progress), `on_hold` (On Hold), `completed` (Completed), `cancelled` (Cancelled).
`priority`	enum		Valid ids: `critical` (Critical), `high` (High), `medium` (Medium), `low` (Low).
`timeHorizon`	enum		Valid ids: `short` (Short-term (< 1 year)), `medium` (Medium-term (1-3 years)), `long` (Long-term (3+ years)).

Description & Objectives

Field	Type	Notes
`description`	text (multi-line)	Executive Summary.
`objectives`	text (multi-line)	Key Objectives.
`successCriteria`	text (multi-line)	Success Criteria.

Timeline

Field	Type	Notes
`startDate`	date	Start Date.
`targetDate`	date	Target Completion.
`actualEndDate`	date	Actual End Date.
`progress`	number	Progress (%).

Ownership & Governance

Field	Type	Required	Notes
`owner`	reference → `STF`	Yes	Initiative Owner.
`sponsor`	reference → `STF`		Executive Sponsor.
`department`	reference → `DEPT`		Lead Department.
`stakeholders`	array of references → `PPL`		Key Stakeholders.
`team`	reference → `TEAM`		Implementation Team.
`reviewFrequency`	enum		Valid ids: `weekly` (Weekly), `biweekly` (Bi-weekly), `monthly` (Monthly), `quarterly` (Quarterly).

Financial Information

Field	Type	Notes
`budget`	number	Approved Budget ($).
`actualCost`	number	Actual Cost ($).
`expectedROI`	number	Expected ROI (%).
`paybackPeriod`	number	Payback Period (months).
`fundingSource`	enum	Valid ids: `operating` (Operating Budget), `capital` (Capital Budget), `grant` (Grant), `mixed` (Mixed Funding).

Impact & Risk

Field	Type	Notes
`impactScore`	enum	Valid ids: `transformational` (Transformational), `high` (High), `medium` (Medium), `low` (Low).
`riskLevel`	enum	Valid ids: `low` (Low), `medium` (Medium), `high` (High), `critical` (Critical).
`risks`	text (multi-line)	Key Risks.
`dependencies`	text (multi-line)	Dependencies.

Benefits Realization

Field	Type	Notes
`expectedBenefits`	text (multi-line)	Expected Benefits.
`realizedBenefits`	text (multi-line)	Realized Benefits.
`benefitScore`	enum	Valid ids: `exceeded` (Exceeded), `achieved` (Achieved), `partial` (Partially Achieved), `notachieved` (Not Achieved), `pending` (Pending).

Attachments

documents: documents.

Additional panels

Activity timeline panel attached.
Dashboard panel attached.

Relationships

Lookups: owner points at a STF record; sponsor points at a STF record; department points at a DEPT record; stakeholders points at a PPL record; team points at a TEAM record.
Related lists: PJ, MILESTONE (format SUB|INI|MILESTONE), KPI (format SUB|INI|KPI), BENEFIT (format SUB|INI|BENEFIT).

Creating a Initiative via the API

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

{
  "entity":   "INI",
  "level":    12000,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "Example",
  "type": "Generic",
  "owner": "",
  "color": "..."
}

Listing Initiatives

# All records in your tenant
GET /v1/entities/INI/SUB:<your-sub-id>

DemandFlow Support Centre

INI: Initiative

INI: Initiative

Entity properties

Use cases

Fields

Attachments

Additional panels

Relationships

Creating a Initiative via the API

Listing Initiatives

See also

Was this article helpful?