Project data checks

Primer

Why a core?

This example proposes a small shared project record. It illustrates how explicit fields and checks can expose inconsistencies; it is not an official Project Data Standard, a full JSON Schema validator or evidence of reliable forecasting.

What’s validated?

Required fields, ID and codelist formats, real dates, start/finish order, finite non-negative amounts, same-currency CAPEX budgets, provenance age and duplicate IDs. Actuals mean spend to date; forecast means total expected spend. Early completion and forecasts below baseline are allowed.

How to use

Try this: set a milestone actual date before its planned date, then change a CAPEX funding currency. The first is allowed; the second blocks the comparison. Tune tolerance/SLA, validate, then download the results with the assessed settings. A check report is not certification or approval.

Playground

SLA (days): Tolerance (sum vs baseline):

Payload (JSON)

Nothing is sent anywhere; validation happens entirely in your browser.

Example-rule results

Scores are the percentage of these illustrative checks that pass, not a measure of project health or readiness. — means no applicable checks. Unknown fields and many domain rules are not assessed.

Ready

Last run: —

Checks passed (%)

—

Completeness

—

Validity

—

Consistency

—

Timeliness

—

Uniqueness

—

Rule violations

Rule	Severity	Message

Parsed header

Project ID

—

Name

—

Phase

—

Owner

—

RAG

—

Visuals

These update after you press Validate.

Milestone timeline

Planned ● Forecast ◆ Actual ▲

Funding vs Baseline/Forecast/Actual

Compares amounts only where the currency matches the baseline. The budget comparison assumes the CAPEX lines cover the whole baseline; partial years are not proof of a funding shortfall. No currency conversion is performed.

Codelists

Filter:

DeliveryPhase

ApprovalStage

RAG

Declared provenance

Shows actors and systems declared in project.provenance and the was_derived_from link. These are assertions in the payload, not independently verified lineage.

Export report

—

(validate to populate)

Illustrative rules and fictional example data. Nothing is uploaded or saved between visits; download any report you want to keep.