# The document pain scale.

> Real-time co-editing, inline comments, one source of truth instead of _final_final. Rollout with an Atlassian Platinum Partner who built Confluence for BSH and EEX.

Source: https://www.xalt.de/en/confluence-collaboration-platform/

Every team knows it. Five ways a comment can go – from “added right in context” to “here is \_final\_final\_v3, please review again”. Confluence has a built-in way back to the good end.

[Book a demo](https://www.xalt.de/en/book-a-meeting/)

## Walk the scale in your head – where does your team sit?

### All good

Comments sit right in context, next to the text. Nobody has to guess what is meant.

### Still okay…?

Notes sit inline in the running text, plus a draft with its own file name – \_draft\_paul.

### Oh.

Someone comments on an older version, not knowing a newer one already exists.

### Not again

The new \_final\_final version needs a full review again – from the top.

### Maximum pain

Everything was changed, but nobody turned on track changes first.

## One document stays one version, and everyone works on it at once.

Every point on the scale has a built-in answer in Confluence – no add-on, no workaround. And with Rovo, an AI summarises pages and drafts the first version right inside Confluence.

### Real-time co-editing

Up to 12 people write in the same document at once, cursors visible. File copies belong to the past.

### Inline comments in context

Highlight text, comment, resolve the thread – feedback stays exactly where it belongs.

### One source of truth

Exactly one current page, with version history, diff view and one-click restore.

### Every change automatically tracked

Tracking cannot be forgotten because it always runs – visible per version, notified via watch.

## This is how the tool becomes a way of working.

A fixed process instead of a self-service trial – from the first space to retiring the old wiki.

1

Step 01

### Define structure

Spaces, page templates and naming conventions, matched to your teams.

2

Step 02

### Migrate content

Word shares, SharePoint and old wikis moved over cleanly, without losing knowledge.

3

Step 03

### Train the team

Training for users and admins until the new way of working feels obvious.

4

Step 04

### Grow the intranet

From a team wiki to a social intranet and digital workplace, step by step.

## The tool is half the job. The way of working is the other half.

Whether your team actually ends up on the good end of the scale is rollout work: structure, templates, governance and training – from an Atlassian Platinum Partner who has built intranets and knowledge bases for companies like BSH and EEX.

- Structure & templates: spaces, page templates and naming conventions that keep order
- Migration: Word shares, SharePoint and wikis moved over cleanly, without losing knowledge
- Training & adoption: sessions for users and admins until the new way of working sticks
- Intranet growth: from a team wiki to a social intranet and digital workplace

## Where does your team sit on the scale?

A 30-minute demo with real use cases – afterwards you will know how far you can get.

[Book a demo](https://www.xalt.de/en/book-a-meeting/)

---

*This version is for AI agents. Every page of this site is available as Markdown: append `index.md` to its path. Index of all pages: [llms.txt](https://www.xalt.de/llms.txt)*