Changes to Create a change order. `originalRevisionItem.id` is required and `disposition.id`, when sent, must resolve to a change order disposition. The change order's sequential number is assigned server-side, `requestedUtc` defaults to the moment of creation, and a change order created Completed is stamped with `completedUtc`. The change order is created with no impacted records and no tasks. Creates are not idempotent: a retried request creates a second change order.

POST /api/change-orders

Every recorded change to this endpoint, newest first. Back to the operation