Constellio

Draw the process.It runs itself.

Constellio runs your processes exactly as you drew them: a BPMN 2.0 diagram, task forms, rules that decide, reminders that follow up. Nobody chases an approval any more.

  • Graphical design in BPMN 2.0
  • Tasks assigned automatically
  • Performance measured per step
  • Rio Tinto
  • Ville de Montréal
  • Université Laval
  • Bibliothèque et Archives nationales du Québec
  • Hydro-Québec
  • CDPQ
  • Barreau du Québec
  • Ville de Longueuil

HOW IT WORKS

Design. Run. Measure.
The same diagram, from end to end.

There is no diagram on one side and software on the other. What you draw is what runs, and what runs is what you measure, in the same place, in the same notation.

  1. 01 Design

    The process is drawn on screen.

    Steps, branches, events, forms: everything is laid out on a BPMN 2.0 canvas. No code, and nothing to be translated by a technical team before you can try it.

    • Graphical BPMN 2.0 canvas
    • Task forms composed on the spot
    • Published as a dated version
  2. 02 Run

    Every case moves without being pushed.

    Tasks go out to the right people, conditions decide the branches, documents are created and filed, and emails go out at the moments you planned.

    • Automatic task assignment
    • Decisions taken on conditions
    • Reminders, escalation and delegation
  3. 03 Measure

    You can see where the time goes.

    Every step is timed, by team and by person. The bottleneck shows up on the same diagram you drew, and the reports are shared.

    • Average duration measured per step
    • Performance of units and individuals
    • Reports shared on every process

BPMN 2.0 is a standard notation: your process stays readable by someone who has never opened Constellio.

ONE PROCESS, FROM CANVAS TO DASHBOARD

The diagram you draw
is the one that does the work.

Follow a supplier invoice: the process is drawn, the form is composed, a case runs through it on its own one Tuesday morning, and the following month the dashboard shows where the three days went.

  1. 01The canvas

    You lay out steps, not code.

    The process is composed on a canvas: a start event, tasks, a gateway that separates the cases, an end event. The notation is BPMN 2.0, so the diagram reads without a manual.

    • Tasks, gateways and events dropped in place
    • Standard BPMN 2.0 notation
    • Published and dated version
  2. 02The form

    Every task has its own screen.

    The task form is composed beside the diagram: the fields to fill in, the ones that arrive already filled, the person the task falls to, and the clock that starts when they open it.

    • Fields composed step by step
    • Owner derived from the role, not typed in
    • Deadline and reminder set on the task
  3. 03The run

    The case moves while you do something else.

    An invoice arrives and the process starts. Steps tick off, the gateway decides on the amount, an email goes out, and the document that gets created is filed in the right place without being asked.

    • Tasks assigned and notified by email
    • Branch decided by the condition
    • Document created, filed, added to the record
  4. 04The dashboard

    The delay has an address.

    Over thirty days, every step has an average duration and a volume. The step holding everything up stands out from the rest, and the report goes to the people who can do something about it.

    • Average duration and volume per step
    • Comparison between teams and people
    • Report exported and shared

REAL-WORLD USE CASES

The mail that comes in,
and the people you hire.

Two processes almost every organization still runs by hand: sorting what arrives at the mail room, and moving an application between people who never cross paths.

A person on a call in front of their laptop

For the mail room

What comes in is already assigned.

Emails, scanned mail, online forms: every arrival starts the process that matches it, goes to the right team, and leaves a record of the delay. The acknowledgement no longer depends on somebody remembering.

See document capture
A person presenting to a seated group in a meeting room

For human resources

An application doesn’t sit in an inbox.

Assessments are requested in parallel, the committee sees who has answered, and the file only moves on when the conditions are met. Letters are created from your templates and filed in the employee record.

Tell us about your processes

What the workflows can do

  • BPMN 2.0 design
  • Task forms
  • Automatic assignment
  • Performance measurement
  • Reports per process
  • Document creation
  • Content filing
  • Conditional decisions
  • Event listeners
  • Email sending
  • Reminders, escalation and delegation

Eleven mechanisms, one diagram

WHO DOES WHAT, AND WHEN

The process crosses teams,
not inboxes.

A process doesn’t move in a straight line: it changes hands. The diagram shows it as it is: one lane per role, the case dropping from one lane to the next, and a gateway deciding who still has to see it.

REQUESTERsubmits the requestMANAGERverifies and codesMANAGEMENTapproves above the thresholdCONSTELLIOcreates, files, retainsSTARTENDRequest submittedonline formVerificationdocuments and codingApprovalmanager’s signatureDocument filedto the classification planAmount?> $5,000≤ $5,000No answer after 48 hreminder, then delegation

Decisions on conditions

An amount, a case type, a date: the gateway compares and picks what happens next. Nobody has to remember the rule, because the rule is in the diagram.

Escalation and delegation

A task left sitting triggers a reminder, then moves to the manager or the designated delegate. One person’s absence no longer parks a case for two weeks.

Documents created and filed

Letters, acknowledgements and decisions are produced from your templates, then added to the right record with their retention schedule.

See unified content management

OUR KEY FIGURES

Less waiting.
Fewer follow-ups by hand.

A case spends most of its life waiting for somebody to notice it. Automating the handoffs is, above all, removing those queues between two steps.

Figures published by Constellio
01

0

Reduction in search time

02

0

Reduction in search costs

03

0

Reduction in security incidents

Why choose Constellio

Time saved

Handoffs are instant: a finished step opens the next one instead of waiting its turn in somebody’s inbox.

Optimization

Complex processes get simpler where the measurements show the time is lost, not where it is assumed to be.

Productivity

Teams handle cases instead of chasing approvals, missing documents and reminders.

Lower costs

Less data entry, less rework, fewer cases starting over because a document was lost between two departments.

Organizations running on Constellio

  • Rio Tinto
  • Ville de Montréal
  • Université Laval
  • Bibliothèque et Archives nationales du Québec
  • Hydro-Québec
  • CDPQ
  • Barreau du Québec
  • Ville de Longueuil

YOUR FIRST PROCESS

Unlock the potential
of your content.

Book a demo and bring the process that costs you the most. We draw it with you, and you see it running before the meeting is over.

Or write to contact@constellio.com. Open source at its core, hosted the way you want it.