MGT 440 Topic 2 project charter example

Project Management Grand Canyon University Free custom sample in 24 to 48h

This MGT 440 Topic 2 sample paper is a two-page charter authorizing a credit union to move its 40-agent member contact center to the third floor of headquarters before the lease ends. It belongs to GCU MGT 440, Project Management, listed as MGT-440 in the Grand Canyon University BS in Business Management program. The charter states the business reason and three measurable objectives, including no more than one day of reduced member service. It names the sponsor and project manager and writes the manager's authority as permissions, such as approving purchases up to $10,000 and escalating conflicts within two business days. Functional managers' hour commitments and the fixed lease date are recorded.

CourseMGT 440 Project Management
TopicTopic 2
Paper typeProject charter
LengthAbout 990 words, 4 pages
FormatAPA 7 student paper
SchoolGrand Canyon University (GCU)
ProgramBS in Business Management
UpdatedOctober 2026

Free sample paper for MGT 440 Topic 2

1

Project Charter: Relocating the Member Contact Center to the Third Floor Before the Lease Ends, With the Project Manager's Authority Written as Specific Permissions

[Author Name]

Colangelo College of Business, Grand Canyon University

MGT-440: Project Management

Topic 2 Assignment

[Instructor Name]

[Date]

The organization, setting and figures below are a composite written as a model document. No real employer, client, colleague or patient is described.

What this page is doingThe charter is titled as the document a sponsor signs, and the subtitle names the feature most charters leave vague, the project manager's actual authority. The credit union, its people and every figure are an illustrative composite; the sources are real.
2

Project Charter: Relocating the Member Contact Center to the Third Floor Before the Lease Ends, With the Project Manager's Authority Written as Specific Permissions

Why This Project

Canyon Ridge Federal Credit Union's member contact center, 40 agents who handle phone and chat service for about 95,000 members, occupies leased space on the first floor of a building two blocks from headquarters. The lease ends on October 31 and will not be renewed, because the credit union owns its headquarters building and has vacant space on the third floor. Moving the contact center into owned space saves an illustrative $210,000 a year in rent once the move is complete. This project relocates the contact center to the third floor of headquarters before the lease ends, with minimal disruption to member service.

This charter formally authorizes the project, names the project manager and states the authority that comes with the role. It is not the project plan; the plan follows once the charter is signed. A charter exists to put the sponsor's commitment on paper and to let the project manager draw on people and money that belong to other departments (Project Management Institute, 2021).

The sponsor's support matters because the project crosses three departments. Facilities, IT and the contact center each report to different managers, and none of them reports to the project manager. Without a signed charter, every request for staff time would become a negotiation.

What this page is doingThe charter opens with the business reason in one paragraph and states plainly what kind of document it is, so no one mistakes it for the plan.
3

Objectives

1. All 40 agent positions take member calls and chats from the third floor by October 24, one week before the lease ends.

2. Member service runs at reduced capacity for no more than one business day during the cutover, measured as calls answered within 60 seconds falling below 80 percent for no more than one day.

3. The project is completed within a budget of $180,000, with a management reserve of $12,000 held by the sponsor.

The objectives are written so that each can be checked at the end. The second, in particular, turns a vague goal of minimal disruption into a measure the contact center already tracks every day, so no one has to argue afterward about whether the move went smoothly.

Sponsor and Project Manager

Sponsor: Rachel Dominguez, Chief Operating Officer. The sponsor approves the charter, controls the management reserve, decides conflicts escalated by the project manager and accepts the completed project.

Project manager: Marcus Lee, Operations Project Manager. The project manager plans and runs the project and reports status to the sponsor every two weeks.

The Project Manager's Authority

Authority in many charters is written as "the project manager has authority to manage the project," which leaves every real question unanswered. In a functional organization where the project manager owns no staff, unclear authority is the most common reason project managers cannot move work forward (Kerzner, 2017). This charter writes authority as specific permissions.

1. The project manager may approve purchases for the project up to $10,000 per item without further approval, within the project budget. Purchases above $10,000 require the sponsor's signature.

2. The project manager may assign tasks directly to the facilities and IT staff committed to the project below, within their committed hours, without going through their managers for each task.

3. The project manager may schedule the cutover weekend and require attendance from committed staff, with two weeks' notice.

4. When a functional manager and the project manager disagree on priorities or staff time, the project manager escalates to the sponsor within two business days, and the sponsor decides within two business days of escalation.

5. The project manager may not change the objectives, budget or end date. Those changes require the sponsor's written approval through the change process.

These permissions were discussed with each functional manager before the charter was drafted. The purchase limit, for instance, was set at $10,000 because most furniture and cabling orders fall below it, so the project manager can keep work moving without waiting for signatures, while larger commitments still reach the sponsor.

What this page is doingAuthority is written as permissions with limits, including what the project manager may not do, which turns a vague phrase into something every party can act on.
4

Functional Managers' Commitments

The project depends on staff who report to other managers. Each commitment below has been agreed by the named manager.

1. Facilities, Dana Price, Facilities Manager: one facilities coordinator at 50 percent of time from June 1 to October 31, about 450 hours, plus the facilities manager's review of layout and building permits.

2. IT, Sam Okoye, IT Infrastructure Manager: one network engineer at 40 percent from July 1 to October 31, about 280 hours, and two technicians for the cutover weekend.

3. Member contact center, Tasha Reed, Contact Center Manager: two senior agents for four hours each week from August 1 for layout review and testing, and full participation in the cutover plan.

Clarifying who supplies which resources, and who decides when demands conflict, is one of the core purposes of defining project roles at the start (Zwikael & Meredith, 2018).

Constraints and Assumptions

Fixed constraint: the current lease ends on October 31. Holdover beyond that date is charged at 150 percent of normal rent, and the landlord has another tenant waiting. The end date is therefore not negotiable.

Other constraints: the third floor's electrical capacity must be upgraded by the building's landlord-approved electrician before build-out, and the credit union's phone platform will not be replaced as part of this project.

Assumptions: the third floor is available from June 1; furniture can be delivered within six weeks of order; and contact center staffing levels remain stable through the summer.

Should one of these assumptions fail, it goes to the sponsor with the sponsor at the next status meeting, since each one affects the schedule. The availability of the third floor from June 1 matters most, because build-out cannot begin until the space is clear.

Approval

By signing, the sponsor authorizes the project and the project manager's authority as described above, and the functional managers confirm their commitments.

Sponsor: ____________________ Date: ________

Project manager: ____________________ Date: ________

Facilities, IT and contact center managers: ____________________ Date: ________

References

Kerzner, H. (2017). Project management: A systems approach to planning, scheduling, and controlling (12th ed.). Wiley.

Project Management Institute. (2021). A guide to the project management body of knowledge (PMBOK guide) (7th ed.). Project Management Institute.

Zwikael, O., & Meredith, J. R. (2018). Who's who in the project zoo? The ten core project roles. International Journal of Operations & Production Management, 38(2), 474-492. https://doi.org/10.1108/IJOPM-05-2017-0274

Reading the GCU MGT 440 Topic 2 instructions

The Topic 2 instructions in MGT-440 ask students to write a project charter. A charter that reads like a project plan, or that grants vague authority to manage the project, misses its purpose. The assignment rewards a short document a sponsor would sign: the reason for the project, measurable objectives, the sponsor and project manager by name and the project manager's authority written as specific permissions with limits. Students should record the commitments of functional managers who supply staff, identify the fixed constraint and the main assumptions, and keep the document brief enough that it can be read and approved in one sitting rather than shelved as background reading.

Inside the MGT 440 Topic 2 example

The charter opens with one paragraph on why the move is needed and states that it is not the project plan. Three objectives follow, each measurable, including a service threshold for the cutover. The sponsor and project manager are named with their roles. Five numbered permissions define the project manager's authority, including what the manager may not change. Functional managers' commitments are listed by name, role and hours. The fixed lease date, other constraints and assumptions are recorded, and a signature block for the sponsor, project manager and functional managers closes the document.

Where the marks sit in the MGT 440 Topic 2 rubric

Instructors grading the charter reward a document that grants real authority in specific terms. Strong charters state measurable objectives, name the people involved and write the project manager's authority as permissions with limits, including escalation timelines. Credit goes to recording functional managers' commitments with hours, since a project manager without staff of their own depends on them. The rubric values identifying the fixed constraint and its consequence, and keeping the charter short enough to be signed. The highest band cites project management sources on the purpose of a charter and the roles involved. Charters that say only that the manager has authority to manage the project usually lose marks.

MGT 440 Topic 2 help: mistakes that cost marks

Authority is where most charter marks are decided. A document naming a project manager and describing that person as responsible for success has handed over responsibility without power, and the topic asks precisely what the role can decide. Objectives written as goals, such as a smooth transition, cannot be checked at closure and invite argument about whether the project succeeded. Charters listing no exclusions leave scope open to every department that hopes to benefit. Staff commitments missing from the document mean the functional managers keep full control of the people the project depends on. Budgets without a stated reserve or its owner blur the point at which spending needs approval. A charter that runs to a full schedule and task list has turned into a plan and lost the purpose of being signed quickly.

Get an MGT-440 Topic 2 example written to your instructions

Send the MGT-440 Topic 2 instructions, your section's rubric and the project or case the charter is for. We write a custom example to those criteria, with checkable objectives, exclusions listed, authority set out as permissions, borrowed staff recorded and the fixed constraint named, in 24 to 48 hours. The first one costs nothing, and all figures come labeled illustrative.

More MGT 440 papers and BS in Business Management samples

MGT 440 Topic 2 questions, answered

Who writes and signs a project charter?

The project manager often drafts it, but the sponsor issues and signs it, because the charter is the organization granting authority and resources to the project. Where staff are lent from other departments, their managers signing as well turns a verbal promise into a recorded commitment. A charter signed only by the person it empowers has authorized nothing at all.

How is a charter different from a project plan?

The charter authorizes the project and sets its boundaries, objectives, authority and summary budget, and it is meant to be short enough to sign quickly. The plan comes afterward and holds the detail: the work breakdown, the schedule, the risk register and the cost baseline. Packing a full schedule into the charter usually delays the signature it exists to obtain.

What authority does a project manager usually have?

It depends on how the organization is structured. In a strong matrix the project manager controls the budget and directs assigned staff; in a weak matrix the role coordinates while functional managers keep the real decisions. The charter should state which applies, in specific permissions, so nobody discovers the limits halfway through the work.

Where can I find a free MGT 440 Topic 2 sample paper?

The contact center charter appears here, including the reason, objectives, sponsor and manager, the five permissions, functional commitments, constraints and the approval block. Share the project you are chartering, and a free charter can be drafted for it.

How is authority written in MGT 440 Topic 2?

As specific permissions: approving purchases up to $10,000 per item, assigning tasks to committed facilities and IT staff, scheduling the cutover weekend and escalating conflicts to the sponsor within two business days.