Audit pack
What you found, and what you did about it. In one export.
BaseShift keeps every record exactly as it was captured, judged against the rule in force at the time, and exports it as an audit pack you can hand straight to a regulator, a lender or an auditor.
Audit pack · Example
Block B, 1–31 October 2026
| Record | Type | Captured | Closed by |
|---|---|---|---|
| Missing tie, Block B east scaffold, lift 3 | Failed inspection | 14 Oct | Site supervisor |
| Crane exclusion zone entered, west gate | Near miss | 11 Oct | HSE officer |
| Tower crane 2 slew alarm | Fault | 07 Oct | Maintenance fitter |
| Excavation edge not barriered, gridline 7 | Hazard | 09 Oct | Site supervisor |
| Concrete pump hose damaged | Fault | 21 Oct | Maintenance fitter |
Filtered by: 01 Oct 2026 – 31 Oct 2026 · Block B · Faults, hazards, failed inspections, rounds · All stages
Contents
What's in an audit pack.
One document for an auditor, a lender or a regulator. Every record in the range, with the evidence attached to it.
Every record in the range.
Every inspection, hazard, fault and corrective action in the dates and the part of the plant you choose.
Before and after photos.
Each photo prints under the question it answers.
Timestamps and location.
On every record, printed with the evidence.
Named signatories.
Who verified each fix, and when.
Closure rate and time to close.
Straight out of the records.
The filters it was made with.
Stated on every page.
Export
Days of file-gathering, now one button.
When an auditor, lender or regulator asks what you found and what you did about it, export the answer. The same records feed your monthly reports.
Filter.
Date range, part of the plant, record types, stage and status. Or start from a single asset.
Filter2 filters appliedLeave a group empty to include everything.
- Dates
- 1–31 Oct
- Area
- Block B
TypeFaultsHazardsFailed inspectionsRoundsBuild.
Tick the records, order the columns, pick the header fields and add comments. Save the setup for next month.
ColumnsSelect allClear allRecord✓Task✓Version✓Submitted by✓Submitted at✓Location✓AssetGPSEvidence itemsAssignment✓Assigned toWork item statusCorrective action✓Action status✓Date closedClosed by✓Reviewed byImagesBefore imageAfter imagePreview.
See the report exactly as it will print before you generate it.
Audit pack · Preview
Block B, 1–31 October 2026Filtered by: 01 Oct 2026 – 31 Oct 2026 · Block B
Generate audit packPage 1 of 14Export.
PDF to hand over, Excel to analyse. Units printed, out-of-range values flagged.
Audit pack · Block B
Near miss · Crane exclusion zone, west gate
Photo taken on the phoneCrane exclusion zone entered during a lift
Reported by crane operator
Photo 11 Oct 14:32 GPS 6.52341, 3.37912 sha256 4f9c1a7d… by crane operator Device FP-04Linked action: Exclusion zone barrier and signage reinstated · Closed 12 Oct 16:10
Closed by HSE officer
Verified by site supervisor · 12 Oct 16:10
Filtered by: 01 Oct 2026 – 31 Oct 2026 · Block B
- Evidence in context. Each photo prints under the question it answers, with time, location and named signatories.
- Integrity you can check. Photos are hash-verified at export, so a missing or altered file shows up instead of passing silently.
- Nothing out of context. Every page states the filters it was made with, and each record prints against the form version it was captured on.
Trust and security
An evidence chain nobody can quietly rewrite. Including us.
An audit pack is only worth something if the records behind it can't be changed afterwards. BaseShift enforces that in the system itself, not in a policy document.
The rule on 14 October
- Form
- Wind speed at jib, tower crane 2 · version 3
- Alert
- Stop lifting above 20 m/s
- Reading
- 17 m/s
The rule from 1 November
- Form
- Wind speed at jib, tower crane 2 · version 4
- Alert
- Stop lifting above 15 m/s
- 14 Oct reading
- Still judged on version 3. Unchanged.
- Nothing is ever deleted. Tasks, locations and assets are retired, never removed, so a record never loses what it refers to.
- Photos you can check. Who, when, where, which device and an integrity hash on every photo.
- Managers see only their area. The database itself refuses rows outside a manager's part of the plant.
- Your company's data is walled off. Each company's records are separated inside the database, not just filtered by the app.
- Support access, locked and logged. BaseShift support uses a locked account, on the web only. Every session is logged, and support can never sign off evidence.
- Your retention policy. You choose how long photos and other media are kept. Records themselves are kept for good.
Questions
What auditors and IT teams ask us.
The short answers. We'll take your security questionnaire too.
Can someone change a record after it's submitted?
No. A submitted record can't be edited or deleted, and it keeps the exact form version it was captured on.
What happens to old records when we change a form?
Nothing. Publishing creates a new version. Old records stay judged against the version they were captured on.
Can a manager see another area's records?
No. Access is scoped to part of the plant, and the database refuses rows outside it.
Can BaseShift staff see our data?
Only through a locked support account in your company, on the web, with every session logged. Support can never verify or sign off evidence.
Do AI tools process our data?
No. No AI tool processes customer data.
How do we know a photo wasn't altered?
Each photo is hashed when it's taken and checked again when you export. A changed or missing file is flagged.
Get started
Start with one site. Add the next in a week.
Begin with a paid pilot on one site. We load your locations and assets, set up your first tasks and rounds, and train your crews. Adding the next site is setup, not a new project.
Back to: Home →