Workflow guide

A cleaner workflow for when the site still is not ready.

For operations teams coordinating daily dispatch, this workflow shows what to do when access, materials, or predecessor work blocks the visit before the crew leaves.

Best fit

Teams that often hear 'not yet' only after the crew is already rolling
Projects where predecessor trades, material deliveries, or access details shift late
Operations leads who need blockers recorded clearly instead of buried in message threads

Common blockers

FoundationFlow is aimed at the blockers that most often cause crews to show up for nothing.

  • The previous trade was not done
  • Materials or equipment were not in place
  • Access, keys, or codes were not available
  • The site contact had not confirmed readiness

The response path

A good site-not-ready workflow does more than say no. It tells the office and crew why the visit should pause and what needs to change next.

  • Mark the visit ready, blocked, or not yet
  • Capture the blocker in plain language
  • Keep the office and field team aligned on the next action

The payoff

The goal is fewer wasted trips, cleaner rescheduling, and less time spent reconstructing what went wrong after the fact.

Related pages

Related pages for your next step.

Pick the page that matches where your team is right now, then move forward with a clear pre-dispatch check plan.

Construction job-site readiness tool

See the broader readiness category and use case.

Readiness glossary

Review the core terms construction teams use in this workflow.

Wasted trip calculator

Estimate what those blocked visits are costing every month.

Take action

Need a cleaner answer when the site is not ready?

Request early access and show us how your team currently captures blockers and makes the pre-dispatch check decision.

Request Early AccessQuantify the cost of blocked visits