Skip to content
Kairos OneBook a demo
Menu
Foundation · 3 min read

Create and govern a P6 project

Set up the EPS location, project identity, dates, calendar, defaults, security, and coding before detailed planning begins.

Working definition

A new P6 project inherits enterprise data and defaults that can silently govern every later activity. Professional setup therefore begins with governance: choose the correct EPS branch, establish a durable project ID, define the planned start and contractual boundaries, select an intentional default calendar, confirm responsible management and privileges, and document which global data the project may use.

Version scope

Desktop P6 Professional workflow. Menu labels are aligned with Oracle’s current Version 26 help; older 24.x deployments may show minor wording or privilege differences.

Key takeaways

  • Create the project in the correct EPS branch with a governed, stable ID.
  • Set dates and default calendars from the approved planning basis, not software convenience.
  • Document inherited enterprise data, security, defaults, and coding before importing or building detail.
01

Identity before detail

Project ID, EPS position, responsible manager, project status, and security are enterprise controls. Agree them before activities are created or data is exchanged. Stable identity makes portfolio reporting, XER lineage, schedule comparison, and audit history defensible.

02

Dates are not interchangeable

Planned Start provides the earliest planning boundary. Must Finish By can affect float and should be used only when the organization’s method requires it and the contractual basis is documented. The data date belongs to the status cycle and should not be advanced merely to make a new project appear current.

Create a controlled project shell

The exact wizard fields vary by deployment, but the control sequence should remain the same.

Menu path: File > New, or Enterprise > Projects > Add

Before you start

  • Approved project naming convention
  • Correct EPS destination
  • Responsible manager and security model
  • Contract date register

  1. Select the EPS node

    Create the project beneath the approved EPS branch.

    Verify: Portfolio grouping, security inheritance, and responsible manager align with the project charter.

  2. Assign identity

    Enter the governed Project ID and concise project name.

    Verify: The ID is unique and conforms to integration and exchange rules.

  3. Set planning dates

    Enter the approved Planned Start and only the authorized contractual or management completion controls.

    Verify: Dates reconcile to the contract date register and schedule basis.

  4. Choose defaults

    Assign the intended default activity calendar, activity ID pattern, percent-complete approach, and other project defaults.

    Verify: A test activity inherits the intended calendar and coding behavior.

  5. Confirm privileges and ownership

    Assign the responsible manager and verify who can edit projects, baselines, costs, global data, and layouts.

    Verify: A role-based access check matches the operating plan.

  6. Record the setup

    Export or capture project details and update the schedule basis memorandum.

    Verify: Another scheduler can reproduce the project shell without relying on memory.

    Field-ready control

    Project setup gate

    • Correct EPS node and environment
    • Unique governed Project ID
    • Contract dates reconciled
    • Default calendar verified
    • Responsible manager and privileges verified
    • Project defaults documented
    • Initial native backup retained

    Common questions

    Should Must Finish By always equal the contract completion date?

    Not automatically. It changes the backward pass and float. Apply the organization’s documented method and disclose the contractual or management basis.

    Sources and scope

    Follow the reference trail.

    This guide is original educational commentary. Kairos reference records identify the source organizations, editions and scope behind this guidance. The original publishers retain their publications and rights.

    Primavera P6 Professional User Guide, Version 26Oracle · checked 2026-08-01Schedule Assessment Guide: Best Practices for Project SchedulesU.S. Government Accountability Office · checked 2026-08-01