Why a crew turned a job down

A crew declining a project picks from a fixed list of sixteen reasons — pay versus scope, schedule conflict, site not ready, skill set, client concerns and more — with optional detail.

What it is

CREW_DECLINE_REASONS is a single centralised list of codes and labels used by the modal, the history view and any future report. Multiple reasons can be selected, plus free text under 'Other'.

Also called: crew refused the job · decline reasons · crew said no · pay too low

See it
Why a crew turned a job down
Apr
May
Jun
Jul
Sutter Kline — 30×40 Garage
Framing
Marlin Hoover — 30×40 Garage
Concrete
Delia Yoder — Riding Arena
Trim
Delia Yoder — Equipment Storage
Framing
Gideon Alt — Riding Arena
Concrete
Framing crewConcrete crewTrim crew
The decline step with sixteen selectable reasons and the Other box, then the history row showing the chosen labels. Sample data — no customer information appears here.
How it works
  1. 1The decline step shows the reasons as checkable options with an 'Other' text box.
  2. 2declineProject stores the codes array, the other text and a decline timestamp alongside the same brief snapshot.
  3. 3The crew's history section renders the labels back from the codes.
  4. 4A separate assignment-level decline path marks the project_crew_assignments row declined so the project needs a new crew.
Why we built it

A crew turning down a job used to be a phone call, so the reason lived with whoever took it and the same problem got declined three months running before anyone spotted the pattern. Declining is done with a reason from a fixed list — pay not matching the scope, too many jobs back to back, site prep not ready, concerns about materials, concerns about the client — so the same reason means the same thing everywhere it is counted. What the builder gets is not one refusal but a count, and the reason crews keep giving is usually something he can fix.

The problem
  • Refusals happening verbally and leaving no trace.
  • Free-text reasons that cannot be counted or compared.
Sound familiar?
What you get
Patterns in refusals become visible.
The record shows the offer that was declined, not just that it was.
One list drives the UI and any reporting.

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →