Implementation

Switch from spreadsheets to live registers

Most teams do not rip out every Excel file on day one. This guide walks through a realistic 4-week path from spreadsheet sprawl to a single live portal — without stopping work or losing open corrective actions.

What you are solving

  • One current version of policies, registers and audit evidence — not Final_v3_REAL.xlsx on five laptops
  • Open NCRs and CARs imported with owners, due dates and status — not re-keyed from memory
  • Site teams capturing incidents and hazards on mobile — not weeks later on a shared sheet
  • Auditor export packs from live data — not a pre-audit copy-paste marathon

Not sure Veridian is the right fit yet? Read Spreadsheet vs Veridian IMS first, then come back here for the how-to.

Plan

Four-week migration path

Adjust the pace to your team — the order matters more than the calendar.

Week 1 — Map & demo

List every spreadsheet your auditors actually sample: NCR log, CAR tracker, hazard/incident lists, training matrix, SWMS index, supplier list. Start a 7-day demo and match each sheet to a Veridian register or document library item. Decide your tier (ISO 9001, 14001, 45001 or combined).

Week 2 — Documents & open actions

Issue controlled policies and procedures from the document library — retire duplicate Word/Excel copies from shared drives. Import open NCRs, CARs and incidents via CSV (see below). Leave closed historical rows in archive folders if you prefer; auditors usually sample recent open items and live operation.

Week 3 — Field & ownership

Invite site supervisors and quality/safety reps to the portal. Install the mobile app from the portal (no app store). Run one real workflow end-to-end: hazard or incident → CAR → verification. Assign register owners so updates do not fall back to a shadow spreadsheet.

Week 4 — Audit in the system

Run an internal audit checklist in the portal. Close findings as CARs with due dates and evidence attachments. Export a Word/Excel evidence pack. Only then retire the old master spreadsheet for that register — keep a read-only export if your policy requires it.

Import

CSV import — what works today

Veridian supports CSV template download, export and import on selected registers. Use spreadsheets as a staging area, then load structured data into the live register.

  • NCR register — Description required; optional Record ID, date, severity, owner, due date, status. Blank IDs auto-generate as NCR-###.
  • CAR register — Description required; optional source, root cause, owner, due date, status.
  • Incident register — Use the portal CSV template; headers must match the live register columns exactly.
  • Import modes — Append/update (default) adds rows and replaces matching Record IDs; replace-all clears the register first (confirmation required).

Hazard, SWMS, supplier, training and aspects registers do not have CSV import yet — enter new rows in the portal or keep a temporary sheet until you migrate those registers manually. Do not maintain two live masters for the same register.

Spreadsheet → register map

Common replacements

Quality

NCR log → NCR register · CAR tracker → CAR register · Supplier list → approved supplier register · Calibration list → calibration register · Customer complaints → complaint register.

Safety

Incident log → incident register · Hazard register → hazard register · SWMS index → construction SWMS workspace · Training matrix → training records · Contractor list → contractor register.

Environment

Aspects/impacts sheet → aspects register · Legal register → obligations register · Monitoring log → monitoring records.

Still fine in Excel

Tender pricing models, one-off calculations, budget worksheets and import staging files — as long as they are not your controlled master for audit evidence.

People

Avoid the rebound to spreadsheets

  • Name owners — Each register needs a person accountable for weekly hygiene, not “the shared drive”.
  • One rule — If it is open for audit, it lives in Veridian. No parallel shadow logs.
  • Short training — 30 minutes for office staff on CAR close-out; 15 minutes for site leads on mobile capture.
  • Consultant handover — If an ISO consultant built your system, load their templates into the document library rather than leaving procedures in a project folder. See vs consultant-led projects.
Get started

Start the migration in a demo workspace

Sample data is included — map your spreadsheets to live registers before you subscribe.