Lewis Enright Prepared for McConnell
3 September 2026 Download as PDF

Delivery commitment

Replacing Mango in six months

Mango does five things for McConnell. One is already replaced. This sets out how the other four follow inside six months, tested and signed off, and exactly what McConnell need to do for that date to hold. 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

What Mango does today, and what replaces it

Every line is evidenced from McConnell's own documents rather than assumed, and every promise carries the decision it waits on. The register is far wider than health and safety: of the 829 documents about 573 are SHEQ's own, and the rest belong to commercial, HR and customer care. They come across in the same work.

Training and competency recordsAlready replaced · every certificateSkills, competencies, training history, providers and assessors.Module 6 section 33 lists MANGO among the sources to migrate from. HR set up the Mango login and each certificate was added into it as well.
Controlled documentsReplaced by month 6 · 829 documents, 41 categoriesPolicies, procedures, quality forms, toolbox talks, risk assessments, contracts, accreditations, Building Safety Act templates and customer care letters.Module 7 section 7 asks for the full Mango controlled document register to be reviewed and rationalised before the new library structure is fixed.Depends on McConnell: Which of the 41 categories are kept, merged, renamed or retired, the standard project folder structure, and the 38 open items the brief lists.
Audits and inspectionsReplaced by month 6 · the audit programmeSite observation reports, manager insights, company and ISO audits, and the audit sections each person is assigned to.McConnell's own Mango Audit Inspection Process guidance note.Depends on McConnell: The 21 open items in Module 3, the content of the six core report templates, and the review routes.
ImprovementsReplaced by month 6 · the improvement registerRaised improvements, owners, due dates, evidence, verification and close out.McConnell's own Mango Improvement Process guidance note.Depends on McConnell: Who owns an action, who verifies it, who closes it, and the escalation rules.
Incidents and near missesReplaced by month 6 · 680 recordsAccidents, incidents, near misses, the classification taxonomy and the statistics built on top of them.Module 4 was designed against the complete 680 record Mango export, and requires the original Mango Type to be retained on every migrated record.Depends on McConnell: The taxonomy crosswalk confirmed against the historic records, and the Taxonomy Stress Test workbook the brief refers to.

Largest categories first: Health and Safety Documentation 170, Quality Forms 140, Standard Forms of Contract 103, Toolbox Talks 67, Building Safety Act 46. The remaining 31 categories hold 152 more, for 829 in total.

02

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

Five vessels, all of them empty at the end of the six months. One is already there. The other four depend on decisions only McConnell can make, and those are set out below rather than left to be discovered.

03

What lands in the six months

Three stages, all five functions, and user acceptance testing completed inside the six months rather than after it.

Months 1 and 2

Documents and forms

Every controlled document into a library McConnell own, with the register, version control and supersession behind it. The Quality Forms and the health and safety templates become forms that complete on a phone, output a PDF and file themselves.

Months 3 and 4

Audits and actions

The audit and inspection records, including the core report templates the brief names, on top of the forms engine built in the first two months. With them the action engine: raised from any record, owned, evidenced, verified and closed.

Months 5 and 6

Incidents, and testing

Incident and near miss reporting with the historic records migrated and the original Mango classification kept alongside the new one. Then user acceptance testing, with McConnell's own site teams inside it rather than waiting at the end of it.

Each stage is specified requirement by requirement in McConnell's own briefs: the documents and forms stage in Module 7, audits in Module 3, actions in Module 5 and incidents in Module 4. 19 named requirements cover the first stage alone. The full list sits in the contract ledger rather than here, because this page is the commitment and that is the detail behind it.

User acceptance testing sits inside the six months, not after them. Rollout follows.

04

What this depends on, and it is not the documents

The documents are already McConnell's, held in McConnell's own SharePoint, because that is where they are authored. Mango carries published copies and the intranet already indexes those by link. So there is nothing to extract and no export to wait for.

What the date depends on is decisions, and they are already written down in McConnell's own briefs. None is difficult. Each one sits in front of a piece of work that cannot start until it is settled, so they can run alongside the build but they cannot run late.

8 decisions. This is the half of the commitment that is McConnell's.
What we needWhoBy
The controlled document register reviewed: which of the 41 categories are kept, merged, renamed or retired. Module 7 asks this of itself.Document control and the working groupMonths 1 to 2
The standard project folder and subfolder structure confirmed.Document controlMonth 1
The 38 open items Module 7 lists for working group review, closed in batches.The working groupMonths 1 to 3
Which forms convert first, and their content signed off.SHEQMonth 2
The 21 open items Module 3 lists, including review routes and intervention types.SHEQ and the working groupMonths 2 to 4
The Taxonomy Stress Test workbook the incident brief refers to, which we have not been sent.SHEQMonth 2
The incident taxonomy crosswalk confirmed against the historic records.SHEQMonth 3
Named user acceptance testing participants, and booked windows, per job.SHEQ and the site teamsMonth 4

Said plainly, because it is better said now than discovered in month five: if these run late, the date moves with them. That is the only thing that would move it.

05

The dates

Two markers inside the six months and one after it. Rollout begins once user acceptance testing is signed off.

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.

06

Rollout, and why six months rather than three

Job by job, not all at once. As each part is ready it goes to the teams who need that part, with McConnell's own site teams inside the testing rather than waiting at the end of it. Nothing is switched off in Mango until what replaces it has been used in anger and the people using it say it is better.

The library is built on SharePoint, which McConnell already own and already administer. The categories are reviewed and rationalised on the way across rather than copied, which is what the controlled documents brief itself asks for.

Why six months, when we first said three

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. But it is a bigger and better defined job than the first brief described, and six months is the honest number for it.