Sessions with substance. Resolutions with effect.
Frozen report snapshots as the dossier, resolutions with four states including “approved with conditions”, approvals straight from the notification - and no item falls between two sessions.
- Status reportsfrozen
- One-pager AtlasPDF ready
- Scenario comparison2 variants
- Last session's resolutions2/3 implemented
Sound familiar?
Committee work rarely fails at the decisions - it fails at documents, minutes and follow-up.
Unverified versions in the session
The table document contradicts yesterday's e-mail. Which version is official? Without a clear approval path, nobody knows.
The first twenty minutes: reconstruction
What was open last time? Who was going to deliver? The session starts with archaeology instead of decisions.
Resolved - and buried in the minutes
Resolutions live in a Word document, but nobody works through minutes. Next session: the same discussion.
Decisions without proof
Months later the auditors ask who decided what, when, and with which reasoning - and all that exists is an e-mail thread nobody can find.
A session cycle with WORKSPACE.PM
Your rhythm isn't the working day - it's the session: five stations from the dossier to the follow-up.
Documents that are decision-ready
Status reports arrive four-eyes-approved and frozen at the reporting date - it stays verifiable at any time which version officially went to the board.
Status reports in detail- Status reports - frozen at the reporting date
- Traffic lights with trend
- Deliverables register
The proposal computes its own variants
Up to five computed scenarios with a live delta against the baseline accompany the decision - with a complete approval history instead of volume.
See scenario planningAgenda, minutes, attendance - live
The “steering committee” template fills the agenda, items are ticked off during the meeting, attendance is documented with roles - and the minutes are written in focus mode while you meet.
Explore project meetingsResolutions with four states - including “with conditions”
Every resolution carries a responsible person and a status. Approval happens straight from the notification - without a detour through the meeting minutes.
Resolution management in detailFour states - your vocabulary included
No item falls between two sessions
Resolutions become kanban cards with a deadline and reminder, open items go onto the next agenda with one click - and the register across the whole series answers what came of every item.
See meeting tasksThe “from meeting” origin stays visible
And between the sessions? Formal requests run as approval workflows with deadline, escalation and mandatory comments - the toolbox below takes you there.
Your toolbox
Six areas boards draw documents, decisions and proof from - every card leads to the matching page.
Your board in interplay
You meet, decide and follow up - on documents from the same data base everyone works in daily.
Boards & committees
Documents, resolutions and proof converge here - decision-ready instead of copied together.
Executive management
Decides between your sessions on the same frozen snapshots.
For executive managementBoards & committees
Documents, resolutions and proof converge here - decision-ready instead of copied together.
Executive management
Decides between your sessions on the same frozen snapshots.
For executive managementGovernance that speaks your language
Formal and verifiable - and still without paper stacks.
Deciding without studying a system
Minutes and one-pagers arrive as PDF exports for distribution - even without system access. Members with an account read everything via the “Auditor / Management” permission and change nothing; they approve resolutions straight from the notification, and a daily digest sums up what's pending.
Formal approvals with named approvers
Quality gates carry approval criteria with named approvers: every vote with a comment, deputy arrangements, and a final decision separate from the individual votes - chronologically documented in the audit log.
Conditions are a status of their own
“Approved with conditions” exists as its own resolution status - and at portfolio level as conditional go. Conditions become trackable tasks with deadlines instead of footnotes in the minutes.
Frequent questions from boards
What committees and steering groups want to know before rolling out.
Not necessarily for the documents: minutes come as PDF or Markdown exports, the project one-pager as a print-ready PDF - explicitly for recipients without system access. For full read access there is the “Auditor / Management” permission: see everything, change nothing. Those who take part in decisions approve resolutions straight from the notification.
As a meeting series with a recurrence rule and a session template: the agenda starts pre-filled, follow-up meetings are created by rule, and the resolution and task register across the whole series answers at any time what was decided and what is open. There is deliberately no separate committee module - sessions, resolutions and approvals work on the same data base as the projects. The committee itself is steered through a user group: created once, it staffs the relevant projects in one step - with the matching read role travelling along automatically.
Status reports are locked from approval on, and marked metrics are frozen as a snapshot at the reporting date - even if the project changes later. It stays provable which version was officially presented.
From resolutions via notification to quality gates with approval criteria, named approvers and an audit log - and at portfolio level as stage gates with go, kill, hold, recycle or conditional go. Deadlines, automatic escalation and mandatory comments included.
Every resolution becomes a trackable task with a responsible person, deadline and reminder. Open items go onto the next agenda with one click - the series register shows the status across all meetings.
Turn sessions into decisions with effect
Try WORKSPACE.PM free for 30 days - from the minutes to the completed condition.