POST/api/v1/forensics/delay-analysis

Delay Attribution Analysis

Identifies, quantifies, and attributes schedule delays across four analysis steps.\n\nSteps:\n1. Variance detection — identifies delayed tasks vs baseline\n2. Float analysis — tracks critical path and float consumption\n3. Causal chains — traces delay propagation through dependency network\n4. Recommendations — recovery actions from the delayed tasks and the paths they sit on\n\nMethodologies: windows (default), contemporaneous, collapsed_as_built.\n\nTier access: Starter and above.\n\nSource: these three methods are this route's. No recommended practice was read for them, 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
tasks	array<unknown>	Required	No description in OpenAPI contract.
tasks[].id	string	Required	Unique task identifier
status_date	string	Required	No description in OpenAPI contract.
options	object	Optional	Options for delay analysis.
options.min_impact_days	integer	Optional	No description in OpenAPI contract.
options.include_causal_chains	boolean	Optional	No description in OpenAPI contract.
options.include_float_consumption	boolean	Optional	No description in OpenAPI contract.
options.confidence_threshold	number	Optional	No description in OpenAPI contract.
options.methodology	string	Optional	No description in OpenAPI contract.
options.include_concurrent	boolean	Optional	No description in OpenAPI contract.
options.include_delay_categories	boolean	Optional	No description in OpenAPI contract.
options.use_half_step	boolean	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_DelayAnalysisData_"
}

Authentication

API key required

Reference details

Operation ID: forensics_delay_analysis
Section: Forensics
Tags: Forensics
Playground link: /playground?endpoint=%2Fapi%2Fv1%2Fforensics%2Fdelay-analysis&method=post

Was this page helpful?

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

Topic: Delay Attribution Analysis · Page: /docs/api-reference/forensics_delay_analysis

Report an issue Suggest improvement

Terms Privacy Contact

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