Forensics

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 — AACE RP 47R-11 prioritized recovery actions\n\nMethodologies: windows (default), contemporaneous, collapsed_as_built.\n\nTier access: Starter and above.\n\nStandards: AACE RP 29R-03, AACE RP 47R-11.

post/api/v1/forensics/delay-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/delay-analysis
  • Auth: none declared

Headers

x-api-keystring nullable
authorizationstring nullable
x-bellator-internal-dispatchstring nullable

Request body

status_datestring required

Example request

{
  "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

Delay analysis completed successfully

status'pass' | 'fail' | 'warning' | 'info' required

Top-level result status — always present in every response.

scorenumber nullable
grade'A' | 'B' | 'C' | 'D' | 'F'

Letter grade derived from a 0–100 score. Null on non-scoring endpoints.

summarystring nullable
breakdownobject nullable

Changes

No recorded changes to this operation across all 1 revision of this API.