Describe the workflow the way you'd brief a new hire
“When someone asks for leave, check it against our policy, ask the HR manager, then email them the answer.” Portus turns that into a map of steps, tries it on sample requests, and waits for you to switch it on.
It asks before it builds
If the sentence leaves something open, such as who approves or what sick leave needs, the builder asks you.
Then it writes down what the workflow must do. As it builds, each line shows whether it is planned, written and practised.
It practises on sample requests first
Before it saves the draft, Portus writes sample requests and runs the workflow on each one.
Each practice is a run you can open and read step by step. The ones that went as expected stay with the workflow as its checks.
Change it by asking the co-pilot
Type the change you want, such as “ask the line manager before HR”. The co-pilot shows each step it adds or removes on the map, and nothing changes until you press Keep changes.
Or change it by hand
Add a step on any line of the map, or pick a step to set who decides, what they are shown, how long it waits and when to remind them.
Add a step that sends something and an approval goes in before it, so nothing leaves without a click.
It goes live when you say so
Changes save as a new draft version. It goes live only when someone allowed to make workflows live promotes it.
The version before stays on record, and you can see what changed between any two.
- Request leave as your team runs it today: the policy check, then the HR manager.
- Added: Line manager approves the leave
- Changed: Approve the leave now waits for the line manager first
Bring one workflow your team runs every week
On the call we build it in Portus with you, in Arabic or English.
Or write toinfo@portusai.co