Document template · generic.project.project_charter
Project Charter
- Render-verified
- Informational
- Version 1.0.0
Formal document authorising the project, naming the sponsor and project manager, fixing the business case, SMART objectives, in-/out-of-scope items, high-level milestones, budget summary, success criteria, key stakeholders, assumptions and constraints, signed by sponsor and PM.
JSON Schema
Fields in this template
Data sent to the API is validated against the template’s JSON Schema before anything is rendered. This template defines 35 fields:
| Field | Required | Type | Description |
|---|---|---|---|
| entity | Required | string | |
| project_name | Required | string | |
| project_code | Required | string | |
| sponsor | Required | object | |
| sponsor.name | Required | string | |
| sponsor.title | Required | string | |
| project_manager | Required | object | |
| project_manager.name | Required | string | |
| project_manager.title | Required | string | |
| charter_date | Required | date | |
| planned_start | Required | date | |
| planned_end | Required | date | |
| business_case | Required | string | |
| objectives | Required | array of string | |
| scope_in | Required | array of string | |
| scope_out | Required | array of string | |
| milestones | Required | array of object | |
| milestones[].name | Required | string | |
| milestones[].target_date | Required | date | |
| milestones[].deliverable | Required | string | |
| milestones[].owner | Required | string | |
| budget | Required | object | |
| budget.capex | Required | number | |
| budget.opex | Required | number | |
| budget.contingency | Required | number | |
| budget.total | Required | number | |
| budget.note | Required | string | |
| success_criteria | Required | array of string | |
| stakeholders | Required | array of object | |
| stakeholders[].name | Required | string |
+5 more fields — the full JSON Schema is available in the dashboard and via the API.
POST /render
Generate it
One POST /render call: send your JSON, get the finished PDF back. Or skip the JSON entirely and describe the document in plain language on chut.app.
curl -X POST https://api.papii.eu/render \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"template": "generic.project.project_charter",
"data": { ... },
"options": {"language": "en"}
}' -o project-charter.pdf Frequently asked questions
What is “Project Charter”?
Formal document authorising the project, naming the sponsor and project manager, fixing the business case, SMART objectives, in-/out-of-scope items, high-level milestones, budget summary, success criteria, key stakeholders, assumptions and constraints, signed by sponsor and PM. On papii this document is available as template generic.project.project_charter: a JSON Schema plus a deterministic PDF renderer, so the same data always produces the same document.
Can I generate a Project Charter with AI?
Yes. chut.app — the AI back office papii powers — fills this template from a plain-language description: you describe the document in one sentence, the AI structures the data, papii validates it against the schema and renders the PDF. Developers can also call the papii API directly with structured JSON.
Is the Project Charter template legally compliant?
This template is render-verified: its schema, sample data and PDF output are automatically tested on every release. It is published with status “ready”, meaning it has not yet been through papii’s final legal review. Where it references specific legislation, that is stated in the template description — always have a professional check documents with legal effect before relying on them.