Svenska Book a walkthrough

Solutions · Processes & forms

Turn a policy into a process people actually follow.

Forms, Workflows, Processes and Obligations are the building blocks. Start from a ready process, let Luis build one from your policy, or put it together yourselves without code – and it inherits the permissions, the log and the rules of the foundation.

Supplier onboardingReady from the start
  • FormSupplier self-assessment
  • WorkflowReview by Procurement
  • ProcessApprove, sign, onboard
  • ObligationYearly re-assessment

Inherited from the foundation

  • Permissions
  • Full log
  • Compliance
  • Shared data
The foundation
Product example

How the process engine works

Answers become data. Data triggers the next step.

Follow one new supplier from the first form to your ERP. Actions fire when a stage starts, conditions choose the path, and every step lands in the log – with or without Luis.

The process startsStart form · New supplier
1Self-assessment2 actions

At the same time, when the stage starts

  • FormSend form to the supplier
  • NotificationNotify Procurement
2Review per question3 actions

Each answer to its owner

  • RoutingQ7–12 → IT Security
  • RoutingQ13–16 → DPO
  • RoutingQ17–20 → Procurement

IfRisk = High

Yes
  • WorkflowApproval by the CISO
No

Straight to the contract

3Contract2 actions

At the same time, when the stage starts

  • DocumentAgreement and DPA from templates
  • E-signingSend for e-signing
4Integration2 actions

When the contract is signed

  • IntegrationCreate the supplier in the ERP
  • ScheduleSchedule yearly re-assessment
Done · every step in the log

Log · Nordlog AB

  1. 09:02Procurement adds Nordlog AB
  2. 09:02Form sent · Procurement notified
  3. 14:37Nordlog submits 24 answers
  4. 14:37Answers routed to 3 reviewers
  5. Day 2Review done · 22 approved, 1 follow-up
  6. Day 2Condition: Risk = High
  7. Day 2Approved by the CISO
  8. Day 3Agreement and DPA sent for e-signing
  9. Day 4Signed by both parties
  10. Day 4ERP: supplier 40213 created
  11. Day 4Re-assessment scheduled · 14 Nov 2027

Luis · New process

We need supplier onboarding that meets NIS2 article 21 on supply chain security. High-risk suppliers need the CISO, and approved suppliers should end up in our ERP.

Luis

I found 6 requirements in article 21 and your supplier policy. Building a draft:

  • Stage 1 · Self-assessment, 24 questions
  • Stage 2 · Review routed by topic
  • Condition · High risk needs the CISO
  • Stage 3 · Contract from your templates
  • Stage 4 · Supplier created in the ERP

The draft is ready. Nothing runs until you publish it.

Every stage Luis adds, you can also build by hand in the Process Designer.

Product example

Three ways to start

Ready, built by Luis or made by you.

Never another system on the side. Every process lands in the same data model as your contracts and Controls – so the supplier you assess is the same supplier you sign with.

Ready from the start

Standard processes come with every Workspace as drafts you can change: supplier assessment, onboarding and offboarding, security events, access reviews, data subject requests and more.

Built by Luis

Attach your policy and ask Luis. He lists every requirement in it, builds the process with its forms and Workflows as a draft, and shows what still needs you.

How Luis builds →

Made by you, without code

Stages, steps, decisions and conditions in the Process Designer. Teams can change their own flows without waiting for IT – and IT can still say yes, because the control follows.

  • Form
  • Workflow
  • Process
  • Obligation

What teams run in Paragraf

From a spreadsheet to a process you can show.

  • SuppliersAssessment, approval and yearly review
  • PeopleOnboarding, offboarding and access reviews
  • IncidentsSecurity events with the deadlines built in
  • PrivacyData subject requests and personal data breaches
  • CustomersComplaints and cases through a public link

Shadow systems

Let the business change its own flows. Without the shadow systems.

Teams already run processes in Excel, email and chat – and the control rarely follows. In Paragraf they get the same speed, while the CIO and the lawyer keep the permissions, the log and the source.

Template: your system map on one page →

The way you work, written down once – and followed.

Teams run the process, and the control follows without anyone chasing.

A man in a camel sweater reads on his phone with a small smile.

Processes are one door. Behind it is the whole house.

Your own processesLuisContracts · Compliance · Processes · FormsThe foundation

Next step

Fewer systems.
More control.

Book a walkthrough of your systems and requirements. We show you the thread from requirement to proof – with your own requirements.

Book a walkthrough Template: your system map on one page →