Lewis Enright Prepared for McConnell
3 September 2026 Download as PDF

Delivery commitment

Replacing Mango in six months

Everything Mango does, replaced inside six months and tested before anyone relies on it, plus two apps for the people actually on site. Every item below names what McConnell need to do for it to land. It is a joint commitment and it is written to be held to.

829controlled documents held in Mango
41categories they are filed under
680incident records behind the taxonomy
6months to replace all five of them

Where the work happens today, in McConnell's own words: audits, improvements and incidents "will still be carried out through the Mango website/app".

McConnell Viewpoint Handbook, page 3. A record of the current state, not a position on what should replace it.
Five functions, not oneThe document register, the audit process, the improvement register, the incident register and the training records.
One is already goneThe training system reads people from HR and evidence from the certificates. It never touches Mango, which is what the other four will look like.
All four inside six monthsDocuments, audits, improvements and incidents. Tested, with McConnell's site teams inside the testing. Rollout follows, about 6 weeks.

01

Five vessels. All of them empty by month 6.

The five things Mango does for McConnell, and how many are empty by month 6 Five glass vessels on a shelf, one for each function Mango performs: training and competency, controlled documents, audits and inspections, improvements, incidents and near misses. 5 of the five stand empty by month 6, lit from the base to show the work has moved to a system McConnell own. The other 0 remain full. The same position is set out in the tables below. Training and competency every certificate ALREADY OUT Controlled documents 829 documents, 41 categories OUT BY MONTH 6 Audits and inspections the audit programme OUT BY MONTH 6 Improvements the improvement register OUT BY MONTH 6 Incidents and near misses 680 records OUT BY MONTH 6

Moved to a system McConnell own Where the contents stood when we started

One vessel for each thing Mango does. All five stand empty at the end of the six months, and one is already there. What replaces them is on the next page, card by card.

02

What McConnell get, and what each one waits on

Eight things, all of them inside the six months, and user acceptance testing completed before rollout begins. Every card carries the decision it depends on, because a date is only worth as much as the things it rests on.

Controlled documents

Months 1 and 2

All 829 of them, about 573 SHEQ's own, out of Mango and into a library McConnell own.

  • The register, with categories that have been rationalised rather than copied across
  • Version control and controlled supersession, so there is one current version and a history
  • Review and approval routes where configured
  • Issue, distribution and acknowledgement
  • Search across the library and across project records
  • Role-based visibility and a full audit trail
McConnell's partWhich of the 41 categories are kept, merged, renamed or retired, and the standard project folder structure. Module 7 asks both questions of itself.

Digital forms

Months 1 and 2

The Quality Forms and the health and safety templates stop being documents to print.

  • A forms library with controlled template versions
  • A builder with conditional logic, photos, files and signatures
  • Project information filled in automatically rather than retyped
  • Draft, autosave, submission lock and controlled amendment
  • A branded PDF of every completed form, filed to the right project on its own
McConnell's partWhich forms convert first, and their content signed off.

The site app

Months 3 and 4

One app on a phone or tablet. Check in on arrival, do the inspection, and it keeps working with no signal.

  • Check in and out at each property, with location recorded on both
  • An alert when someone who should be on site has not checked in
  • The core report templates completed on site, offline, syncing when back in range
  • Photographs and evidence attached to any finding, and actions raised from the report itself
  • Booked leave carried across, so a holiday raises no alert
  • A live map of who is where
McConnell's partThe content of the core templates and who signs a report off, the property list, and confirmation that the leave feed is licensed on McConnell's HR system.

Audit programme and records

Months 3 and 4

The register and the programme behind the app.

  • A safety records register on every project
  • The audit programme workspace, and what is due when
  • Reviewer mark-up and return for clarification
  • Repeat themes visible, with drill-down to the records underneath
  • Reporting by project, region, subcontractor and finding type
McConnell's partThe 21 open items Module 3 lists, including intervention types and frequencies.

Improvements and actions

Months 3 and 4

One action engine, fed by every other part of the system.

  • Raise an action from any record, with the source context attached
  • A named owner, a due date and a priority
  • Evidence uploaded against the action
  • Verification kept separate from closure
  • The actions register, with reminders and escalation
McConnell's partWho owns an action, who verifies it, who closes it, and the escalation rules.

Incidents and near misses

Months 5 and 6

Reporting from a phone, and all 680 historic records brought across.

  • One report route for accidents, incidents and near misses
  • Classification, severity and the links to project, person and subcontractor
  • A RIDDOR decision record with the reasoning kept
  • Project, regional and company registers
  • The historic records migrated, with the original Mango classification kept beside the new one
McConnell's partThe taxonomy crosswalk confirmed, and the Taxonomy Stress Test workbook the brief refers to but we have not been sent.

Training and competency

Already live

In use now, and the reason Mango's training records are already redundant.

  • A competency matrix built from source records rather than maintained by hand
  • Certificates read by AI, confirmed by a person before anything counts
  • Signed validity rules that beat a certificate's printed expiry
  • Booking, reminders, exemptions and the evidence behind every figure
McConnell's partThe remaining course names and validity rules, which are open now.

03

The dates, and why six months rather than three

Month 3

Documents and formsThe controlled library live with the register behind it, and the forms engine turning the Quality Forms and the health and safety templates into forms that complete on a phone.

Month 6

Mango replaced, and testedAll five functions across, the historic records migrated, and user acceptance testing completed with McConnell's own site teams inside it rather than waiting at the end.

Month 7

Rolled outAbout six weeks from the end of user acceptance testing. Job by job, not all at once. Nothing is switched off in Mango until what replaces it has been used in anger.

When we first looked at this we were working from a single health and safety system brief, and three months looked right. Since then McConnell have written nine briefs across the whole estate and they are considerably more detailed than the original. Modules 6 and 7 alone grew from 78 requirements to 87 as recently as the first of September.

That is not a problem, it is the opposite. The specification is now good enough to build from and good enough to commit to a date against. Rollout begins once user acceptance testing is signed off, job by job, and takes about 6 weeks. Nothing is switched off in Mango until what replaces it has been used in anger.