Change Decision

Record the rationale, decision date and Decision Status. About (Content) is a real link; author and decision-maker fields are text. Supersedes links an earlier decision. Releases records delivery separately: accepting a change does not mean it is deployed.

Use and boundaries

Field names below are the current product labels. * and ° are UI markers, not database constraints. A preferred single-record selection is not a global cardinality constraint either. The related guide explains operational rules.

Related guide · All entities

Fields

Field	Storage	Source, options or boundary
Name	Text	Stored value.
Rationale	Long text	Stored value.
Author	Text	Text reference; not a linked record.
Author Membership	Text	Text reference; not a linked record.
Decided By (Person)	Text	Text reference; not a linked record.
Decided By (Position)	Text	Text reference; not a linked record.
Decided By (Team)	Text	Text reference; not a linked record.
Decided By (Department)	Text	Text reference; not a linked record.
Decision Date	Date	Stored value.
Decision Status	Single select	Proposed, Accepted, Rejected, Superseded, Deprecated
About (Content)	Linked records	Content
About Type	Single select	Task, Procedure, Compliance Obligation, Milestone, Incident, Metric, Tool, Organization, Person, Membership, Other
About Key	Text	Stored value.
Releases	Linked records	Release
Incidents (Postmortem)	Linked records	Incident
Supersedes	Linked records	Change Decision
Superseded By	Linked records	Change Decision
Tags	Linked records	op:tags · optional labels from the Core Tags catalog; classification only.

Example and maintenance

Illustrative example: accept a new evidence policy with rationale and date, then link the later Release.

Use the existing fictitious records to inspect relationships in the guide. Before changing fields, check lookups, formulas, intakes and workflow contracts. This page documents structure; a field does not prove that an integration populates it.