Charter Decision Wizard for Hardware and Construction Project Managers
A branching decision wizard that picks the right charter depth for hardware or construction projects in mid-size companies — and flags the ones that need program governance instead.
Pick the charter depth your physical project actually needs
Hardware and construction projects fail more often from over-charter than under-charter — the symptom is a 60-page document nobody re-opens until the lawyers ask for it.
Mid-size hardware and construction project managers face a peculiar charter problem: physical projects carry compliance and safety stakes that demand documentation, but the same documentation often becomes an inert artifact filed against the contract and never re-read. This wizard helps you pick the charter depth your specific project needs — light, moderate, or full — and flags the projects that should not be a project at all but a program with multiple charters.
The wizard below is a decision tree. Answer each question honestly. Skip ahead if you already know the answer.
Step 1: Scope envelope
0 / 4- Is the project budget under $500K, $500K–$5M, or above $5M?
- Does the project have any safety-critical components (life-safety systems, structural elements, regulated emissions)?
- Will the deliverable have a hand-off to operations beyond final commissioning?
- Is there a single physical site, multiple sites, or a moving site (e.g., field installation)?
Step 2: Stakeholder envelope
0 / 4- Does the project involve more than one external contractor?
- Is there a regulatory inspection or permit gate that drives the schedule?
- Are there community or public stakeholders (residents, end users, local authorities)?
- Does sign-off require multiple internal departments (procurement, legal, ops)?
Wizard outcomes
Match your answers to one of four outcomes below. The outcome determines which charter template to use.
Outcome A — Light charter (one page, two-week sign-off). All scope envelope answers are 'small' (under $500K, no safety-critical, no ops handoff, single site) and stakeholder envelope is internal-only. This is rare for physical work but does occur on small refits. Use a four-to-six-field charter and re-read it weekly.
Outcome B — Moderate charter (3–5 pages, three-to-four-week sign-off). Mixed scope envelope with one contractor and one regulatory gate. This is the most common physical project shape in a mid-size company. Use the moderate charter template and pair it with a brief risk register from day one.
Outcome C — Full charter (10+ pages, six-to-eight-week sign-off). Above $5M, multiple contractors, multiple permits, or community stakeholders. This is the right shape for a single large physical project. Charter must be paired with full risk, communications, and procurement plans, all initiated in parallel.
Outcome D — Not a project, a program. If you have multiple safety-critical sites, multiple regulatory regimes, or a deliverable that itself contains multiple sub-deliverables with their own sponsors, you should not be writing one charter. You should be writing a program charter and child charters per workstream. Trying to fit a program into a project charter is the most common cause of charter rewrites in physical work.
| Outcome | Light (A) | Moderate (B) | Full (C) | Program (D) |
|---|---|---|---|---|
| Charter length | 1 page | 3–5 pages | 10+ pages | Program + child charters |
| Sign-off window | 2 weeks | 3–4 weeks | 6–8 weeks | 8–12 weeks |
| Budget threshold | <$500K | $500K–$5M | >$5M | Multi-stream |
| Contractors | Internal only | 1 external | Multiple | Multiple per stream |
| Regulatory gates | None | 1 | Multiple | Multiple regimes |
What the wizard is preventing
This wizard exists because the most expensive charter mistake in physical projects isn't writing too short — it's writing too generic. A 30-page document with a generic risk section, generic communications plan, and generic acceptance criteria looks rigorous and provides almost no operational value. A focused 5-page charter with crisp exclusions, a real schedule of regulatory gates, and a named single contractor lead does more work.
Use this wizard once at initiation. If your answer changes mid-project — most often when scope grows or a second contractor is added — re-run it and consider a mid-flight re-charter. The mechanics translate from software to physical work; the politics are different but the structure is the same.