Skip to main content
STRIPED DONKEYWe do the heavy lifting.

Lagos · Built environment

Construction.
Compare project dates, units and costs.

Compare project dates, planned units and costs with the completion fields represented in the public sample.

Public sample available

Published domain facts

Construction Projects, Lagos
2,001
Building Permits, Lagos
2,000
Site Inspections, Lagos
2,000
Occupancy Certificates, Lagos
2,000

Overview

Domain scope

Compare project dates, planned units and costs with the completion fields represented in the public sample.

Read the published guide →

Known limits

Projects are administrative histories, not BIM or architectural models. Licence references are illustrative, not professional registrations. Affordable-housing linkage is unimplemented; construction does not automatically create a housing unit. Application and Review share one pending phase. Named real project exceptions are documented.

Review the source limits →
Full scope reference 2 documented sections
Published domain scope.

Published domain scope.

Follow synthetic projects through planning, permits, inspection and completion. Connected land, businesses and residents provide the wider city context.

  • Inspect planned and completed units
  • Compare project dates and status
  • Review budget and actual cost coverage
Construction Projects, Lagos
2,001
Building Permits, Lagos
2,000
Site Inspections, Lagos
2,000
Occupancy Certificates, Lagos
2,000
Domain scope.

Domain scope.

Inspect the published scope and deployment boundaries.

Read the published detail

FCTE models construction as a lifecycle, not a static inventory of buildings. A synthetic project moves through planning, permitting, professional oversight, site inspection and completion — within the same City Twin™ as land, business, employment and housing.

A building should not appear overnight — and in FCTE, it doesn't.

Lagos City Twin™ · 1940–2026

Samples & fields

Published sample records.

Public sample · rows and field definitions

Public sample

Project codeStatusStart datePlanned end datePlanned unitsCompleted unitsProject budgetActual project cost
LOS-CPRO/0001888Completed1958-02-191961-05-193129428000000.00415160000.00
LOS-CPRO/0001914Completed1941-05-091946-04-09494469463000000.00513930000.00
LOS-CPRO/0001988Completed2000-01-182003-02-18238226102000000.0093840000.00

Showing 3 of 100 sample rows and 8 of 9 fields. “Not recorded” is a display label; downloads retain original values.

Published field definitions · 8 visible fields

Project code

The published code identifying the project. Codes are retained as supplied in the source.

Original field: ProjectCode
Example: LOS-CPRO/0001888

Status

The state recorded for the in this extract.

Original field: Status
Example: Completed

Start date

The date recorded for the start event.

Original field: StartDate
Example: 1958-02-19

Planned end date

The date recorded for the planned end event.

Original field: PlannedEndDate
Example: 1961-05-19

Planned units

The number of housing or construction units planned for the project.

Original field: PlannedUnits
Example: 31

Completed units

The number of project units recorded as complete.

Original field: CompletedUnits
Example: 29

Project budget

The recorded project budget, in local currency.

Original field: BudgetLocal
Example: 428000000.00

Actual project cost

The project cost recorded to date, in local currency.

Original field: ActualCostLocal
Example: 415160000.00

Complete published field dictionary · 9 fields
ProjectCodeProject code
The published code identifying the project. Codes are retained as supplied in the source.Example: LOS-CPRO/0001888
WardIdWard reference
The reference used to identify the ward associated with this record.Example: 245
StatusStatus
The state recorded for the in this extract.Example: Completed
StartDateStart date
The date recorded for the start event.Example: 1958-02-19
PlannedEndDatePlanned end date
The date recorded for the planned end event.Example: 1961-05-19
PlannedUnitsPlanned units
The number of housing or construction units planned for the project.Example: 31
CompletedUnitsCompleted units
The number of project units recorded as complete.Example: 29
BudgetLocalProject budget
The recorded project budget, in local currency.Example: 428000000.00
ActualCostLocalActual project cost
The project cost recorded to date, in local currency.Example: 415160000.00
Download complete field guide JSON ↓
Additional records and schema context 1 documented sections
From project to completion.

From project to completion.

Inspect the published definitions and release context.

Read the published detail

Representative public release rows — exact run-level values are intentionally not published. Explore the release-backed analysis-ready examples in City Twin™ for current data.

Explore Construction Data →

Public entity familyRepresentsDisclosure boundary
Project contextSynthetic construction projects, geography and sector contextPhysical project fields and identifiers are controlled
Permit & approval contextLifecycle approvals and regulatory milestonesExact workflow and dependencies are controlled
Project phasesConstruction progress through timeTransition sequencing and timing rules are controlled
Built-environment linksLand, housing and area contextComplete physical relationship graph is controlled
ProjectCodePermitInspectionsPassedProject StatusTimeline
CPJ/0028419APPROVED44Completed2021 → 2024
CPJ/0041207APPROVED21 (1 remediation)Active2023 → —
CPJ/0009981REJECTED0—Planned— → —

Connections

Known and possible relationships

Inspect the published definitions and release context.

Domain or contextRelationship and published scope
LandProject, a documented relationship to Parcel (added this graduation)
BusinessBuildingPermit / Project, relationship integrity checked
GeographyWard on every Project, BuildingPermit, SiteInspection and OccupancyCertificate row
HousingProject / AffordableHousingProject are plain nullable fields, no relationship enforced today
Employment / Economya contractor Business participates in Employment and the Economic Modifier the same way any other business does, but no direct direct behavioral link is implemented
Infrastructureplanned. The current public release does not assert direct project-to-infrastructure-asset traversal
Full relationship reference 1 documented sections
Known and possible relationships.

Known and possible relationships.

Inspect the published definitions and release context.

Read the published detail

Connections follow the published domain scope. Optional, contextual and planned relationships retain their stated limits below.

Domain or contextRelationship and published scope
LandProject, a documented relationship to Parcel (added this graduation)
BusinessBuildingPermit / Project, relationship integrity checked
GeographyWard on every Project, BuildingPermit, SiteInspection and OccupancyCertificate row
HousingProject / AffordableHousingProject are plain nullable fields, no relationship enforced today
Employment / Economya contractor Business participates in Employment and the Economic Modifier the same way any other business does, but no direct direct behavioral link is implemented
Infrastructureplanned. The current public release does not assert direct project-to-infrastructure-asset traversal

Domain guide

Construction · archived guide edition

Striped Donkey V5.89 - 7 September 2026

Counts, prices and “live/today” certification statements reflect this dated edition. They are not a current rerun or offer. The current scope, known limits and accepted quote take priority.

Published scope and limits

Projects are administrative histories, not BIM or architectural models. Licence references are illustrative, not professional registrations. Affordable-housing linkage is unimplemented; construction does not automatically create a housing unit. Application and Review share one pending phase. Named real project exceptions are documented.

Read the source limits →
Accessible HTML reference 3 documented sections
Modelled entities.

Modelled entities.

Explore the entities and states represented by this domain.

Read the published detail

Every capability below is backed by release evidence or certification. The public page presents the data model rather than the physical design. Construction does not claim a physical-building (BIM/architectural) model it doesn't have — it models the administrative and regulatory process a development goes through.

the Project record family — synthetic construction and development projects, each with a sector, type, ward, status (Planned/Active/Suspended/Completed), budget and actual cost.

the Building Permit record family — application, approval, fee and expiry dates, permit type (new-construction, extension, renovation, change-of-use, demolition, temporary) and issuing authority.

Projects carry synthetic professional-license references and regulator/inspection context aligned to Lagos institutions such as LASBCA, COREN and ARCON. No record represents an actual professional or approval.

the Site Inspection record family — structural, electrical, plumbing, fire-safety, environmental, final and remedial inspection types, each with a real PASS/CONDITIONAL/FAIL/PENDING outcome.

Every project progresses through four tracked phases — Foundation, Structure, MEP, Finishing — rather than appearing instantly as a completed structure.

the Occupancy Certificate record family — issued only against a project whose own status is Completed, a real, checked invariant (certification check), not an assumption.

Synthetic by design: FCTE construction projects, permits, professional-license references and inspections are analytical representations of a plausible development process. They do not represent actual developments, regulatory approvals, or identifiable real engineers, architects or contractors.

Construction models how the physical city comes into existence — not simply what buildings exist today.

  • Parcel
  • OwnershipHistory
  • TitleStatus
  • DisputeRiskProfile
  • MarketValueIndex
  • Project
  • BuildingPermit
  • ProjectPhase
  • SiteInspection
  • OccupancyCertificate
  • HousingUnit
  • Tenancy
  • UrbanDevelopmentProject
  • (residential occupancy)
A building should not appear overnight.

A building should not appear overnight.

Inspect the published definitions and release context.

Read the published detail

FCTE preserves the process that created the synthetic built environment — not only the final state.

Representative public release example — exact live identities and run-level values are intentionally not published. Explore the release-backed analysis examples in City Twin™ for current data.

The public lifecycle uses one pre-decision pending phase. “Application” and “Review” are human-readable views of that phase rather than claims of two separate production states.

All status values above (PENDING/APPROVED/REJECTED/EXPIRED/REVOKED/SUSPENDED; PASS/CONDITIONAL/FAIL/PENDING; ACTIVE/EXPIRED/REVOKED/SUSPENDED) are the governed public status vocabulary in the current release.

The architecture is shared. The regulatory environment is not.

The architecture is shared. The regulatory environment is not.

Inspect the published definitions and release context.

Read the published detail

Construction's public semantic entity coverage is aligned across Lagos. The issuing authorities, inspecting departments and professional license references are genuinely different real institutions — no integrity rule in Core, each jurisdiction's own extension enforces its own vocabulary.

LASBCA (Lagos State Building Control Agency) has been the primary permit/inspection/occupancy authority since becoming operational in 2012, under the real 2010 Lagos State Urban and Regional Planning and Development Law.

FCTE reuses common construction architecture while allowing Lagos to implement its own regulatory rules, institutions and evidence — not the acronyms themselves, but the fact that the model genuinely diverges where the real cities do.

All 8 events are real, dated rows in the shared historical-event record, category-tagged for Construction, and feed ConstructionEventIndex — the same per-year modifier mechanism every published domain uses to perturb permit-approval-rate and inspection-outcome via the shared event-modifier function.

Construction began 5 May 2017, commissioned 10 June 2021, contracted to China Civil Engineering Construction Corporation (CCECC), financed via a real China Eximbank facility.

Both contractor records are marked DORMANT, not ACTIVE or LIQUIDATED — CRBC and CCECC are real, active, globally-operating contractors; only their local project engagement has concluded. This is a deliberate, disclosed distinction, not a claim that either company itself is defunct.

Open Construction Evidence Catalogue →

EventCountryDateSeverityWhat it represents
LASBCA-LAW-2010Nigeria2011-06-010.50Lagos State Urban and Regional Planning and Development Law establishes LASBCA's legal foundation
LASBCA-OPERATIONAL-2012Nigeria2012-08-120.55LASBCA begins enforcement operations — Lagos's first dedicated agency-level building-control regulator
SYNAGOGUE-COLLAPSE-2014Nigeria2014-09-160.55115+ deaths — one of the deadliest building collapses in Nigerian history
IKOYI-COLLAPSE-2021Nigeria2021-11-010.5021-storey building collapse, 42 deaths — building had exceeded its approved floor count

Evidence & limits

Scope and known limits

Projects are administrative histories, not BIM or architectural models. Licence references are illustrative, not professional registrations. Affordable-housing linkage is unimplemented; construction does not automatically create a housing unit. Application and Review share one pending phase. Named real project exceptions are documented.

Evidence, findings and release history 2 documented sections
Known limits.

Known limits.

Projects are administrative histories, not BIM or architectural models. Licence references are illustrative, not professional registrations. Affordable-housing linkage is unimplemented; construction does not automatically create a housing unit. Application and Review share one pending phase. Named real project exceptions are documented.

Read the published detail

Synthetic projects, permits and occupancy certificates do not correspond to actual developments or regulatory approvals unless explicitly documented otherwise (the two real, named infrastructure projects above).

CORENLicenseRef, ARCONLicenseRef, NCALicenseRef and EBKLicenseRef are real-shaped reference fields, not registrations against any real engineer, architect or contractor.

Project and AffordableHousingProject link are plain nullable fields with no relationship today. Don't assume every construction project currently creates a Housing Unit — that linkage isn't implemented yet.

The public model has one pre-decision pending phase. The plain-English “Application” and “Review” labels describe that same phase rather than separate production states.

Unless represented elsewhere, a construction project is not a Building Information Model (BIM) or detailed architectural drawing set — it is an administrative and regulatory-lifecycle record.

The remaining ~100,000+ generated projects per city are fully synthetic, real-shaped records, not disguised real developments.

View All Construction Limitations →

A project cannot complete a lifecycle that never happened.

A project cannot complete a lifecycle that never happened.

Inspect the published definitions and release context.

Read the published detail

Construction carries some of the clearest lifecycle invariants on this site: a permit can't approve before it's applied for, an inspection can't predate the project it inspects, and an occupancy certificate can't exist against a project that isn't actually Completed.

Open Construction Realism Report →

The published construction certification set covers volume sufficiency, relationship integrity, temporal ordering, lifecycle completeness and realism checks for schedule and cost behavior. Internal rule expressions remain controlled.

C13–C15 were added for the two genuinely new capabilities this graduation introduced; C16 is a regression guard added after a real external audit found unbounded inspection dates.

Explore Every Construction Check →

  • C05 — BuildingPermit temporal order (ApprovalDate ≥ ApplicationDate)
  • C07 — completed-unit count within [0, PlannedUnits]
  • C09 — permit/contractor-business reference integrity
  • C11 — planned completion date > StartDate
  • C12 — Permit approval rate plausible (30–80%)
  • C13 — Every phased project has exactly 4 phases
  • C14 — historical construction index populated
  • C15 — OccupancyCertificate only issued against Completed projects
  • C16 — inspection date not before linked Project/Permit dates
  • C10 — SiteInspection PASS rate plausible (30–90%)

Access & datasets

Scope your data request

Choose the records, dates and connected domains you need. Final availability, delivery scope and licensing are agreed with your quote.

Published access and recorded examples 1 documented sections
Recorded example.

Recorded example.

Explore the supplied synthetic example and its source references.

Read the published detail

A real Construction Project, started 2018-06-07.

Real ProjectPhase and SiteInspection rows track the build against this real, dated project.

A Building Permit enters the applicable approval process with its own jurisdiction's authority.

A real OccupancyCertificate, issued by LOCAL-GOVT — the completed development entering the synthetic built environment.

Land → Project → Permit → Build → Inspect → Complete → City.

Available as Standalone Domain · Multi-Domain Bundle · Full City Twin™