Project charter is an output in the initiating phase. This is a document which officially gives authorized project manager to manage the project. The project charter can be created by PM as assigned by project sponsor. The information is high level and need to be elaborated further in the next phase. In Rita’s book (2013), the information that must be written in the project charter including:

1. Project Tittle and description (what is the project?)
2. PM assigned and authority level (who is given authority to lead the project and can he/she determine, manage and approve changes to the budget, schedule, staffing etc?)
3. business case (why is the project being done? on what financial or other basis can we justify doing the project? describe the project aims and justification)
4. resource preassigned (How many or which resources will be provided?)
5. stakeholders (Who will affect or be affected by project [the project influence], as known to date?)
6. stakeholders requirements as known (requirements related to both project and product scope)
7. product description/deliverables (what specific product deliverables are wanted and what will be the end of the project?)
8. assumption (what is believe to be the true or reliable in the situation? who do we believe to be the case but do not have proof or data for?)
9. constraints (which factors may limit our ability to deliver? what boundaries or parameters will the project have to function within?)
10. Measurable project objective (how does the project tie into the organization strategic goals? what project objective support these goals? the objective need to be measurable and will depend on the defined priority of the project constraints)
11. Project Approval Requirements (what items need to be approved for the project and who will have sign-off? what designated success?)
12.  High level project risk (potential threats and opportunities for the project)
13. Project sponsors authorizing the project