Spreadsheet sprawl

When the whole inspection business runs on spreadsheets

Spreadsheets fail an NDT company not because they are bad tools but because each holds one slice of the business and a person joins them up. When certifications, calibration, crews, reports and billing are separate files, errors hide in the joins. Moving to one system lets each fact be entered once and read by everyone who needs it.

Business overview: sample dashboard from the Atlantis NDT platform

Quotations, work won but not yet invoiced, and overdue cash, the way the owner sees the business.

  • Cards: confirmed quotations (up on last quarter), open quotations (several past validity), work won, not invoiced (needs billing), overdue invoices (chase this week).
  • Charts: quotations issued against confirmed by month, quotation ageing (this fortnight, within the month, one to two months, older) and confirmed work by service line.

Panels in the preview: Certifications, Calibration, Reports, Jobs, Sales & cash. Names and statuses are sample data.

How spreadsheets quietly become the operating system

It starts sensibly. A certification tracker for the QA manager, a calibration list for the equipment room, a planning sheet for dispatch, a rates workbook for quoting, a timesheet template for the crews and an accounting package for invoices. Each file is well kept by its owner and each works. For a small team, together they are a reasonable way to run an inspection company.

The trouble is what sits between the files. To put a crew on a job, someone reads the planning sheet, checks the cert tracker, checks the calibration list and remembers who is on leave. To invoice the job, someone re-keys hours from timesheets, checks the rates workbook and hunts for the PO in email. The company's real integration layer is a handful of experienced people copying and comparing, and they are the busiest people in the building.

Growth breaks it. A second base, a run of turnarounds, a client who wants qualification packs before mobilisation, an auditor who samples a job from last spring. Formulas break when rows are inserted, versions multiply on laptops, and the file everyone trusts turns out to be the copy someone saved locally last week.

  • Version roulette

    Several copies of the same tracker exist, and nobody is sure which one is current.

  • The same fact typed repeatedly

    A technician's name, a job PO or an instrument serial is entered separately in every file it appears in.

  • Key-person dependency

    Certain files only make sense to whoever built them, which makes holidays a risk.

  • Checks done by eye

    Whether a technician is qualified or an instrument calibrated is confirmed by someone comparing sheets side by side.

  • No single picture

    A simple question such as how much won work is unbilled takes a morning of collation to answer.

What spreadsheet sprawl costs as you grow

  • Errors in the joins

    Mistakes happen not inside a sheet but in the copy between sheets: the wrong rate, a transposed serial, a missed leave entry.

  • Senior time on clerical work

    Operations managers and Level IIIs spend hours collating rather than planning work or reviewing technique.

  • Fragile audits

    Evidence spread across files is slow to assemble and easy to get partly wrong under time pressure.

  • A ceiling on growth

    The business can only take on as much work as the people joining the spreadsheets can hold in their heads.

Enter each fact once and let the apps share it

Atlantis NDT ERP replaces the joins rather than the people. Technicians are employee records with an NDT profile, and their certifications and vision tests sit on that record. Instruments are serial records with calibration history. A job is a project with its PO, site, methods and crew. Because these are the same records everywhere, a timesheet can warn on an invalid certificate, dispatch can refuse a double-booked serial, and an invoice can carry the PO without anyone copying it.

The Business overview dashboard gives the owner the cross-company view that used to need collation: confirmed quotations, open quotations awaiting the customer or past validity, quotation win rate, confirmed work not yet invoiced, invoiced, collected, receivables and overdue, with company and currency filters and period selection. Tabs separate sales and quotations, invoices and cash, training, enquiries and operations, and a needs-attention tab lists what has slipped.

Moving off spreadsheets is a project, not a switch. Data is cleaned and imported, rules are agreed and people are trained on the parts they use. Many companies start with a few apps, such as Certificates, Asset Management and Timesheets, and add the rest later. Some teams run the old tracker alongside for a short period until they trust the new register, which is sensible.

  1. List the spreadsheets

    Inventory every tracker in use, who owns it and which other files it gets compared against.

  2. Start where the joins hurt

    Begin with the apps that remove the most re-keying, often certificates, equipment and timesheets.

  3. Import, do not retype

    Existing registers are cleaned and imported, so the first day starts with your real data.

  4. Retire files deliberately

    Once a register is live and trusted, archive the spreadsheet it replaced so nobody keeps updating both.

  5. Add apps in sequence

    Bring in quoting, dispatch, reports and invoicing as each team is ready, connecting them as you go.

Before and after

A tracker per department, joined by hand.Shared records read by every app that needs them.
Qualification checked by comparing sheets.A timesheet warning when a certificate is not valid.
Unbilled work found by a morning of collation.A confirmed-not-invoiced card on the Business overview.
Files only their author understands.Records with defined fields and role-based access.

The modules doing the work

Each module is part of the same platform, so a certification, an instrument, a job and a report are linked records rather than files in different places.

  • Dashboards

    Business overview with quotation, billing, cash and needs-attention views across companies and currencies.

  • Employees

    One technician record with NDT profile, documents and availability, instead of a folder per person.

  • Project

    The job record that quotes, timesheets, reports and invoices all point back to.

  • Quotations

    Structured quotes with job type, site, dates and codes that convert into the job without retyping.

Questions owners ask

When should an NDT company stop running on spreadsheets?

Usually when keeping files consistent with each other takes more effort than the work they track, or when errors start appearing in the copying between files rather than inside any one sheet. Growth, a second base and audit pressure tend to bring that point forward.

Do we have to move everything at once?

No. Many companies start with Certificates, Asset Management and Timesheets and add the other apps later. The connections between apps apply as each one is added.

Will our existing data come across?

Yes. We import your current registers, including technicians, certificates, equipment and open invoices, during implementation, so day one begins with real records rather than an empty system.

Can the platform handle more than one company or currency?

The Business overview dashboard has company and currency filters, so a group running more than one entity can view them separately or together.

Can we try before committing?

Yes. You can start on a free trial, and both a guided demo and a quote are available on request.

See it on your own records

Bring a sample of your certifications, equipment list or reports and we will show the workflow configured to how your company runs. Demo on request.

Speak to an ASNT NDT Level III

Discuss your inspection requirements with Atlantis NDT. Include the asset, method, location and documents you need reviewed.