Purchase request
Request → department manager → budget owner. Budget code and justification are mandatory before submitting for approval; rejection requires choosing from a list of reasons.
Build approval workflows without writing code.
Purchase requests, leave and expenses, corrective actions, contract approval… These processes work a little differently in every company. In MitosOne you define, from the interface, who approves at which stage and under what condition, which fields are mandatory, and what happens after approval.
Examples of processes built on the platform
These are not ready-made templates; each is built from the same building blocks, using your company’s rules.
Leave and expenses
An employee’s request goes to their manager; expenses above an amount limit go for additional approval. Business-day calculations use the public holiday calendar.
Corrective action (CAPA)
Non-conformity record, root cause, owner and due date; a reminder as the due date approaches, and a verification stage at closure.
Maintenance request
Requests raised from the field via the mobile interface, offline if needed; photo attachments and technician assignment.
Contract approval
Contracts that pass legal and finance approval; renewal reminders tied to the end date, and a PDF from a document template.
Recruitment
Stages from headcount request to candidate evaluation; the salary field is visible only to authorised roles.
The building blocks of an approval workflow
- Stages and transitions: for each transition, the authorised role, condition, fields mandatory at that stage, a list of reasons and a required comment.
- Segregation of duties: the person who created a record cannot approve it.
- Conditions that look at other records: rules such as “send the order for approval if the customer’s risk limit is exceeded” are written against the related record.
- Stage-based permissions: the records a person can see and change are narrowed down according to the stage.
- Notifications and reminders: in-app notifications, email and webhooks; reminders triggered by stage changes or by time.
- Workflow: on a visual canvas with 26 nodes — request approval, create/update record, generate document, send email and HTTP call steps; retries and a step-by-step run log.
- Traceability: how long a record waited at each stage, who moved it on, and with what reason it was sent back — tracked on a dashboard; every change is written to the audit log.
How is it set up?
01
Data structure
Define the request’s fields, relationships and calculated values — or start from an Excel file.
02
Stages and roles
Add the transitions, approving roles and mandatory fields; use “try as this person” to see in advance who will see what.
03
Test and go live
Try the change in a test environment; move the versioned configuration to production with approval, and roll it back if needed.
If you like, the AI-assisted setup assistant turns your description of the process into a plan; you approve every step. More details: automation and processes · security and permissions · What is MitosOne?
Let’s build one of your approval workflows in a demo.
Bring a process that runs on email or Excel today; we’ll build it on screen and leave it with you.