Internal Notes
Internal notes provide the team with implementation instructions and make it easier to move from planning to execution.
Internal notes are part of every work package in a project component. Their purpose is to give employees clear guidance and instructions for implementation. While the description and customer requirements are included in the specification, internal notes are intended exclusively for the internal team.
Project components structure recurring projects and make it easier to transition from planning to execution. Each work package usually consists of three areas:
- Description: What needs to be completed in the work package
- Customer requirements: Which individual requests need to be taken into account
- Internal notes: How the task should be implemented in practice
Once the specification has been approved, the work packages are converted into tickets. The internal notes are then visible there, giving employees implementation context and specific instructions.
Where are internal notes available?
Internal notes are available for the following objects:
- Components
- Epics
- Work packages
- To-do lists
- Acceptance checklists
The building blocks of project components
Usage
This example shows how descriptions and internal notes address different audiences—the customer on the one hand and the internal team on the other.
Description (left column) – written for the customer
The description explains to the customer what will be delivered in this work package and what value it provides.
It is part of the specification and forms the basis for a later quote or service description.
In the example:
“In this step, we work together to determine what content your website should contain, how it should be structured and which texts should appeal to your visitors.”
arrow_right Goal: The customer understands the purpose and the outcome of the work package. The tone is explanatory, service-oriented, and focused on customer value.
Internal note (right column) – written for your team
The internal note is intended exclusively for the internal project team. It contains specific work instructions, checkpoints, or guidance on how the work package should be implemented.
In the example:
“The aim is to receive all relevant content from the customer as independently as possible via the content questionnaire […] If there are any ambiguities or gaps: ask questions or suggest the ‘Editorial support’ work package.”
arrow_right Goal: The team knows how to proceed, what to pay attention to, and when follow-up questions are required.
The tone is pragmatic, precise, and intended for internal use.
In summary:
- Description: For the customer → explains what will be done and why.
- Internal note: For the team → explains how it should be done.