Templates

Templates in smenso provide a way to standardize structures and content across projects, tasks and reports. They help teams avoid repetitive setup work and enforce consistent patterns.

Template Types

smenso supports three main template types:

• Project templates
• Task templates
• Status report templates

Project Templates

Project templates define a reusable baseline for projects, for example:

• master data fields (dates, status, classifications)
• default flavors and metadata
• optional structural elements (e.g. initial tasks, phases, folders)
• possibly standard configurations such as permissions or access

They are used to:

• create new projects with a consistent structure
• optionally update existing projects by applying template master data

Task Templates

Task templates define a reusable baseline for tasks and are commonly used to standardize recurring work items. Depending on configuration, they may include:

• predefined task fields (e.g. title patterns, status, priority)
• default flavor values
• description content
• predefined subtasks or structured task elements (where applicable)
• permissions and access

Task templates help ensure that tasks created across projects follow consistent structure and required metadata.

Status Report Templates

Status report templates define:

• the sections and structure of a report
• default values for supported fields
• default RichText content (e.g. placeholders, headings, standard texts)
• optional default flavors or metadata

They are used to generate new reports that follow a consistent layout - e.g. weekly status, monthly steering committee reports, or customer status updates.

Templates in APIs

Templates can be used via APIs to:

• Create projects from templates
• ensuring standardized setup across systems
• Update project master data using templates
• bring existing projects in line with updated standards
• Create status reports from templates
• populate new reports with predefined structures and content

APIs usually expect a Template ID/GUID and may provide controls for what should be inherited (e.g. overwrite behavior for certain fields).

Summary

Templates standardize recurring structures across tasks, projects, and status reports, ensuring consistent setup across teams while reducing manual configuration effort. They support governance and automation by transferring predefined values (including RichText where applicable) and offering overwrite controls, making template-based workflows especially useful for API-driven integrations and external system triggers.