A project charter is a document that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities. It can be developed by the project sponsor or the project manager in collaboration with the initiating entity.

The project charter documents the high-level information on the project and on the product, service, or result the project is intended to satisfy. It ensures a common understanding by the stakeholders of the key deliverables, milestones, and the responsibilities of the project manager. A project charter usually includes the following key sections:

  • Project description
  • Project requirements
  • Assigned project manager and authority level
  • Summary milestone schedule
  • Business case

This process is performed once or at predetermined points in the project. As a result, the project charter shouldn’t be too detailed. You shouldn’t have to update the charter every time you change something about your project for it to stay accurate.

The other output of the Develop Project Charter process, besides the project charter itself, is an assumption log. The assumption log is used to record all assumptions and constraints throughout the project life cycle. These are lower-level activity and task assumptions generated throughout the project such as defining technical specifications, estimates, schedule, risks, etc.

Create Project Charter Doc

Create a Project Charter doc with Project Charter and Assumption Log pages. Provide the page structure and content manually, paste the content from an MS Word document (ClickUp will do its best to transform the content into the ClickUp format) or create the pages from company templates (organizational process assets).

Create Related Tasks

To ensure that any assignments and changes related to the project charter are easy to execute and monitor by relevant team members, create a Develop Project Charter task with two subtasks corresponding to the Develop Project Charter process outputs (project charter and assumption log).

You can designate assignees or watchers to the corresponding tasks to keep the team members notified of the new assignments, changes, and comments to the related tasks (and docs) via notifications based on their settings. The changes to Project Charter and Assumption Log pages need to be tracked during the doc creation stage (e.g. as the project sponsor will often delegate the actual creation of the project charter to the project manager or as project requirements and milestones are discussed and finalized within the project management team) as well as going forward as the team logs all assumptions and tracks the validation of each one.

You can also build simple links between tasks and pages or create an advanced database using relationships between different lists (e.g. a task list and a team resources list). Reference relationships are created automatically when a task or doc is linked or mentioned somewhere else. If you’ve mentioned a task or doc in a comment, you’ll see them added to the relationship table. Links to tasks from inside a doc help you cross-reference resources anywhere you need them.

Attach the Project Charter doc or the Project Charter and Assumption Log pages to the relevant tasks as an attachment, relationship or with a link to enable quick access between a task and the corresponding doc or page.

Edit Project Charter Doc

ClickUp’s collaboration features ensure everyone in your workspace is able to comment, edit, and work on docs at the same time, without any overlap. When someone else is editing, you see their live cursor typing. You’re also able to edit at the same time, just like Google Docs.

Add a contributor to a doc or designate a team member as the author.

Comments are one of ClickUp’s most powerful tools for collaboration. Assign a comment if it requires effort from anyone on your team. This creates a new required item for the assignee to complete before the task can be closed.

In addition:

  • Mention people in comments
  • Organize your doc comments by nesting your replies with threaded comment
  • Keep conversations organized by highlighting text to reply to specific parts of a comment
  • Share a link to doc comments to share conversations
  • Turn comment text into a reminder

Share Project Charter Doc

A project charter can be shred with:

  • Project sponsor(s): the person who formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities
  • Project management team: the members of the project team who are directly involved in project management activities
  • Project team: a set of individuals performing the work of the project to achieve its objectives

Here are your sharing options:

  • Everyone in the workspace (does not include guests)
  • Specific people and teams, including guests
  • People you invite to your workspace while sharing a doc
  • Specific tasks or locations

You can also:

  • Export a doc
  • Share publicly
  • Copy the Internal link to share it with your team

You can also use similar sharing options with individual pages:

  • With workspace members using the internal link
  • Export the page
  • Share publicly

Pages always inherit permissions from the doc they live in.

When sharing with specific people, you can set their permissions.

Leave a Reply

Your email address will not be published.