Install crew scheduling in monday.com, step by step

Step one One row per install, not per job

Most people get the first decision wrong: a job is not an install. A kitchen is three installs on three crews. Demo and cabinets come first, then countertops a week later, once the slab is templated. One row per job cannot show that, so the scheduler ends up back in a calendar app.

So make two boards, the shared tables monday.com runs on. The jobs board holds the sale, the customer and the money. The Installs board holds one row per visit, linked to its job by a connect column. For the flooring contractor, this split collapsed a wall of shared Google Calendars, one per crew, into one board.

Step two The columns

Stick to the columns the scheduler touches every day. Crew is a people column if crew leads have seats, otherwise a dropdown. Install date is a timeline, not a single date, because a two-day install needs a start and an end. Status has five labels: Scheduled, Confirmed, In progress, Done and Callback.

Address is a location column, so the mobile app opens directions in one tap. Material status has Not ordered, Ordered, Received and Short. Add duration in days and a notes column for the gate code and the dog.

Leave the sold amount, measure sheet and purchase order on the job; a mirror column shows them here if needed. Nobody reads a 30-column schedule board on a phone.

Step three Calendar and timeline views grouped by crew

Add a calendar view and a timeline view, two ways of showing the same board, and group both by crew. Each crew becomes a lane, and two installs on one crew in a day show as two bars. Color by status so you can tell Confirmed from Scheduled across the room. Add a table view of the next seven days for the morning huddle, and one view per crew for its lead.

You build views by hand in the monday.com interface rather than through its API, so this step takes clicks, not a script.

Step four Confirmations, and where a small app takes over

monday.com automations send each crew its reminder. Use a recipe of the form "when the install date arrives, one day before, notify the person in the Crew column". It fires once per install, the evening before, to that row's crew. If your crew leads live in the monday.com mobile app, that's the whole confirmation system.

A native automation sends the message; reading the answer takes an app. If the crew lead answers "cannot make it, truck is in the shop", nothing happens. The install stays Scheduled, and the office finds out at seven the next morning. For crews that live in email and text, that gap is the whole problem.

The fix is a small app hosted on monday.com's own app platform. It emails each crew a digest of its next day and reads the replies. It marks each install Confirmed or flags it with the reply text, then updates each crew's own calendar. For the flooring contractor, that app is what the crews see.

Step five Material gating

Material gating is the automation that pays for the build. If an install moves to Confirmed before its material is Received, it drops back to Scheduled and the scheduler gets a notice. Pair the automation with a rule on the jobs board that moves a job to Scheduled only when every linked install is Confirmed. The showroom can still promise a date, but nothing is confirmed until the material is on the shelf. Whoever promised the date can see at once that it is not confirmed.

When material arrives short, the Short label flags it, and a view of every install with Short material is the purchaser's morning list.

Step six Punch lists as subitems with photos, and callbacks as new rows

Each punch item is a subitem, a short row tucked under the install, with a files column and a status of Open or Fixed. Installers add a photo from the mobile app before they leave. The office sees the chipped edge that afternoon, not three weeks later from the customer. When every subitem is Fixed, an automation marks the install Done.

A callback is a new install row, not a status on the original. It links to the original install and the job, with Callback as its status. The history stays intact, and the callback lands on the calendar. Callbacks per crew become a number most owners have never seen.

Step seven Capacity: installs per crew per week

Build one dashboard with a chart of installs per crew per week. Add counts of installs waiting on material and in Callback, and a list of installs in the next seven days still Scheduled, not Confirmed. The scheduler checks it before quoting the showroom a date. The owner opens it on Monday to see which crew carries the load and which has Thursday free.

Step eight What to migrate from the old calendar, and what to leave

Migrate the future: every install in the next eight weeks, with its job, crew and dates. Use a script keyed on the calendar event id, so a run that stops halfway restarts without duplicating anything already imported. Before anyone schedules on the new board, reconcile the count both ways: every future event has a row, and every row has an event.

Leave the past where it is. Export the old calendars to a spreadsheet, then keep them read-only and never delete them. When someone asks which crew did the 2024 install, the export answers.

What this costs if we build it

An office manager can build everything above in a long week, and we publish this guide so you can. Or we build it, verify it and hand it over with recorded training.

Foundation, from $3,000, takes one week: the jobs board with stages, a web lead form, three automations, one dashboard and a recorded one-hour training. If the Installs board is the one you need first, Foundation builds it instead, with its views and the native notifications. Full System starts at $7,000 and takes two weeks. It adds the install schedule by crew, purchase orders and material gating, punch lists with photos, customer notifications, permissions and dashboards.

Full System also includes the move from a spreadsheet, Google Calendar or another tool, reconciled row by row. These are starting prices, and after the free 30-minute review we send a fixed quote for the build. The care plan covers changes after the build, at $600 a month for 4 hours or $1,100 for 8. Work too big for the care plan's monthly hours gets its own fixed quote.

monday.com Pro licenses are extra, at $19 per seat per month billed annually (monday.com/pricing, read October 7, 2026). The reply-reading app in step four is custom app work, priced into the fixed quote. Every price is on the pricing page.

If your crews are already scheduled on monday.com, Asana, Smartsheet, Airtable or ClickUp and the setup has grown messy, Overhaul fixes it, from $5,000. We audit the account, rebuild the install boards and automations nobody trusts and clear out the duplicates. The price includes permissions, dashboards and a recorded training, and your data stays where it is. Most overhauls take one week, and a large account takes two.

Limitations