Document infrastructure for renovation projects

Make it impossible to build the wrong thing.

Less money spent on defects · Smoother document workflows · Happier teams and clients

Plans change. Linked documents don't follow. Work carries on from outdated versions — until someone builds the wrong thing. rdoc makes this structurally impossible.

Built for Switzerland · ZertES + eIDAS ready · Data residency in Zürich

The problem

The document layer fails silently.

Multiple organisations, each managing their own documents. When one changes, the others don't automatically know. The drift is silent — until it surfaces on site.

Documents travel by email. Every contractor works from whichever version they last downloaded. Nobody is negligent — the system just has no memory.

rdoc is the shared memory. Every version, every dependency, every signature — traceable and enforced.

not propagatednot propagatednot propagatedArchitectGen.ContractorClientKitchenSpec.PriceAddendumBankSupplier

What makes it different

The moat is in the mechanics.

Cascade re-review

When a leading document changes, every downstream document that depends on it is automatically flagged for review. No manual coordination. No silent drift.

review pending

AI cross-document auditor

An AI inspector reads every leading document in your project and surfaces contradictions across them. Then ask follow-up questions in plain language.

HIGH · Color mismatchAsk about these documents…

Multi-party permissions

Each organisation, each project group, each user — only sees what they need to. Audit trails on every action. Modelled on VDR data room access controls.

ProjectArchitectsAliceBobClientCarol

How it works

From chaos to traceability in three steps.

01

Upload your project documents

Every contractor uploads their documents — plans, specifications, price addenda, renderings — to a shared, version-controlled project workspace.

02

Link related documents to each other

Declare that the kitchen specification depends on the architect's floor plan. That the price addendum references the tile specification. The graph is now explicit.

03

Every change is tracked, audited, and propagated

When any leading version changes, all dependent documents are flagged. The AI auditor checks for semantic contradictions. Re-signature is mandatory — always.

Swiss data residency

Project documents are stored in Google Cloud Storage, Zürich region (europe-west6). Swiss data never leaves Switzerland.

Encrypted at rest and in transit

All files are encrypted with AES-256 at rest. All connections use TLS 1.3. No exceptions.

Full audit trail per document

Every state change — who uploaded, who signed, who voided, when — is recorded permanently and cannot be deleted.

Stop losing documents in email threads.

Request access to the closed pilot. We are onboarding the first contractors in Switzerland in 2026.