LogoSmall
Login

Why a Bar List Built in Excel Costs More

A bar list built in Excel costs almost nothing to fill in, but its errors carry over to the tags, the site and the invoice.

MBBy Maxime Beaupré · Updated on · 6 min

A bar list built in a spreadsheet costs more than it looks, because its cost doesn't show up where you fill it in. It gets paid further down the line, because the shop doesn't fabricate from the bar list but from the tags made from it: in hours of retyping and checking, in wrong tags, in bars produced twice or forgotten, in wrong weights that throw off the invoice, in lost revisions and extras, and in depending on the one person who understands the file.

For the definition, see what a rebar bar list is and the bar list section of the complete guide to rebar software. Here, we follow the money: where each error gets paid for, who pays it, and how to measure what your file costs you.

Why is this cost so hard to see?

Because it has no line in the books. The spreadsheet is already paid for, and nobody ever gets an invoice titled "spreadsheet error."

The cost lands somewhere else, with other people. The shop foreman sees it as bars to remake. The project manager sees it as a call from the site. Accounting sees it as a disputed invoice, or doesn't see it at all when the steel was never billed. Everyone deals with their own piece without connecting it to the others, and the whole thing ends up filed under "that's the trade."

And the further an error travels, the more it costs. A length typed wrong and caught in the office costs a few minutes. Carried onto the tags and caught at the shop before cutting, it costs a stoppage and a phone call. Caught after cutting, it costs the steel, the cutting and bending hours, and a slot in an already full production schedule. Caught on site, it costs a placing crew standing around, an extra delivery and a bit of the general contractor's trust. The spreadsheet doesn't create these errors; it just doesn't stop them.

What does retyping cost, even when it doesn't cause an error?

It costs time twice: the time to retype, then the time to check. A spreadsheet bar list is rarely the last place the information gets written down. The lines get copied again for the fabrication shop, for the tags, for the steel order, for the invoice. Every copy needs someone to type, and someone else, or the same person later, to proofread.

That proofreading is a real cost, even when it finds nothing: detailer or project manager time spent comparing columns instead of detailing. And proofreading done at the end of a busy day lets through the very errors it was supposed to catch.

There's also a skills cost. A spreadsheet doesn't transfer easily to the shop's machines. So someone has to read the bar list and know exactly how bars are measured, so that the bent bar matches the drawing. That knowledge exists in an experienced operator, much less in a new hire or the summer replacement. Every handoff between the detailers and production then becomes a chance for a costly mistake.

The tags are where the spreadsheet hits its limit. The bar list matters because the shop tags are made from it, and the shop fabricates from the tags. But a spreadsheet doesn't make barcode tags. It doesn't let you scan them in the shop or the yard, doesn't track truck loading and doesn't trace heat numbers. Whatever the spreadsheet doesn't do, someone redoes by hand, from drawing to invoicing.

How does a wrong weight turn into a wrong invoice?

By repeating itself quietly. The weight of a line comes from three numbers: the number of bars, the length and the mass per metre of the bar size. In a spreadsheet, that mass comes from a cell somebody filled in one day. If it's rounded, copied wrong or a formula points to the wrong row, every line that uses it is wrong. The file doesn't flag anything: a wrong number looks just like a right one.

Take a fictional example. A line of 200 bars of 15M (about a #5) at 6 metres is 1,200 metres of steel. The standard says 1.570 kg per metre. If the spreadsheet cell says 1.5, you're short 70 grams per metre, or 84 kg on that one line: the spreadsheet says 1,800 kg while you deliver 1,884. On nearly two tonnes, nobody notices 84 kg.

But the cell isn't used just once. If the project has 25 lines of 15M like that one, the 84 kg becomes 2,100 kg, more than two tonnes. And if your 20 projects for the year start from the same template, that's 42 tonnes of steel delivered over the year without ever showing up on an invoice. Nobody sees it, because the 1.5 is hidden in a cell nobody opens anymore. If the cell actually holds the mass of another size, say 10M at 0.785 kg per metre, the same line weighs only 942 kg instead of 1,884: half the steel disappears from the calculation. When invoicing is based on weight, which is common, the gap goes straight onto the invoice.

If it works against you, you deliver steel you don't bill for, and nobody notices. If it works in your favour, the client eventually compares the weights and the invoice gets disputed. Either way, the wrong weight was also used to order the steel and load the trucks. That's why the specifics of rebar (bar sizes, the standard masses per metre, bend shapes) have to come from a single correct source, not from a cell anyone can overwrite.

How do bars end up produced twice, or not at all?

Because a spreadsheet knows what's written, not what's been done. It doesn't know that one line has already been cut and bent, or that another is still waiting. Without barcode tags scanned at the shop and at loading, that tracking relies on a "done" column someone has to remember to fill in, or on the shop foreman's memory.

The accidents are ordinary: a block of lines pasted twice, a sort applied to a single column that shifts the lengths against the marks, a line hidden by a filter and never printed, two copies of the file in circulation and both sent to the shop. One busy day is all it takes.

A bar produced twice costs the steel, the cutting and bending hours, then the space to store it. A forgotten bar costs even more: it's missing on site on placing day, it has to be produced in a rush, bumping planned production, and it takes an extra delivery.

Why do revisions and extras get lost along the way?

Because a spreadsheet keeps what is, not what changed. When the drawing moves to a new revision, the simplest way to fix the bar list is to overwrite the old values. The file is right again, and the record of the change is gone.

But that record is exactly what's worth money. The difference between two revisions is the steel added, the steel already produced that's no longer needed, the detailing hours redone. Those are potential extras, if you can show what changed, when and at whose request. Once the cells are overwritten, all that's left is an up-to-date bar list and a memory. Extras noted on site on a scrap of paper go the same way if they never reach the file.

Two habits limit the losses: never overwrite a revision, keeping the old version next to the new one, and tell the person who does the invoicing about the change the same day, not at the end of the project, when nobody remembers what was asked for.

What happens when the only person who understands the file is away?

The company finds out its file was really a person. Over time, a bar list spreadsheet piles up formulas, hidden tabs, colour codes and exceptions that only its author knows. Everything's fine as long as that person is there.

The day they go on vacation in the middle of the season, get sick or leave the company, everyone else has to guess. They make changes carefully, then less carefully, and all the errors described above show up at once. Even when nothing breaks, that dependence slows growth: every new detailer has to learn the file before learning the company, which is long and tedious for everyone.

How do you measure what your spreadsheet really costs you?

By bringing the scattered costs together in one place for a few weeks. A sheet on the shop wall and one in the office are enough. Write it down every time:

  • bar list information is retyped somewhere else, and how long checking it takes;
  • a bar list is corrected after it was sent to the shop;
  • a bar is remade, produced twice or rushed out;
  • a change or extra isn't billed because there's no record of it;
  • a question waits for the person who knows the file to get back.

On a few finished projects, also compare the weight invoiced to the weight produced and delivered. A gap nobody can explain is part of the cost. To then decide between keeping the spreadsheet, building an in-house system or moving to software, read the comparison of spreadsheets, in-house systems and rebar software, then the questions to ask before choosing rebar software.

Metacis is rebar software designed by people in the trade. If these costs sound familiar, let's talk: request a demo.

Share

Frequently asked questions

Related articles

Metacis is rebar software designed by people in the trade.