POST/api/v1/forensics/as-planned-vs-as-built

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\nSource: the variance classes and the critical-path overlay are this route's. No recommended practice was read for this comparison, so none is named.

Try in Playground

Request example

json

{
  "tasks": [
    {
      "id": "T1",
      "duration_days": 5
    }
  ]
}

Request fields from OpenAPI contract

Required fields and the optional fields that change this call are listed here. The shared task model stays on the task schema guide.

This table is generated from the endpoint schema in openapi.json.

Field	Type	Required	Description
as_planned	object	Required	As-planned (original baseline) schedule.
as_planned.tasks	array<unknown>	Required	No description in OpenAPI contract.
as_planned.tasks[].id	string	Required	Unique task identifier
as_built	object	Required	As-built (actual execution) schedule.
as_built.tasks	array<unknown>	Required	No description in OpenAPI contract.
as_built.tasks[].id	string	Required	Unique task identifier
options	object	Optional	Options for as-planned vs. as-built analysis.
options.include_logic_diff	boolean	Optional	No description in OpenAPI contract.
options.include_critical_path_overlay	boolean	Optional	No description in OpenAPI contract.
options.include_resource_diff	boolean	Optional	No description in OpenAPI contract.
options.match_strategy	string	Optional	No description in OpenAPI contract.
options.fuzzy_threshold	number	Optional	No description in OpenAPI contract.
options.min_variance_days	integer	Optional	No description in OpenAPI contract.
options.exclude_task_types	array<string>	Optional	No description in OpenAPI contract.
options.methodology	string	Optional	No description in OpenAPI contract.

Response example

json

{
  "score": 92,
  "grade": "A"
}

Response fields from OpenAPI contract

This table is generated from the endpoint response schema in openapi.json.

Field	Type	Required	Description
status	string	Required	Top-level result status — always present in every response.
metadata	object	Required	Audit trail and processing context — always present, never null.
metadata.task_count	integer	Required	Number of tasks in the submitted schedule
metadata.endpoint	string	Required	Endpoint path e.g. /api/v1/health/score

Schema

json-schema

{
  "$ref": "#/components/schemas/BellatorResponse_AsPlannedVsAsBuiltData_"
}

Authentication

API key required

Reference details

Operation ID: forensics_as_planned_vs_as_built
Section: Forensics
Tags: Forensics
Playground link: /playground?endpoint=%2Fapi%2Fv1%2Fforensics%2Fas-planned-vs-as-built&method=post

Was this page helpful?

Your feedback helps us improve docs, reference pages, and Playground flows.

Topic: As-Planned vs. As-Built Comparison · Page: /docs/api-reference/forensics_as_planned_vs_as_built

Report an issue Suggest improvement

Terms Privacy Contact

Schedule analysis guidance. Not legal advice. You remain responsible for contract and agency compliance.