Parsware
All articles

Capital Planning

Decided, and written down

The second van has been ordered. Thirty thousand pounds. Who said yes? Here are three requests decided, with a row left behind for every decision: who, when, at what level, and what they said.

A bright blue card reading "£30,000. Who said yes?" beside a screenshot of a list of decisions, each naming who decided, at what level and with what outcome.

The second van has been ordered. Thirty thousand pounds. Who said yes?

In most companies, the yes is a word in a corridor, a line in a group chat, and a note from a meeting. And a year later, nobody can find it.

Here is the same thing on Parsware, in a demonstration company of forty people. Three requests from the warehouse are waiting for the finance director. Nobody forwarded them.

The finance director's inbox, holding three requests to decide.

Four choices, and a note

The first is a forklift battery, at £8,500. Opening it shows the whole request, with the decision beside it. There are four choices:

Choice What happens next
Approve It's approved, and the budget is charged. If it's over the top limit, it goes on to the investment group first
Send to the investment group The group decides, whatever the amount
Return for more detail It goes back marked Returned, with the note saying what's missing
Reject It's turned down, with the note saying why

The forklift battery request open, with the decision panel offering Approve, Send to the investment group, Return for more detail and Reject.

This one they approve, with a note saying why.

The second is pallet racking, for £12,000. Something's missing, so it goes back, and the note says what: Which supplier, and is fitting included?

The pallet racking request open, with the question typed into the comment box.

Over the top limit, one yes isn't the last word

The third is the van, for £30,000. That's over the top limit, so the finance director's yes isn't the last word. They approve it with a note, and it goes on.

The van's request open, with the finance director's note typed in, ready to approve.

Now it's waiting for a member of the investment group. They get the request on one page, to read, with nothing to change. They agree, and they say so.

The request for approval as a one-page report: the reference, the second delivery van, the department, the category, the level and £30,000.

A row for every decision

Here is what all of that left behind. Each decision has its own row, and the van has two: the finance director's yes, then the group's.

The approval history, with the investment group's and the finance director's approvals of the van at the top, then the racking and the battery.

Open one, and there it is. Who decided, on what day, at what level, and what they said.

One decision opened: Sam Taylor, the finance director, approved the van on the day, and the comment reads "Agreed, if it covers the spring rounds."

And the racking says Returned, with the question that was asked.

The history's comment column, showing each person's note, including "Which supplier, and is fitting included?" against the racking.

The warehouse manager can see where each one got to on their own list, without asking anybody.

The warehouse manager's list of requests: the battery Approved, the racking Returned, and the van Approved.

What it means for you

  • Every decision is written down as it's made, with the name of the person who made it and their own words.
  • When a request needs two people, both of them are there.
  • A year from now, when somebody asks who said yes, you look it up.

Tell us how your business runs, and we'll show it to you running on Parsware: parsware.com/contact.