See at a Glance Where Every Ringi Is Stuck

A sales manager files a 12-million-yen quotation on a Monday. By Friday she still does not know where it is. Did the department head see it? Is it on the executive desk? Is it lost in someone's inbox while they travel? She does what every requester does. She sends a polite email asking whether the approval has moved. Then she sends another. Then she walks down the hall to ask in person. Multiply that by hundreds of requests across a company, and a quiet, expensive behavior takes hold. The organization spends more energy chasing approvals than running them.

This is the real shape of the problem behind approval workflows in Japan. The request itself is rarely the hard part. The hard part is that, once submitted, a request becomes a black box. Nobody can see who has it, who is next, or how long it has been sitting. The company cannot even name its own bottleneck. This post walks through how a core business system fixes that by making every approval step visible in real time, letting stakeholders follow a request without being approvers, and turning silent delay into a named, measurable bottleneck.

Why "Where Is My Request?" Is the Wrong Question to Have to Ask

The phrase itself is a symptom. In a healthy approval flow, the requester never needs to ask, because the status is one click away. In a paper or email flow, the status exists nowhere. It lives in the memory of whoever happens to hold the folder, and it dies the moment that person travels, takes leave, or simply forgets.

The cost of that invisibility is larger than it looks. First, there is the requester's time. Every "is it done yet?" email is a small interruption, and across a manufacturer running hundreds of approval workflows a month, those interruptions add up to real hours of lost engineering and sales capacity. Second, there is opportunity cost. A quotation that sits unstamped for nine days is a quotation a competitor can undercut. A purchase order that waits on a traveling manager is a machine that ships late. Third, there is the corrosive effect on trust. When staff cannot see the system working, they stop believing it works and route around it through chat and side channels. The approval workflow, in name only, no longer reflects what the company decided.

The data backs this up. A 2025 SIOS report found that roughly 40 percent of companies that adopted a workflow tool are still stuck at "electronified paper ringi." They scanned the form and kept the invisibility. The approval still moves by the same word-of-mouth chase, only now by email. An atled survey found that 67.7 percent of companies use some kind of workflow system, yet the same research shows visibility into where a request sits remains one of the most widely reported unsolved pains. Adoption without visibility is not adoption. It is paper in a new folder.

What Real-Time Step Status Actually Means

The fix begins with a simple but radical idea: the approval is not done until every step is done, and the status of every step is visible the moment it changes. In a core business system, an approval workflow is not a folder passed from desk to desk. It is a sequence of steps, each with an owner, a state, and a timestamp.

The states are concrete. A step can be pending (waiting for its approver), in progress (the approver has opened the request), approved, rejected, or sent back for revision. Each transition is recorded with who acted and when. The requester does not need to email anyone, because the screen already says "step 3 of 5, currently with the plant manager, opened Tuesday at 9:14." That single line removes most of the chasing email an organization generates.

This is not a spreadsheet someone updates by hand, which is only as current as the last person who remembered to edit it. Real-time step status in an ERP updates itself, because the workflow engine is the thing executing the approval. When the manager approves, the next owner is notified, the status flips, and the requester sees the change without doing anything. The truth and the display are the same object.

Watchers: Following a Request Without Being an Approver

Visibility for the requester solves one problem. There is a second, less obvious one most systems miss. A large approval often concerns people who are not approvers. The finance lead cares whether the capital expenditure clears, because they must plan the cash. The project manager cares whether the purchase order lands, because it gates their schedule. The audit team cares whether the big contract was countersigned, because they must prove it later.

In a paper or email flow, those people have no legitimate way to follow the request without becoming noise. They cc themselves onto every thread, which pollutes the approver's inbox, or they ask the requester for updates, recreating the exact chasing the system was supposed to eliminate. Stakeholders either over-communicate or lose sight of the request.

The watcher solves this cleanly. A watcher receives the same status updates as the requester and the approvers, but has no authority to approve or reject. They see the request move through its steps and when it stalls. They do not appear in the approval chain, so they cannot block it and add no signature requirement. The finance lead becomes a watcher on the capital expenditure and simply knows, without asking anyone, the morning it clears. The project manager becomes a watcher on the purchase order and stops interrupting purchasing. The audit team becomes a watcher on the large contract and inherits a clean history without requesting it later.

This turns approval visibility from a feature for the requester into a feature for the whole organization, letting the right people stay informed at zero interruption cost to the people doing the work.

The Bottleneck Becomes Visible, and Therefore Fixable

When every step carries a timestamp, the company can finally answer the question that paper made unanswerable: who, exactly, is the bottleneck?

In most organizations, the answer is a surprise. Staff assume it is the busiest executive, or the most senior approver, or the department with the most requests. Often it is none of those. It is one specific role where requests consistently sit for days, perhaps because that person travels, perhaps because they were never given a clear service-level expectation, perhaps because the routing sends them requests they should never have seen.

A core business system surfaces this without anyone running a study. The workflow engine already records how long each step takes. Aggregated across hundreds of requests, the pattern emerges on its own. Step 4 of the capital expenditure flow averages 6 days. Step 2 of the quotation flow averages 11 hours. The conversation shifts from "approvals are slow" to a specific, named, fixable problem.

The fixes follow the data. If a single role is the consistent holdup, add a delegate so approvals do not freeze when that person is out, with a mandatory re-approval for high-risk items so the safeguard holds. If the holdup is structural, change the routing so the request reaches the right desk faster. If it is volume, split the load or raise a threshold so small requests no longer climb to the top. None of these are possible while the bottleneck is invisible. All become obvious once the timestamps sit in one place.

A Scenario: The Precision Parts Maker in Shizuoka

Picture a precision parts manufacturer in Shizuoka, about 280 staff, supplying automotive and industrial machinery OEMs from a head office in Tokyo and a plant in Shizuoka. Before their core business system, their approval workflows ran on paper and the hanko stamp. A capital expenditure request for a new machining center would leave the plant manager's desk, travel by internal mail to the head office, sit in an executive's inbox while that executive was on a customer visit, and return a week or two later with no one able to say where the time had gone.

After moving their approval workflows into one ERP, the picture changes. The same capital expenditure is filed electronically and routed automatically to the right roles by amount and department. The plant manager sees a live status line: the request is on step 3 of 5, with the chief financial officer, opened at 8:50 this morning. The finance lead, who must plan the cash for the machine, is a watcher. She receives the same updates without appearing in the approval chain, so she stops emailing the requester and interrupting the executive.

When the executive travels, the request does not freeze. A delegate keeps the flow moving, with a mandatory re-approval for the high-risk portion so the control holds. Over the first quarter, the timestamps reveal something the company had never been able to prove. The bottleneck was not the executive at all. It was a single mid-level role where requests sat for five days because that person also ran a production line and only checked approvals once a day. With that named, the company added a delegate for travel days and set a clear step-turnaround expectation. Average approval time across the company dropped from over a week to under two business days, and the chasing email fell to almost nothing, because there was nothing left to chase.

Why This Matters Beyond Speed

The benefit is not only faster approvals, though the speed is real. A core business system that makes every step visible does three things a paper process cannot.

It restores trust. When staff can see their request moving, they stop routing around the workflow through chat and side conversations. The approval flow becomes the single source of truth for what the company decided.

It builds the audit trail as a byproduct. Every status change, approval, and delegation is timestamped and attached to the request. For a company thinking about J-SOX or internal control, the records an auditor wants are generated by the act of running the approval, not assembled after the fact.

It turns governance from a guess into a measurement. The company that can name its bottleneck can fix it. Visibility converts approval management from folklore into operations.

Frequently Asked Questions

Does real-time status mean staff are micromanaged on every approval?

No, and that is a reasonable concern. The point of step status is not to surveil approvers but to remove the need for requesters to chase. Most companies surface status only to the requester, the watchers, and the people in the approval chain. The bottleneck data is reviewed in aggregate and used to fix routing and add delegation, not to penalize a busy approver. Visibility reduces pressure on approvers, because it ends the interruptions.

What happens when an approver is out of the office?

The workflow does not stop. A delegate can be assigned so approvals keep moving during travel or leave. For high-risk items, a mandatory re-approval can be required when the primary approver returns, so the safeguard holds. A single person's calendar no longer gates the whole company. This is built now, not a roadmap promise.

Can stakeholders follow a request without adding an approval step?

Yes, that is exactly what the watcher is for. A watcher receives status updates and sees the request's progress, but is not in the approval chain. They cannot approve, reject, or block. The approval count and the watcher count are separate, so adding ten watchers adds zero signatures.

Will this work if we are not ready to connect approvals to our records yet?

Yes. The workflow engine can be deployed standalone first, with no dependency on the rest of the ERP. Many companies start by digitizing their approval flows and proving the visibility and speed gains, then expand later. Real-time status, watchers, and bottleneck reporting all work standalone. Automatic writeback of certain approvals into core business records is on the roadmap, a separate additive step, not a prerequisite for the visibility described here.

Key Takeaway

The question "where is my request?" should never have to be asked. A core business system makes every approval step visible in real time, gives stakeholders a way to follow a request without becoming approvers, and turns silent delay into a named, fixable bottleneck. When those three live together, chasing email disappears, approvals stop freezing when one person travels, and the company can finally see and improve the approval machine it has been running blind.

Get Started With Kikan System

If your requesters spend more time chasing approvals than the approvals themselves take, look at Kikan System. The approval workflow module shows the live status of every step, adds watchers so stakeholders follow without approving, and reports on bottlenecks so you can fix them by name. Start on the free plan with up to 2 users, no credit card required. Begin at /#get-started, and see the full catalog of manufacturer approval workflows in our workflow ROI overview.