Key concepts
Expand each section below for more information.
What is a phase guard?
Phase guards work hand-in-hand with data quality rules. Data quality rules allow you to validate that any required or recommended data or actions have been completed on your work at the right time and, where necessary, prevent work progression until those rules have been met.

Use data quality phase guards to prevent users from progressing from one stage to another without completing the required data. Configure phase guards against the phase model of the work type.

Where do I see data quality rules?
Data quality rules can be made available to the user on your main portal using the data quality widget. The widget allows users to immediately see and rectify missing information before progressing the work. In addition, the user is prompted to fill out any missing or mandatory data on transition from one phase to another.
How do I configure a phase guard?
There are three steps to creating a data quality rule.
- Create a matching rule - this is used to validate the data and determine whether or not you have missing items.
- Creating the data quality rule - this determines the available actions and guidance the system will give the user when a piece of data is missing.
- Add the phase guard to your work type phase plan.
Are data quality rules inherited between work types?
Yes, data quality rules can be inherited between work types. If you create a new derived type, the type inherits the phase plan from the parent work type. If you also wish to inherit the data quality rules, click the Copy guards from parents button on the phase plan screen within your work type portal.

Phase Guards
You can create data quality rules within the modeller area of the system. Go to Modeller > Work Type Modeller and select the work type you wish to work with. In the work type portal, navigate to the phase model area.
To add a phase guard, edit the transition where the guard is required. Select the line between two phases, right-click and select edit to open the Edit transition blade. You can also double-click on the transition line to edit it.

To apply a guard, select the Phase Guards navigation option at the bottom of the blade. The shield icon and count indicate the number of guards already implemented.

Phase Guard Types
You can apply several different phase guard types to a phase transition.

Data | Description |
---|---|
Data Quality Guards
|
This type of guard will allow you to add a data quality rule you have defined for the work type to a phase guard. Add these to work types on the data quality rule page of the work type definition portal. ![]() |
All Data Quality Guards | This guard enforces all data quality rules that apply to this work type. |
e-Signature |
e-Signature allows you to get the user to confirm the information manually. The user's signature will be visible on the guard if a signature is assigned to their profile. ![]() |
Information Only
|
Information Only phase guards display a message to the user but do not require any action. ![]() ![]() |
Mandatory Action Plan Items
|
This guard checks that all mandatory in-phase tasks have been completed. ![]() |
Child Work Items Completed | This guard checks that all child work items have been completed. |
Mandatory Participants Phase Guard
|
The Mandatory Participants phase guard allows you to block a phase transition if all mandatory participants have not been completed. By default, this guard uses the participant role configuration for the work type, which indicates whether participants are mandatory, recommended, or optional. You can specify the participant roles to check if the user role configuration model is switched off. This is useful where you want the participants to become mandatory at certain phases. ![]() |
System Phase Guards | In addition to the configurable phase guards above, ShareDo contains several pre-built Phase Guards for common purposes. It's important to note that these don't appear in the Phase Plan screens but run in the background. Should you want to turn off this default behaviour, see the article Managing System Phase Guards. |