THE INTELLIGENT EPC LEADERSHIP PROGRAMME
The contractor that can explain its delivery.
30 Sessions · 25 Minutes Per Day · Six Weeks · Free · For leaders in Nigeria’s engineering, procurement and construction sector
Hello — I am Coach Ritchie. I am the AI assistant for this programme. Ritchie Wingo built me, and your work is marked against the rubric he published; anything that falls below the mark to continue, he reviews himself, because that is the point at which a person needs help rather than a score. I am here for the moments in between, when the steering committee meets on Monday and you want to argue a point through with someone first.
Thirty sessions, twenty-five minutes a day, six weeks. Engineering reports most documents issued, procurement most orders placed, construction thousands of hours worked, finance substantial revenue recognised — and nobody can say when a usable system will be handed over. AI can examine document relationships, forecast late supply and prepare a decision brief. It can also make the confusion more convincing. An intelligent EPC company therefore begins with a delivery discipline, and AI becomes part of that discipline.
Every assignment is about your company and one decision chain between commitment and collected cash, and every assignment comes back with a written letter: what holds up and why, and where something is thin, exactly where to look. By Session 30 you will hold a signed 90-Day Intelligent EPC Programme for that decision chain.
Ask me anything as you work and I will help you think it through, but I will not write your plan for you, I do not give investment, legal or engineering advice, and I switch myself off while you sit a quiz or an exam.
There is nothing to buy and no licence key to redeem. You sign in with your Google account so that your work can be marked and returned to you, your progress page follows you between devices, and your certificate can be issued in your own name.
With your Google account. Name, email, the company you work for and your role — that is the whole enrolment.
The project that looks healthy and the six frameworks. Name your company and the one decision chain you will carry.
Twenty-five minutes, then one written assignment. It is marked against a published rubric and comes back as a letter.
You assemble and sign your ninety-day plan, sit the final, and your certificate is issued.
Already started? Open my progress page → · Just looking? Read Week 1 →
This programme assumes you are not a data scientist and do not intend to become one. It ends with you able to ask of any AI proposal what decision it changes, who owns the action, what evidence shows it worked — and to choose a simpler method, or stop, when that is the better answer.
A decision portfolio rather than an application catalogue, the commitment chain, and evidence preserved as it was at the time of decision.
Match the method to the question and govern the use rather than the model name, with explicit approval conditions.
Estimate integrity, contract responsibility boundaries, the design basis and the consequence of a revision.
Qualification matched to consequence, long-lead forecasting, traceability, logistics and Nigerian content.
Readiness as a conjunction, productivity, schedule and cost, HSEQ and a usable system at handover.
Event evidence before entitlement, client information boundaries, and release on a stated claim.
Daily portal monitoring, PSR completeness and coaching, and quote preparation and completeness review.
The intelligent project review, a scorecard that leads to decisions, and the ninety-day programme.
| It is written for | It is not written for |
|---|---|
| Leaders of Nigerian oil and gas EPC contractors — managing directors, project directors and heads of engineering, procurement, construction and commissioning | Engineers looking for model-building or coding work — that is a different course |
| Commercial, finance, HSEQ, business-development and technology leaders whose decisions the delivery model depends on | Anyone looking for investment, legal, contractual or engineering advice on a specific project |
| Clients, subcontractors, fabricators, vendors and consultancies who need to understand how an EPC contractor’s commitments are made | Anyone wanting a certificate without writing about a real company |
| Executives who sign bids, approve recovery plans or answer to a board for project delivery | Anyone expecting twenty minutes of video and a pass |
This programme does not end in a folder of notes. In Session 1 you name your company, its place in EPC delivery and one decision chain between commitment and collected cash, and every session after that writes one section of a single document — your 90-Day Intelligent EPC Programme — around it. By Session 30 you assemble and sign it. Written properly, it is the paper you table at your next executive committee or board meeting.
| Week | Sections you write |
|---|---|
| Week 1 Leadership and the Enterprise Foundation | 1. Section 1 — Our company, the one decision chain we will carry, and where its loop breaks. 2. Section 2 — The commitment, the portfolio entry and the board's evidence. 3. Section 3 — The business specified, the Nigerian conditions modelled and the commitment chain traced. 4. Section 4 — Identities, the state at decision time, reconciliation and the source register. 5. Section 5 — The method that fits our decision and how it would be evaluated. |
| Week 2 Governance, Tendering and the Design Commitment | 6. Section 6 — The governed use, its approval conditions and its assurance argument. 7. Section 7 — What we agree to carry, the estimate basis, the modelled exposure and the bid record. 8. Section 8 — The agreement, the promise tracked through interfaces and the contract assistant's test. 9. Section 9 — The engineering problem, configuration and bounded surrogate models. 10. Section 10 — The revision followed, checking versus generation and the engineering output contract. |
| Week 3 Constructability, Procurement and Supply | 11. Section 11 — Constructability, the digital model's purpose and its value through intervention. 12. Section 12 — The requirement, qualification matched to consequence and the procurement advisory. 13. Section 13 — The long-lead forecast, the response economics and technical control in recovery. 14. Section 14 — Traceable identity, executed inspection and arrival tracked to usability. 15. Section 15 — Capability by design, observable outputs and evidence that matches the claim. |
| Week 4 Construction, Commissioning and Acceptance | 16. Section 16 — Executable work, readiness as a conjunction and a bounded release service. 17. Section 17 — Productive output measured, the work system changed and competence preserved. 18. Section 18 — Delivery logic, stated assumptions, a common scope and the forecast of remaining work. 19. Section 19 — Support for the management system, meaningful leading indicators and their limits. 20. Section 20 — The usable system, accepted completion states and evidence kept with configuration. |
| Week 5 Claims, Trust, Validation and Finance | 21. Section 21 — The event preserved, its consequence connected and the review pack specified. 22. Section 22 — Information boundaries, retrieved content as data and provider exit. 23. Section 23 — The claim, the dataset, the response chain and the explicit threshold. 24. Section 24 — Competent owners, demonstrated competence, honest incentives and succession. 25. Section 25 — Profit and funding separated, currency exposure and the benefits ledger. |
| Week 6 The Author's Practices and the Ninety Days | 26. Section 26 — Monitoring with a source basis and a digest that leads to decisions. 27. Section 27 — The report structure, real completeness and coaching the action. 28. Section 28 — The visible commitment, the requirement-to-quote matrix and complete pricing. 29. Section 29 — The integrated position, the weekly rhythm and a scorecard that leads to decisions. 30. The signed 90-Day Intelligent EPC Programme. |
This programme is free, and nothing is upsold to you inside it. When you finish, you receive an ERW CommandEPC certificate of completion in your own name — issued on a pass, not on attendance.
| To receive it | What that means |
|---|---|
| Every assignment passed | Sessions 1 to 29, each marked at 70 or above against its published rubric. Work below the mark comes back with what to fix; resubmit and the new mark replaces the old one. |
| The capstone passed | Your signed 90-Day Intelligent EPC Programme, Session 30, marked at 70 or above. |
| The Final Exam passed | Fifteen questions, three of them rebuilt from your own earlier mistakes, at 70 or above. |
The certificate is emailed to the Google address you signed in with. It certifies completion of an ERW leadership programme; it is not a professional licence, an engineering qualification or a university award.
Only people who have finished the programme can write one — the Session 30 capstone passed and the marked Final passed, both recorded by the server rather than by anyone’s say-so. They are shown exactly as written, never solicited and never edited.
One session a day, twenty-five minutes. Each one teaches part of the doctrine and makes you use it on your own company.
Every session ends in a written assignment — a diagnosis, a value case, a pilot design, a plan section. Four hundred to nine hundred words.
Against the rubric printed under the assignment. A written letter comes back, usually within minutes.
Session 30 assembles twenty-nine sections into one document, then the final exam — three of whose questions are rebuilt from your own mistakes.
No mystery, and no waiting days for a mark. Here is the whole loop.
One document per session — Word or Google Docs — with the first line reading Session: N. Your own company, your own numbers.
Against that session’s published rubric, criterion by criterion. The same rubric every time, for everybody.
Not a score — a letter naming what holds up, what is asserted without evidence, and exactly where to look to fix it.
Your mark joins your progress page and the corrected section goes into your plan, so Session 30 is assembly rather than writing.
An illustration of the letter format, using Session 3’s real rubric.
| Criterion | Awarded |
|---|---|
| Specifies the contract arrangement and responsibility-matrix items from executed terms, not the title | 24 / 25 |
| Models the project conditions relevant to the decision, separating verified from assumed | 19 / 25 |
| Traces all six states with an owner and record per transition, and names the break | 20 / 30 |
| Names a real current weakness in how states are merged or backlog is classified | 16 / 20 |
Six weeks. Five sessions a week, twenty-five minutes each, at whatever pace your diary allows. Every session ends in one written assignment about your own company, and every assignment becomes a section of your ninety-day plan.
Thirteen papers, marked the moment you submit, every question returned with the reasoning behind it. Six pop quizzes of five questions, six practice exams of fifteen, and a fifteen-question final. You are never left to guess when to sit one: the session that opens a paper says so, prints the paper beside its assignment, and flags itself on the session tab — and your progress page always names the paper due now. Closed book, no notes, and Coach Ritchie switches himself off while you sit one. Pass mark 70 — and you may resit the practice papers as often as you like.
5 questions · after Session 3
15 questions · after Session 5, closing Week 1
5 questions · after Session 8
15 questions · after Session 10, closing Week 2
5 questions · after Session 13
15 questions · after Session 15, closing Week 3
5 questions · after Session 18
15 questions · after Session 20, closing Week 4
5 questions · after Session 23
15 questions · after Session 25, closing Week 5
5 questions · after Session 28
15 questions · after Session 29, before the final
15 questions · in Session 30
Twenty-nine sections written one per session, assembled and signed in Session 30: the decision chain you carry and where its loop breaks, the mandate, operating model, evidence and governance behind it, tendering, contracts and engineering, procurement, fabrication and supply, construction readiness, schedule, cost and commissioning, claims, security, validation, people and finance, the three practices, and your ninety days stage by stage.
The Intelligent EPC — A Leadership Doctrine for AI in Nigerian Engineering, Procurement and Construction. A reader’s toolkit of six frameworks and thirty-one chapters in six parts: leadership and the enterprise foundation; engineering and the design commitment; procurement, fabrication and supply; construction, commissioning and acceptance; trust, validation and people; and capital and the leadership execution. An EPC company earns trust by turning commitments into technically sound work, accepted systems and collected cash.
These 30 sessions teach the doctrine and make you use it. The book carries what twenty-five minutes cannot: every chapter in full with its sources, an integrated project walkthrough, a casebook of ten decisions, eleven appendices and a technical annex — including the practices the author has implemented: daily tender and permit monitoring, AI review of project status reports, and quote preparation and completeness review.
Nothing in this programme depends on buying it. Every session, paper and certificate is free whether you own the book or not.
The whole programme on one printable page — the six frameworks, the common decision record, the AI use and pilot charter, and the ninety days stage by stage. Keep it beside you from Week 1.
The document every assignment is written in — opens in Word or Google Docs, with the first line already correct.
Read the first session before you sign in, and decide for yourself whether the rest is worth six weeks.
Your marks, your letters, your plan sections and your paper results, in one place.
| Question | Answer |
|---|---|
| Is it really free? | Yes. No card, no key, no paid tier. The certificate is free too. The book is available separately for anyone who wants the full chapters, figures and sources, and nothing in the programme depends on it. |
| How much time, honestly? | Twenty-five minutes of reading and thirty to sixty minutes of writing per session. Call it twelve to fifteen hours over six weeks, and rather more if you do the capstone properly. |
| Do I need a technical background? | No. The technical sessions teach you what to ask, not how to build. You need a real company, a real decision, and the willingness to look at both honestly. |
| Is this specific to EPC? | Yes. It is written for Nigerian oil and gas engineering, procurement and construction — tendering, design, supply, fabrication, construction, commissioning, contracts, quality and finance. Every session sets a case at the workfront — the drawing, the package, the equipment, the test — beside the same decision in the commitment: the contract, the quote, the schedule promise, the invoice and the cash. |
| Is this investment or legal advice? | No. It is an operating doctrine for leaders. Figures and regulator facts are taught only as the book states and sources them. |
| Can my leadership team do it together? | Yes, and it works better that way — but each person signs in and submits their own work, because the plan is only useful if it is argued over. |
| What if I miss a week? | Nothing happens. There are no cohort dates and no deadlines. Your progress waits for you. |
| Who marks it? | It is marked against R. Wingo’s published rubric, criterion by criterion, the same way every time. Anything that comes out below the mark to continue, he reviews himself before it reaches you. Coach Ritchie helps you think; he does not mark and he does not write your plan. |