Creating your own PowerPoint export templates allows you to specify which information is exported for projects. Below is an overview of all available fields and their placeholders.
General
When building your PowerPoint export templates, you can include system and project fields by inserting the corresponding placeholders into your file. During export, Meisterplan replaces each placeholder with the actual field content.
See the article Customizing Your Microsoft PowerPoint Templates for Project Data Exports for more details on creating and uploading your custom PowerPoint templates.
Non-Project-Specific Placeholders
| <report_title> | Will be replaced with "Project Brief" or the localized title |
| <report_sub_title> | Will be replaced with "Key details at a glance" or the localized subtitle |
| <timestamp_of_export> | Contains the timestamp of the export: time, day, month, and year |
Custom Project Fields
You can include any project field configured under Manage > Fields > Project Fields in your templates. You can find the corresponding placeholder when you open the field's configuration. The placeholder format is “cust_” followed by the API name that is generated when creating a field. This is often the same as the field's name (e.g., “<cust_newfield>”).
If you add “_label” at the end of a placeholder, the field name will be displayed in the export instead of the field content. This is particularly helpful if you have changed the field name in Meisterplan (e.g., from “Stage Gate” to ‘Stage’) but the API name remains the same. Using “_label” ensures that the current field name appears in the export.
| Field | Placeholder | In Default Template |
| External Link | <cust_project_link> | - |
| Strategy Fit | <cust_strategy_fit> | - |
| Stage Gate | <cust_stage_gate> | x |
| Risk Level | <cust_risk> | - |
| Payback Period | <cust_fb_payback> | - |
| Description | <cust_description> | x |
| Need for Decision | <cust_need_for_decision> | - |
OBS Fields
You can also include any OBS field configured under Manage > OBS in your templates. The placeholder format is "obs_" followed by the name of the OSP, such as "obs_branch."
| Field | Placeholder | In Default Template |
| Department | <obs_department> | - |
| Office | <obs_office> | - |
| Value Stream | <obs_value_stream> | - |
Milestone Fields
You can also export milestone fields if you include the placeholders in a table in your template.
To export only past or future milestones, add ":past" or ":future" to the <milestone_name> placeholder: <milestone_name:future>. You cannot add these filters to other milestone placeholders. To export all milestones, you can either add ":all", or use the placeholder <milestone_name> without an additional filter.
We recommend putting each milestone table on a separate slide to ensure a consistent layout.
| Field | Placeholder | In Default Template |
| Name | <milestone_name> | x |
| Phase | <milestone_project_phase> | x |
| Date | <milestone_date> | x |
| Status | <milestone_status> | x |
Risk Fields
You can export both system and custom risk fields (under Manage > Fields > Risk Fields) if you include the placeholders in a table in your template. The placeholder for custom risk fields is the API name found in the field's configuration with the added prefix "risk_" (e.g., “<risk_cust_riskfieldname>”).
To export only selected risks, you can filter the risks by their single-select options. For example, to export only risks with the impact "High", add ":high" to the placeholder: <risk_impact:high>.
If a single-select option consists of more than one word, use underscores to replace the spaces: for example, to export only risks with the likelihood "Almost Certain", add ":almost_certain" to the placeholder: <risk_likelihood:almost_certain>.
This works for both system and custom fields of the single-select type. The Risk Level field, however, is a Number field and cannot be used for filtering.
You can use only one filter per risk table in your template, but you can configure as many risk tables as you like. We recommend putting each table on a separate slide to ensure a consistent layout.
| Field | Placeholder | In Default Template |
| Name | <risk_name> | - |
| Key | <risk_key> | - |
| Risk Owner | <risk_owner> | - |
| Impact | <risk_impact> | - |
| Likelihood | <risk_likelihood> | - |
| Risk Level | <risk_level> | - |
| Custom Risk Fields | <risk_cust_riskfieldname> | - |
System Fields
The following system fields are available for your PowerPoint templates. Insert the appropriate placeholder into your file to include the field.
| Field | Placeholder | In Default Template |
| Name | <project_name> | x |
| Project Key | <project_key> | - |
| Notes | <project_notes> | x |
| Cost Type | <project_costtype> | - |
| Project Manager | <project_manager> | x |
| Goal | <project_goal> | x |
| Priority Score | <project_score> | - |
| Approved Total Effort | <project_approved_total_effort> | x |
| Actual Time Worked | <project_actual_time_worked> | - |
| Actual Allocation Costs | <project_actual_allocation_cost> | - |
| Actual Financial Events Costs | <project_actual_financial_events_costs> | - |
| Last Booking Date | <project_last_booking_date> | - |
| Approved Budget | <project_approved_budget> | x |
| Actual Benefit Total | <project_actual_benefit_total> | - |
| Approved CapEx Budget | <project_approved_capex_budget> | - |
| Approved OpEx Budget | <project_approved_opex_budget> | - |
| Status | <project_status> | x |
| Project Type | <project_type> | x |
| Connected Tool | <project_connected_tool> | - |
| Start | <project_start> | x |
| Finish | <project_finish> | x |
| Program Name | <project_program_name> | x |
| Rank Category | <project_rank_category> | x |
| Last Changed | <project_last_changed> | - |
| Planned Allocations | <project_planned_allocations> | x |
| Planned Benefit | <project_planned_benefit> | - |
| Total Planned Costs | <project_planned_costs> | x |
| Future Costs | <project_planned_future_costs> | - |
| Planned Net Value | <project_planned_net_value> | - |
| Planned CapEx | <project_planned_capex> | - |
| Planned OpEx | <project_planned_opex> | - |
| Planned Allocation Costs | <project_planned_allocation_costs> | - |
| Future Allocation Costs | <project_planned_future_allocation_costs> | - |
| Planned Financial Events Costs | <project_planned_financial_events_costs> | - |
| Future Financial Events Costs | <project_planned_future_financial_events_costs> | - |
| Planned Allocation Costs until Last Booking Date | <project_planned_allocation_costs_until_last_booking_date> | - |
| Planned Allocations until Last Booking Date | <project_planned_allocations_until_last_booking_date> | - |
| Future Allocations | <project_planned_future_allocations> | - |
| Allocation Estimate at Completion | <project_allocation_estimate_at_completion> | x |
| Deviation of Allocation EAC from Approved Total Effort (in time unit) | <project_deviation_of_eac_from_approved_total_effort> | - |
| Deviation of Allocation EAC from Approved Total Effort (in %) | <project_deviation_of_eac_from_approved_total_effort_percentage> | x |
| Deviation of Actual Time Worked from Plan (in time unit) | <project_deviation_of_actual_time_worked_from_plan> | - |
| Deviation of Actual Time Worked from Plan (in %) | <project_deviation_of_actual_time_worked_from_plan_percentage> | - |
| Deviation of Actual Allocation Costs from Plan (in currency) | <project_deviation_of_actual_costs_from_plan> | - |
| Deviation of Actual Allocation Costs from Plan (in %) | <project_deviation_of_actual_costs_from_plan_percentage> | - |
| Cost Estimate at Completion | <project_cost_estimate_at_completion> | x |
| Deviation of Cost EAC from Approved Budget (in currency) | <project_deviation_of_cost_eac_from_approved_budget> | - |
| Deviation of Cost EAC from Approved Budget (in %) | <project_deviation_of_cost_eac_from_approved_budget_percentage> | x |
| Estimated Benefit at Completion | <project_estimated_benefit_at_completion> | - |
| Estimated Net Value at Completion | <project_estimated_net_value_at_completion> | - |
| Percentage of Completion | <project_percentage_of_completion_allocation_based> | x |
| Deviation Status Compared to Connected Tool | <project_connected_tool_deviation_status> | - |
| Missing Allocations Compared to Connected Tool | <project_missing_allocations_compared_to_connected_tool> | - |