Leaders won't live in your procurement portal because their working day runs in email, on a phone, between meetings. A portal asks them to log in, find their way and hunt for the one decision waiting on them. So approvals stall, or happen in chat with no record. The fix is to bring the decision to the inbox, with a secure link that works once.
This is not a training problem, and it is not a sign that your leaders do not care about process. It is a design problem, and it is one of the most common reasons procurement software gets bypassed.
What actually happens when the approver is not in the portal?
The same story plays out in most procurement teams. The evaluation is done, the recommendation is ready, and the award needs one senior signature. Then:
- The decision waits. The approver is travelling, the portal notification is buried under forty other emails, and the password has expired since the last time.
- The decision moves to chat. Someone sends a message: "Can I go ahead with supplier B?" A thumbs-up comes back. The award goes out.
- The record has a hole. The system shows an award with no approval, or an approval clicked later by someone else on the leader's behalf. When the auditor asks who decided and why, the answer is a screenshot.
- The tool gets blamed. Buyers learn that the portal slows things down, so they route around it. Adoption falls, and the next software review asks why nobody uses what was bought.
Each step is reasonable on its own. Together they turn a controlled process into an informal one, at exactly the point where control matters most.
Why doesn't training fix it?
Because the problem is frequency, not skill. A buyer uses a procurement system every day. A business head or CFO might approve something twice a week. A portal built for daily users is full of menus, filters and dashboards. For someone who visits occasionally, every visit starts with remembering how it works.
Leaders already have a tool they open a hundred times a day: their inbox. Any design that asks them to leave it, for a two-second decision, loses to the path of least resistance.
What should a leader get instead?
The decision should arrive where the leader already is, with enough context to decide without opening anything else.
- One email per decision. What is being approved, the amount, who asked, and the recommendation, in the body of the email.
- One tap to decide, on a phone. Approve, reject or send back, with a comment. No login, no app to install.
- Replies that count. A reply to the email is recorded on the event as that person's remark, not lost in one inbox.
- Status without asking. For leaders who want to know where things stand, a control room shows who has evaluated, what is pending and what is late, without anyone preparing a file.
The portal does not disappear. It becomes the place where work is prepared, not the only place work can be completed.
Isn't approving from email insecure?
It can be, if it is done carelessly. Done properly, it is safer than the chat message it replaces. The standard we build to:
- A signed one-time link. It is meant for one person and one decision, works once, and expires in 72 hours.
- Nothing is approved by accident. A decision needs a deliberate tap from the approver, never just an opened email.
- Every action on the audit trail. The decision is logged with the channel it came from, so an auditor sees an email approval as clearly as a portal one.
- Stricter rules for confidential work. For sensitive events, an organisation can tighten the rules or turn email actions off.
The demo walks through the whole flow on a phone.
Does this change who is accountable?
No. It makes accountability easier to prove. The approval is the same whether a leader decides in the portal or from the email: the same chain, the same approvers, the same comments. What changes is that the decision is recorded at the moment it is made, by the person who made it.
For a CPO, that is the difference between an audit trail with holes and one without. Our page for CPOs walks through a week of it.
What is live in iProcure today?
We are pre-launch, and we label everything honestly.
- Live: approve, reject and comment from a signed one-time email link that expires in 72 hours; one approval queue across modules, so an intake request and an RFx award land in the same queue.
- Demo on sample data: the event control room, showing what is waiting on whom.
- Roadmap: an AI summary in the approval email, and approvals through Teams and Slack.
How do you know if this is your problem?
Ask three questions about your last few awards. How long did the final approval take? Where did it happen? Could you show an auditor the record today? If the answers are "days", "chat" and "not really", your leaders are not living in your portal either.
Take the RFx Health Check to see what else is leaking, or see the approval email live in 10 minutes. The approval moment is the first thing we show, because it is the one every leader notices.