Skip to content

Document template · generic.project.change_request

Project Change Request

  • Render-verified
  • Informational
  • Version 1.0.0

Project-scoped change request (CR) routed through the change control board (CCB). Captures scope, schedule (days) and cost (amount) impact together with quality and risk impact. Records the CCB decision: approved, rejected or deferred.

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 33 fields:

Field Required Type Description
entity Required string
project_name Required string
project_code Required string
cr_id Required string
change_title Required string
submitted_date Required date
requestor Required object
requestor.name Required string
requestor.title Required string
priority Required enum
currency Required string
change_description Required string
reason Required string
scope_impact Required string
schedule_impact Required object
schedule_impact.days Required integer
schedule_impact.detail Required string
cost_impact Required object
cost_impact.amount Required number
cost_impact.detail Required string
quality_impact Required string
risk_impact Required string
alternatives Optional array of string
do_nothing Optional string
recommendation Required string
ccb_decision Required object
ccb_decision.outcome Required enum
ccb_decision.date Required date
ccb_decision.rationale Required string
ccb_decision.conditions Optional string

+3 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
curl -X POST https://api.papii.eu/render \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "template": "generic.project.change_request",
    "data": { ... },
    "options": {"language": "en"}
  }' -o change-request.pdf

Frequently asked questions

What is “Project Change Request”?

Project-scoped change request (CR) routed through the change control board (CCB). Captures scope, schedule (days) and cost (amount) impact together with quality and risk impact. Records the CCB decision: approved, rejected or deferred. On papii this document is available as template generic.project.change_request: a JSON Schema plus a deterministic PDF renderer, so the same data always produces the same document.

Can I generate a Project Change Request 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 Change Request 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.