The procurement decision list: one place for approvals
A decision list is one list of everything in procurement that waits for a person, meaning approvals, reviews and choices, each with what to do, by when and what it is worth. It keeps three kinds of thing apart. Decide is what waits for a person in the organisation. Waiting is what waits for someone outside, such as an employee, a supplier or a vendor. Automatic is what the system did or will do without a click. The list is ordered by deadline first and worth second, the worth of a decision is copied from the finding or the offer behind it, and unverified figures are shown without being added up.
A procurement decision list puts everything that waits for a person in one place: the campaign to approve, the offer to confirm, the message to a supplier, the form an agent has filled in. Each row says what you do, by when and what it is worth. The list works when it separates three kinds of thing that most tools mix: what you decide, what you wait for and what happens automatically.
Why one list
A system that prepares work produces approvals in many places: in licences, in invoices, in sourcing, in the mailbox. If each of them announces itself with a banner on its own page or a mail of its own, the approvals turn into noise, and the one with a notice date next Tuesday sits behind a tab nobody opened. One list is the condition under which human approval stays a check when the number of prepared steps grows.
Three kinds of thing
| Kind | What it is | What the row shows |
|---|---|---|
| Decide | Something waits for a person: an approval, a review, a choice | One button that says what you do, and the worth |
| Waiting | Something waits for someone outside: an employee, a supplier, a vendor, an agent at work | The date on which the system acts next |
| Automatic | Something the system did or will do without a click | A line in the audit trail |
The three must never look alike. A reminder that goes out by itself on Thursday and a message that stays where it is until you approve it mean opposite things for the reader. If both appear as "pending", people either approve things twice or wait for things that wait for them.
What belongs on the list
- Drafts to approve. A campaign of questions to seat holders, a message to a supplier or a vendor, a follow-up.
- Prepared steps. A change at a vendor, a task for an agent, a filled-in form whose submit has to be confirmed.
- Things to confirm. An offer a model read from a reply, invoices read from PDFs, researched prices that nobody has verified.
- Choices. A sourcing event with offers on the table, a proposal for a request for quotation.
- Things that came back. A reply nobody has read, a conversation that stayed silent after the last follow-up, a mail that bounced, a seat holder who did not answer and has no manager to ask.
- Things that broke. A connection to a vendor or a mailbox that stopped working.
- Findings without a next step yet.
A finding appears once. When its next step is already on the list as a draft, a prepared step or a conversation, that row stands for it.
Order: deadline first, worth second
- What is overdue.
- What is due within two weeks, by date.
- Everything else by worth, highest first.
- Among equals, the oldest first.
Two additions keep the list honest. A finding with a deadline in the near future, such as the notice date of a contract within the next sixty days, gets a row of its own whatever it is worth, because a missed notice date usually binds the organisation for another term. See preparing a SaaS renewal. And the many small findings are summed in one row, so that they do not push the large ones off the first screen.
What a decision is worth
The worth of a row is a figure from somewhere else, and the list must not make up a new one.
- Copied, with its origin. The saving of the finding, or the saving of the lowest complete offer, with a note saying whose figure it is.
- None where none exists. A request for quotation has no figure until offers arrive, and says so.
- Each figure once. A campaign draft and a prepared step of the same finding share its figure.
- Unverified apart. A figure that rests on an unverified price is shown and not added to the total.
- Once and yearly apart. A refund is recovered once, a lower price recurs.
An example with invented figures:
| Decision | Worth | Whose figure |
|---|---|---|
| Approve the questions to 6 seat holders | 2,160.00 a year | The finding's saving |
| Award a sourcing event | 9,600.00 a year | The lowest complete offer |
| Reclaim a duplicate invoice | 1,190.00 once | The finding's amount |
| Change a plan, list price unverified | 1,200.00 a year, unverified | The finding's saving |
| Approve a proposed request for quotation | None | Nobody has quoted |
The list is worth 11,760.00 a year and 1,190.00 once. The unverified 1,200.00 is shown next to that and is not part of either sum. How figures move from this list to a result that finance accepts is described in proving procurement savings.
What goes wrong
- One total for everything. Yearly, one-off and unverified amounts in one sum give a number nobody can defend.
- Waiting shown as a task. A person opens a row and finds there is nothing to do until the supplier answers.
- Everything is urgent. Without real deadlines the order becomes whoever shouted last.
- Decisions for the wrong person. Someone who may not send to suppliers sees a send button that refuses them.
- A list next to banners. If pages still announce their own approvals, people stop trusting the list to be complete.
How Cureman does it
Cureman builds one list of decisions and uses it for the overview, the decisions page, the count in the sidebar and the digest mail. Decide, waiting and automatic have a look of their own everywhere in the interface: a solid tag for what a person decides, an outlined one for what is waited for, a dashed one for what the system did. The order is overdue, then due within two weeks by date, then by worth, then oldest first; a finding with a deadline within sixty days gets a row whatever it is worth, and the smaller findings are summed in one row. Worth is copied from the finding or from the lowest complete offer with a note saying whose figure it is, each figure counts once, unverified figures are shown and not added up, and amounts recovered once are summed apart from yearly ones. What the autopilot prepared appears marked as prepared, and a proposal of the buyer appears without a worth. A conversation with a supplier that stays silent after its follow-ups comes back to the list as unanswered. Each decision names the permission it needs, so people see what they may decide and a count of what waits for other roles. The rules behind this are on the page about principles, and how it works describes the daily work around it.
Questions and answers
What is a decision list in procurement?
- It is a single list of every item that needs a person's approval, review or choice, across licences, invoices and sourcing. Each row says what to do, by when and what it is worth. It replaces banners on individual pages and notification mails from separate tools.
How should procurement decisions be prioritised?
- By deadline first and worth second. Overdue items come first, then items due within the next two weeks by date, then the rest by worth, and among equals the oldest. An item with a contractual date, such as the notice date of a renewal, keeps a row of its own whatever it is worth.
What is the difference between decide, waiting and automatic?
- Decide means something waits for a person inside the organisation. Waiting means the next move is with someone outside, such as a supplier who was asked for an offer, and the list shows when the system acts next. Automatic means the system did or will do something without a click, which is possible only for steps that were approved before.
Where does the worth of a decision come from?
- It is copied from the figure behind the decision, which is the saving of the finding it belongs to or the saving of the lowest complete offer in a comparison. The row says whose figure it is. A decision without such a figure, for example a proposed request for quotation, shows none.
Who sees which decisions in Cureman?
- Each decision in Cureman names the permission it needs. People see what they may decide, and a count of what waits for other roles. A digest mail lists each member's decisions weekly or daily, is not sent when nothing waits, and leaves out figures for people who may not see them.