As-Planned vs. As-Built Comparison
Compares the original as-planned schedule against actual execution (as-built), identifying task-level variance and execution performance.\n\nOutput:\n- Per-task variance (start/finish/duration)\n- Variance classification (on_time, minor_slip, moderate_slip, severe_slip, early_completion, incomplete)\n- Critical path overlay (planned vs. actual CP)\n\nOptional analysis:\n- include_logic_diff — detect added/removed/modified dependencies\n- include_resource_diff — compare resource assignment changes\n\nMatch strategies: exact_id (default), fuzzy_name, wbs.\n\nTier access: Starter and above.\n\nStandards: AACE RP 29R-03 (Forensic Schedule Analysis).
Request
- Base URL: https://api.bellatorsi.com (the document declares no server; this is the origin it was published from)
- URL: https://api.bellatorsi.com/api/v1/forensics/as-planned-vs-as-built
- Auth: none declared
Headers
Request body
Example request
{
"as_planned": {
"tasks": [
{
"duration_days": 10,
"id": "T1",
"name": "Design Phase",
"percent_complete": 0,
"planned_finish": "2026-01-15",
"planned_start": "2026-01-01",
"predecessors": [],
"resource": "Team A"
}
]
},
"as_built": {
"tasks": [
{
"duration_days": 10,
"id": "T1",
"name": "Design Phase",
"percent_complete": 0,
"planned_finish": "2026-01-15",
"planned_start": "2026-01-01",
"predecessors": [],
"resource": "Team A"
}
]
}
}Response
As-planned vs. as-built comparison completed
Changes
No recorded changes to this operation across all 1 revision of this API.