On-demand workshop60 minutesHealth and safety 2021

Health and safety workshop: digitize an incident management process in under 1 hour

Watch David Shanley build a four-step incident management process live in FlowForma Process Automation, from geolocation and photos to hide/show rules, automatic investigator assignment and pass-back, with no code.

What does this workshop show?

In this August 2021 virtual workshop, registrants voted for incident management, and David Shanley built a four-step health and safety incident process live in FlowForma Process Automation: incident details, regulatory reporting, investigation and closure. He added geolocation, repeating tables, photo upload with annotation and wet signatures, then used hide/show, get list data and pass-back rules so the form adapts to each answer, assigns the right investigator automatically and returns unresolved incidents for more work, with no code. Stewart Miller covered how customers use FlowForma across the business, and the session closed with document generation, process performance and governance. For a construction-focused version of the same build, see our December 2022 workshop.

31%of registrants voted for incident management, ahead of change requests and purchase orders
4 stepsincident details, regulatory reporting, investigation and closure
~30 minto build the process live, by David's estimate
4–6 weeksaverage time to see a return on investment, per Stewart

What the audience told us

Two live polls from the workshop. The shares for the other answers weren't read out.

64%

are still running processes on paper

What process challenges are you currently facing?

  • Processes are paper-based 64%Top answer
  • Lack of mobile access, online and offline
  • Poor communication with suppliers and third parties
  • Information submitted incorrectly or lost in email
“With 64% on manual processes, you're really going to enjoy this session, because you're going to see how easy and how quick it is to digitize your processes.”Stewart Miller, 04:30

Live poll at 02:45

88%

want the ability to automate processes in-house

What outcome is most important to you from digitizing your processes?

  • Ability to automate processes in-house 88%Top answer
  • Speed of digitizing processes
  • Integration with other systems
  • Strong reporting capabilities
“That naturally flows from the majority of the audience having manual processes. It's that agility to digitize processes at will.”Stewart Miller, 55:00

Live poll at 54:00

See your own process built live

Book a demo with our process experts and see one of your processes digitized, from incident reports and inspections to risk assessments and permits.

  • A demo built around one of your processes
  • Incident management, inspections or risk assessments
  • Advice on mobile, offline use and external parties
  • No cost and no obligation

Working in health and safety? See FlowForma for health and safety

Pick a time that suits you

00:00

Welcome and introductions

Watch

Conor McGrath00:00

Hi everyone, and thanks for joining us for another FlowForma virtual workshop, where you'll see another business process digitized in under one hour. My name is Conor McGrath, I'm a Digital Marketing Executive at FlowForma, and I'll be your host today.

Conor McGrath00:30

I'm delighted to be joined by my colleagues David Shanley, Product Specialist, and Stewart Miller, Territory Manager. We want to show you how easy it can be to use FlowForma Process Automation to digitize your processes quickly, gain rapid adoption and get an early return on your investment. Please use the chat box for questions and take part in the polls.

02:00

Registration vote: incident management wins

Watch

Conor McGrath02:00

Before today, we asked you which process you'd like to see digitized, and the clear winner, with 31% of registrants, is incident management.

02:45

Live poll: your process challenges

Watch

Conor McGrath02:45

Next poll: what process challenges are you currently facing? Your processes are paper-based with a lack of mobile access online and offline, poor communication with suppliers or third parties, or information submitted incorrectly or lost in email.

Conor McGrath04:00

The results are in, and 64% of our audience are currently paper-based, a staggeringly high number compared with the other challenges. A landslide.

04:30

Processes customers digitize across the business

Watch

Stewart Miller04:30

Hello and welcome to our global audience. With 64% on manual processes, you're really going to enjoy this session, because you're going to see how easy and how quick it is to digitize your processes with a 100% no-code tool.

David Shanley05:00

Incident management is a very good choice. It applies across all businesses and all verticals.

Stewart Miller05:15

It was a three-way race with the change request and purchase order processes, so you'll learn plenty whichever you chose. There's also an open invitation for a one-to-one session on your own process challenges, or a tailored demo of one of your own processes.

Stewart Miller06:15

This isn't about digitizing just one process. It's about business users digitizing processes across the organization, self-sufficiently and with speed. Here's a small example of what our customers digitize themselves, across every department, with external suppliers and contractors, sign-offs and document management. And they do it after two days of training.

08:15

Forms in SharePoint, dashboards and Power BI

Watch

David Shanley08:15

This is the landing page for the FlowForma app. It sits on SharePoint Online, and every form created is added to this list, with published questions shown as extra columns. End users don't come in here, though. They just need a link to start a form or open an existing one.

David Shanley09:00

This construction accelerator dashboard is a SharePoint team site with tiles to start each process and a list of forms awaiting my input. For the materials requisition, built-in SQL rules push data to SQL Server and pull it back into a Power BI dashboard, so users get a holistic view of everything they need to engage with.

10:00

Tour of the finished incident form

Watch

David Shanley10:00

Here's the winning process, incident management, from the end user's point of view. The header can show a logo or data from the form. Underneath is the step bar: the current step is always in white, followed by regulatory reporting, investigation and closure. It's one single form interface, so users understand where they sit in the process.

11:30

Question change rules: hide/show and list data

Watch

David Shanley11:30

As the user engages with the form, rules fire under the hood. A question change rule fires on the trigger question. Here, a hide/show question rule says that if the incident type is first aid or a medical emergency, show injury information and whether emergency services were called. Unselect it, and that content is gone.

David Shanley12:15

The site is a SharePoint list lookup. When I select site A, a get list data rule pulls through the right investigator, which happens to be me. When I submit, a step completed rule can assign the investigation step to that person.

David Shanley13:00

There's a geolocation question to pinpoint exactly where the incident happened, the date and time, a description, and a repeating table for the incident timeline. If witness statements are required, a hide/show rule shows the witness statements table.

David Shanley14:00

If I report hazards, I can upload an image and annotate it. On the iOS or Android app, I'm prompted for a photo. If the incident isn't reported to the regulatory body, a rule asks why, and the regulatory step disappears from this form. And there's a wet signature, so you can sign with your finger or a stylus.

15:30

Step-level rules: assign, email and pass back

Watch

David Shanley15:30

So far you've seen question change rules. Rules also fire at step level. When I click submit, a step completed rule assigns the investigation step to the investigator and sends them an email. Rules can also fire on step save, for long-running processes you dip in and out of.

David Shanley16:30

The investigator can view the initial step, record actions and who completed them, and sign. On closure, if the reviewer says the incident isn't closed, a comments box appears, and a pass-back rule sends the form back to the investigation step with those comments shown read-only.

David Shanley18:00

There's also a generate document rule that creates a PDF of the form. That's what we're going to build.

18:30

Creating the process and its steps

Watch

David Shanley19:00

I've given the process a prefix that appears ahead of the ID of every form created from it. This opens the flow designer, a three-in-one toolkit that combines forms, workflow and document generation in one build interface, with 100% no code.

David Shanley19:30

Many tools use canvas-based technology. You can pull a form together quickly, but then you apply business logic with expression language and knit it together with a separate workflow component. This build interface is designed from the ground up for process owners.

David Shanley20:00

You start by adding steps, a step being a block of content you assign to a person or a group. You don't need a predefined data set to create your form. You decide what information to capture, then what to do with it, such as pushing it to a SharePoint list or SQL Server.

21:00

Adding questions and question types

Watch

David Shanley21:00

Now the questions. There are lots of question types: SharePoint list lookups, Dynamics CRM, SQL lookups, tables, wet signatures and location. Who reported the incident is a person or group question set to the current user. Incident type is a choice, shown as checkboxes so users can select more than one.

25:30

Separators, repeating tables and photo uploads

Watch

David Shanley25:30

A separator is a graphical way to denote a section, here in bold white text on a dark gray background. The incident timeline is my first repeating table. Each sub-question is its own column, and you can apply rules inside the table, for example to cascade categories, pull through prices and calculate totals.

David Shanley27:30

As with a lot of processes, the first step is front-loaded with data collection. After that, you move through approvers and gatekeepers. The rules you'll see apply regardless of the process or its complexity.

28:00

Q&A: integration options

Watch

Conor McGrath28:00

Michael says it's an impressive system and asks about integration options.

David Shanley28:20

There's built-in integration out of the box with SQL Server, Dynamics CRM and SharePoint lists. You can also call Azure Logic Apps, so if a system has a Logic Apps connector, we can integrate through the flow designer. Where REST APIs are available, we can create custom connectors.

Stewart Miller29:45

For people seeing this for the first time, how much training do they need to be self-sufficient?

David Shanley29:50

A couple of days, which is not a steep learning curve compared with a lot of tools. Once you see the business rules applied, you get a strong sense of how intuitive it is, because you can see where your rules sit and why.

30:45

Regulatory, investigation and closure steps

Watch

David Shanley31:30

The last question on the first step is a wet signature, since this will be used on site on a tablet. FlowForma's mobile apps work offline: data you enter is cached on the device and uploaded to SharePoint when you have connectivity.

David Shanley32:00

The regulatory reporting step looks up the regulatory body from a SharePoint list and records when they were notified. The investigation step records who investigated and a repeating table of actions, who completed them and when. For a more complex process, you could push actions to a SharePoint list and give each person their own step.

34:30

Q&A: changing a live process

Watch

Conor McGrath34:30

Alicia asks how easy it is to amend a process once it's live, for example after feedback from a department.

David Shanley34:55

It's a very agile tool to build with. It's quick and easy to make changes, and it's easy to understand what was built and why, so you don't have to untangle it.

36:00

Applying hide/show question rules

Watch

Stewart Miller36:00

That's about 25 minutes to build the steps and questions. Very quick.

David Shanley36:30

Now the question change rules. The reported-by question is read only. I hide the two injury questions by default, then add a hide/show question rule on the incident type: if it contains first aid or medical emergency, show injury information and emergency services called. There are lots of rule types, from data integration to location and SharePoint actions.

38:00

Get list data and hide/show step rules

Watch

David Shanley38:00

Once the site is chosen, a get list data rule filters the sites list for that site and maps the investigator into a person field, which we'll use to assign the investigation step.

David Shanley39:00

If witness statements or hazards are required, hide/show rules show their tables. You get into a rhythm of building very quickly. If the incident isn't reported to the regulatory body, a hide/show step rule hides that step, and a question rule asks for the reason.

42:00

Preview, step assignment and pass-back

Watch

David Shanley42:00

I can preview what I've built and see my rules firing as I go. Now step-level rules: a workflow control rule assigns the investigation step to the person in the investigator field, and a send email rule uses a template with tokens from the form and a link to it.

David Shanley43:30

On closure, if the incident isn't closed, a pass-back rule sends it back to the investigation step. A hide/show rule shows the comments there, and a set question value rule copies the reviewer's comments across. Two days of training, and business users can do all of this.

45:00

Testing the finished process

Watch

David Shanley45:00

Let's test it. Selecting first aid shows the injury questions. The site pulls through the investigator. Saying no to regulatory reporting hides that step and asks why. I sign and submit, the investigation step is assigned and an email is sent.

David Shanley46:30

The closure owner has view permission on the earlier steps. If I say the incident isn't closed, add comments and submit, it passes back to the investigation step with the comments embedded. Instead of a pass-back button, a business rule governs it. That's the build done in about 30 minutes.

47:30

Document generation in Word

Watch

David Shanley47:30

For document generation, you install the FlowForma plug-in for Word, upload a template to the process's document library, and insert tokens for answers from the form. Rules can include or remove sections, so a section on injury information only appears for first aid or medical emergencies. Documents can be converted to PDF and attached to emails.

49:00

Process performance and work items

Watch

David Shanley49:00

It's not just about how fast you can build, but managing the forms once they're live. Process performance shows how each step is doing against its SLA, and an administrator can reassign late forms to free up bottlenecks. You can also cap how many forms one person holds and reassign automatically, and there's a full audit trail of rules fired.

51:00

Governance and environments

Watch

David Shanley51:00

Governance is a hub that lets IT manage which environments are created, who has access and which processes are promoted from one environment to the next. Process owners can build in a sandbox without breaking anything, and IT decides when processes move to UAT. There are also adoption and licensing hubs.

David Shanley52:30

Because you build in a single interface, you can go back into a build from nine months ago and see where each rule sits and why. It's a single interface, 100% no code and intuitive to build with.

53:30

Live poll: the outcome that matters most

Watch

Conor McGrath54:00

A final poll: what outcome is most important to you from digitizing your processes? The ability to automate processes in-house, speed, integration with other systems or strong reporting? The ability to automate in-house wins with 88%.

Stewart Miller55:00

That naturally flows from the majority of the audience having manual processes. It's that agility to digitize processes at will, and the confidence to build it yourself without outsourcing and incurring that overhead.

55:30

Audience Q&A

Watch

Conor McGrath56:00

Mike has a lot of staff in remote areas. Would FlowForma work for remote users?

David Shanley56:15

There's a FlowForma mobile app for iOS and Android with offline capabilities. It's used a lot for on-site process engagement, particularly in construction.

Conor McGrath56:45

Can I engage external parties, such as suppliers, in our processes?

David Shanley57:00

Yes. You can engage third parties either anonymously or with secure access, and across a process, not just the first step.

Stewart Miller57:30

On how soon you could see a return on investment, every organization is different and wants different outcomes, so we work with customers on a business case. As soon as you go live with your first process, you're seeing a return, and on average that's four to six weeks.

Conor McGrath58:30

We're out of time, but we'll answer the remaining questions afterwards. You can book a one-to-one call with one of our process experts on our website. Thanks to David and Stewart, and to everyone who attended. Have a great day.

Frequently asked questions

Can staff in remote areas use these processes?

Mike asked this in the session. Yes. David explained that FlowForma has mobile apps for iOS and Android with offline capabilities, and they're used a lot for on-site work, particularly in construction.

Can external parties such as suppliers input into our processes?

Yes. David said you can bring in third parties either anonymously or with secure access, and they can take part across a process, not just in the first step.

How soon could we see a return on investment?

Stewart said it depends on the organization and the outcomes it wants, and FlowForma works with customers on a business case. You start seeing a return as soon as your first process goes live, and on average that's within four to six weeks.

What integration options are there?

Michael asked this in the session. David listed built-in integration with SQL Server, Dynamics CRM and SharePoint lists, plus Azure Logic Apps connectors. Where a system has a REST API, custom connectors can be created.

How easy is it to change a process once it's live?

Alicia asked this in the session. David's answer: it's an agile tool, so changes are quick, and because everything is built in one interface it's easy to see what was built and why, without untangling it.

What are the most popular features?

Philip asked this in the session. David picked FlowForma Engage, for bringing third parties into processes, and the core of the product: a single build interface, a single form interface and no code.

Who presented this workshop?

David Shanley, Product Specialist at FlowForma, built the process live, with Stewart Miller, Territory Manager. Conor McGrath, Digital Marketing Executive, hosted the session and ran the polls and Q&A.

Digitize your next health and safety process

Talk to our team about incident management, inspections, risk assessments or permits.