Permits. No-parking signs. Utility locates. Neighbor approvals. On a big project, the work that has to happen before the crew arrives is often the work most likely to slip through the cracks. Until now, teams tracked those prerequisites in loose text notes and tags — and when something got missed, they usually found out too late to fix it.

Today we’re rolling out Job Requirements, a structured way to track every prerequisite on a job, give each one a clear status, and stop work from advancing until the right boxes are checked.

Why we built it

On larger projects, relying on free-text notes and tags to keep track of permits and no-parking signs isn’t viable. The problem with notes and tags is that nothing enforces them. A missing permit doesn’t announce itself — it shows up as a crew that can’t start, a re-scheduled day, and a frustrated client.

Job Requirements replaces that informal tracking with a system that does three things notes never could:

1. Gives every requirement a clear, color-coded status so anyone can see at a glance what’s done and what’s outstanding.

2. Blocks the job from moving forward at key checkpoints — project review, work order scheduling, and pre-execution — so issues surface early instead of on the morning of the job.

3. Travels with the work, carrying requirements automatically from the project all the way through to the crew’s mobile app.

The result: issues get caught while there’s still time to act on them, not after they’ve already blocked the job.

How it works

Requirements can be attached at the project level (things that apply to the whole job) or to individual tree IDs (requirements specific to one tree), and they flow through every stage of the workflow.

Set up your requirement library

Admins define the requirement types your organization uses under Settings → Job Requirements. Each requirement type can carry a few attributes that make it smart rather than just a label:

– Category groups requirements by type — for example, “Access” covers site-entry items like needing a key card.
– Default Owner Role sets who’s responsible for following up, such as Sales or Ops.
– Block Level defines the stage where an incomplete requirement blocks further action: scheduling, execution, or both.
– Required by Stage marks when in the workflow the requirement is needed.

Only the requirement name is mandatory — everything else is optional and configurable to match how your team already works.

Add requirements to a project

From the desktop app, open a project, click Actions → Requirements, then pick a requirement and set its status. Once the first requirement is saved, a Requirements box appears at the top of the project so it’s always visible. Need a requirement on a single tree instead? Double-click the tree pin to open the side bar, find the Requirements field, and add it there — the same way, with the same dialog.

Watch it carry through to proposals and work orders

When a proposal is created for a project that has requirements, **all project-level requirements and the tree-level requirements for any trees in that proposal carry over automatically** — no re-entering anything. From the scheduler queue, click the requirement icon to review or update statuses, upload and view attachments, and edit details before scheduling.

Enforcement at scheduling

This is where Job Requirements earns its keep. When you drag a work order onto the scheduler with incomplete requirements:

– Admins see a prompt that lists exactly what’s still pending and can choose to override and proceed.
– Non-admin users see the same prompt but can only cancel — they can’t override the block.

Once scheduled, the work order detail page shows a Requirements section (and only shows it when requirements exist), so the status stays front and center right up to execution.

On mobile and in the field

Job Requirements isn’t just a back-office feature — it reaches the crew.

– In the mobile app, tap the clipboard icon on a project to view and add Project Requirements and Tree Requirements. Pick from your existing requirement library or create a new one on the spot. Each requirement opens to a detail screen where you can set status, add a note, attach a file, and review its Category, Owner Role, and Stages.

– In the Works crew app, tapping into a work order with incomplete requirements shows the same prompt logic — admins can override, non-admins can only cancel and return. Crews can tap the Requirements section to review the status of everything tied to the job before they start.

A badge on the project surfaces the number of incomplete requirements, so nothing relies on someone remembering to check.

Who this is for

Any team running larger or multi-step jobs where prerequisites pile up — permits, locates, signage, HOA or neighbor approvals, compliance standards — and where a single missed item can stall a whole crew. If you’ve ever lost a day because a sign-off didn’t happen, this is for you.

Get started

Requirements are available now across the desktop app, mobile app, and the Works crew app. To set up your requirement library, head to Settings → Job Requirements, then start attaching requirements to your next project.

For the full step-by-step walkthrough, see the help center article: [Adding Requirements To A Job].