Branding & customisation

A company logo can be stored centrally and used by all team members.

The logo is shown automatically in documents and in the viewer.

• Set the logo once for the whole team
• Use in the PDF protocol
• Shown in the protocol viewer
• A consistent look for all protocols

👉 Example: After upload, your company logo appears on every PDF protocol and in the web viewer for all users.

🎯 Consistent branding: set once, visible everywhere in the app and protocols.

Equipment can be defined freely with group, product name and an optional link, e.g. to a manual or documentation.

You can then add the equipment to an object and use it in protocols.

• Freely definable equipment
• Grouping supported
• Product name for identification
• Link to documentation
• Can be assigned to an object

👉 Example: A kitchen unit with a link to its manual is assigned to the object and appears clearly structured in the protocol.

🎯 Define equipment centrally – clear and recognisable in every protocol.

Document links can be assigned to objects permanently.

Saved links are available automatically when you create protocols and can be stored long-term for object types.

• Save links to documents or portals
• Assign to an object or object type
• Automatic display in the protocol
• Consistent use across the team

👉 Example: A link to the house rules is stored on the “Apartment” object type – it appears automatically in every handover protocol.

🎯 Important documents always at hand – no manual follow-up.

Areas let you structure an object into rooms or sections.

Areas are maintained as master data and used automatically when you create protocols.

For each area you can store a name, group and a description.

The description can be written in Markdown and supports headings, lists and notes.

Areas can be filtered by object type so only relevant areas are shown.

• Freely definable area name
• Areas can be grouped
• Description in Markdown
• Headings and bullet lists supported
• Filter by object type
• Used when creating protocols
• Consistent structure for the whole team

👉 Example: “Bathroom” and “Kitchen” are separate areas – the plumbing checklist only appears in Bathroom.

🎯 Structure objects logically – capture and protocols stay clear.

Checklists can be built as your own sets and tailored to your company, objects and workflows.

Each checklist consists of freely definable checkpoints and rating types and is shown automatically when creating a protocol whenever the defined conditions are met.

• Create your own checklist sets
• Several checklists in parallel
• Use by protocol occasion or object
• Freely definable rating types
• Define checkpoints with preset wording
• AI-assisted creation of new entries
• Filters by occasion, object type, address, object and area
• Automatic use in the protocol

👉 Example: A take-back checklist only appears for take-back protocols – not for first handover.

🎯 The right checklist at the right time – no manual searching.

Protocol types define the occasion and flow of a protocol.

Alongside handover and take-back, you can define your own protocol terms to match your company, objects or workflows.

• Name and configure your own protocol types
• Add explanatory texts in Markdown
• Combine checklists, text blocks, areas, equipment and document links per type
• Filter and assign by object type, address, object, area and further criteria
• Consistent terminology and workflows across the team

👉 Example: The “Maintenance” protocol type automatically shows your maintenance checklists and matching text blocks.

🎯 Every occasion with a clear structure – wording and content fit your use case.

Text blocks provide consistent documentation language while still allowing company-specific customisation.

Recurring phrases can be prepared and inserted automatically or manually depending on the use case.

• Maintain company-specific wording centrally
• Markdown-based editing with headings and lists
• Automatic insertion via filters
• Manual add-on at any time
• AI-assisted creation of new blocks

👉 Example: The “Handover notes” block is inserted via filter only for handover protocols.

🎯 Consistent wording – faster protocols, fewer typos.

Image quality can be tuned to match your company requirements.

This lets you control file size, upload speed and visual detail per workflow.

• Configurable photo quality for protocol images
• Optimised for mobile networks and slower connections
• Balanced ratio of sharpness and storage usage
• Consistent quality settings for the whole team
• Faster upload and archiving performance

👉 Example: On a slow site network, photos upload at reduced quality – policy stays the same for everyone.

🎯 Clear photos, less data – smoother teamwork, evidence stays usable.