FROM ROADMAP TO A REVIEWABLE DRAFT

A plan with visible ownership.

Turn a roadmap, responsibility matrix and dependencies into a portable project charter. Resolve gaps before sharing the draft.

Technical Python team recommended. Buyer-owned workspace; no AI, external connector or automatic approval.

{"format": "pt-charter-project-1", "project": {"title": "Community workshop renewal", "purpose": "Replace a fictional workshop booking process with a reviewed shared plan.", "sponsor": "Workshop steering group", "in_scope": "Booking workflow\nEquipment register\nOperator handover", "out_scope": "Payment collection\nHistorical record migration", "assumptions": "Volunteer owners confirm the plan before any work starts.", "success_measures": "Each selected capability has an accountable owner and a reviewed completion date."}, "tables": {"Roadmap": [{"ID": "WK-01", "Workstream": "Foundation", "Capability": "Booking intake", "Target": "Shared booking form", "Availability": "Available", "Team": "Delivery", "Status": "In progress", "Start": "2026-11-02", "End": "2026-11-06", "Relevant": "Yes"}, {"ID": "WK-02", "Workstream": "Operations", "Capability": "Equipment register", "Target": "Reviewed inventory", "Availability": "Gap", "Team": "Operations", "Status": "Not started", "Start": "2026-11-09", "End": "2026-11-13", "Relevant": "Yes"}, {"ID": "WK-03", "Workstream": "Transition", "Capability": "Operator handover", "Target": "Documented runbook", "Availability": "Unknown", "Team": "", "Status": "Not started", "Start": "", "End": "", "Relevant": "Yes"}, {"ID": "WK-04", "Workstream": "Future", "Capability": "Fee collection", "Target": "Future decision", "Availability": "Unknown", "Team": "", "Status": "Not started", "Start": "", "End": "", "Relevant": "No"}], "RACI": [{"Roadmap ID": "WK-01", "Area": "Booking design", "Delivery": "RA", "Operations": "C", "Sponsor": "I", "Notes": "Review with volunteers"}, {"Roadmap ID": "WK-02", "Area": "Register ownership", "Delivery": "R", "Operations": "C", "Sponsor": "I", "Notes": "Accountability is intentionally missing for review"}], "Dependencies": [{"Roadmap ID": "WK-02", "Dependency": "Confirm equipment naming convention", "Owner": "Operations coordinator", "Status": "Open"}], "Scorecard": [{"Criterion": "Usability", "Weight": "60", "Score": "4", "Notes": "Synthetic workshop assessment"}, {"Criterion": "Maintainability", "Weight": "40", "Score": "3", "Notes": "Human score; not a forecast"}]}}

01 / PROJECT INTENT

State the boundaries

TitlePurposeSponsorIn scopeOut scopeAssumptionsSuccess measures

02 / SOURCE TABLE

Roadmap

Relevant: Yes/No · Availability: Available/Gap/Unknown · Status: Not started/In progress/Done/Blocked · Dates: YYYY-MM-DD or blank.

ID	Workstream	Capability	Target	Availability	Team	Status	Start	End	Relevant	Row

03 / SOURCE TABLE

RACI

Delivery, Operations, Sponsor: blank, R, A, C, I or RA. Exactly one accountable role per area is a review check.

Roadmap ID	Area	Delivery	Operations	Sponsor	Notes	Row

04 / SOURCE TABLE

Dependencies

Reference a roadmap ID. Status: Open or Resolved.

Roadmap ID	Dependency	Owner	Status	Row

05 / SOURCE TABLE

Scorecard

Whole weight 0–100; score 1–5. Weights must total 100 for a weighted score.

Criterion	Weight	Score	Notes	Row

OPTIONAL / PLAIN XLSX INPUT

Replace tables from a workbook

Download a fresh synthetic schema, edit its four exact sheets, then select your copy. Project intent above is preserved; all four tables are replaced only after validation. No formulas, macros, links or embedded media.

Download synthetic workbook

06 / HUMAN REVIEW

What still needs a decision?

This snapshot changes only when you validate. It is a deterministic checklist, not a forecast or approval.

3 / 4Relevant capabilities

6Review notes

3.6Human-weighted score / 5

WK-02: capability availability needs review (Gap).
WK-02: Register ownership needs exactly one accountable role.
WK-03: capability availability needs review (Unknown).
WK-03: team or schedule remains incomplete.
WK-03: no responsibility row supplied.
WK-02: unresolved dependency — Confirm equipment naming convention

I reviewed this source and its remaining gaps; the export is a draft, not authorization to execute.

JavaScript is required for table editing

Use the CLI with your project JSON if JavaScript is unavailable. The initial synthetic data is not your edited project without the browser editor.