> ## Documentation Index
> Fetch the complete documentation index at: https://help.yournewdoor.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Exceptions and red flags

> Where flagged jobs show up, how to resolve them, and the warning signs to catch early.

When something is wrong with a job, Field Ops flags it instead of guessing. Flagged jobs wait on the **Exceptions** page (`/jobs/exceptions`) until someone deals with them. Office staff can open the page.

## Field exceptions

Installers flag problems from the job's field packet. Each one shows the job, the customer, the reason, who flagged it and when, and whether **Work must stop** or **Work can continue**.

The reasons are **Site not ready**, **Wrong size / measure**, **Customer not home**, **Material missing** and **Other**.

**1. Open the exception**

Click the job number to open the job. Its **Exceptions** tab shows the same flag.

**2. Resolve it or send it back**

If the office can fix it, write **How it was resolved** and click **Resolve in office**. If it's a sales problem, such as the wrong door being sold, write **Why Sales must take it** and click **Send back to Sales**.

Dispatchers, admins and the Owner can resolve or send back an exception. Other office roles can see the list.

## Sold-job problems

When a sale can't become a job, for example because the service address or the sold lines are missing, it lands under **Sold-job problems**. Field Ops fixes small mix-ups on its own and only lists what it can't fix safely. It never makes up a customer's details.

Most office staff see **A sold job couldn't be created. An admin is fixing it.** Admins and the Owner see the details so they can fix the sale.

## Held jobs

A job that's paused shows in **Needs review**, not on the Exceptions page. See [Put a job on hold](https://help.yournewdoor.com/jobs/hold.md).

## Red flags to catch early

> [accordion] Only one decision-maker was pitched
>
> High risk of a cancel or a rewrite. Book the **Decide** call again with both people.

> [accordion] The first call turned into product trivia
>
> 40 minutes of model details and no Align or Discover answers. Go back to Align, Discover, Design, Decide, and keep intake to 5 to 7 minutes.

> [accordion] Sold with a TBD address or no sold lines
>
> The job won't be created. Fix it in Sales Ops. Don't ask Field Ops to fill it in.

> [accordion] A gate marked Ready that isn't
>
> A false **Ready** on Material, Site or Execution sends the wrong truck or door. Checking is everyone's job.

> [accordion] Scheduling before the job is ready
>
> A job needs all four gates **Ready** and a real date and time before it goes on the map. Don't look for a way around that.

> [!WARNING]
>
> Never make up a customer's name, phone, email, street, city, state, ZIP or what was sold, whether in sales notes you paste into Field Ops or anywhere else.

## Next

> [card] [Readiness gates](https://help.yournewdoor.com/guides/readiness-gates.md)
>
> What has to be ready before a job can be scheduled.

> [card] [Roles](https://help.yournewdoor.com/guides/roles.md)
>
> Who can do what.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.