What is a process house?
A process house (also called a process architecture) is the central backbone for process management: a coherent overview of all of your organisation's processes, from value stream to activity, with the roles, risks, controls, data and KPIs attached to them. In a single picture it answers the question: what work do we do, how does it fit together, and who is responsible for what?
The definition in brief
The term process house comes from the metaphor of a building: a foundation, floors and rooms that together form one whole. In process management, the process house is the overarching model in which you order all processes and relate them to one another. It is deliberately hierarchical: the large value streams at the top, the processes below them, and right at the bottom the concrete process steps where the work actually happens.
Where a single process map or flowchart describes just one process, the process house is the map of the whole. And it is more than a picture: a good process house is a system of record in which accountability, control and evidence are captured in a structured way — and stay current.
Why build a process house?
Without a central model, process knowledge lives in people's heads and in scattered documents. That leaves organisations vulnerable: when people leave, knowledge walks out the door; audits cost weeks of digging; and nobody can say with certainty who is responsible for what. A process house solves that by providing a single source of truth. Concretely, it delivers:
- Overview and coherence — you see in one structure which processes exist and how they connect, instead of isolated islands.
- Role clarity — with a RASCI matrix on the process step, everyone knows who is responsible, accountable, consulted or informed.
- Demonstrable control — you attach risks and controls straight to the process via a risk & control matrix, so you can prove you are in control.
- Continuous improvement — with ownership, reviews and an audit trail, the process house becomes a living model rather than a snapshot.
The structure: from value stream to activity
A process house is built hierarchically. The exact naming differs by methodology, but the core is a descending level of detail: from coarse-grained chains to the concrete action. A common breakdown into three main levels:
The top level: the main chains that deliver value, such as 'order to cash' or 'procure to pay'.
A coherent set of steps within a value stream, with a clear beginning, end and result.
The concrete action where the work happens — and where roles, risks, controls, systems and data attach.
The depth follows your organisation, not a fixed template. Some value streams split into many subprocesses; others stay shallow. What matters is that the numbering and levels are consistent, so the model stays navigable and you can report on it.
What do you attach to a process step?
The power of a modern process house is not in the drawing, but in what you attach to the process step. The activity is the anchor point where all the relevant information comes together:
Roles (RASCI)
Who is Responsible, Accountable, Support, Consulted or Informed — exactly one R and one A per step.
Risks
What can go wrong in this step, and how likely and severe that is.
Controls
Which controls cover those risks — preventive or detective.
Systems & data
Which application the step runs in and which data object it touches.
KPIs & work instructions
How you measure performance and how staff carry out the step correctly.
APQC reference
The mapping to the international framework to benchmark and measure coverage.
By capturing this as connected data instead of in separate registers, everything stays consistent. When a process step changes, you immediately see which roles, risks and controls move with it — no spreadsheets drifting apart.
Process house vs. process diagram, BPM tool and GRC
A process house is often confused with neighbouring concepts. The difference is in the starting point and the depth:
| Concept | Starting point | What it mainly does |
|---|---|---|
| Process diagram | One process | Visualise the sequence of steps of a single process (flowchart / BPMN). |
| BPM drawing tool | Diagram | Produce nice diagrams — but without connected governance they go stale. |
| GRC tool | Risks & controls | Manage risks and controls; the process is a tag at best. |
| Process house | The process model | Order all processes and attach roles, risks, controls and data to them. |
What makes the process house distinctive is that it starts from the process model and connects the other disciplines to it. A GRC tool starts from risks and controls; a drawing tool stops at the picture. The process house brings them together on the process step.
What to look for in process-house software
A process house kept in loose documents or drawing tools ages quickly. Process-house software turns it into a governed, current model. When choosing, look for:
- Connected data, not separate registers — roles, risks and controls should hang off the process step, not sit in separate lists that drift apart.
- Governance built in — ownership, review cycles, version control and an audit trail, so the model stays demonstrably current.
- Benchmarkable — a mapping to a reference framework such as the APQC Process Classification Framework shows where you lack coverage. In Proceshuis, APQC is built in, with a coverage percentage.
- Fits your way of working — Proceshuis supports the ways of working behind ISO 9001, ISO 27001, GDPR and Three Lines of Defense by letting you model the associated roles, risks and controls. That is different from an off-the-shelf compliance framework; we are building that layer out step by step.
- Right-sized for the mid-market — enterprise depth without the enterprise weight: live in days, transparently priced, no consultants.
Proceshuis: process architecture with risk & control and governance
One connected model in which process, RASCI, risk, control, system, data and the APQC benchmark all hang off the same process step — for the mid-market.
Frequently asked questions about the process house
What is a process house?+–
A process house is the central backbone for process management: a hierarchical overview of all of an organisation's processes — from value stream down to activity — with ownership, roles, risks, controls, data, KPIs and work instructions attached. It shows which processes exist, how they relate and who is responsible for what.
What is the difference between a process house and a process diagram?+–
A process diagram (flowchart or BPMN diagram) shows the steps of a single process. A process house sits one level above: it orders all processes into a coherent hierarchy and connects them to roles, risks, controls and systems. The process house is the map; the process diagram is the turn-by-turn directions for a single journey.
What is process-house software?+–
Process-house software is a system in which you capture the process house not as a loose drawing but as a governed model: with version control, ownership, reviews, an audit trail and connected data. That keeps the model current and demonstrably in control, instead of ageing in scattered documents.
Which organisations benefit from a process house?+–
Any organisation that wants a grip on how work gets done — sector-neutral. It is especially valuable for quality, process and risk managers, internal audit and compliance at mid-sized to large organisations that need to demonstrate they are in control.
How does a process house relate to APQC?+–
The APQC Process Classification Framework is an internationally recognised reference taxonomy of business processes. You can map your own process house to it to benchmark and see where coverage is missing. In Proceshuis that APQC mapping is built in, with a coverage percentage.