Project Templates

The Templates module provides reusable PM methodology templates that bundle WBS skeletons, stage-gate definitions, document checklists, and calendar defaults for rapid project setup. It supports both system-level templates (shared across all organizations) and organization-level custom templates with full CRUD, preview, and clone capabilities.

Overview

Setting up a new PPM project from scratch -- defining the WBS hierarchy, configuring gates, listing required documents, and establishing review cadences -- is time-consuming and error-prone. Different project methodologies require different structures, and maintaining consistency across an organization's project portfolio demands standardization.

ProBeya's template system solves this by providing pre-built methodology templates that can be applied to any project with a single action. Templates create WBS elements, gate definitions, and associated artifacts in seconds, ensuring every project starts with a consistent, methodology-aligned structure. Organizations can also create their own custom templates by cloning and modifying system templates or building from scratch.

Getting Started

1. Navigate to Portfolio > Templates in the sidebar.
2. Browse available templates filtered by methodology (PMBOK 7, PM2, P3Express, Custom).
3. Click a template to Preview its WBS tree, gate sequence, and document checklist.
4. Open a PPM project and navigate to the Setup tab.
5. Select Apply Template and choose the desired template.
6. The project is populated with WBS elements and stage-gate definitions from the template.

Key Concepts

Template Types

Two categories of templates exist:

• System templates: Built-in templates shipped with ProBeya, available to all organizations. They are read-only -- organizations cannot modify or delete system templates directly. To customize, clone the system template first.
• Organization templates: Custom templates created by the organization's PMO team. These can be fully edited, deleted, and versioned according to organizational needs.

Supported Methodologies

Templates are categorized by PM methodology:

• PMBOK 7: Project Management Body of Knowledge, 7th edition. Includes principle-based domains (stakeholder, team, development approach, planning, project work, delivery, measurement, uncertainty) with corresponding WBS phases and governance gates.
• PM2: The European Commission's open-source PM methodology. Structures projects into initiating, planning, executing, and closing phases with specific PM2 deliverables and review gates.
• P3Express: A lightweight, one-page project management framework. Provides a streamlined WBS with minimal overhead, suitable for smaller transformation projects.
• Custom: Organization-defined templates that follow a bespoke methodology. These can combine elements from multiple methodologies or implement proprietary process frameworks.

Template Components

Each template bundles four component types:

WBS Template

A hierarchical tree of work package definitions. Each element has a name and optional children, forming a multi-level breakdown structure. When applied, the template creates actual WBS elements with auto-generated WBS codes based on the tree position.

Example structure:

1. Initiating
   1.1 Business Case
   1.2 Project Charter
2. Planning
   2.1 Scope Statement
   2.2 Schedule Baseline
   2.3 Cost Baseline
3. Executing
   ...

Gate Template

A sequence of governance gates with:

• Name and code (e.g., "G1 - Charter Approval")
• Criteria: the conditions that must be met to pass the gate
• Required documents: document types that must be submitted
• GxP required flag for regulated gates
• Sequential ordering: each gate references its predecessor

When applied, the template creates stage-gate definitions with predecessor links enforcing the review sequence.

Document Checklist

A list of documents required at various project stages. Each entry includes:

• Document name (e.g., "Risk Register", "Stakeholder Analysis")
• Description: what the document should contain
• Mandatory flag: whether submission is required for gate passage

Calendar Template

Default review cadences and meeting schedules for the methodology. This includes steering committee frequency, status report cadence, and other recurring governance events.

How It Works

Listing Templates

The list procedure returns all system templates plus any templates belonging to the caller's organization. An optional methodology filter narrows the results. System templates appear first, followed by organization templates.

Previewing Templates

Before applying a template, the preview procedure returns a simulation of what would be created: the WBS tree structure, element count, gate sequence, gate count, document checklist, and calendar template. No data is persisted during preview, making it safe for exploration.

Applying Templates

The applyTemplate procedure creates actual database records from a template:

1. Verify project access: the project must exist and belong to the caller's organization
2. Fetch template: either a system template or an organization template
3. Create WBS elements: recursively inserts WBS elements with auto-generated codes and parent-child relationships. Each element receives a unique ID and is linked to its parent.
4. Create stage gates: inserts gate definitions with predecessor links to enforce sequential ordering. Required documents are converted to structured objects with name, description, and mandatory flag.

The procedure returns the count of WBS elements and gates created.

Creating Custom Templates

The create procedure adds a new organization-level template. All required components (WBS template, gate template, document checklist, calendar template) are provided in the input. The template is flagged as non-system and linked to the organization.

Modifying Templates

The update procedure allows editing organization-level templates. System templates cannot be modified -- the system returns a FORBIDDEN error with the message "Cannot modify system-level templates. Clone it first."

Updatable fields include: name, methodology, description, WBS template, gate template, document checklist, and calendar template. Only provided fields are updated.

Cloning Templates

The clone procedure creates a deep copy of any template (system or organization) as a new organization-level template under a specified name. The cloned template is always non-system, allowing full editing. This is the primary path for customizing system templates.

Customizing on Apply

The customize procedure provides a preview-with-overrides capability. It accepts a template ID along with caller-specified modifications (renamed elements, excluded gates, additional documents) and returns the customized preview without persisting. This enables organizations to see the effect of their modifications before committing.

Configuration

Setting	Location	Description
Methodology filter	Template list	Filter templates by PMBOK 7, PM2, P3Express, or Custom
Template name	Template create/edit form	Human-readable template identifier
WBS template	Template editor	Hierarchical tree structure for work packages
Gate template	Template editor	Sequential gate definitions with criteria
Document checklist	Template editor	Required documents per project stage
Calendar template	Template editor	Default review cadences and meeting schedules

Permissions

• View templates: all organization members with PPM access can browse and preview templates
• Apply templates: requires project manager or PPM admin role on the target project
• Create custom templates: requires PPM admin or PMO lead role
• Edit custom templates: requires PPM admin or template creator
• Delete custom templates: requires PPM admin role (system templates cannot be deleted)
• Clone templates: requires PPM admin or PMO lead role

Tips & Best Practices

• Preview before applying: Always preview a template before applying it to a project. Applied WBS elements and gates must be individually edited or deleted if they are not needed.
• Clone system templates for customization: Never attempt to modify system templates directly. Clone first, then customize the copy.
• Standardize on one or two methodologies: While ProBeya supports multiple methodologies, organizations benefit from consistency. Pick one primary methodology and create a polished custom template.
• Include GxP flags for regulated projects: If your organization operates in a regulated environment (pharma, medical devices), ensure gate templates have the GxP required flag set for applicable gates.
• Version your custom templates: When making significant changes, clone the existing template with a version suffix (e.g., "Acme PMBOK v2") rather than overwriting. This preserves the original for reference.
• Align document checklists with governance: The document checklist should mirror the documents required at each governance gate. Cross-reference with your governance framework.
• Keep WBS templates to 3-4 levels: Deep WBS hierarchies are difficult to manage. Templates should define the standard structure; teams can add project-specific detail after application.

Troubleshooting

Issue	Cause	Resolution
"Cannot modify system-level templates" error	Attempting to edit a system template	Clone the system template first, then edit the clone.
"Cannot delete system-level templates" error	Attempting to delete a system template	System templates are permanent. Hide them by filtering to organization templates.
Applied template created zero WBS elements	Template has an empty WBS tree	Verify the template's WBS template is populated before applying.
Gate predecessor links are incorrect after apply	Template gate order was modified	Review the gate template's sequential ordering before applying.
Template not visible to user	Template belongs to another organization and is not a system template	Organization templates are only visible within the creating organization.
Customize preview differs from expected	Override syntax incorrect	Verify the override input matches the expected schema for element renaming and exclusion.

Related Features

• WBS -- Applied WBS templates create elements in the project's work breakdown structure
• Stage-Gate Reviews -- Applied gate templates create gate definitions for governance
• Projects -- Templates are applied to PPM projects during initial setup
• Governance Framework -- Governance processes should align with template gate sequences
• Schedules -- Template-generated WBS elements form the basis for project scheduling