What you do with Stakeholders
Record stakeholders
For each stakeholder you record the type of party, internal or external, and their needs, expectations, concerns or sensitivities. An administrator can add your own stakeholder types in the module settings.
Matrix by influence and interest
Influence and interest determine the position automatically: manage closely, keep satisfied, keep informed or monitor. Click a name in the matrix to open the file.
From expectation to requirement
From a stakeholder's file you turn an expectation directly into a requirement.
Requirements register with source
Legal, contractual, normative, customer and internal requirements sit in one register, with source, level of obligation, evaluation cycle, owner and optionally a source document from Document management.
Compliance and evidence per requirement
For each requirement you choose complies, partly complies, does not comply, unknown, not applicable or review needed. If evidence is missing, the requirement is flagged.
Follow-up via Actions
When a requirement is not or only partly met, the file asks for follow-up. You create a pre-filled action or CAPA in Actions.
How it works
- 1
Add a stakeholder
Choose new stakeholder and describe in four steps who it is, what they expect and how important they are.
- 2
Position in the matrix
Open the matrix to see where each stakeholder stands and whom you need to involve actively.
- 3
Record requirements
Turn expectations into requirements and record source, compliance, next evaluation and owner.
- 4
Evidence and follow-up
Add evidence or link a document, and assign an action or CAPA where you fall short.
- 5
Include in the context review
Stakeholders and requirements are part of the periodic context review in the Context module, with an outcome per item such as unchanged and still current, or follow-up needed.
Where it helps you
BrydgeOne contains no text of the standards. Here you see which topics from standards and legislation this module helps you with.
Stakeholders, their expectations and the resulting requirements, such as customer and contractual requirements, support clause 4.2.
For clause 4.2 you record stakeholders and their requirements with compliance and evidence; environmental aspects refer to requirements in the register.
Stakeholders can be internal or external, so workers and their expectations are part of the analysis for clause 4.2 as well.
Works together with
Every module works on its own. Switch on more and they fill each other in automatically.
Read more about Stakeholders
Terms related to Stakeholders
Questions about Stakeholders
What is the difference between Stakeholders and Context?
Stakeholders is about who expects something of you and which requirements follow from that (clause 4.2). Context is about the internal and external factors that affect your management system (clause 4.1). Together they form one connected file, and you link them to each other.
Does every stakeholder need requirements?
No, but relevant stakeholders without recorded expectations are usually a sign that the analysis is not finished yet.
Can I also record legal requirements and permits?
Yes. A requirement can come from legislation, a permit, a standard, a contract or a customer, with its level of obligation and a source reference.
Does the system create actions by itself?
No. When a requirement is not or only partly met, the file asks for follow-up, but you create the action or CAPA yourself. It arrives pre-filled in Actions.
Start with just Stakeholders and expand when you want
You do not have to set up everything at once. Switch this module on, add other modules later and keep using the same data and the same app. BrydgeOne fits every organisation, from a small company to enterprise, and you only pay for what you switch on, from € 49 per month.
See Stakeholders in your own situation
You only pay for the modules you switch on, from € 49 per month. In a demo we show how it works with your own processes.