BrydgeOne
Book a demo
  1. Home
  2. Modules
  3. Automation
AutomationManagement system

Agreements safeguarded, without anyone having to remember them

Automation lets BrydgeOne carry out work itself using IF-THEN rules, alongside workflows that enforce approval and task routes step by step. Agreements are safeguarded, while critical decisions remain human work.

Features

What you do with Automation

IF-THEN rules

IF something occurs, such as a new incident, an audit finding or a missed deadline, AND the conditions apply, THEN BrydgeOne carries out the actions. A condition could be severity = high or type = nonconformity.

Tasks, notifications and escalations

A rule creates a task or CAPA, sends a notification, makes a field such as root cause mandatory, escalates or starts an approval route.

Test first, without consequences

Run a dry run of a rule with an example. You see whether the rule would fire and what it would do, without anything actually being created.

Approval routes as flowcharts

In the editor you place steps with a responsible role, SLA and instructions, decisions with outcomes, and end points. A built-in check shows whether every route has a destination.

Defaults as a starting point

Default workflows and rules are ready per theme, free to adapt and easy to restore to the default. Version history lets you compare and restore earlier versions.

Flowchart from a procedure

AI turns your procedure text into a draft flowchart. You then review and adjust that flowchart yourself.

In practice

How it works

  1. 1

    Choose a rule or a workflow

    Use a standalone automation when the system should react by itself, and a workflow when people need to approve or review in a fixed order.

  2. 2

    Set up

    For a rule you choose the trigger, the conditions and what BrydgeOne should do. For a workflow you choose what it applies to, such as documents, quality reports or MoC, and build the steps.

  3. 3

    Test and activate

    Test a rule with an example first, then switch it on. A workflow can only become active once every route leads somewhere.

  4. 4

    Let it run

    When the situation occurs, the route starts: those responsible receive a task and notification. Steps that exceed the SLA trigger a reminder and can escalate.

  5. 5

    Trace back

    Every automatically created task can be traced to the rule and what triggered it, and all decisions are in the log.

In the employee app

Rules look at what was reported, not at the channel. A report from the employee app or a public form triggers the same rules as one entered in the platform.

Frequently asked questions

Questions about Automation

Can a rule accidentally create lots of tasks?

Test it first with the dry run and start with a narrow condition. You can always switch a rule off immediately.

Does automation make decisions for us?

No. Automation suggests and prepares; critical decisions such as approvals and closures remain human work through the relevant module or a workflow.

What if we change a workflow while routes are running?

Running routes finish their original steps; changes apply to new starts.

Can a step be assigned to a specific person?

Steps are assigned to roles, so they stay correct when staff change. Within the role, a specific person picks up the task.

Start small

Start with just Automation 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 Automation 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.