Skip to main content
Help Center

Minutes & status reports with teamspace elements

Create project minutes and status reports from templates and embed real teamspace elements such as open items and work packages instead of typing them out.

Prerequisites

Minutes or a status report are only as good as their content – and in teamspace that content usually already exists: as open items, work packages, appointments or receipts. Instead of typing them out (and letting them go out of date), you embed the real elements. The report then stays linked to day-to-day operations and remains current.

ℹ Note (review). That teamspace elements can be embedded in minutes/status reports is part of the product concept (status report template, linked elements). The exact UI route for embedding (element selection, command or link) differs by document type – wiki page or file – and has not yet been fully checked against the live interface in this version (last_verified: null).

Variant A: Status report as a wiki page

Wiki pages are well suited to living, linked reports because they can reference elements.

  1. In the Knowledge → Wiki pages tab, create a new page via the blue + button (or use a status report template, see Set up templates, headers and footers).
  2. Write the report text in wiki syntax (period, progress, risks).
  3. Embed the relevant teamspace elements – e.g. an open-items list or individual work packages. The current status then appears directly in the report.

→ Basics: Create and edit wiki pages

Variant B: Minutes/status report as a document from a template

For formal reports that need approval, use the file template.

  1. In file management, choose Actions → New document → the status report template (see QM document templates at a glance).
  2. Fill in the report; teamspace partly fills placeholders (project, period) automatically from the context.
  3. Set references to open items and work packages as links, so you can jump from the report straight to the elements.
  4. Have it approved if needed (see Review and approve a document).

On the Input data tab you embed the real elements, in the Preview you see the finished, rendered document, and in the project you find the report again under Communication → QM documents.

Status report 'New homepage project', 'Input data' tab: fields for Current status, Completed tasks (team leader event) and Future tasks with embedded elements 'Negotiation of tenancy agreements' and 'Concept new corporate design' as link chips
1 On the "Input data" tab you embed real open items and work packages as links, instead of typing them out.
'Preview' tab of the status report: the finished, rendered teamspace document with the heading 'STATUS REPORT', project data, a traffic-light graphic and the sections Project status, Completed/Future tasks and The next steps
2 The "Preview" shows the finished, rendered report including the traffic light and the embedded content.
Project 'Launch of Big Brand', 'Communication' tab → 'QM documents' sub-tab: list with the status report (status Draft, Volker Vorstand, 24/06/2026)
3 In the project the report sits under "Communication" → "QM documents" and stays linked to day-to-day operations.

Which elements work well

Why embed instead of type out

  • Up to date: if an open item changes, the change is visible through the link – the report shows the real status.
  • Fewer errors: no typing mistakes, no outdated copies.
  • Traceability: from the minutes you jump straight to the element and carry on working there.

Common questions & needs

You want to …How to
Show open to-dos in the minutesEmbed an open-items list in the wiki page (Variant A).
Report on project progressEmbed work packages in the status report.
Approve a report laterCreate it as a file from the status report template and have it reviewed (Variant B).
Keep decisions traceableCreate decisions as open items and reference them in the minutes.
Keep the report currentLink elements instead of typing the content out.