POST/api/v1/forensics/change-tracking

Time-Series Change Detection

Detects field-level changes across schedule snapshots in six categories.\n\nChange categories:\n- baseline — baseline date or duration differs between snapshots\n- actual — an actual date differs between snapshots\n- forecast — forecast date drift\n- logic — dependency adds, removes, or lag changes\n- resource — resource assignment changes\n- progress — progress decrease or an erratic pattern\n\nComparison modes: all_periods (default), latest, specific_dates.\n\nTier access: Starter and above.\n\nSource: the six categories are this route's. DECM 06A504a and 06A504b divide tasks whose actual start or actual finish no longer equals the previously reported actual by tasks that have that actual date. The v8.1 tracker allows up to 10 percent. This route does not compute that ratio. GAO-16-89G practice 10 says a baseline schedule is the basis for managing scope, time, and resources, and that it is under configuration control. That sentence is not this diff.\n\nOutput: comparison_summary, changes_by_category (all 6 categories), impact_analysis, trends, compliance_tags, processing_metadata.

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
current_schedule	object	Required	The current schedule submitted for change tracking comparison.
current_schedule.tasks	array<unknown>	Required	Current task array
current_schedule.tasks[].id	string	Required	Unique task identifier
current_schedule.status_date	string	Required	Current schedule status date (ISO 8601)
schedule_history	array<unknown>	Required	Historical snapshots (min 1 required)
schedule_history[].snapshot_date	string	Required	Snapshot date (ISO 8601 YYYY-MM-DD)
schedule_history[].tasks	array<unknown>	Required	Task array at snapshot time
schedule_history[].tasks[].id	string	Required	Unique task identifier
options	object	Optional	Options controlling change tracking behaviour.
options.comparison_mode	string	Optional	No description in OpenAPI contract.
options.change_categories	array<string>	Optional	Categories: baseline, actual, forecast, logic, resource, progress, all
options.include_impact_analysis	boolean	Optional	No description in OpenAPI contract.
options.include_trends	boolean	Optional	No description in OpenAPI contract.
options.include_details	boolean	Optional	No description in OpenAPI contract.
options.materiality_thresholds	object	Optional	Overridable materiality thresholds for change detection.
options.materiality_thresholds.date_change_days	integer	Optional	Min days for a date change to be material
options.materiality_thresholds.progress_change_pct	number	Optional	Min % decrease to flag

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_ChangeTrackingData_"
}

Authentication

API key required

Reference details

Operation ID: forensics_change_tracking
Section: Forensics
Tags: Forensics
Playground link: /playground?endpoint=%2Fapi%2Fv1%2Fforensics%2Fchange-tracking&method=post

Was this page helpful?

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

Topic: Time-Series Change Detection · Page: /docs/api-reference/forensics_change_tracking

Report an issue Suggest improvement

Terms Privacy Contact

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