---
title: "Living Documents on Shared Context — Plans, Wikis, Decision Logs | In Parallel"
description: "In Parallel Pages are documents built on your live organisational context: plans that maintain themselves, wikis that stay true, decision logs with the source one click away."
url: https://www.in-parallel.com/pages
---

Pages

# Documents that stay true.

Plans, wikis, runbooks, decision logs — written as pages on top of your shared context, so the facts underneath keep them current. The wiki stops being where information goes to age.

In short

In Parallel Pages are documents written on top of your shared context: plans, wikis, runbooks and decision logs whose decisions, owners, dates and risks come from what was said in meetings. After each meeting the page agent adds what changed to the pages it touched, and every edit lands in version history with its source.

[Book a demo →](https://www.in-parallel.com/demo)

What it does

## Narrative on top. Live record underneath.

### Prose backed by the record

A page reads like a document, but its claims — the decisions, owners, dates, and risks — are drawn from the same shared context your meetings feed. When reality changes, the page has a source of truth to change with.

### A plan is a page that keeps up

Owners, decisions, and status stay tied to what was actually said in meetings. After each meeting the pages it touched are updated, and every edit lands in version history.

### Organised as a tree, connected as a graph

Pages nest the way your work nests — workspace, project, topic — and link to each other and to the meetings and decisions they cite. Backlinks mean nothing important goes orphaned.

How it works

## Start it, link it, let it hold.

#### 01 · Start

### Start from work, not from blank

Draft a page yourself, or have one assembled from context — a project overview, a decision log, a plan — already populated from the record.

#### 02 · Link

### Link claims to their sources

Facts in the page point at the decisions and meetings behind them. Readers can trust a line or check it in one click.

#### 03 · Hold

### Let it keep up

After each meeting, the pages it touched are updated, and a nightly pass rereads every active page. Each page shows what grounds it, and every edit lands in version history.

What it replaces

## The document graveyard, retired.

3.8 hrs

#### searching for information, per manager, per week

Measured in the 2026 Coordination Tax Index. Most of it spent finding out which document is the current one.

One

#### source of truth under every page

The same shared context feeds Notes, Chat, Briefings, and Pages — so documents can’t fork from reality without it showing.

Sourced

#### claims you can check

A date, an owner, a decision in a page links back to where it was established.

Before you ask

## The questions every team asks first

**How is this different from Notion or Confluence?**

A conventional wiki is frozen the moment it’s written — nobody maintains it, so everyone quietly stops trusting it. Pages sit on top of your live shared context: they are updated after each meeting and show the record that grounds them.

**What happened to Plans?**

Plans became pages. A project plan is now a workspace page like any other, updated after each meeting and grounded in the decisions, owners, and risks behind it.

**Who can edit, and what can AI touch?**

People edit pages like any document, within workspace permissions. Your AI can draft and propose updates from context — changes land for review, with sources attached.

**Is it included in the price?**

Yes — Pages is part of every plan, from €29 per user per month.

## Write it once. Let the context keep it honest.

When documents share a live source of truth with your meetings, "is this still current?" stops being a question anyone has to ask.

[Book a demo →](https://www.in-parallel.com/demo)

[Get started →](https://www.in-parallel.ai/)

- Backed by live shared context
- Updated after every meeting
- Sources one click away