Why this page exists: there are 6+ ways to create a Job in the Hub. That's
the #1 source of confusion — people take two different paths for the same work and
it forks into duplicate Jobs. This page gives you one blessed path and
explains when each alternate is actually appropriate.
GoBuild's lifecycle is linear:
A Job can also be created on its own with no upstream Lead or Proposal — that
is the blessed manual path below. The blur ("when does something become a Job?") is
resolved by one rule:
A Job exists once you're going to do the work. Before that it's a Lead/Proposal.
Don't create a Job to "hold a maybe" — that's what a Lead is for.
/portal/jobs) — the Portfolio./portal/jobs/new → /plan → /create) — 🟢 the default. The wizard drafts scope/tasks; you review before it commits./portal/jobs/from-photo) — 🟢 express lane, AI estimate from a site photo./portal/jobs/from-plan) — 🟢 express lane, AI takeoff from an uploaded plan.⚠️ Express-lane drafts auto-delete after 7 days if not promoted. If you started
from a photo/plan, hit Save to Jobs — don't assume it persisted.
A Job created without these is a frequent "why is this broken" cause:
| Path | How | Use it when | Risk |
|---|---|---|---|
| From a Lead | Sales → Lead → convert, or /portal/jobs?lead={id} |
The work came through the pipeline and you want attribution carried over | If you also click "New project" later, you get a duplicate — convert, don't re-create |
| From an accepted Proposal | Proposal accept → auto-creates Job (conversion.py:212, sets lead.status=won, won_job_id) |
Quote-to-job; keeps the money trail linked | Don't then manually create "the real one" — the accepted proposal already made it |
| From a template | /portal/jobs?template={id} |
Repeatable job types (same scope each time) | — |
| AI bar (Keystone) | Ask it to create a job (ai_bar.py:270) |
Fast capture mid-flow | Review the confirm-card; it's a real write |
| API | POST /api/jobs |
Integrations / scripted creation | Not for humans |
The forks happen when two of the above are used for the same work. Rules:
view=classic job page is legacy and ❌ slated for removal — don't build habits on it. Use the command-center job view.Related: Jobs command center · Sales · Known Risks