Title Page

  • Project Name

  • Date

  • Project Number

  • Version Number


    Describe the business need, opportunity or problem that the project was undertaken to address – i.e., the project justification.

  • State the project goals


    Provide a high level list of “what” needs to be done in order to reach the goals of the project. Each deliverable should be sufficiently detailed so that the Project Team will understand what needs to be accomplished. Describe the deliverable using action words (verbs) such as “deliver, provide, create, research, etc.

    Deliverables should be measurable, so the Project Sponsor and Team can determine whether the deliverable has been successfully completed at the project’s conclusion.

  • State the project's deliverables


    Document the scope of work to be delivered. To assist you in defining scope, use documentation such as RFP’, sales proposals, business requirements, functional specifications, etc. to set and limit the scope.

    In Scope is what the project will include to meet the requirements of the Project goals.

    Out of Scope excludes responsibilities, activities, deliverables or other areas that are not part of the Project.

  • The project will include:

  • The project will not include:


    Identify the significant project milestones, including invoicing dates to the client.

  • Enumerate the project milestones


    Identify the assumptions that were made to form the basis of defining scope. Also identify any assumptions that will be made for the purposes of planning the project. The objective here is to set the boundaries and address how the triple project management constraint (scope, time and cost) are potentially impacted/managed.

    List any constraints (potential factors that will impact the delivery or make it difficult to manage the project) on the project or dependencies on resources or funding to the project. Consider time, cost, dates and regulatory issues as constraints or dependencies to the project.

  • Enumerate assumptions, constraints, and dependencies


    Reference any related documents that were used to define scope and assumptions – e.g., RFQ, RFP, Sales Proposal, etc.

  • Enumerate related documents

  • Name and role of team member

Project Authorization

  • Full name and signature of Business Manager

  • Full name and signature of Project Manager

The templates available in our Public Library have been created by our customers and employees to help get you started using SafetyCulture's solutions. The templates are intended to be used as hypothetical examples only and should not be used as a substitute for professional advice. You should seek your own professional advice to determine if the use of a template is permissible in your workplace or jurisdiction. You should independently determine whether the template is suitable for your circumstances.