A walk through
Every screen below is the real product, photographed from a sample workspace belonging to a fictional fit-out contractor. Nothing here is a drawing.
Step one
A site engineer opens AxisFlow and raises a purchase request: what it is, how much of it, which project and cost centre it belongs to, and why. The quotations go on with it — that can be made compulsory, and on most sites it should be.
Step two
At the moment it is submitted, every rule for that kind of document is tested in order and the steps of the ones that match are strung together. Here three rules fired: the cost-centre owner sees everything, anything above a hundred thousand climbs the management line to somebody whose limit covers it, and above a million finance has to see it too.
That chain is then frozen onto the document. Edit the rule next week and next week's requests change; this one keeps the chain it was given.
Step three
A rule is a set of conditions and a set of steps, written on one screen in language you would use out loud. You can test one against a figure before turning it on, and see the chain it would produce.
Value including tax, project, cost centre, supplier, category, location, who raised it, or whether the budget would be exceeded. Combine as many as you like.
A named person · anyone in a group · the cost-centre owner · the project manager · the requester's own manager · the whole management line · or up the line until somebody's approval limit covers the value.
Rules are tested in an order you set, and any rule can be marked “stop here” so the ones below it never run. Duplicated people are collapsed; nobody is asked twice.
Step four
The approver gets an email and a line in their inbox. The value, the justification, the attachments and the budget position are all on the screen with the button, so there is nothing to go and check first.
Step five and six
An approved request becomes a purchase order, carrying its lines and its supplier across. When the goods turn up, whoever received them says what actually arrived, in full or in part. When the invoice comes in, AxisFlow compares all three.
The tolerance is a percentage and a floor, so small rounding differences pass and a five per cent overrun on twenty million does not.
And afterwards
Not a chart library — seven views, each named after the question it answers, and every one exportable to a spreadsheet.
Everything waiting, oldest first, with the days on it.
By person — who is the bottleneck this month.
Requested, committed and spent against each one.
Time from submitted to decided, by kind and by person.
Setting up
The management line is what makes “climb until somebody can sign for it” work, so it is worth ten minutes. Give each person a manager and an approval limit, put them in the groups that describe their job, and the rules do the rest.
On a phone
The same screens, laid out for a phone — not a separate app to install and not a cut-down version. An approver can read the justification, open the quotation and approve from the car park.
There is nothing to download. It is a web address.
Signing up takes a minute and the free plan does not expire. Put one project in and raise one request — you will know within the hour whether it suits you.