Add a job to the schedule
Pick a JobTread job, confirm scope, propose install dates, commit one.
How this works
Click to expand the step-by-step walkthrough.
Show walkthrough
- Pick a JobTread job. Active JT jobs (anything not Complete / Lost / On-Hold) are in the dropdown.
- Confirm the auto-pulled values. Contract price comes from the sum of approved customer orders in JT. Travel comes from the job's address (Google Routes). Address shows below the travel field.
- Confirm or override predicted hours. Predicted comes from Jesy's JT cost-card labor budget when she's filled it in (Manufacturing line + Installation + Pack/Sort/Load lines, master rows only -- doc copies on proposals/invoices are skipped). If the labor budget is empty, it falls back to the regression model (price-only fit, n=7 standard_closet jobs). Committed = what we actually plan for. Override either if you disagree with the predicted number.
- Customer-requested install date is optional. Leave both fields blank to see just earliest-feasible + one-week-buffered. Single date: pick "from" only. Builder window ("second week of June"): fill both.
- Click "Propose install dates." System returns up to 3 cards: customer-requested (or window-best), earliest-feasible, one-week-buffered. Wednesday is preferred; Friday/weekend never proposed.
- Click "Commit this date" on the card you want. Three things happen: (a) entry written to local schedule JSON, (b) calendar event created on the CM Operations Google Calendar with full Lee-style POA description (Jesy invited), (c) JT's "Installation Date" custom field on the job is set.
Reversible. The schedule entry, the calendar event, and the JT custom field can all be edited or cleared without breaking anything. Re-committing the same job replaces the old calendar event cleanly.