How to document a cost reduction project so other people trust it

This is the starting point. It does not teach costing for a specific industry — the industry guides do that — it answers the question that comes first: **how do you record a cost reduction project so that a year from now somebody else can reuse it, and so that your customer believes it**.

This is where most shop floor improvements die. The work was done, the money was genuinely saved, but the record lives in one engineer's head and in one spreadsheet on that engineer's laptop. The engineer moves to another plant, the file gets renamed, and two years later somebody solves the same problem from scratch.

What Costdown does that a spreadsheet cannot

Excel does a great many things well, and wherever Excel is enough, that is not a reason to leave Excel. Only five things are genuinely out of its reach, and all five involve a second person:

• A shared library — processes, machines and materials carry standard codes, so two people describing the same operation use the same code and their numbers line up.
• Other plants' data — you see the savings achieved by projects in your industry and your country, without seeing their unit costs.
• Counterpart verification — the other side of the project confirms it, and the trust level changes because that evidence exists, not because you claimed it.
• Change history — every change to an amount, a status or a permission records the old value, the new value, who changed it and when.
• One formula — every project is calculated the same way, so two projects are comparable; in Excel every file is its own formula.

Four steps to record a project

1. Pick the industry and the processes first, type numbers second

Once the industry is set, the process, machine and material lists narrow down to what that industry actually uses. This is not a decorative step: the codes you pick here decide whether your project is ever found and ever compared.

Two rows describing the same operation in different free text — TIG welding SUS304 and welding 2 mm stainless — will never line up with each other. The same code will.

2. Break down the cost structure, including the fields you have no number for

Cover every cost item in the production sequence of your industry. Where you have no number yet, leave the field empty. Do not type 0.

The guide on the six fields everyone leaves blank lists the items that drop out most often, and which direction each one skews the result.

3. Record the improvement as before, after and investment

An improvement needs three anchors: the current state, the state after the change, and the money spent getting from one to the other. With all three present, the system derives the saving and the payback period using the same formula it applies to every other project.

Before you report that number as money saved, read the guide on whether the saving is real. An improvement that is not at the bottleneck usually releases no cash at all, and that is the fastest way to lose credibility when finance goes to reconcile it.

4. Invite the other side to verify

A cost reduction project almost always has two sides: a plant and its customer, or a plant and its supplier. Until the other side confirms it, the number is a one-sided claim.

This is why Costdown cannot deliver its full value to one person working alone. It is not a referral gimmick — verification needs a real counterpart, and benchmarking needs colleagues in the same country.

Four trust levels, and who decides them

The trust level is not a label you choose. The system recomputes it from what is actually in the record:

Ranking reads this level before any count. The number of entries you have posted is never a criterion, not even a tie-breaker. Posting more does not make your numbers more credible; having someone verify them does.

Comparing against other plants, and the limits of that

Benchmarking compares only within one country, and it measures percentage saved and payback in months, never absolute currency amounts.

The reason is practical: a project saving 30 percent in Vietnam and a project saving 30 percent in Japan are comparable. The same absolute amount in those two countries describes two completely different scales, and a direct comparison would simply hand the win to the larger number for reasons that have nothing to do with the quality of the improvement.

Reusing a project that has already been proven

When you find a proven project in your industry, you apply it to your own plant. What gets copied across is the structure: the cost items they broke out, the processes they touched, how they measured before and after.

The numbers do not, and that is deliberate. Their numbers are their data, measured on their machines, at their material prices. Copying them produces a spreadsheet that is neat and wrong. Copying the structure tells you what you need to go and measure — which is the hard part of starting.

Where to start when you have nothing yet

Start with one product line you know best, not with the whole plant. Break down its cost using your industry's guide in the left menu, leave the fields you have no number for empty, then go find those numbers in order of how much each one moves the total.

One thoroughly documented project is worth far more than ten sketchy ones — to you, and to the trust level of your record.