The definition of a project's objectives lives in the project charter — the authorizing document that names the project, its purpose, and its measurable objectives before work begins. That answer holds under the PMBOK Guide, Sixth Edition (2017), and it survives the Seventh Edition's (2021) shift to principles, because the charter never stopped being the document that authorizes the project and pins down what it must achieve. Two other documents can carry objectives later: the project management plan, which operationalizes them, and the business case, which justifies them. Keep that order straight and you'll answer exam questions, audit questions, and stakeholder arguments correctly.

What the Project Charter Is and Why Objectives Sit Inside It

The charter is the formal document that authorizes the project and gives the project manager authority to apply organizational resources to project activities. That language comes straight from the PMBOK Guide, Sixth Edition, Section 4.1, and it explains why objectives belong there rather than anywhere else. If the document grants authority, it must also state what the authority exists to achieve. The charter is issued by the sponsor or a senior manager, not authored by the project manager alone.

Objectives enter the charter as part of the project's high-level description. The Sixth Edition lists the charter's typical contents as project purpose, measurable project objectives and related success criteria, high-level requirements, high-level risks, summary milestone schedule, summary budget, stakeholder list, approval requirements, and the assigned project manager with authority level. Notice that objectives sit right next to purpose. A charter that names a purpose but no measurable objective has left the most useful half blank.

Measurability is the operational test. An objective such as "improve customer satisfaction" fails it; "raise post-support satisfaction from 4.1 to 4.4 on a 5-point scale within 18 months of launch" passes. The charter sets that target. Later planning breaks it into requirements, acceptance criteria, and deliverables, but the charter is where the number first appears with a date attached.

One consequence trips people up: objectives are set under conditions of high uncertainty. The charter is written when little is detailed, so its objectives are strategic and outcome-level rather than task-level. A manufacturing sponsor charters a plant upgrade to cut unplanned downtime by 20% before anyone knows which machines will be replaced. Precision arrives through progressive elaboration, and the charter's objectives are meant to stay coarse enough to survive that elaboration.

The Business Case Upstream: Objectives Start With a Justification

Objectives don't appear from nowhere. The business case supplies the rationale — the documented economic feasibility study or value estimate that justifies the investment — and the charter translates that rationale into authorizing objectives. The Sixth Edition treats the business case as an input to developing the charter, which means the two documents form a chain of custody for every objective you'll later be measured against. Break the chain and nobody can explain why the target exists.

The business case usually belongs to the sponsor or the portfolio function, not the project manager. It carries cost-benefit analysis, expected value, and often a "do nothing" option for comparison. A sponsor who approves a charter without a live business case is chartering activity, not investment. That distinction matters at audit time, when the question is why the organization spent money, not which tasks ran late.

The two documents serve different readers. The business case speaks to whoever approves funding; the charter speaks to whoever executes and governs. Objectives appear in both but with different weight — strategic and financial in the business case, measurable and success-criteria-linked in the charter. If you only remember one, remember that the charter is the controlled, approved version that binds the delivery team.

Here's the edge case nobody documents well. When a business case is revised mid-project — the market shifted, a competitor moved — the objectives in the charter don't automatically update. They change only through formal change control or a charter amendment approved by the sponsor. A team that quietly shifts its targets to match a new business case has detached its authority from its objective, which is a governance failure even when the new target is smarter.

The Project Management Plan Takes Objectives Operational

The project management plan integrates all subsidiary plans, baselines, and supporting documents into one coherent whole, and it is where the charter's objectives get decomposed. The charter says "cut downtime by 20%"; the plan says which lines get replaced, on what schedule, with what acceptance criteria and which quality metrics. Confusing the two documents is the most common error this keyword surfaces, because both contain objectives in some form.

The Seventh Edition's shift supports this reading. It replaced the process groups with performance domains and dropped the named knowledge areas, but it kept the principle that a project needs a documented, approved approach to delivery. It also kept the business case and benefits management as central concerns, which means objectives still trace back to value, not to task lists. The form changed; the function didn't.

Watch for a version-specific wrinkle. The PMBOK Guide Seventh Edition is principle-based and cites only a handful of documents by name; the Sixth Edition remains the process-and-document reference most certification candidates use, and it remains widely in circulation. If your exam or audit standard cites the Sixth, answer "charter" without hedging. If your organization has moved to the Seventh, the charter still exists — it just gets discussed as an input to the performance domains.

The plan is also where objectives become changeable in practice. Baseline changes to scope, schedule, or cost flow through integrated change control and route to the change control board, which is typically chaired by the sponsor. The charter sits above that machinery. You can re-baseline schedule and budget within tolerances; you cannot redefine why the project exists without the sponsor's signature.

Documents Compared: Where Each One Carries Objectives

Reading these side by side prevents the confusion that motivates the question. Objectives appear in more than one document, but they appear with different authority, different audience, and different change rules.

Document Form objectives take Author or owner Change route Answers the question "why are we doing this?"
Business case Value rationale, cost-benefit, strategic fit Sponsor or portfolio office Revised only if the investment decision reopens Yes, originally
Project charter Measurable objectives and related success criteria, high-level Sponsor or senior manager Formal amendment approved by sponsor Yes, in binding form
Project management plan Decomposed objectives, baselines, acceptance criteria Project manager with team Integrated change control, change control board Partially, through scope statement
Benefits management plan Targeted benefits, owners, metrics, timeframes Sponsor with business owners Updated as benefit owners reforecast Yes, in measurable-benefit form

The benefits management plan deserves a mention because the Sixth Edition ties it to business documents rather than the project plan. It names benefit owners, metrics, and expected realization timeframes. A charter objective without a benefits plan behind it tends to drift into theater — everyone agrees dashboard downtime fell, nobody checks whether the operational cost recorded by finance actually moved.

Here's a comparison row the top results usually skip. Objectives in the charter are binding on the project manager; objectives in the plan are binding on the team. Those are different contracts. If a customer demands an outcome that contradicts the charter, the project manager escalates to the sponsor. If a customer demands a feature that contradicts the plan's baselines, the project manager convenes change control. Mixing the escalation paths wastes weeks.

Verdict time. If the question is "which document defines the objectives?" the charter wins on both PMBOK editions and across audit practice. If the question is "where do I look to check whether objectives are being met?" the answer flips to the plan and its measurement baselines. Keep both answers available and you'll be right every time.

Objectives Versus Deliverables, Requirements, and Benefits

Four terms get swapped in hallway conversations, and the swap is expensive. An objective names a measurable outcome the investment is meant to produce. A deliverable is a verifiable product or service the team hands over. A requirement is a condition or capability the deliverable must satisfy. A benefit is the realized value that follows from the delivered product in use. Only the first belongs in the charter as a defining element.

Consider a payroll system migration. The objective is "process 100% of monthly payroll runs on the new platform within 6 hours, by October next year." The deliverables include the migrated data set, configured interfaces, and a tested parallel-run report. The requirement is "support 14 pay cycles across three regions." The benefit is the estimated reduction in processing staff hours after adoption. Each of those lives in a different document — charter, scope statement, requirements documentation, benefits management plan.

Finance folks use "objective" to mean the return target. Quality folks use it to mean fold the defect rate. Legal folks use it to mean fulfill the contract obligations. All three are legitimate readings of objectives, but they load different documents. A project manager who learns to ask "which objective do you mean — the charter target, the contractual deliverable, or the benefit?" saves themselves a meeting.

The misuse that costs the most is treating a deliverable as the objective. "Deliver the new CRM by June" defines activity, not success. If the CRM ships in June and adoption stalls at 40% of the sales floor, the project met its deliverable and failed its objective. Charter the adoption target, not the deployment date.

How Objectives Get Written Into the Charter: A Worked Sequence

Writing objectives into a charter is not a fill-in-the-blank exercise. It's a sequence with inputs, a drafting step, and a formal approval that converts a draft into authority.

1: Collect the business case and any portfolio-level benefit targets. Confirm with the sponsor that the values being promised are still current before drafting anything. 2: Draft the purpose statement in one to three sentences that name the strategic problem the project addresses, distinct from any solution preference. 3: Draft each objective with a metric, a target value, a timeframe, and — where practical — a baseline to measure against. 4: List the high-level requirements, risks, milestones, budget summary, key stakeholders, and the appointed project manager with authority level. 5: Route the draft to the sponsor and any approver named in the organizational governance structure. Capture comments in version control. 6: Obtain formal approval and record the signature or digital approval evidence. Archive the approved version where the team can retrieve it. 7: Communicate the objectives to the delivery team in a kickoff or charter review and confirm each objective has an owner for measurement.

Failure handling matters in step three. If the sponsor can't supply a baseline for a proposed metric — no current downtime figure, no survey baseline, no cycle time record — the option is to define the baseline measurement as an objective in its own right rather than guess. An objective reading "establish a defensible baseline for X within 30 days" is honest. An objective reading "improve X by 20%" against a fabricated baseline is audit bait.

The single most common failure in this sequence is skipping step six and treating verbal approval as authority. If the sponsor said "looks good" in a hallway and the business case collapsed two months later, the project lacks defensible authority. Get it in writing, get it archived, and get it sent to the last person who read it half-asleep during review.

When a Missing or Wrong Document Causes Failure

The failure mode is predictable and worth rehearsing before it happens. A project that starts with no approved charter has no formal objective, no authority, no success criteria, and no baseline to measure against. Every subsequent issue becomes a negotiation, because there's no reference point. The cost is rarely visible on day one; it appears at month six when two departments argue over what "done" means.

Two named patterns make the failure concrete. First, change requests that reshape objectives without a charter amendment. If a customer asks for an extra integration that materially changes the cost-benefit case, and the team just adds a scope line, the plan is now asserting an authority it does not have. Escalate to the sponsor, amend the charter or the business case, and route the resulting change through change control. Second, audits that find no baseline measurement. Sponsors demand reductions; no one recorded the starting figure; the finance close-out has no number to defend.

The second failure is repairing objectives on the fly. A project manager who silently lowers a success target to make a milestone status report look green has converted a governance failure into a reporting fraud. The correct move is a documented change to the charter, approved by the sponsor, even if the new target is smaller than the old one. Sponsors can accept a reduction. They cannot accept discovering it after the fact.

For organizations working under the Seventh Edition's principles, one risk is cultural. The principle-based guide nudges teams toward adaptive delivery, and some interpret that as permission to skip formal charters. Don't. Adaptive delivery changes how scope evolves; it doesn't change who authorizes the project or what success means. An approved charter with coarse, measurable objectives is compatible with adaptive delivery. So is a charter reviewed and refreshed at major stage boundaries.

Where Objectives Appear Under the Seventh Edition and Agile Practice

The Seventh Edition didn't relocate objectives even though it changed how projects are described. Its eight performance domains — stakeholder, team, development approach and life cycle, planning, project work, delivery, measurement, and uncertainty — all lean on the principle that a project's purpose is explicitly defined and approved. The delivery domain covers deliverables, but measurement domain covers outcomes. Objectives still live in the authorization document, because otherwise the measurement domain has nothing to measure against.

Agile practice aligns with this. Product visions and product goals sit above the team in the product hierarchy, and the initiative that requires funding gets a lightweight charter — commonly called a lean charter or one-page charter. The contents are recognizable: purpose, measurable outcome, key stakeholders, high-level constraints, rough budget, and sponsor. The team's sprint goals and product backlog sit under those. A sprint goal answer to "what are the objectives?" is not wrong for a single iteration; it's wrong for the project.

A useful contrast row for anyone comparing standard and agile-oriented documents: charter objectives are outcome-focused and sponsor-approved, while sprint goals are delivery-focused and team-committed. Both contain measurement, but only one binds spending and authority. Many teams assume the modern document supersedes the classic one. It doesn't. Each layer answers a different question.

One regional wrinkle is worth mentioning if your organization operates under a contract-heavy delivery model. Government and public-sector procurements in several jurisdictions publish standard contract conditions that mirror the charter's function — the tender documents plus the awarded contract define the objectives and the acceptance criteria. The charter still exists in the internal project governance, but its objectives must align with those contract obligations. Confirm on your own procurement authority's published conditions; the specifics vary by jurisdiction and sector.

Prerequisites, Assumptions, and the Limits of the Charter

If you want the charter to define objectives defensibly, plan for four prerequisites: an approved business case, a named sponsor with approval authority, high-level requirements from the requesting stakeholders, and a candidate project manager to be assigned. Miss any one and the charter either fails approval or contains unreviewed guesses. The Sixth Edition treats the business case, agreements, enterprise environmental factors, and organizational process assets as the inputs to developing the charter; the first two are the ones that carry the content, and the last two carry the rules.

Assumptions embedded in objectives deserve explicit capture. When a sponsor sets a 15% cost reduction objective based on headcount assumptions, those assumptions need to be written into the charter's high-level assumptions list. Otherwise the objective remains silent on the dependency that could invalidate it. A written assumption can be reviewed, contested, and validated. An unwritten one is a surprise waiting in the closeout meeting.

What the charter cannot do is also useful to know. It cannot detail what work is in scope — that's the scope statement and work breakdown structure. It cannot produce a schedule or a resource plan. It cannot determine the measurement methodology — the measurement plan under the project management plan does that. A charter that attempts all of these is either a mislabeled project plan or a document that will get rewritten within a month.

Return to the limiting condition. If the metric target has no baseline, the charter should require baseline establishment as an explicit first objective. If the sponsor will not sign, no objective is authorized regardless of how well it's written. If the business case is stale, the objective is built on sand. The charter answers where the objectives live; it only works when the sponsor signs and the baseline exists.

FAQ

Is the project charter always the document that defines objectives?

Yes, with one qualification: the project charter is the authorizing document, but the objectives it contains trace back to the business case and downstream to the project management plan. If your organization uses a portfolio-level mandate as the sole authorization, the mandate functions as the charter for these purposes. Confirm which document your organization treats as the authorizing one.

What is the difference between the project charter and the project management plan?

The charter authorizes and defines measurable objectives; the plan operationalizes them through baselines, subsidiary plans, and acceptance criteria. The Sixth Edition ranks the charter above the plan in authority. A change to the plan stays in the change control board's jurisdiction; a change to the charter needs the sponsor's signature. Both contain objectives; only one binds the project's existence.

Can objectives be changed after the charter is approved?

Yes, through formal amendment approved by the sponsor, and through the business case revision if the investment rationale changes. The charter is the highest reference point for the delivery team; the exam expectation is that charter changes route to the sponsor, not to change control. Many organizations treat the change control board as advisory to the sponsor on charter changes, which is close to standard practice.

How would I compute a measurable objective from a baseline?

Take a baseline reading — say, 42 hours of unplanned downtime per quarter — divide by the target percentage reduction, and derive the target value: a 25% reduction gives 31.5 hours per quarter. The formula is target = baseline × (1 − reduction%). If the baseline doesn't exist, define "establish a baseline reading" as the objective and attach a deadline for the reading.

Does the Seventh Edition still require a charter?

The Seventh Edition is principle-based and cites fewer named documents, so some teams assume the charter is optional. It isn't optional in governance practice; the authorization step survives. Its language gets lighter and more adaptable, but approved objectives still precede funded work. Check your certification body's current reference edition before studying.

What about the scope statement — where does that fit?

The scope statement lives inside the project management plan and describes what is in and out of scope with acceptance criteria attached. It inherits its objectives from the charter and its detail from requirements documentation. Scope change is a plan-level change; objectives change is a charter-level change.