The are three essential document required for a project:
  - Project Charter -- to document authorization to proceed and set high level goals and objectives.
  - Project Plan -- to describe how to manage the project.
  - Project Schedule -- to describe the sequencing of activities, document work assignments and track progress.
 
The format I prefer for a Project Charter is to follow the outline of the PMBOK and then refer to the PMBOK for specifics about a charter. The following table provides a quick summary of the sections and the purpose for each section.

Section	Purpose
Signatures	One of the most important components of a project charter is the signatures or authorizations that state that this project is to proceed. Too many projects with tightly defined goals flounder because they do not have backing. Get corporate buy-in before proceeding.
Integration	The purpose for this section is to outline the purpose for the project and describe the framework that will guide the project from inception to closure. Include a description of the business need that is motivating this project.
Scope	The purpose for this section of the Project Charter is to define what is included in this project and in the product that this project will create. Document the goals for this project and then expand on the specific objectives required to achieve those goals. Include a preliminary work breakdown structure if possible.
Time	Use this section of the document to describe the major project milestones. Also list any time constraints that pose a project risk.
Cost	Use this section of the document to describe the cost of the project -- both positive (benefits and cost reductions) and negative (expenditures). Include a return on investment calculation.
Quality	Use this section of the document to describe quality criteria and measurements that are expected for both the project and the product.
Human Resources	Use this section of the document to describe the roles and responsibilities for this project. Include a Responsibility Assignment Matrix (RAM). If appropriate, use an ARCI chart to show Accountable (corporately responsible), Responsible (resource), Consultative (information provider or subject matter expert) and Informed (information recipient).
Communication	Use this section of the document to describe the type and frequency of communication that will be used to coordinate this project.
Risk	Describe the risks, both positive and negative, and provide a preliminary explanation of the approach that will be taken to manage each risk.
Procurement	Describe the purchases that will be required for this project. Note if those purchases can be capitalized or must be expensed.
References	List the references that support the work for this project.
Revision History	List the revisions that have been made to this document.

  - The charter should either include or reference an external document that includes:

PMBOK 2004 Project Charter	Prior Version
Assign the project manager while the charter is being developed	The project manager is identified in the charter and assigned to the project.
Projects are usually authorized external to the organization that will execute the project	The charter is created by a manager external to the organization that will execute the project.
Business need	Business need
High level project description	High level project description
Assumptions	Assumptions
Constraints	Constraints
Requirements from: sponsor, customer and other stakeholders
Product requirements
Purpose
Milestones
Stakeholder identification and needs
Project organizational chart
Justification
Cost estimate and return on investment