# Readying & Reviewing

{% hint style="info" %}
**Who can use this feature?**

Task Owners can make their part of the plan Ready&#x20;

***

Reviewers and Admins can approve plans on behalf of other Task Owners.
{% endhint %}

Before a plan is published, you can mark your part as Ready to signal it’s up to date and good to go. Even if you don’t mark it as ready, your tasks will still be included in the published version.

## Unresolved Issues

***

If you own Tasks in the lookahead period, it's your responsibility to make sure they're accurate, up to date and don't have any outstanding Unresolved Issue. This means Task Owners need to be mitigating any Clashes, adding Missing Data and resolving any Overdue Blockers.

<figure><img src="https://2273109354-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLu0mYklsCTm7XQm3ZGqv%2Fuploads%2F9jRU6vZa6SgvGGKqlKYF%2FMake%20Read%2C%20With%20issues.svg?alt=media&#x26;token=0a108023-be2d-4650-a57d-e7c5de96d464" alt=""><figcaption></figcaption></figure>

#### To see unresolved issues in your Plan:

* Click your Publishing Deadline in the top right of the page
* This will open the `Make Ready Window`
* You'll see a count of all your `Clashes`, `Missing Data` and `Overdue Blockers`
* Click any of the counts to open the relevant panel and start resolving issues

<details>

<summary>Issue definitions </summary>

| Issue        | Meaning                                                                                                        |
| ------------ | -------------------------------------------------------------------------------------------------------------- |
| Clashes      | Any unresolved clashes within the lookahead period                                                             |
| Blockers     | Any overdue Blockers within the lookahead period                                                               |
| Missing Data | Any tasks missing Publication Requirements set on the publication routine that are within the lookahead period |

</details>

### **Missing Data Panel**

***

The Missing Data Panel highlights tasks you own that are missing required info, based on the lookahead set in the publishing schedule.

**Open the Missing Data panel:**&#x20;

* Open the Gantt
* Towards the right-hand side, select <img src="https://2273109354-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLu0mYklsCTm7XQm3ZGqv%2Fuploads%2FQIT4s3pYvNL9ZhQU9JmI%2FMissing%20Data%20Icon.svg?alt=media&#x26;token=75bd8c00-f4b3-452e-b1f1-1d918266e038" alt="" data-size="line">
* This will open the `Missing Data Panel`
* Click into any Task Name in this panel to automatically open the specific columns you need to complete

### **Blockers Panel**

***

The Blockers Panel highlights Open and Overdue Blockers, with Overdue ones always visible even if they fall outside the lookahead window so nothing critical gets missed.

<figure><img src="https://2273109354-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLu0mYklsCTm7XQm3ZGqv%2Fuploads%2FLwtXYjQ4xrKuTr63RVmV%2FOverdue%20blockers%20pannel.svg?alt=media&#x26;token=67e06060-9059-400c-8f38-93bca75cb4de" alt=""><figcaption></figcaption></figure>

**Open the Blockers Panel:**&#x20;

* Open the Gantt
* Towards the right-hand side, select <img src="https://2273109354-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLu0mYklsCTm7XQm3ZGqv%2Fuploads%2FCO9w1KuBOYu8j3bTT1XQ%2FBlocker%20Icon.svg?alt=media&#x26;token=a30668c7-f0a0-418d-ad45-f789e6e047d8" alt="" data-size="line">
* This will open the `Blockers Panel`
* Click the ![](https://2273109354-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLu0mYklsCTm7XQm3ZGqv%2Fuploads%2FptA8pQQejxgMLavNkYFW%2F%EF%8B%BE.svg?alt=media\&token=ed7c6a98-ee8c-4d73-aa87-8a3e99e04de8) next to the Blocker to Resolve it

See also: <a href="blockers" class="button secondary">Blockers</a>

### **Clashes Panel**

***

The Clashes Panel shows Tasks in your lookahead that share the same work area, helping you spot and resolve scheduling conflicts.

**Open the Clashes panel:**&#x20;

* Open the Gantt
* Towards the right-hand side, select <img src="https://2273109354-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLu0mYklsCTm7XQm3ZGqv%2Fuploads%2FCVh66VTJsJmLI0g64EDK%2FClashes%20Icon.svg?alt=media&#x26;token=73457203-0ca1-4757-8b2c-bbfb9e4e6eb7" alt="" data-size="line">
* This will open the `Clashes Panel`
* Click any Task Name in the panel to see which Task it’s clashing with, and who owns it.

See also: <a href="clashes-and-work-area" class="button secondary">Clashes</a>

## **Filter by Unresolved Issue**

***

Filtering by Issue lets you focus on specific Tasks based on what issues they have. It’s a quick way to review and manage work related to a particular issue across your plan.

<figure><img src="https://2273109354-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLu0mYklsCTm7XQm3ZGqv%2Fuploads%2FNXriDsV40ARwYA0PgEMm%2FFiltered%20by%20Issue%201.svg?alt=media&#x26;token=044f7378-4fe1-44b8-8365-cca4cdd1c481" alt=""><figcaption></figcaption></figure>

#### Filter by Issue:

* Click <img src="https://2273109354-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLu0mYklsCTm7XQm3ZGqv%2Fuploads%2F1uSzhSb5aSNnZd5vTaGB%2FFilter%20Button.svg?alt=media&#x26;token=8ddd7f1c-0296-4af2-bdeb-d08d56fc56b6" alt="" data-size="line"> and <img src="https://2273109354-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLu0mYklsCTm7XQm3ZGqv%2Fuploads%2FbVv9qtyepRHQfkVwypud%2FText%20Buttons%20(2).svg?alt=media&#x26;token=fce29edb-8b74-4d75-bfa0-d8ad7292c94b" alt="" data-size="line">
* Select `Issue` in the first dropdown
* Select from `Is`, `Is Not`, `Is Empty` or `Is Not Empty` in the second dropdown
* Select your from `Clashes`, `Overdue Blockers` or `Missing Data` in the third dropdown

#### Pre-made Unresolved Issues View:

Your Project comes with a pre-made Unresolved Issues View.

* Click `+ Views` within the open View Tabs
* Select `Unresolved Issues View`

See also: create & share <a href="view-controls" class="button secondary">Views</a>

<details>

<summary>Filter Breakdown </summary>

| Filter | Operator                                           | Value                          |
| ------ | -------------------------------------------------- | ------------------------------ |
| Issue  | <p>Is <br>Is Not <br>Is Empty <br>Is Not Empty</p> | <p>Multi-Select</p><p><br></p> |

</details>

## Make Ready

***

Marking your part of the plan as Ready lets your team know your Tasks are up to date and good to go for publishing.

<figure><img src="https://2273109354-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLu0mYklsCTm7XQm3ZGqv%2Fuploads%2FsdqDLxN8fDZztyF8lerV%2FMake%20Read%2C%20No%20issues%20(1).svg?alt=media&#x26;token=b357b7c2-b645-40e0-b742-43ba05e10794" alt=""><figcaption></figcaption></figure>

**How to Make Ready:**

* Click your Publishing Deadline in the top right of the page
* This will open the `Make Ready Window`
* Select <img src="https://2273109354-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLu0mYklsCTm7XQm3ZGqv%2Fuploads%2F8dZBLe43uFB0BkxI594O%2F01%20Normal.svg?alt=media&#x26;token=426e3d96-b72a-4145-ab67-e90980d88011" alt="" data-size="line">
* Additionally, if you’re confident in your plan, you can still choose to `Make Ready` even if some issues haven’t been resolved.
  * Select `Make Ready with Issues`

See also: <a href="../published-versions-and-shared-plans#check-if-the-plan-is-ready-to-publish" class="button secondary">Publishing</a>

<details>

<summary>Make Ready Rules</summary>

* If you make changes to the plan after marking it as ready, it will automatically be un-readied.
* You can only Ready Tasks that you own, and that fall within the Project’s Lookahead Period.

</details>

## Reviewing Plans

***

You can assign a Reviewer to any User, ideal for reviewing Subcontractor's plans, or if someone on the Project is away. Reviewers are notified when plans are Ready and can either approve them or mark them Ready on the User’s behalf.

<figure><img src="https://2273109354-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLu0mYklsCTm7XQm3ZGqv%2Fuploads%2FpuGaZtl4wjJIr9faju5i%2FChecking%20before%20publishing%20(1).svg?alt=media&#x26;token=6a419d6e-1231-49e9-b6c0-ad9717158eb7" alt=""><figcaption></figcaption></figure>

#### To set a Reviewer:

* Click your Project Title in the top left then select `Users`
* Find the user you want to assign a Reviewer to
* Click the `+` in the `Reviewer` column
* Select the User you'd like to set as the Reviewer

#### To mark Plans as Reviewed:

* Click the `0/X Reviewed` button in the top right of the page
* Find the `Work for Review` section in the menu that opens
* Use the ![](https://2273109354-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLu0mYklsCTm7XQm3ZGqv%2Fuploads%2FtmKa0esyx9sHu9S2hGQX%2FVisibility.svg?alt=media\&token=3947542b-038d-492c-a254-3ea86e810728) to view each User's plan
* Tick off their plan once you're ready to mark it as Reviewed

See also: <a href="../../../organisations-and-projects/projects#to-set-a-plan-reviewer" class="button secondary">Plan Reviewer</a>
