A sling comes off the shelf, goes into a basket and ships to a rig. Somewhere in a folder or a spreadsheet there is a certificate for it. Whether that certificate is current, whether it belongs to this exact sling, and whether the person at the lifting point can see it in thirty seconds are three separate questions. On many sites the honest answer to at least one of them is “we would have to check”.
This guide is for HSE managers, TIC inspection leads and rig or asset managers who are responsible for lifting equipment records. It covers why those records matter, what a useful record contains, how to stop certificates lapsing unnoticed, and what to look for when you evaluate lifting equipment inspection software. Later on it explains how Bexel Pro handles the same problems.
Regulations and client requirements differ by country and by site, so this article stays general. If you want the background on the standards most often mentioned in this area, our comparison of LEEA and LOLER standards is a good place to start.
Why lifting inspection records matter
Lifting equipment is the kind of equipment where a failure injures people. Hooks, shackles, slings, chains, spreaders, lifting beams, hoists and cranes carry loads over work areas, and the consequences of a bad lift are rarely small. That is why lifting equipment is examined and inspected on a schedule, and why those examinations produce a record.
The record does three jobs. It proves that a competent person looked at the equipment and found it fit for use. It tells the next person what was found, what was done about it and when the equipment must be looked at again. And it gives an auditor, a client or an incident investigator something to read that does not depend on anyone’s memory.
The inspection itself happens in the field. The record is what survives afterwards. If the record is missing, wrong or impossible to find, the inspection might as well not have happened as far as the next shift, the next client or the next audit is concerned. For a wider view of why this work matters offshore and onshore, see our article on why lifting inspection is important on onshore and offshore rigs.
What goes wrong with paper and spreadsheets
Paper files and spreadsheets are where most teams start, and for a small inventory they can work. The trouble appears as the number of items, sites and clients grows. These are the failures that come up most often:
- Certificates that cannot be found. The certificate exists, but it is in a drawer at another site, a scanned PDF with a meaningless file name, or an email attachment from two years ago.
- Expiry dates that nobody is watching. A spreadsheet column of dates only helps if someone filters it every week. When that person is on leave, nobody does.
- Several versions of the truth. The inspector’s copy, the office copy and the client’s copy drift apart. A re-test is recorded in one and not in the others.
- Equipment that cannot be matched to its paperwork. A tag has worn off, or two items share a similar serial number, and the certificate may belong to a different piece of equipment.
- Retyping errors. Data written on a site form and typed into a spreadsheet later picks up mistakes: a swapped digit in a serial number, a wrong date, a certificate attached to the wrong row.
- No history. When a shackle fails an inspection, the team wants to know how many similar items were inspected, what was found earlier and whether this is a pattern. Paper makes that question slow to answer.
- Slow client reporting. Clients ask for evidence and someone spends a day collecting files, formatting a report and emailing it.
None of these is a failure of effort. They are what happens when a records system relies on people remembering to do the right thing, with tools that do not prompt them. The better question to ask is which parts of the process a system can do reliably so that people can spend their time on the equipment.
What a good inspection and certificate record contains
Before comparing any tools, it helps to be clear about what a record should hold. Different organisations and clients ask for different things, so treat the table below as a practical starting point rather than a definitive list.
| Record element | What it should capture | Why it matters |
|---|---|---|
| Equipment identity | A unique ID, type, description, manufacturer where known, and a serial or tag number that is physically marked on the item | The certificate has to be tied to one specific item, not to “a 10 tonne shackle” |
| Location and owner | The site, rig, vessel or client the item belongs to, and where it is currently kept or deployed | You cannot inspect or recall what you cannot locate |
| Inspection details | Date, type of examination, who carried it out, the method used and the result | Shows what was done and by whom |
| Findings and defects | Observations, defects found, photos where relevant, and the decision: pass, fail or conditional | Lets the next inspector see what was noticed before |
| Corrective actions | What was repaired, replaced or removed from service, who owns the action and when it closed | A defect that is noted but never closed is a liability |
| Certificate | A reference number, issue date, expiry or next-due date, and the signed document itself | This is the evidence that people at the lifting point and auditors ask for |
| History | Previous certificates, earlier findings and past repairs for the same item | Trends and repeat problems only show up over time |
A few principles make the difference between a record that is merely complete and one that is useful.
One item, one identity. Every piece of equipment should have a single record with a unique identifier that matches what is physically marked on it. Everything else, including certificates, findings and repairs, hangs off that identity. Many records problems come down to an identity that is ambiguous or duplicated.
The certificate is data, not only a document. A scanned PDF of a certificate is better than nothing, but a system that also stores the certificate number, issue date and due date as fields can search, sort and warn. A folder of PDFs cannot tell you which of them expire next month.
Findings are linked to actions. A failed item should lead to a visible follow-up, such as repair, replacement or quarantine, with an owner. It should be possible to see at a glance which defects are still open.
History is never overwritten. When an item is re-inspected, the new certificate should be added alongside the old one. Overwriting destroys the trail you will want after an incident or during an audit.
Managing certificate expiry
Expiry is the quiet failure mode of lifting records. Nothing dramatic happens on the day a certificate lapses. The sling looks the same, it sits in the same place, and it keeps being used until someone notices, or until an auditor or client does.
Good expiry management has four parts.
- A single source of due dates. Every certificate has a next-due date stored as data in one place, not in someone’s calendar and a separate spreadsheet.
- Early warnings, not last-day warnings. A warning that arrives on the expiry date is a notice of failure. The useful warning arrives early enough to book an inspector, move the equipment and, if needed, arrange cover.
- The right people are told. The inspection team needs to know what is coming due so they can plan their visits. The client or asset owner also needs to know so they can release equipment and plan around downtime. A system that only warns one side leaves a gap.
- A clear rule for expired equipment. Everyone should know what happens to an item with an expired certificate: it is tagged, quarantined or withdrawn until it is re-examined. The best software cannot enforce this on the deck, but it can make the status impossible to miss.
It also helps to look at expiry as a workload problem. If a large share of your equipment was certified in the same few weeks, it will fall due in the same few weeks. A view of upcoming due dates by month, site or client lets you spread the work before it becomes a crunch. This is one of the places where a dashboard earns its keep: it turns a long list of dates into a plan.
QR codes for quick verification in the field
The person who most needs to know whether a lifting accessory is in date is usually standing next to it: a rigger, a crane operator, a supervisor or a client representative. Walking back to an office, or phoning someone to find the file, is exactly the step that gets skipped when the job is under time pressure.
A QR code on the equipment closes that gap. The idea is simple. A durable sticker or tag carries a code, and scanning it with a phone opens the record for that item, including its current certificate. Instead of reading a coloured tag and trusting that it is still right, the person checking can see the certificate that is actually on file.
A few practical points decide whether this works in practice:
- The code must link to the live record. A QR code that points to a static PDF will show an out-of-date certificate once the item is re-inspected. A code that points to the record always shows the current state.
- The sticker has to survive the environment. Heavy machinery gets wet, oily, dirty and knocked about. Placement and material matter, and stickers need to be replaced when they wear.
- Scanning should not need training. If it takes more than pointing a phone at the sticker, people will not do it.
- Access must be controlled. Not every viewer needs to see every detail. Decide what is visible to someone who scans the code and what stays behind a login.
- A QR code does not replace inspection. It makes the result easy to find. It says nothing about the condition of the equipment on the day.
Used well, QR codes also reduce small disputes. When a client asks whether a particular item has a valid certificate, the answer is a scan away.
Bulk handling of lifting accessories
Large equipment such as cranes tends to be inspected one at a time and has a well-understood record. The harder volume problem is lifting accessories: slings, shackles, hooks, chains, eyebolts and similar items. A single site or inspection campaign can involve hundreds or thousands of them, often with similar descriptions, and they are inspected in batches.
Entering that many items one form at a time is slow and invites mistakes. If a system supports only one-at-a-time entry, teams end up keeping their own spreadsheets on the side and loading the results later, which brings back the problem of two sources of truth.
What a team handling accessories in volume should look for:
- Bulk upload. The ability to load many items and their certificates from a spreadsheet, using a format inspectors already know.
- Validation on the way in. Duplicate IDs, missing dates and malformed entries should be flagged before they become records.
- Review before release. Bulk entry increases the cost of a mistake, so a reviewer or approver should be able to check a batch and approve it together rather than approving each item by hand.
- Consistent naming. Agreeing a convention for IDs and descriptions before the first batch saves a great deal of cleaning later.
The aim is to keep the speed of a spreadsheet while ending up with controlled records that have identities, certificates, due dates and an approval trail.
Working offline on remote sites
Lifting inspection often happens where connectivity is poor or absent: offshore installations, remote yards, desert sites, workshops with thick steel walls. A system that needs a live connection to record an inspection will push inspectors back to paper forms, with retyping later.
When you evaluate a tool for use on remote sites, ask how it behaves without a connection. Can an inspector open the equipment list, record findings and attach photos with no signal? What happens when the device comes back online? How are conflicts handled if two people have edited the same record? Is it clear to the inspector what has and has not been saved?
It also matters which devices the inspectors actually use. Inspectors often work on tablets or laptops rather than phones, and a tool built around the latest phone may not suit them. Check the supported devices before you commit.
Offline capability is not a nice-to-have for these teams. If it does not work in the places where inspections happen, the paper process stays, and so do its problems.
Sharing records with clients
If you are a TIC company or an inspection contractor, your client does not only want the inspection done. They want evidence, they want it quickly, and they want to know what is outstanding. If you own the assets yourself, your own HSE, operations and audit teams are your clients in the same sense.
Without a shared system, this means a steady stream of emails: requests for inspections, requests for copies of certificates, requests for status updates, requests for a list of open findings. Each one takes someone’s time, and each reply is a snapshot that goes out of date.
A client-facing portal changes the pattern. Clients can request an inspection, follow progress, and look up reports, records and corrective actions themselves. The inspection team spends less time answering the same questions, and the client sees the current position rather than last week’s.
The details deserve attention:
- Visibility control. A contractor will have documents that are internal and others that a client should see. Look for control that goes down to the level of individual files and folders, not only a single on or off switch.
- A central document store. Technical documents, certificates and historical data should live in one place, so that the same document is not stored three times with three different dates.
- Clear separation between clients. One client must never see another client’s records.
- Corrective actions in view. A client who can see open actions and their progress will ask fewer questions about them.
What to look for when evaluating lifting inspection software
Feature lists tend to look alike. The questions below are more useful in a demo than a checklist of feature names, because each one tests whether the tool fits the way your team actually works.
| Question to ask | What a good answer looks like |
|---|---|
| Can I see all certificates due in the next few months, across all sites? | A filterable view or dashboard, not an export you have to sort yourself |
| Who is warned before a certificate expires? | Both the inspection team and the client or asset owner, ahead of the date and not on it |
| How do I check one item in the field? | A scan or a search that brings up the item and its current certificate within seconds |
| How do I load a large batch of equipment? | A bulk upload from a spreadsheet, with checks and an approval step |
| What happens with no signal? | Inspectors can keep working and record findings, and the tool handles reconnection clearly |
| What can my client see? | Documents, reports and actions for their own equipment only, with control over files and folders |
| Is history preserved? | Earlier certificates and findings remain linked to the item |
| Which inspection types are supported? | All the methods and equipment categories you actually inspect, not just the main ones |
| Can I get my data out? | A clear way to export your records if you ever change tools |
| How does the vendor describe compliance? | As support for managing your inspections and records, and not as a promise that using the tool makes you compliant |
The last question deserves emphasis. No software makes an organisation compliant. Compliance depends on competent people, sound procedures and honest inspection. Software can make the records easier to keep accurate, easier to find and harder to let slip, but responsibility stays with the duty holder. Be wary of any vendor who suggests otherwise.
Run any shortlisted tool against a real, messy sample of your own data, not the vendor’s clean demo set. Try the awkward cases: an item with a missing serial number, a certificate that has just expired, a batch with a duplicated ID. How a tool handles the bad data tells you more than how it handles the good.
How Bexel Pro handles lifting inspection
Bexel Pro is Bexel’s inspection software. The sections below describe how it addresses the points covered above. For a fuller view, see the Bexel Pro lifting inspection page and the wider Bexel Pro features overview.
Lifting inspection and QR-enabled certificates. Bexel Pro manages all lifting inspection methods and supports QR code-enabled certificates, so a certificate can be verified quickly by scanning.
QR code stickers. You can design and print custom stickers with QR codes to place on heavy machinery, and link each one to the inspection certificate for that equipment.
Batch handling of lifting accessories. Inspectors can create and upload equipment and certificates in bulk using Excel sheets, with mass approval rather than item-by-item sign-off.
Notifications and alerts. Bexel Pro sends automated notifications for inspection activities. It also provides two-way notifications, reaching both operations and clients, for certificate expiry alerts.
Client Portal. Clients can submit inspection requests and track inspection reports, records and corrective actions. A live dashboard shows the current position.
Document Library. Technical documents and historical data are held in a central library. Clients can reach their certificates and records through the portal, and you control the visibility of files and folders.
Offline Desktop App. Inspectors can work offline on Windows tablets or laptops, which suits sites with limited connectivity.
Dashboards and reports. Dashboards and reports give managers an overview of the inspection programme.
Bexel Pro helps teams manage inspections, certificates and records. It does not make a company compliant or certified. That still depends on how inspections are carried out and who carries them out.
Frequently asked questions
At a minimum, it should identify the specific item (a unique ID and a serial or tag number), state the date and type of examination, name who carried it out, record the result and any defects, and give a certificate reference and the next due date. Requirements differ by organisation and client, so check what yours ask for.
It depends on the type of equipment, the rules that apply where you work, your client’s requirements and how the equipment is used. Intervals are usually set by the applicable regulations, standards and your own risk assessment, so confirm them with your competent person rather than relying on a single rule of thumb.
No. A QR code is a way to reach the record quickly. The certificate and the inspection behind it are still what matter. The code is only useful if it links to the current record for that exact item.
Store every certificate’s due date as data in one place, send warnings well before the date, and make sure both the inspection team and the equipment owner or client are told. Review upcoming due dates by month so that inspection work can be planned ahead.
No. Software can help you manage inspections, certificates and records more reliably, but compliance depends on competent people, sound procedures and honest inspection. Treat any claim that a tool makes you compliant with caution.
A practical next step
If your lifting records live in folders and spreadsheets today, you do not need to replace everything at once. A sensible first step is to pick one site or one equipment category, work out how long it takes to answer three questions about it (what is due, what is overdue, where is the certificate), and compare that against what you would want.
If you would like to see how Bexel Pro handles lifting inspection with your own kind of equipment and clients, you can talk to the Bexel team. A short conversation is enough to find out whether it fits.