Create intermediate Works with: Any AI

Project Charter One-Pager

Before after Has example

Agree purpose, scope, and authority before starting.

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.

Write a project charter. Project idea and background: [PROJECT_BACKGROUND]. Sponsor and key stakeholders: [SPONSOR_AND_STAKEHOLDERS]. Budget and deadline constraints: [BUDGET_AND_DEADLINE]. Known risks: [KNOWN_RISKS].

Produce a one-page charter with sections: purpose (the problem and who it affects); objectives (measurable, no more than four); success measures with baseline and target; scope in (deliverables) and scope out (explicit exclusions); assumptions and constraints; milestones with dates; budget and resources; roles (sponsor, manager, team, reviewers); governance (decision rights, meeting rhythm, change control); top five risks; and approval lines.

Rewrite any objective that is vague: Before "Improve onboarding". After "Reduce time to first completed task for new customers from 14 days to 7 by 30 September, measured in the product dashboard." List open questions that must be answered before signing. Flag any assumption I did not support with evidence as [VERIFY]. Keep language plain.

Keep the charter to one page of at most 450 words. Where a field cannot be filled from my inputs, write 'to be agreed with sponsor' and list who must decide, rather than inventing a figure or a date.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

Project: Move customer orders to the new booking system.
Purpose: lost bookings average 11 a month because staff re-key orders.
Objective: cut re-keying errors from 11 to 3 a month by 30 September.
Scope in: web form, order import, staff training. Scope out: payment changes, mobile app.
Sponsor: operations director. Manager: Elena. Team: two staff, one contractor.
Budget: 18,000; contingency 10 percent.
Milestones: design agreed 15 June; pilot 10 August; go-live 1 September.
Top risks: data import quality; staff time during peak season; vendor delay.
Decision rights: Elena decides within budget; the sponsor approves scope changes.
Approval: signed by sponsor on 3 June.

• charter