Conflicts and constraints

A booking conflict records a raised issue against a booking with a title, severity, reporting date, reporter and owner. When a new conflict is Open, the configured triage workflow moves it to Triaged and writes an operation receipt. The workflow refuses to triage an item whose status has changed or whose severity is empty, and records the failed attempt. Triage means the issue has entered review. The delivery team still needs to investigate, fix, verify and close it using the available states.

Resource constraints hold a different kind of exception: a delivery risk with category, probability, impact, mitigation and owner. The Project Manager can use them to discuss a schedule or resource concern before it becomes a blocked assignment. For example, a vendor dependency might threaten the date of a work group. The lead records the probability and impact, gives the constraint to an owner and follows its mitigation while the booking remains active.

• Raised issues. Conflicts identify a specific problem on a booking and its severity.
• Forward risks. Constraints identify a possible effect and the intended mitigation.
• Execution outcome. Receipts show whether automated triage succeeded or was blocked.

Define when a blocked work item also needs a conflict or constraint record. Set a practical severity scale for the team and decide who becomes the owner after an issue is raised. Agree what evidence the owner needs before marking an issue verified or closed. For constraints, make probability and impact judgments explicit, and revisit mitigation after a schedule change. Establish how the booking owner hears about a high-severity issue, since the issue and the overall engagement have separate owners.

Raise a conflict against a live booking, assign a severity and owner, and check Open Booking Conflicts. The triage workflow should move the item to Triaged and add a successful receipt. Raise a second conflict without severity and confirm it does not pass the guard rail. Then record a resource constraint on the same booking with an owner and mitigation. The Delivery Lead should see both exceptions in Operations Overview and be able to trace each to the booking. The issue’s triage should not silently mark the constraint resolved.

When an assigned task is blocked, use Blocked Booking Resources to find the work affected. The owner can decide whether the problem requires a changed due date, a new mitigation or a status change on the booking. Keep the decision on the relevant record so the next reviewer can follow it.

• Open Booking Conflicts — Raised and in-progress issues, with severity, date and owner.
• Open Resource Constraints — Risks still open or being monitored, with category and impact.
• Blocked Booking Resources — Delivery items affected by an unresolved problem.

Use exception follow-up to trace a raised issue through review.