---
title: "Validate Schedule"
method: POST
path: "/api/v1/analysis/validate"
tags: ["Analysis"]
---

# Validate Schedule

`POST /api/v1/analysis/validate`

## 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/analysis/validate`
- Auth: none declared

Validate schedule for errors and warnings

## Headers

- `x-api-key` string, nullable
- `authorization` string, nullable
- `x-bellator-internal-dispatch` string, nullable

## Request body

- ScheduleRequest: Request model for schedule analysis. This is the base schedule payload used across all Tier 1 and Tier 2 APIs. Additional Tier 2-specific fields enable full DCMA 14-Point compliance.
  - `tasks` Task[], required: List of tasks in the schedule
    - `id` string, required: Unique task identifier
    - `duration_days` number: Task duration in days
    - `predecessors` union[]: List of predecessor task IDs or dependency links. Supports: 'T1', 'T1FS+5 d', 'T2SS-2 d', or DependencyLink objects
      - union
        - string
        - object
        - DependencyLink: Rich dependency link with relationship type and lag/lead. Supports parsing from various scheduling tool formats including: - MS Project: "10FS+5 d", "/path/file.mpp/10FS+5 d" - Primavera P6: Similar format with XER encoding - Server-based: "<ServerFile>10FS+5 d" - Simple: "10" (defaults to FS with zero lag) Examples: >>> DependencyLink(task_id="10", relationship_type="FS", lag_days=5.0) >>> DependencyLink.from_string("10FS+5 d") >>> DependencyLink.from_string("15SS-2 d")
          - `task_id` string, required: Predecessor task ID
          - `relationship_type` 'FS' | 'SS' | 'FF' | 'SF': Task relationship types per PMBOK 6.3.2.2. Attributes: FINISH_START: Predecessor finish → successor start (most common, ~90%) START_START: Predecessor start → successor start (~5%) FINISH_FINISH: Predecessor finish → successor finish (~4%) START_FINISH: Predecessor start → successor finish (rare, ~1%)
          - `lag_days` number: Lag (positive) or lead (negative) in days
          - `is_external` boolean: True if link to external project file
          - `external_path` string, nullable: Path to external file if is_external=True
    - `name` string, nullable: Task name
    - `resource` string, nullable: Resource assigned to task
    - `resources` string[]: List of resources assigned (for multi-resource tasks)
    - `percent_complete` number: Percent complete (0-100)
    - `physical_percent_complete` number, nullable: Physical percent complete (0-100). Manual EVM entry by scheduler (MSP PhysicalPercentComplete). Authoritative for BCWP calculations. Captured separately from percent_complete on MSP imports.
    - `planned_start` string, date, nullable: Planned start date (ISO 8601)
    - `planned_finish` string, date, nullable: Planned finish date (ISO 8601)
    - `actual_start` string, date, nullable: Actual start date (ISO 8601)
    - `actual_finish` string, date, nullable: Actual finish date (ISO 8601)
    - `baseline_start` string, date, nullable: Baseline start date (ISO 8601)
    - `baseline_finish` string, date, nullable: Baseline finish date (ISO 8601)
    - `constraint_type` string, nullable: Constraint type: ASAP, ALAP, SNET, SNLT, FNET, FNLT, MSO, MFO
    - `constraint_date` string, date, nullable: Constraint date if applicable (ISO 8601)
    - `task_type` string, nullable: Task type classification. Valid values: task (default), milestone, loe, summary, schedule_margin, planning_package, slpp, schedule_visibility. Drives DCMA check exclusions per PAM 200.1 § 3.2.
    - `wbs_code` string, nullable: WBS code (e.g., '1.2.3')
    - `organization_code` string, nullable: Org/dept identifier for anomaly categorization (Progress Audit)
    - `custom_field_map` object, nullable: All WBS/OBS-pattern custom fields discovered in this MS Project file, keyed by alias (e.g., 'CWBS', 'OBS'). Null for XER imports or when no matching aliases exist.
    - `forecast_start` string, date, nullable: Current forecast start date (ISO 8601)
    - `forecast_finish` string, date, nullable: Current forecast finish date (ISO 8601)
    - `total_float_days` number, nullable: Pre-computed total float in days. Auto-computed by CPM if absent.
    - `baseline_duration_days` number, nullable: Baseline duration in days. Auto-computed from baseline dates if absent.
    - `delay_category` string, nullable: Delay attribution category. Valid values: owner, contractor, design, procurement, weather, force_majeure.
    - `earned_value` number, nullable: Earned Value (BCWP) in cost units. Requires options.include_ev_validation.
    - `budgeted_cost` number, nullable: Budgeted Cost of Work Scheduled (BCWS) in cost units.
    - `approval_required` boolean, nullable: Whether this task requires explicit approval before it can start.
    - `approval_status` string, nullable: Approval workflow state. Valid values: not_required, pending, approved, rejected.
  - `start_task_ids` string[]: Task IDs that anchor the project start (DCMA Check #1). If empty, tasks with no predecessors are treated as start tasks.
  - `finish_task_ids` string[]: Task IDs that anchor the project finish (DCMA Check #1). If empty, tasks with no successors are treated as finish tasks.
  - `status_date` string, date, nullable: Data date / status date for progress validation (ISO 8601 YYYY-MM-DD)
  - `target_finish_date` string, date, nullable: Target project finish date or key milestone date for CPLI calculation (ISO 8601)
  - `baseline_approved_date` string, date, nullable: Date when baseline was approved (for governance tracking)
  - `resource_availability` AppModelsSchemasResourceAvailability1[]: Per-resource availability for over-allocation detection (Resource Analysis API).
    - `resource_name` string, required: Resource name (must match tasks[*].resources)
    - `available_from` string, date, nullable: Start of availability window (ISO 8601). Null = project start.
    - `available_to` string, date, nullable: End of availability window (ISO 8601). Null = project finish.
    - `units_per_day` number: Available resource-units per working day (default: 1.0 = 100%)
  - `options` ValidationOptions: Options for POST /api/v1/schedule/validate (v0.2.0).
    - `calculate_pop` boolean: Calculate Probability of Performance (PoP) score (v0.2.0).
    - `include_pop_details` boolean: Include dimensional PoP breakdown in response.
    - `strict_mode` boolean: Treat warnings as errors (fail validation on any issue).
    - `check_dcma_compliance` boolean: Include DCMA-specific checks (#1, #8).

## Response `200`

Successful Response

- BellatorResponseValidationData
  - `status` 'pass' | 'fail' | 'warning' | 'info', required: Top-level result status — always present in every response.
  - `score` number, nullable
  - `grade` 'A' | 'B' | 'C' | 'D' | 'F': Letter grade derived from a 0–100 score. Null on non-scoring endpoints.
  - `summary` string, nullable
  - `breakdown` object, nullable
  - `findings` Finding[]
    - `code` string, required: Stable machine-readable identifier e.g. DCMA_CHECK_8_HIGH_DURATION
    - `severity` 'critical' | 'high' | 'medium' | 'low' | 'info', required: Severity level for findings; reused as priority level for recommendations.
    - `title` string, required: Short human-readable label
    - `description` string, required: Full explanation of the issue
    - `standard` string, nullable: Standard citation e.g. 'DCMA PAM 200.1 Check #8'
    - `affected_tasks` string[]: Task IDs implicated by this finding
    - `metric_value` number, nullable: Observed measurement e.g. 60.0 days
    - `threshold` number, nullable: Threshold that was violated e.g. 44.0 days
  - `recommendations` Recommendation[]
    - `priority` 'critical' | 'high' | 'medium' | 'low' | 'info', required: Severity level for findings; reused as priority level for recommendations.
    - `action` string, required: What to do — specific and actionable
    - `standard` string, nullable: Supporting standard citation
    - `finding_codes` string[]: Finding.code values this recommendation addresses
  - `data` ValidationData: Data payload for POST /api/v1/schedule/validate.
    - `valid` boolean, required: Whether the schedule is valid
    - `errors` string[]: List of validation errors
    - `warnings` string[]: List of validation warnings
    - `probability_of_performance` ProbabilityOfPerformance: Probability of Performance (PoP) — schedule deliverability score (v0.2.0).
      - `pop_score` number, required
      - `rating` string, required
      - `confidence` number, required
      - `dimensions` object, required
      - `risk_factors` PoPRiskFactor[]
        - `factor` string, required
        - `score` number, required
        - `severity` string, required
        - `description` string, required
        - `recommendation` string, required
      - `recommendations` string[]
  - `simulation` SimulationEnvelope: Probabilistic simulation outputs for Tier 3 endpoints. Null on all Tier 1 and Tier 2 responses. When Tier 3 launches, this field transitions from null to populated without changing any other envelope field — existing consumers are unaffected.
    - `method` string, required: Simulation method: monte_carlo | latin_hypercube
    - `trial_count` integer, required
    - `duration_days` PercentileResult: Percentile distribution across simulation trials. Reserved for Tier 3 Monte Carlo / risk simulation endpoints (v0.3.0+).
      - `p10` number, required: 10th percentile outcome
      - `p50` number, required: 50th percentile (median)
      - `p80` number, required: 80th percentile — common contract delivery threshold
      - `p90` number, required: 90th percentile
      - `mean` number, required
      - `std_dev` number, required
    - `cost` PercentileResult: Percentile distribution across simulation trials. Reserved for Tier 3 Monte Carlo / risk simulation endpoints (v0.3.0+).
      - `p10` number, required: 10th percentile outcome
      - `p50` number, required: 50th percentile (median)
      - `p80` number, required: 80th percentile — common contract delivery threshold
      - `p90` number, required: 90th percentile
      - `mean` number, required
      - `std_dev` number, required
    - `completion_date` object, nullable: Map of p-value strings to ISO completion dates e.g. {'p50': '2027-04-15'}
  - `metadata` ResponseMetadata, required: Audit trail and processing context — always present, never null.
    - `task_count` integer, required: Number of tasks in the submitted schedule
    - `processing_time_ms` integer, nullable: Wall-clock processing time in milliseconds
    - `api_version` string: API version that produced this response
    - `endpoint` string, required: Endpoint path e.g. /api/v1/health/score
    - `standards_applied` string[]: Standards consulted during analysis e.g. ['DCMA PAM 200.1', 'GAO BP-2']
    - `confidence` number, nullable: Confidence in the result (0–1). Present on scoring endpoints.
    - `status_date` string, nullable: ISO date used as analysis reference point. Present on time-aware analyses.

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/bellatorsi/apis/bellator-schedule-intelligence-apis.md) · [All operations](https://skmtc.dev/bellatorsi/apis/bellator-schedule-intelligence-apis/llms.txt) · [OpenAPI document](https://skmtc.dev/bellatorsi/apis/bellator-schedule-intelligence-apis/revisions/03e7b786e43b?raw)