> For the complete documentation index, see [llms.txt](https://docs.shortcutco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shortcutco.com/readme/projects/schedule-and-dispatch-install.md).

# Schedule and Dispatch Install

Give each phase a team and a start day, read the Backlog's capacity, move days on the schedule strip, run the day from Dispatch → Install, handle rain and holds, and order the materials the scheduled

Once a project is approved, its phases wait in the **Backlog** until each one has a team and a start day. Scheduling puts the phase on **Dispatch → Install** and on the crew's **Today**, and texts the customer the start date.

## The Backlog

Open **Projects → Backlog**. The strip at the top is **Install capacity**: for each install team, the hours booked against the hours available for this week and the next two (*13/45*, *0/75*), how many hours each team has free over the three weeks, and whether the unscheduled work **Fits in the next 3 weeks** or **Won't fit before** a date. Only teams with **Takes install work** count, unless you tick **Count route teams in capacity** under **Filter**.

Below, every approved project with unscheduled phases: the **Unscheduled phases** (*1 of 2 · Planting*, or *CO-1 only · Patio drain*), their **Hours**, when it was **Approved** and how long it's been waiting, the **Deposit** (**Paid**, **Invoiced**, **Not requested**, or **Not required**), the **Contract**, and the **Sold margin**. Projects sit under **Ready to schedule** or **Waiting on deposit**. Hover a row for **Schedule**, or **Remind** on an unpaid deposit.

<figure><img src="https://2299783971-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOhi7KtJ4vY1pDKwWu5SV%2Fuploads%2Fgit-blob-42720179f4e19b842975a44ebb6be9e190c7b477%2Fprojects-list-backlog.png?alt=media" alt="The Backlog tab: the Install capacity strip showing Install A and Install B booked hours against capacity for three weeks with the free hours, then Ready to schedule rows for three projects with their unscheduled phases, hours, approval date, deposit state, contract and sold margin"><figcaption><p>The Backlog: sold work that isn't on the calendar yet, and how much room your install teams have.</p></figcaption></figure>

## Schedule a phase

Click **Schedule** on a phase row (or the main button, **Schedule French drain**, or **Not scheduled – pick team & start day** on the schedule strip). The window shows the phase's hours budget and:

* **Team** — the phase's planned team, with how many people are rostered. **Change team size** uses a different number for the day count. **Add another team** splits the hours between teams; type the hours for each.
* **Start day** — the team's **first free day**, or pick another.
* **The days** — how many days it takes and the maths behind it: *5.33 h ÷ (2 × 7.5 h) = 0.36 → 1 day*. Each day shows **Free**, the hours of this phase on it (*5.3h*, with the rest of the day open), or **Booked**. Weekends and non-working days are skipped.
* **Chain next phases on this team** — the following phases start right after this one on the same team (*Regrade & seed (T\&M) would start Mon 2 on Install A*).
* **Text \[name] the start date** — on by default. The customer gets one text with the start date, and another only if the date moves.
* The footer says where it lands: *Shows on Dispatch for Lena from Fri 30*.

Click **Schedule**. The phase turns **Scheduled**, the days appear on the strip and on Dispatch → Install, and the lead gets a push.

<figure><img src="https://2299783971-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOhi7KtJ4vY1pDKwWu5SV%2Fuploads%2Fgit-blob-6272e8d4fd90ff9dfa1ca01b5e36425951e87cff%2Fprojects-schedule-popover.png?alt=media" alt="The schedule window for French drain: Team Install A with 2 people, Start day Fri, Oct 30 (first free day), the day count worked out as 5.33 h ÷ (2 × 7.5 h) = 0.36 → 1 day with a row of day chips, Chain next phases on this team ticked, Text Luis the start date ticked, and the Schedule button"><figcaption><p>Pick the team and the start day; Shortcut works out the days and offers to text the customer.</p></figcaption></figure>

**When the team is already booked**, the start day turns amber and the window offers ways out: **Next free start**, **Start after \[the clashing phase]**, **Use \[another team] – free \[day]**, or **Double-book anyway**. Double-booking is allowed; it's logged on the project.

**An unpaid deposit** only warns, unless **Require deposit before scheduling** is on in Settings. Then the window is blocked, with **Schedule before the deposit is paid** for admins, which is logged.

**A T\&M phase** schedules on its estimated hours and says so: *Estimate only – billed on punched hours × $65.00/h*.

## The schedule strip (Gantt)

The strip along the bottom of the project page is the project's calendar: a row per phase, a column per working day, today in red. Toggle it with the Gantt button in the header. Each bar shows the phase's status and hours (*70% declared Tue · 63 h/41.67 h*, *Scheduled · 20 h*, *Reviewed*), with **Rain** and **Resumes · 15 h left** blocks for held days, and a red stretch when the days ran past the plan.

* **Drag a bar** to move the phase; **drag either end** to stretch or shrink it (the hours budget stays, the days change). Shrinking below the hours already worked asks first and never deletes a day with hours on it.
* **Moving a phase** that later phases depend on asks *Finish grade & seed is on Mon 28 – shift it 1 day?* with **Shift them too** or **Keep dates**. Moving the first phase asks whether to **Move and text** the customer or **Move, don't text**.
* **Click a bar** for the same choices as the schedule window: **Move**, **Change days**, **Add a day**, **Rain day**, **Release days**, **Hold the day**.
* **Keyboard:** focus a bar, then **←** / **→** moves it a day, and **Enter** saves.

Phases run over all the time. When a team clocks out with a fixed-price phase under 100 %, Shortcut adds a day on that team's next working day with room (*Day 4 of 3*), and asks about the phases behind it. A day you release is never added back. T\&M phases, and phases with no room in the next two weeks, are handed to you instead: the activity reads *left an unfinished phase for the office to plan*, and you add the day yourself.

A finished phase with a day still booked shows *Steps & edging is complete – 1 day is still planned* with **Keep days** or **Release the day**, so the team's day frees up on Dispatch.

## Dispatch → Install

[Dispatch](https://shortcutco.com/dispatch) has two scopes. **Maintenance** is the route board you know; **Install** is project work. Switch with the **Maintenance (n) | Install (n)** control under the title; Dispatch remembers which you used. A route team pulled onto a project shows **On install · \[project]** on its row in Maintenance, with **Switch to Install**.

**Today** lists each team with install work (*Install A · Lena, Cal · 2 projects today*), and for each project: the customer and address, **Today** (*Phase day 5 of 5 · Patio & seat wall*, or **Punch list**), **Hours · measured** against the budget (red when over), **Declared** (*70% · Tue*), and the **Status**. Click a row to open the project. Filter by **Status** or **Team**, or search.

<figure><img src="https://2299783971-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOhi7KtJ4vY1pDKwWu5SV%2Fuploads%2Fgit-blob-c50b944a320df3dceee256c367ce4401eda662a5%2Fprojects-dispatch-install-today.png?alt=media" alt="Dispatch → Install on Today: Install A with Backyard patio &#x26; seat wall on phase day 5 of 5 and Front steps reset on a punch list, Install B with Retaining wall rebuild on phase day 4 of 4 showing 63 of 41.67 hours in red and 70% declared, with the Maintenance | Install switch and the Rain day button"><figcaption><p>Dispatch → Install, Today: who is on which project, how far along, and how the hours are running.</p></figcaption></figure>

**This week** is a grid: teams as rows, working days as columns, one bar per phase day (*Phase day 3 of 5 · 56/63.34 h*, *Retaining wall rebuild · Wall · 70% declared*), and under each cell the hours booked against the team's capacity (*15 / 15 h*, *5.3 / 15 h*). Along the bottom, **Unscheduled** holds every phase without days as a chip (*CO-1 · Backyard patio & seat wall · Patio drain · 6 h*, *Side yard drainage · 2 phases · ≈ 11.33 h · approved Oct 19*). Drag a chip onto a team's day to schedule it there (the schedule window opens, filled in), or drag a bar's end to stretch it. **Open Backlog** goes to the Backlog tab. A chip waiting on its deposit can't be dragged until it's paid.

<figure><img src="https://2299783971-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOhi7KtJ4vY1pDKwWu5SV%2Fuploads%2Fgit-blob-94c17557bd3c45a37d11a506382ba1781f0bf9df%2Fprojects-dispatch-install-week.png?alt=media" alt="Dispatch → Install on This week: Install A and Install B as rows across Mon 26 to Fri 30 with phase-day bars and booked-against-capacity hours under each day, and the Unscheduled tray along the bottom with three draggable chips and Open Backlog"><figcaption><p>This week: every team's project days, the hours booked each day, and the unscheduled work ready to drag on.</p></figcaption></figure>

## Holds, rain days, and moving days

**Rain day.** On Dispatch → Install, click **Rain day**. The **Rain day · \[date]** window lists every team with project work that day; tick the ones that are rained out (a lead who tapped **Rained out** on their phone is pre-ticked, *Suggested by Marco*). **Shift later phases** moves each project's later phases on that team along, and **Text customers** tells the affected customers the new start. Click **Mark n teams rained out**. The held days show **Rain** on the strip, and the team's work moves to its next free day.

**Put a phase on hold.** On the phase's **⋯** menu choose **Put on hold…**. Pick the **Reason** (**Waiting on material**, **Customer asked**, **Weather**, **Inspection**, **Other**), the **Team** (on a phase with several teams, one team or **Every team (whole phase)**), the **Resume** day, and whether to **Text \[name] the new start**. The held days come off Dispatch, the remaining hours move to the team's first day back (the window shows where), and the lead sees it on their app. **Resume** brings it back. A whole project is held from the main button's arrow, **Put project on hold…**.

<figure><img src="https://2299783971-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOhi7KtJ4vY1pDKwWu5SV%2Fuploads%2Fgit-blob-80767c1b31fe54aaf43faa7d3b73391a68ff1474%2Fprojects-hold-popover.png?alt=media" alt="The Put on hold window for Retaining wall rebuild: Reason chips Waiting on material, Customer asked, Weather, Inspection and Other, a Resume day picker, Details, the line Every phase pauses; leads see it on their app, and the Put on hold button"><figcaption><p>Hold a project or a phase with a reason and a resume day; the team's days come off Dispatch until then.</p></figcaption></figure>

**Move or release days.** From the phase's **⋯ → Reschedule or change team** (or by clicking its bar), choose **Move** (a new start, with **Move this team's later phases along**), **Change days**, **Add a day** (one more day like the others, or **Double-book anyway**), or **Release days** (**Upcoming days**, **Past days nobody worked**, or **Both**; their hours go back to the Backlog, and worked days always stay).

## Calendar

Scheduled phases also show on the [Calendar](https://docs.shortcutco.com/readme/jobs-and-scheduling/calendar.md) as read-only all-day bars per team. Click one to open the project.

## Materials to buy

**Reports → Materials to Buy** adds up what the scheduled phases need, so you can order before the crew needs it. Under **Include**, tick **Projects** (phases scheduled in the period), **Maintenance products** (products on maintenance visits), and, if you like, **Unsigned change orders** (phases on change orders the customer hasn't signed yet).

Each item shows what's **To buy**, its **Est. cost**, when it's **First needed**, and what it's **For** (*2 projects*). A part of a bundle is marked **From bundle**. To buy is what each scheduled phase estimates minus what the crew has already marked as used on their checklist; a phase counts once, in full, on its next work day, and the cost is today's price book cost. Open **Materials to buy** from the **⋯** menu on the Projects list, or from Reports. See [Reports](https://docs.shortcutco.com/readme/reports.md#materials-to-buy) for periods, saved views, and scheduling the report by email.

<figure><img src="https://2299783971-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOhi7KtJ4vY1pDKwWu5SV%2Fuploads%2Fgit-blob-184d51050cc483ee86e753968f5de23b9aa13329%2Fprojects-materials-to-buy.png?alt=media" alt="Materials to Buy for the next 30 days with Projects and Maintenance products ticked under Include: the Period, Items to buy, Est. cost, Projects · visits and First need tiles, and rows for base stone, polymeric sand, wall block, pavers, shrubs and mulch with the quantity to buy, estimated cost, first needed date and how many projects need each"><figcaption><p>Materials to Buy with Projects ticked: what the scheduled phases need, minus what the crews have already used.</p></figcaption></figure>

<details>

<summary>Still stuck?</summary>

Email <hello@shortcutco.com> with the project name, the phase, and a screenshot of the schedule window or Dispatch → Install.

</details>
