Projects and initiatives profile

How government projects are described, from where they stand in their lifecycle to their milestones and what they deliver.

Schemas: 2

Code lists: 3

Standards: schema.org, OC4IDS, OCDS, GOV.UK Service Manual

Milestone milestone link

A dated point of progress in a project. Linked to its project with schema:about (schema:superEvent accepts only an Event). Status and dates follow the Open Contracting Data Standard milestone: dueDate is when it is scheduled, dateMet is when it was reached.

Standards: Open Contracting Data Standard

Field	Type	Definition	Required
`@id`	`string`	This milestone's own dereferenceable identifier.	Yes
`@type`	`"Milestone"`		Yes
`name`	`string`	The milestone's title, e.g. 'Public beta'.	Yes
`description`	`string`		No
`url`	`string`		No
`about`	`Reference`	The `Project` this milestone belongs to.	Yes
`status`	`string`	termCode from the `MilestoneStatus` code list (OCDS). Not the project status vocabulary.	No
`dueDate`	`string`	When the milestone is scheduled to be reached.	No
`dateMet`	`string`	When the milestone was actually reached.	No

Example

{
  "@id": "https://example-city.gov/id/project/pothole-reporting-redesign/milestone/discovery-complete",
  "@type": "Milestone",
  "name": "Discovery complete",
  "description": "Research with residents and 311 staff finished.",
  "about": {
    "@id": "https://example-city.gov/id/project/pothole-reporting-redesign"
  },
  "status": "met",
  "dueDate": "2026-03-01",
  "dateMet": "2026-03-04"
}

Download JSON

Project project link

A government project or initiative. Subclass of schema:Project, so funder, member and parentOrganization are schema.org terms unchanged. Status (is work happening?) and phase (where in its lifecycle?) are separate: a digital service in beta and a bridge under construction are both 'active'. Only @id, @type and name are required, so a publisher with no project-management system can still publish a valid record. Project health, tasks and assignments are out of scope.

Standards: Open Contracting for Infrastructure Data Standard, Open Contracting Data Standard, GOV.UK Service Manual

Field	Type	Definition	Required
`@id`	`string`	This project's own dereferenceable identifier.	Yes
`@type`	`"Project"`		Yes
`name`	`string`	The project's title.	Yes
`description`	`string`	A plain-language summary of what the project is for.	No
`url`	`string`	Where this project's canonical human-readable page lives.	No
`identifier`	`Identifier[]`	Scheme-qualified identifiers beyond @id, e.g. a capital-budget project number.	No
`status`	`string`	termCode from the `ProjectStatus` code list. Whether work is happening, not where in the lifecycle (see phase) or how well it is going (not modelled).	No
`phase`	`object`	A DefinedTerm from a lifecycle scheme. Any scheme may be used, so the term is referenced by @id rather than enumerated here. schemaGov publishes the `DigitalServicePhase` scheme; a publisher may reference its own. Whether the term belongs to the scheme it claims is checked by the SHACL shapes.	No
`startDate`	`string`	When work began.	No
`expectedEndDate`	`string`	When the project is currently planned to finish. endDate is the actual end.	No
`endDate`	`string`	When the project actually ended.	No
`parentOrganization`	`Reference`	The organization responsible for the project.	No
`member`	`Reference[]`	Organizations taking part in the project.	No
`funder`	`Reference[]`	Organizations funding the project. Amounts belong in the budget profile.	No
`produces`	`Reference[]`	What the project delivers: a service, dataset, application, facility or document. Separate from the project, which can complete while its output stays in operation.	No
`dateModified`	`string`	The date this record was last reported or confirmed as accurate. A project's status, phase and forecast dates are true as of a date, and without one a consumer cannot tell a current record from a stale one. For a record converted from a dated snapshot, the snapshot date.	No
`sourceDataset`	`string`	The `Dataset` this record was published as part of.	No

Example

{
  "@id": "https://example-city.gov/id/project/pothole-reporting-redesign",
  "@type": "Project",
  "name": "Pothole reporting redesign",
  "description": "Rebuild the online pothole reporting form so residents can report a pothole in under a minute from a phone.",
  "url": "https://example-city.gov/projects/pothole-reporting-redesign",
  "status": "active",
  "phase": {
    "@id": "https://schema.govfresh.com/v1/dsphase/public-beta",
    "@type": "DefinedTerm",
    "name": "Public beta"
  },
  "startDate": "2026-01-15",
  "expectedEndDate": "2026-12-15",
  "parentOrganization": {
    "@id": "https://example-city.gov/id/organization/public-works"
  },
  "member": [
    {
      "@id": "https://example-city.gov/id/organization/city-government"
    }
  ],
  "produces": [
    {
      "@id": "https://example-city.gov/id/service/pothole",
      "name": "Pothole repair"
    }
  ],
  "dateModified": "2026-09-30"
}

Download JSON