# Project Charter

> YogoQ Core AI-readable term handoff. Preview, read-only, Reviewed/Verified only.

- Canonical URL: https://core.yogoq.com/en-US/core/charter
- Locale: en-US
- Quality: reviewed
- Publication status: published_reviewed
- Schema version: core-reviewed-term-ai-handoff-v1
- Trust policy: core-trust-policy-v1-2026-06-22

## Short Definition

Charter is a decision charter contract used for aligning sponsors, teams, and reviewers before work starts.

## 一言でいうと

Charter is a decision charter contract used for aligning sponsors, teams, and reviewers before work starts.

## 意味

Charter is a short decision contract that states why a project or initiative exists, who owns it, what is in scope, and how success will be judged. In practice it is used for aligning sponsors, teams, and reviewers before work starts by making owners, boundaries, evidence, and review triggers explicit.

## 役立つ場面

Charter changes decisions by making the owner, boundary, required evidence, and review trigger explicit before work proceeds. Charter helps teams decide whether to start, stop, resize, or resequence work using evidence rather than meeting momentum. Charter reduces rework because assumptions, unresolved questions, and follow-up responsibilities are visible enough to challenge.

- Charter changes decisions by making the owner, boundary, required evidence, and review trigger explicit before work proceeds.
- Charter helps teams decide whether to start, stop, resize, or resequence work using evidence rather than meeting momentum.
- Charter reduces rework because assumptions, unresolved questions, and follow-up responsibilities are visible enough to challenge.

## 使い方のポイント

- Define the decision question, accountable owner, and time horizon before using Charter as an operating artifact.
- Separate evidence from opinion so Charter supports judgment instead of decorating a preferred answer.
- Record what was accepted, what was deferred, and what signal would cause a future change in Charter.
- Use Charter to choose a management action, not merely to produce a tidy document or status label.
- Revise or retire Charter when the boundary, owner, evidence, or operating context changes materially.

## 判断するときの注意点

Charter will not speed execution when ownership remains ambiguous. Charter becomes storage instead of a decision aid when it is too long to use. Charter needs change history or teams cannot reconstruct why the decision moved.

- Charter will not speed execution when ownership remains ambiguous.
- Charter becomes storage instead of a decision aid when it is too long to use.
- Charter needs change history or teams cannot reconstruct why the decision moved.

## よくある誤解 / 落とし穴

- Charter is not valuable because the label exists; it is valuable only when it changes a decision or execution behavior.
- More detail is not automatically better for Charter; the useful level is the one that clarifies ownership and review.
- Charter is not a one-time workshop output because the artifact must stay current while the decision remains live.

## 最小例

A team uses Charter after noticing that discussion keeps producing activity without a clear management decision. For Charter, the team defines the intended outcome, names one accountable owner, and lists the evidence that would change the decision. During the Charter review, the team compares current evidence with the recorded boundary, adjusts the scope, and assigns follow-through work. The Charter record now helps people see why the action was chosen, what risk was accepted, and when the decision should be revisited.

## 似ている言葉との違い

Separate nearby terms by the decision each one supports. Business plan | Explains the business logic | Charter defines the operating authorization Scope | Draws the boundary | Charter connects boundary to owner and outcome Project | Organizes execution | Charter authorizes why that execution should exist

- Business plan | Explains the business logic | Charter defines the operating authorization
- Scope | Draws the boundary | Charter connects boundary to owner and outcome
- Project | Organizes execution | Charter authorizes why that execution should exist

## FAQ

### How long should a charter be?

Long enough to settle owner, outcome, scope, risks, and review cadence, but short enough to be used in meetings.

### Who approves it?

The accountable sponsor and the person who owns delivery should both approve it.

### When should it change?

Change it when scope, owner, success measure, or material risk changes.

## Sources

- Principles of Management (OpenStax) - https://openstax.org/details/books/principles-management
- Wikipedia reference: Project Management - https://en.wikipedia.org/wiki/Project_management

## Limitations

This page is reference information for research and learning. For accounting, legal, finance, health, security, or other individual decisions, confirm against primary sources or qualified professionals.

- Public pages support general understanding and practical context; they are not professional advice for individual cases.
- Fast-changing information such as regulations, accounting standards, prices, product specs, and legal requirements should be checked against primary sources before final decisions.
- Even when AI-assisted drafting or audit is used, publication relies on quality gates and human-readable evidence.