Signals Synergy: Failed Work Order Status

The 25.10 release of Signals introduces a new feature allowing Contract Research Organizations (CROs) to mark a Work Order as Failed when it cannot be completed. This update enhances transparency and communication between CROs and Sponsors, ensuring that failed synthesis or design attempts are properly documented and communicated.

Key Features
• Failed Work Order Status:
• CROs can mark a Work Order as Failed during submission if synthesis or design efforts are unsuccessful.
• A reason for failure must be provided during submission.
• Kanban Board Integration:
• The Failed status is visually represented on the Work Order Kanban Board.
• This allows CROs and Sponsors to track failed Work Orders alongside other statuses such as To-Do, In Progress, and Submitted."
• External Notifications:
• The Failed status triggers an external notification, ensuring all relevant parties are informed promptly.
• Notifications can be configured to include details about the failure reason.

Use Case Example
A CRO attempts to synthesize a compound as part of a Work Order. Despite several successful steps documented in Synergy Experiments, the final synthesis fails. Instead of submitting the Work Order as incomplete, the CRO marks it as Failed and provides a detailed explanation. This status is then visible on the Kanban Board and communicated to the Sponsor through external notifications.

Benefits
• Improved Communication:
• Sponsors are immediately informed about failed Work Orders, enabling them to reassess priorities or provide additional guidance.
• Enhanced Tracking:
• The Kanban Board's integration ensures failed Work Orders are easily identifiable and can be analyzed for patterns or recurring issues.
• Streamlined Workflow:
• CROs can focus on other tasks without delays caused by unresolved Work Orders.

Practical Next Steps
1. For CROs:
• Familiarize yourself with the updated Kanban Board and notification settings.
• Ensure reasons for failure are documented clearly to facilitate Sponsor understanding.

2. For Sponsors:
• Review failed Work Orders promptly and provide feedback or alternative approaches to CROs.
• Use the Kanban Board to monitor the status of all Work Orders, including failed ones.

3. For Administrators:
• Configure external notifications to include Failed status updates.
• Train CRO users on how to use the new feature effectively.