Project change request

A project change request is a structured document that evaluates a proposed change to a project's scope before it's approved or rejected.

Its purpose is to slow down scope changes just enough to force an honest accounting of their cost, rather than letting scope creep in through informal side conversations. A well-formed change request states the change itself, the rationale behind it, the value it's expected to add, its impact on the project's existing constraints (time, cost, scope, quality — changing one usually means adjusting at least one of the others), and who has the authority to approve or reject it. Kanbai's version, drawn from the 17-book project-management corpus (Project Management for the Unofficial Project Manager), structures exactly those five sections. It's one of Kanbai's seven corpus-grounded instruments, fillable per-project or standalone with no account, exporting as Markdown either way. Kanbai deliberately doesn't implement change control as a workflow with approval states — v1's scope excludes baselines and formal change control — so a change request here is a document you fill in and share, not a ticket that moves through a queue.