Skip to content
fig. 01 · features / workflows

Match your process, run by your own team.

Draw the states, actions, and transitions your process needs in a visual editor. Your document controller configures it, runs it, and changes it as the process changes. There is no implementation project and no consultant on retainer.

configured and run by your own team · minimal rollout

WORKFLOW EDITOR · AURORA WHARFfig. 01.1
document workflow · E-101states + transitions
CHANGES REQUESTEDDraftIn reviewApprovedIssued
audit trail
  1. Draft createdA. Chen09:14
  2. Submitted for reviewA. Chen11:02
  3. ApprovedR. Okafor14:32
  4. Issued for construction · REV CR. Okafor14:40
Draw states, actions, and transitions in a visual editor. Watch an approval step through, with every move written to the audit trail.
fig. 02 · the workflow editor

States, actions, and transitions, drawn by hand.

A workflow is the states a document moves through, the actions that move it, and who is allowed to perform each move. You wire all three on a canvas, so the workflow matches the process you already run.

  • Define the states a document moves through, from draft to issued.
  • Define the actions that move a document between states.
  • Set which role can perform each transition, so approvals stay controlled.
  • It is a visual editor. You wire states and transitions on a canvas, not in a config file.

states · actions · transitions · role-based transitions · visual editor

EDITOR · TRANSITION · IN REVIEW → APPROVEDfig. 02.1
workflow editor · canvasediting
In reviewApprovedAPPROVE
action
Approve
to state
Approved
performed by
Reviewer
actionsSubmitApproveRejectIssueArchive
Wire a transition between two states, then set the action that moves a document and the role allowed to perform it. It is a visual editor, with no config file to hand-write.
fig. 03 · running a workflow

Run one document, or the whole batch.

Move a single document through its workflow, or apply an action across a selection at once. Every move is recorded, so the record shows who did what, and when.

  • Run a workflow on a single document, step by step.
  • Batch-execute an action across a whole selection in one move.
  • Keep a full workflow audit trail on every document.
  • See documents pending approval, and run workflow reports across the repository.

single execution · batch execution · workflow audit trail · documents pending approval · workflow reports

RUN WORKFLOW · BATCH · 12 SELECTEDfig. 03.1
apply workflowIssue for construction12 documents
  • AW-EL-DR-0140Issued
  • AW-EL-DR-0141Issued
  • AW-ME-DR-0402Issued
  • AW-ST-DR-2001Issued
  • AW-AR-DR-1001Issued
12 of 12 issuedwritten to audit trail
Run a workflow on one document, or on a whole selection at once. Every document advances together, and each move is written to the audit trail.
fig. 04 · out of the box

Workflows ready to run, and reports to match.

Alongside the workflows you build, Lunr ships the everyday ones, and the reports that show where every document sits.

Archive and Un-Archive

Built-in workflows to retire a document from the working set and bring it back when it is needed.

Quick-Change

A built-in workflow for a fast, controlled change, with the approval still recorded.

Documents pending approval

A standing report of everything waiting on a sign-off, so nothing sits unseen.

Workflow reports

Report on where documents sit across your workflows, and export the result.

Document number request

A workflow to request a controlled number, with reviewers and assignment.

Notifications

Reviewers and approvers are notified at each step, so the next action is clear.

Workflows sit alongside automated document and version numbering, with sequence sets that keep every controlled number in order. See document control.

fig. 05 · run by your own team

Configured by the people who run it.

A document controller configures the workflow, runs it, and changes it when the process changes. There is no implementation partner to hire and no dedicated administrator role to fill. Rollout is minimal, and the system stays in the hands of your own team.

configured by
your own team
implementation
no project
changed
as the process changes
fig. 06 · questions

Questions teams ask about document workflows.

What a workflow is, who configures it, and how it runs.

01
What is a workflow in Lunr?
A workflow is the states a document moves through, the actions that move it between those states, and who is allowed to perform each move. You define the states, from draft to issued, the actions that move a document between them, and the role allowed to make each transition, so the workflow matches the process you already run.
02
Do I need a consultant or an implementation project to set up a workflow?
No. Your document controller draws the states, actions, and transitions in a visual editor, on a canvas rather than in a config file. They configure it, run it, and change it as the process changes. There is no implementation project to run, no consultant on retainer, and no dedicated administrator role to fill. Rollout is minimal.
03
Can I run a workflow across many documents at once?
Yes. Move a single document through its workflow step by step, or batch-execute an action across a whole selection in one move. Every move is recorded on a full workflow audit trail, so the record shows who did what, and when.
04
What workflows does Lunr ship with out of the box?
Alongside the workflows you build, Lunr ships the everyday ones: Archive and Un-Archive, Quick-Change for a fast controlled change, and a Document number request with reviewers and assignment. It also includes a Documents pending approval report, workflow reports that show where documents sit across the repository, and notifications to reviewers and approvers at each step.
05
Does Lunr support ISO 19650 states?
Yes. ISO 19650 moves each document through work in progress, shared, published, and archived. You run those states as configurable workflows, so a document advances only when the right person approves it, and the state and every transition sit on the audit trail. See the common data environment page for how the states fit together.
06
Can I control who is allowed to approve a document?
Yes. Set which role can perform each transition when you draw the workflow, so approvals stay controlled and a document advances only when the right person signs it off. Reviewers and approvers are notified at each step, and a Documents pending approval report shows everything waiting on a sign-off.
fig. 07 · get started

See the workflow match your process.

Book a walkthrough and we will wire a workflow to a process you run today, in the visual editor, in front of you.

10M+ documents under management · Hosted in Australia and the US · SAML · Full audit trail · Export anytime

entity
Lunr Labs Pty Ltd
location
Melbourne AU
workspace
documents.lunr.app
rev
2026