Definition
A ringi-sho (稟議書) is a formal proposal-and-approval document circulated through an organization so that every relevant department can review, raise objections, and stamp their seal of approval before a project or expenditure proceeds. The process built around it — ringiseido (稟議制度) — is a standard feature of Japanese corporate and government organizations, not a Toyota invention.
At Toyota the ringi-sho served as the primary mechanism for capital project approval, policy changes, and any cross-functional decision of significance. It functioned as a written complement to nemawashi: where nemawashi builds informal alignment through conversation, the ringi-sho creates a formal, documented record of that consensus with explicit sign-off from every affected party.
Japanese Origin
The word 稟議 (ringi) combines 稟 (rin) — to submit a proposal to superiors for approval — and 議 (gi) — deliberation, discussion. The suffix 書 (sho) means “document” or “written record.” Together: a document submitted for deliberative approval.
The ringi system predates Toyota and is deeply rooted in Japanese organizational culture, particularly in government bureaucracies where formal documentation of consensus is required. It reflects the broader Japanese preference for stakeholder alignment over unilateral top-down decision-making. Any Japanese person working in a large organization — government or corporate — would recognize the ringi-sho as a routine part of working life.
How Toyota Used It
The ringi-sho process at Toyota was practical, not ceremonial. Based on firsthand accounts from Toyota managers:
Capital and project approval — Retired Toyota engineering manager Mike Johnson described the ringi-sho as “basically the Toyota term for a combination appropriation and project approval document.” It provided the project purpose, goal, benefit, financial justification including payback period, cost-per-unit impact, and implementation schedule. Ringi-sho documents were required for all capital items or projects costing more than $5,000. Approval levels scaled with cost — general managers could approve up to $50,000; larger projects went up to the president.
Cross-functional sign-off — Every ringi required sign-off from affected departments before proceeding. Projects affecting emissions needed environmental section approval. Safety-related projects required safety section sign-off. This cross-functional review prevented problems that arise when one department acts without consulting others — a structural mechanism for catching issues early rather than fixing them after the fact.
Annual plan integration — Projects had to be part of the annual capital plan, or substituted for one already in it. Monthly reporting on ringi submission and approval status ran from each shop all the way up to the president. In later years, the tracking system even prevented overspending by blocking purchase order processing when a ringi’s budget limit (amount plus 10%) was reached.
The most elaborate ringi-sho documents were written for model change and capacity increase projects — providing upper management with both the technical and financial information needed to make sound decisions.
Relationship to Nemawashi and A3
The ringi-sho does not exist in isolation. It is one element in a connected system of communication and decision-making:
Nemawashi → Ringi-sho → Decision meeting. Retired Toyota Vice President Russ Scaffede described the flow: “We would write the A3 and identify all parties who needed to sign off or return with questions.” The ringi-sho was circulated before the formal decision meeting with the president, ensuring all questions were answered and consensus was built in advance. The meeting itself became a confirmation rather than a debate.
Scaffede called the ringi-sho “a written form of nemawashi or consensus building in the organization.” It was not used as permission or approval in itself — rather as a notification process to ensure everyone who would be in the approval meeting had reviewed the proposal, understood it, and had their questions addressed beforehand.
Connection to A3 — At Toyota, the ringi-sho and the A3 report served complementary purposes. The A3 presented the analysis, problem-solving thinking, and proposed action. The ringi-sho formalized the approval routing and cross-functional sign-off. In practice the two were often prepared together for significant decisions.
Why Toyota Found It Valuable
A senior Toyota manager emphasized that the real value of the ringi-sho system went beyond communication and documentation. The deeper purpose was personnel development — improving staff communication skills, problem-solving skills, and certain forms of leadership. Writing a clear, persuasive ringi-sho that anticipates objections and addresses every stakeholder’s concerns is itself a developmental exercise.
The system also enforced discipline: it required proposers to think through financial justification, cross-functional impact, and implementation scheduling before requesting resources — not after.
Common Mistakes
Treating it as a magic process to copy. The ringi-sho is a formal document routing process, not a competitive advantage. As one retired Toyota manager cautioned, no one should adopt a process simply because another group practices it — copying is not a legitimate form of problem solving or improving. Without critical thinking skills, a ringi-sho process may not deliver much return on the time invested.
Adopting the form without the culture. The ringi-sho works at Toyota because it operates within a broader system that includes nemawashi, A3 thinking, hoshin kanri, and a deep respect for cross-functional alignment. Implementing a circulation-approval document in an organization that lacks these supporting practices produces paperwork, not consensus.
Confusing it with Toyota-specific innovation. The ringi-sho is common across Japanese companies and government agencies. It is not part of the Toyota Production System in the way that kanban, andon, or standardized work are. Understanding its role at Toyota requires recognizing it as a general Japanese management practice that Toyota adapted effectively — not as a proprietary Toyota tool.
Falling prey to Japanese buzzwords. There is a tendency in the Lean community to elevate Japanese terms into something more than they are. As with any management practice, the question should always be: what problem are we trying to solve? Starting from “should we adopt ringi-sho?” rather than “what communication and approval problems do we have?” inverts the logic of improvement.