Lewis Enright Prepared for McConnell
3 September 2026 Download as PDF

Delivery commitment

Replacing Mango

Mango does five things for McConnell. One of them is already replaced. This sets out which of the others goes next, exactly what that means, and what is honestly still in Mango at the end of six months.

829controlled documents held in Mango
41categories they are filed under
680incident records behind the taxonomy
5separate functions Mango performs

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.
The largest goes nextAll 829 controlled documents, inside the six months, within what has already been agreed.

01

What Mango does for McConnell today

Every line below is evidenced from McConnell's own documents rather than assumed. The register itself is far wider than health and safety: it holds policies, contracts, insurances, marketing and customer care alongside the quality forms.

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.
Audits and inspectionsStill in Mango at 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.
ImprovementsStill in Mango at month 6 · the improvement registerRaised improvements, owners, due dates, evidence, verification and close out.McConnell's own Mango Improvement Process guidance note.
Incidents and near missesStill in Mango at 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.

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. Two 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. 2 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 3 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 IN MANGO Improvements the improvement register IN MANGO Incidents and near misses 680 records IN MANGO

Still held in Mango Moved to a system McConnell own Where the contents used to stand

Two of the five stand empty at the end of the six months. The other three are full, and saying so is the point of drawing it this way.

03

What lands in the first six months

In McConnell's own words, taken straight from the Core Build Requirements of the controlled documents brief. This is the commitment, and it is the whole of it.

Months 1 and 2

The register moves

Every document comes out of Mango and into a controlled library that McConnell own, on SharePoint, with its categories rationalised rather than copied across.

Months 3 and 4

Control

Revision, supersession, review and approval, issue and acknowledgement. The things that make a library a controlled library rather than a folder.

Months 5 and 6

Forms

The Quality Forms and the health and safety templates stop being documents to print and become forms that fill in on a phone, output a PDF and file themselves.

19 requirements, and when each one is complete.
RefWhat is deliveredWhen
M7.48Microsoft 365 and SharePoint integration, bulk legacy migration utilities, controlled client collaboration and structured reporting or API export.Months 1 and 2
M7.12SharePoint or Viewpoint style expandable project folder hierarchy with centrally governed primary folders and useful subfolders.Months 1 and 2
M7.2Document owner, status, revision, issue date, review date and approval history.Months 1 and 2
M7.1Central controlled document library with current and superseded version control.Months 1 and 2
M7.3Configurable categories and searchable controlled document register.Months 1 and 2
M7.20Clear current version, document status and previous version history.Months 1 and 2
M7.40Permission controlled visibility of revision summaries, internal notes and document review comments.Months 1 and 2
M7.4Create revision from current document and controlled publication and supersession.Months 3 and 4
M7.21Project document review and approval workflow where configured.Months 3 and 4
M7.22Issue and distribution history and acknowledgement capability.Months 3 and 4
M7.34Full document and record audit trail.Months 3 and 4
M7.31Project level search plus authorised cross project Project Records search from the primary Documents and Forms workspace.Months 3 and 4
M7.19Fast upload, drag and drop and smart filing prompts.Months 3 and 4
M7.23Digital Forms Library with controlled template versions.Months 5 and 6
M7.24Core digital form builder with conditional logic, photos, files, signatures and auto populated project data.Months 5 and 6
M7.7Primary navigation Documents and Forms workspace providing company level Controlled Documents, Digital Forms, Project Records, reviews and approvals.Months 5 and 6
M7.25Draft save, autosave, submission lock and controlled amendment for completed forms.Months 5 and 6
M7.26Automatic PDF record output where required.Months 5 and 6
M7.27Automatic filing of completed forms to the correct project category.Months 5 and 6

Alongside these, and already inside the same plan:

04

What is still in Mango at month 6

Three of the five. Their briefs are written and they are good briefs, but none of them sits inside what has been agreed, so none of them is promised here.

Audits and inspectionsStill in Mango · the audit programmeStill in Mango at month 6. Module 3 is written but is not inside the agreed scope.
ImprovementsStill in Mango · the improvement registerStill in Mango at month 6. Module 5 is written but is not inside the agreed scope.
Incidents and near missesStill in Mango · 680 recordsStill in Mango at month 6. Module 4 is written but is not inside the agreed scope.

And four items from the documents brief that move to the second half

Moving the document work to the front of the term means it has to fit the front of the term. These four are the ones that give way, and they are refinements rather than capabilities.

M7.49Role based Controlled Document views for administrators and standard users.Second half
M7.5Prominent Documents and Records workspace available from every project profile.Second half
M7.38Controlled printable versions of digital forms retaining branding and version.Second half
M7.35Admin configuration for categories, metadata, review routes and retention rules.Second half

05

After the six months

Sequence, not a promise. The first two are inside the agreement already made. The third is a separate conversation and is shown so that nobody has to guess at it.

Month 6

Controlled documents out of MangoAll 829 documents live in a controlled library McConnell own, with the forms engine behind them. Two of Mango's five functions replaced.

Month 12

The Worker Safety PassportThe second half of the agreed term completes the training module: the passport, the learning engine, competence assurance and formal authorisations. All of it beyond anything Mango does.

Month 24

Mango darkAudits and inspections, improvements and actions, and incidents with the 680 records migrated. That is a second agreement, sized but not yet scheduled.

06

How it reaches people

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.

The one thing we need from McConnell

A full export of the Mango register. The migration is the first thing built, in month 1, so this is the only external dependency in the whole six months and it is worth settling before the clock starts. The register review the controlled documents brief asks for can then run alongside the build rather than blocking it.