Capability 01
Spaces for the way you organise
A space for each product, programme or team, with its documents beside the backlog rather than in a separate wiki.
Living documentation
Document Spaces are collaborative documents inside SyncupHUB, organised into spaces for a product, programme or team. Comments, suggestions, approvals and version history are built in, and each document sits next to the work it describes — a BRD, a runbook or an architecture note is one click from the stories and decisions it governs.
Capability desk
Capability 01
A space for each product, programme or team, with its documents beside the backlog rather than in a separate wiki.
Capability 02
Reviewers comment and suggest edits on the text itself, and the author accepts or declines each suggestion.
Capability 03
A document moves through review to approval and every version is kept, so you can see what changed and who agreed to it.
Capability 04
Business requirements documents with objectives, scope, numbered requirements, acceptance criteria and open decisions, exported to Word for sign-off.
Capability 05
Architecture, API, schema and flow documentation produced from repository analysis, saved beside the documents people wrote and reviewed the same way.
Capability 06
Attachments live in an S3-compatible bucket you configure.
How it works
No 9-month transformation programme. Most teams are live inside a fortnight and measuring outcomes by the end of the first quarter.
Create a space for a product, programme or team and keep its documents beside the backlog.
Reviewers comment and suggest edits on the text itself, and the author accepts or declines each one.
A document moves through review to approval, and every version is kept.
Documentation produced from repository analysis is saved into a space, next to the documents people wrote.
Inside the product
Module 01
Documents where the work is.
Module 02
BRDs the team builds against.
Module 03
What AI writes, kept and reviewed like the rest.
Who it is for
Keep the approved BRD next to the stories built from it.
Store architecture notes where engineers will read them.
See what changed in a document and who agreed to it.
Find the runbook beside the work, not in a separate wiki.
Works with
Native connectors, webhooks and a documented REST API. Not listed? It is usually two days of work, and we will tell you before you buy.
How you get it
There is no separate licence and no separate bill. Document Spaces is part of SyncupHUB at no additional cost.
FAQ
A wiki sits beside the work; Document Spaces sit inside it. Each document lives in a space for a product, programme or team, next to the stories and decisions it describes, with comments, suggestions, approvals and version history built in.
Yes. A document moves through review to approval and every version is kept. A BRD is re-approved when its source changes, so the approved version is always the one the team is building against.
AI documentation analyses a repository and produces source-linked architecture, API, schema and flow pages. Teams can save it into a space, where it sits beside the documents people wrote and is reviewed the same way.
No. Document Spaces are part of SyncupHUB at no additional cost.
The platform
The delivery platform for the AI era.
Explore SyncupHUBTest cases drafted from your acceptance criteria. Approved by your QA lead.
Explore QA IntelligenceA whiteboard that stays attached to the work.
Explore Visual CanvasEvery vehicle, reporting in real time.
Explore SyncV2XWe would rather prove the product on the messy programme than the tidy one. Book 30 minutes with an engineer who has run this before.