Needs get lost
Decisions from workshops disappear into minutes, slide decks, and disconnected spreadsheets.
Project Briefing before design starts
Turn needs into a brief your design team can use
Define usage scenarios, connect them to proven room types, publish one professional room programme and project brief, and get BIM requirements as a byproduct.
- Configure the project free before committing
- Trace every requirement and decision through version history
- Continue into BIM requirements without re-entering the brief
Open standard. Git-style traceability. Ready for people, software, and AI.
1
Make a few project choices
Your sample room programme
Live result
Store strollers
At the entrance
Entrance hall
Stroller parking
The problem
A room list is not a project brief
Static spreadsheets record areas, but they rarely explain how people use a building or why a room is needed.
Rooms lack context
Design teams receive names and areas without the scenarios, relationships, and constraints behind them.
Changes cannot be traced
Overwritten files make it difficult to prove who changed a requirement, when it changed, and why.
Interactive example
From usage scenarios to room programme
Make a few project choices
Built as data
A brief that remains useful after the workshop
Open by default
Requirements use an open, machine-readable structure instead of being trapped in one document or application.
Fully traceable
Git-style commits record who changed what and why. Published versions remain fixed and reviewable.
AI-ready with provenance
Structured requirements and known version history give AI reliable context for comparison, generation, and review.
Project Briefing beyond a document workflow
BriefBuilder and pragmaticBIM both support structured briefing. pragmaticBIM makes the published requirements an open, versioned source of truth that continues into BIM and automated validation.
How it works
From goals to a published project brief
Start with intent, make the spatial consequences visible, and hand over a controlled version.
01
Define goals and scenarios
Select the outcomes the project must support and choose relevant usage scenarios from templates.
02
Build the room programme
Reuse predefined room types, adapt quantities and relationships, and see which spaces each scenario requires.
03
Review and publish
Agree changes through a versioned review and publish a stable project brief for the design team.
Simple add-on pricing
Configure free. Pay when you publish.
Add Project Briefing when the room programme and project brief are ready to become a controlled project deliverable.
- Unlimited configuration before publication
- Usage scenarios and predefined room types
- Published room programme and project brief
- Git-style review and complete change history
- Continuity into IDS and BIM requirements
Project Briefing questions
How does Project Briefing produce BIM requirements?
Usage scenarios and room types define what the project must deliver. pragmaticBIM carries those decisions into model specifications and IDS, so BIM requirements become a byproduct of the project brief instead of a separate exercise.
What is included in the 750 CHF price?
The price covers one published project for one year. Configuration is free until publication is ordered.
How is pragmaticBIM different from BriefBuilder?
Both support structured project briefing. pragmaticBIM uses an open, machine-readable standard and Git-style versioning, so every published requirement has traceable authorship and history and can continue into BIM validation.
Why does version history matter for AI?
AI works best with structured context and known provenance. Fixed versions and explicit changes make it possible to compare, generate, and review requirements without losing which source was agreed.
Start with the needs, not the model
Configure the scenarios and room programme free. Order publication only when the project brief is ready.