Design system / Print / Report

Report

A4 portrait. Eleven sheets in a full report: cover, index (TOC), summary, body, quote, diagram, table, info box (standard + playful), sources, attachments, back. Every body page shares a markdown-style running header and hex pagination. Filled "Acme BV" example below the empty template; mix-and-match the page types your report actually needs.

Filled example · data category · "Open registers Acme BV"

Conduction · Quick scan · #CND-2026-042

Open registers for Acme BV.

How we turn 142 spreadsheets into one auditable register.

Date30 April 2026 ForMarleen de Vries, IT lead ByRuben van der Linde

Cover · cat-data · forest hex

# Open registers Acme BV CND-2026-042 · p. 02

Management summary

Holiday-proof access to your customer register, in seven weeks.

Acme currently has 142 Excel files whose logic is in three people's heads. Two have retired. With OpenRegister, four roles each get their own view, schema validation, and an audit trail out of the box. Hardware stays on your own Nextcloud.

Problem: knowledge sits with people, not roles. Work stops on holidays.
Approach: OpenRegister + 5 entities + 4 roles, seven weeks to live, fixed price.
What you get back: one truth, audit-ready, holiday-proof, no vendor lock-in.

RvdL

Ruben van der Linde CTO · Conduction

Drafted30 April 2026

conduction.nl · #CND-2026-042

Summary page · gray hex veil · signed by consultant

# Open registers Acme BV CND-2026-042 · p. 03

What we found

142 spreadsheets, in 9 folders, managed by 4 people. No version control. Three people know which field is optional; two have retired.

The urgency isn't an audit, it's holidays. If Henk is out, nobody knows which column has the right BSN format.

"We just made an Excel of it because the system we had wasn't keeping up." — Henk, customer-register manager

Where OpenRegister fits

One register, five entities (customer, contract, invoice, contact person, location). Schema validation, audit trail, roles per entity.

Schema is versionable: you can add a field without a migration.
Permissions per role, not per person, holiday-proof.
Imports your 142 spreadsheets without a week of consultancy.

What we don't do

We don't rebuild your CRM. OpenRegister is for data you can define and validate, not for 360-degree sales flows. For that kind of work we refer you on.

Timeline

Schema sprint (weeks 1–2). Import + audit (weeks 3–4). Roles + UI (weeks 5–6). Live (week 7).

conduction.nl · #CND-2026-042

Body · running header is markdown-style #

# Open registers Acme BV CND-2026-042 · p. 04

Voices from the field

Three quotes from interviews at Acme. Italic body, KNVB-orange left bar, attribution below in Plex Mono.

“We just made an Excel of it because the system we had wasn't keeping up.” Henk · customer-register manager

“Three people know which field is optional; two have retired. When I'm on holiday nobody can onboard a customer without calling Henk.” Marleen · IT lead

“An audit trail has been an issue here for a year. Nobody wants to fix it because that means phasing out 142 spreadsheets at the same time.” Anonymous · finance team

conduction.nl · CND-2026-042

Quote · italic + orange bar + Plex Mono attribution

# Open registers Acme BV CND-2026-042 · p. 02

Seven chapters, one back page. For each chapter, what it covers and where to find it.

01Management summaryp. 03

02What we foundp. 04

03Timeline and approachp. 05

04What you need to knowp. 06

05Architecture diagramp. 07

06Sourcesp. 08

07Attachmentsp. 09

conduction.nl · CND-2026-042

Index · flat TOC · Plex Mono num + page

# Open registers Acme BV CND-2026-042 · p. 07

Three ways to draw this register

Most consultant diagrams fall into one of three patterns. Each pattern below, with arrows that always run hex-edge to hex-edge (no floating lines).

01 · Linear · sequential

Time axis where something shrinks or consolidates. 142 spreadsheets → 5 schemas in a staging bridge → 1 register. Use when there's one direction and a clear endpoint.

FIG 01 · Linear

02 · Hub · one source, many consumers

One source in the middle, multiple consumers around it. The register is authoritative; CRM, invoices, contact, and locations are views, not copies. Use for architecture or integration overviews.

FIG 02 · Hub-and-spoke

03 · Branched · decision with outcomes

From one decision point, two outcomes. The valid? hex (KNVB orange, the must-read colour) splits to accept or queue. Use for what-do-you-do-when-X questions.

FIG 03 · Branched

conduction.nl · CND-2026-042

Diagram · three patterns · SVG arrows hex-edge to hex-edge

# Open registers Acme BV CND-2026-042 · p. 05

Timeline

Seven weeks in six blocks. Owner per row, fixed price through week 4.

#	Action	When	Owner
01	Schema working session, lock down five entities	wk 1	Ruben
02	Pilot import: three heaviest spreadsheets	wk 2	Mark
03	Go/no-go based on the pilot	wk 3	Marleen
04	Import the remaining 139 spreadsheets	wk 4–5	Mark
05	Set up roles and UI	wk 6	Ruben
06	Live + warm handover	wk 7	Marleen

Lead time 7 weeks · fixed price through wk 4

conduction.nl · CND-2026-042

Table · 4-col action plan, cobalt header + Plex Mono nums

# Open registers Acme BV CND-2026-042 · p. 06

What you need to know

Four kinds of margin. A note is background, a tip is a quick win, a warning is a risk, an important is something you shouldn't miss.

Note · Background

OpenRegister runs on Nextcloud, which you host yourselves. Same server, same backup, same permissions.

Tip · Quick win

Start with the customer register. That's where the most pain is, and it's the simplest import. One week for cleanup, one for the migration.

Warning · Risk

Henk is on holiday for two weeks in July. Plan the schema session before week 26 or the whole timeline slips by a week.

Important · For the decision

The fixed price holds through week 4. After that we go hourly, since the work depends on what you decide at go/no-go.

conduction.nl · CND-2026-042

Info box · note / tip / warning / important · one orange per page

# Open registers Acme BV CND-2026-042 · p. 06b

What you need to know, with more confidence

Same four margins, different execution. The hex carries the border; the card runs all the way to the paper edge.

Note · Background

OpenRegister runs on Nextcloud, which you host yourselves. Same server, same backup, same permissions.

Tip · Quick win

Start with the customer register. That's where the most pain is, and it's the simplest import. One week for cleanup, one for the migration. The Henk factor is smallest there.

Warning · Risk

Henk is on holiday for two weeks in July. Plan the schema session before week 26 or the whole timeline slips by a week.

Important · For the decision

The fixed price holds through week 4. After that we go hourly, since the work depends on what you decide at go/no-go.

conduction.nl · CND-2026-042

Info box playful · full-bleed · hex IS the border

# Open registers Acme BV CND-2026-042 · p. 08

Sources

Standards, documentation, and earlier migrations this approach builds on.

[01]

Forum Standaardisatie. "Comply or explain" list, NEN-ISO/IEC 26300.

forumstandaardisatie.nl/open-standaarden/iso-iec-26300

Accessed · 12 April 2026

[02]

Nextcloud GmbH. App API and authentication, technical documentation.

docs.nextcloud.com/server/latest/admin_manual

Accessed · 15 April 2026

[03]

Conduction BV. Case study: WOO register, Municipality of Rotterdam, January 2026.

conduction.nl/cases/rotterdam-woo

Own material

[04]

VNG Realisatie. Common Ground architecture, principle 3: data at the source.

commonground.nl/principes

Accessed · 20 April 2026

conduction.nl · CND-2026-042

Sources · numbered, academic-ish · Plex Mono link

# Open registers Acme BV CND-2026-042 · p. 09

Attachments

Files sent along, for anyone who wants to read further or review the schema.

[A1]

acme-bv_customer-register-schema_v01.json Proposed schema for the customer register, five entities, all field types.

json12 kB

[A2]

acme-bv_inventory_142-spreadsheets.xlsx List of the 142 existing spreadsheets with owner and last modified date.

xlsx86 kB

[A3]

acme-bv_quote_open-registers_v02.pdf Fixed price for weeks 1–4, hourly for weeks 5–7, with signed SLA.

pdf241 kB

[A4]

conduction_reference_woo-rotterdam.pdf Earlier implementation this approach leans on.

pdf1.8 MB

conduction.nl · CND-2026-042

Attachments · numbered, filename + type pill + size

What's next.

Three steps, one owner per step, one date. No "we can offer", concrete moves that can happen now.

01 · this week Schema working session Two hours with Henk and Marleen, we lock down your five entities. Output: a working OpenRegister schema. Owner Ruben · By 7 May

02 · week 2 Pilot import We import your three heaviest spreadsheets into a staging OpenRegister. Validation errors become visible. Owner Mark · By 14 May

03 · week 3 Go/no-go conversation 30 minutes, you and us. Based on the pilot we decide whether to continue with sprints 2–7 or stop. Owner Marleen · By 21 May

RvdL

Ruben van der Linde

CTO, Conduction

ruben@conduction.nl
+31 70 756 1240

Conduction BV · conduction.nl · this report is a working document, mark it up

Back · "wat is volgende" + contact + LinkedIn QR

Empty template · placeholders only · pick a category to set the cover hex

Conduction · {{ doc-type }} · {{ #ID }}

Date{{ DD month YYYY }} For{{ Recipient + role }} By{{ Author + role }}

Cover template · cat-process (lavender) shown

# {{ chapter }} {{ #ID }} · p. 02

Management summary

{{ One paragraph, two to three sentences. Person-voice; explains the situation, the move, and what changes. }}

Problem: {{ what's broken now, one line }}
Approach: {{ what we're doing about it, one line }}
What you get back: {{ the outcome, one line }}

{{ Author name }} {{ role }} · Conduction

Drafted{{ DD month YYYY }}

conduction.nl · {{ #ID }}

Summary template · gray hex veil · signed by consultant

# {{ chapter }} {{ #ID }} · p. {{ n }}

{{ Bullet 1 }}
{{ Bullet 2 }}
{{ Bullet 3 }}

What we don't do

conduction.nl · {{ #ID }}

Body template

# {{ chapter }} {{ #ID }} · p. {{ n }}

“{{ Short quote, one sentence, lifted verbatim. }}” {{ Speaker }} · {{ role }}

“{{ Longer quote spanning two or three lines, still verbatim. Keep the punctuation the speaker used, even if it is not how you would write it. }}” {{ Speaker }} · {{ role }}

“{{ Quote attributed to an anonymous source. }}” Anonymous · {{ context }}

conduction.nl · {{ #ID }}

Quote template

# {{ chapter }} {{ #ID }} · p. {{ n }}

01{{ Section title }}p. {{ n }}

02{{ Section title }}p. {{ n }}

03{{ Section title }}p. {{ n }}

04{{ Section title }}p. {{ n }}

05{{ Section title }}p. {{ n }}

06{{ Section title }}p. {{ n }}

07{{ Section title }}p. {{ n }}

conduction.nl · {{ #ID }}

Index template

# {{ chapter }} {{ #ID }} · p. {{ n }}

{{ One paragraph introducing the diagram patterns used in this report. }}

01 · Linear · {{ subtitle }}

{{ One paragraph describing the sequential progression A → B → C. }}

FIG {{ NN }} · Linear

02 · Hub · {{ subtitle }}

FIG {{ NN }} · Hub-and-spoke

03 · Branched · {{ subtitle }}

FIG {{ NN }} · Branched

conduction.nl · {{ #ID }}

Diagram template

# {{ chapter }} {{ #ID }} · p. {{ n }}

#	{{ Column 2 }}	{{ Column 3 }}	{{ Column 4 }}
01	{{ Row text }}	{{ when }}	{{ owner }}
02	{{ Row text }}	{{ when }}	{{ owner }}
03	{{ Row text }}	{{ when }}	{{ owner }}
04	{{ Row text }}	{{ when }}	{{ owner }}
05	{{ Row text }}	{{ when }}	{{ owner }}
06	{{ Row text }}	{{ when }}	{{ owner }}

conduction.nl · {{ #ID }}

Table template

# {{ chapter }} {{ #ID }} · p. {{ n }}

Note · {{ label }}

Tip · {{ label }}

Warning · {{ label }}

Important · {{ label }}

conduction.nl · {{ #ID }}

Info box template

# {{ chapter }} {{ #ID }} · p. {{ n }}

Note · {{ label }}

Tip · {{ label }}

Warning · {{ label }}

Important · {{ label }}

conduction.nl · {{ #ID }}

Info box playful template

# {{ chapter }} {{ #ID }} · p. {{ n }}

Sources

[01]

Accessed · {{ DD month YYYY }}

[02]

Accessed · {{ DD month YYYY }}

[03]

Accessed · {{ DD month YYYY }}

[04]

Accessed · {{ DD month YYYY }}

conduction.nl · {{ #ID }}

Sources template

# {{ chapter }} {{ #ID }} · p. {{ n }}

Attachments

[A1]

[A2]

[A3]

[A4]

conduction.nl · {{ #ID }}

Attachments template

01 · {{ when }}{{ Action }}{{ One-sentence detail. }}Owner {{ name }} · By {{ date }}

02 · {{ when }}{{ Action }}{{ One-sentence detail. }}Owner {{ name }} · By {{ date }}

03 · {{ when }}{{ Action }}{{ One-sentence detail. }}Owner {{ name }} · By {{ date }}

{{ role }}, Conduction

Back template

Why we built it this way

The cover tells you what kind of report this is

A consultant's report has to be readable in 30 seconds and useful for 30 weeks. Cover signals category. Body is markdown-shaped. Back page is the meeting agenda for next week, not a contact form.

Category prism on the cover. The hex top-right is forest (data), lavender (process), terracotta (documents), or mint (integrate). Pile six reports on a desk and you can see at a glance which is the data one.
Title is a sentence with a period. "Open registers for Acme BV." reads like a finished thought, not a category label.
Markdown running header. "# Chapter title" in Plex Mono. Treats the report as a document checked into a repo, not a one-off PDF.
Index is a flat TOC. Plex Mono section number, Figtree title, Plex Mono page number. No chapter/subsection nesting, the report isn't a book.
Diagram is now → bridge → next. Three pointy-top hexes, cobalt-300 / cobalt / forest. The reader sees the transition in three glances, then the body explains the move.
Tables earn their cobalt header. Plex Mono for nums and dates, Figtree for owners, hairline cobalt-100 between rows. The eye knows where to land without zebra stripes.
Four info-box variants, standard. Note (cobalt), tip (mint), warning (terracotta), important (KNVB orange). Just a tinted card with a left bar, no hex, no icon. The colour is the rule, the label confirms it. One orange per page; the others can repeat.
Playful info-box variant. Same four colours, but the card bleeds to the paper's right edge and the hex IS the left border. Each hex carries a Material-style icon (info-i, lightbulb, triangle-!, exclamation). Short content: the hex alone reads as the full left edge. Tall content: the hex stays fixed at the top-left, and a thin line continues underneath, lined up with the hex's vertical centre.
Quote. Italic body in cobalt-700 with a KNVB-orange left bar. Attribution underneath in Plex Mono uppercase, "Speaker · role" format. Same component used inline on body pages and stacked on its own sheet.
"What we don't do" callout. Every body page can hold a honesty box. Builds trust faster than three claims.
Sources are academic-ish. Numbered [01], author + title, Plex Mono URL. Auditors can find the source, the rest of the readership can ignore it.
Attachments name themselves. Plex Mono filenames with type pill and size, so the reader knows what each blob is before they open it.
Hex-pagination. Three honeycomb cells at the bottom, one filled. Tells you where you are without "page 2 of 3" boilerplate.
Back page is "wat is volgende". Three concrete actions, owner per action, date per action. The reader leaves the meeting with a calendar invite, not a feeling.
Contact card with a hex monogram. Same monogram pattern as the business card, the brand is consistent across paper sizes.
"This report is a working document, mark it up." A footer that gives the reader permission to scribble. Reports that don't get marked up don't get used.

Uses

tokens.css · cover-page template · section-divider template · hex-bullet icon · running-header pattern shared with letterhead · .paper--A4

Download .odtLibreOffice / Word →

Open in your editor, fill the {{ placeholders }}, export to PDF.

Report

Open registers for Acme BV.

Holiday-proof access to your customer register, in seven weeks.

What we found

Where OpenRegister fits

Timeline

Voices from the field

Contents

Three ways to draw this register

01 · Linear · sequential

02 · Hub · one source, many consumers

03 · Branched · decision with outcomes

Timeline

What you need to know

What you need to know, with more confidence

Sources

Attachments

What's next.

Ruben van der Linde

{{ Title goes here. }}

{{ Outcome sentence with period. }}

{{ Section heading }}

{{ Subhead }}

{{ Page title }}

{{ Contents }}

{{ Page title }}

01 · Linear · {{ subtitle }}

02 · Hub · {{ subtitle }}

03 · Branched · {{ subtitle }}

{{ Table title }}

{{ Page title }}

{{ Page title }}

Sources

Attachments

{{ What's next. }}

{{ Author name }}