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

As-Planned vs. As-Built Comparison (Async)

Submit async as-planned vs. as-built comparison for large schedules. Poll GET /api/v1/jobs/{job_id}.

Request example

json

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

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.

json

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

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

Field	Type	Required	Description
type	string	Required	Documentation URL for the code: https://bellatorsi.com/problems/<slug>.
title	string	Required	Short summary of the problem type.
status	integer	Required	HTTP status code.
detail	string	Required	What went wrong in this request.
code	string	Required	Stable UPPER_SNAKE machine code.

json-schema

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

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

Was this page helpful?

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

Topic: As-Planned vs. As-Built Comparison (Async) · Page: /docs/api-reference/forensics_as_planned_vs_as_built_async

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