THE INTELLIGENT EPC LEADERSHIP PROGRAMME
The contractor that can explain its delivery.
30-Session Programme · 25 Minutes Per Day · Free · For leaders in Nigeria’s engineering, procurement and construction sector
WEEK 2 OF 6 · GOVERNANCE, TENDERING AND THE DESIGN COMMITMENT · SESSIONS 6–10 · WORK AT YOUR OWN PACE
Part One · Leadership and the Enterprise FoundationSESSION 6
Authority, Governance and Technical Assurance
Why This Matters
Last week you built the foundation: the decision chain, the commitment behind it, the operating model, the evidence and the method that fits. This week the decision meets authority. The same model can draft a harmless covering letter and recommend which procurement exceptions need review. Those are two uses with different consequences, and governing them by the product name hides the difference. Today you write the use register entry for your decision, name the authorities who must each accept it, set approval conditions before any pilot produces results and sketch an assurance argument your board can challenge. You also decide how the service is changed, suspended and withdrawn.
25-Minute Module
0:00 – 5:00
Govern the use, not the model name
- The plain idea first. A model is a capability. A use is that capability applied to a stated purpose, for stated users, on stated data, with stated permissions. The same model can support low-consequence drafting and high-consequence recommendations, so governance attaches to the use.
- Maintain a use register. Each entry records purpose, users, data population, outputs, permitted actions, excluded actions, owner and approved environment. Review a change in purpose even when the underlying model remains unchanged.
- THE DOCTRINE
Govern the use rather than the model name. A change in purpose needs review even when the model is exactly the same.
- NIST's voluntary AI Risk Management Framework (NIST AI RMF 1.0, NIST AI 100-1, January 2023) organises risk work around Govern, Map, Measure and Manage. The book uses that structure as a reference for organising responsibility. A project still needs its own evidence and release decision.
- This is the Autonomy Ladder from Session 1, written down. The excluded actions field is where you record that permission to draft a technical query is not permission to send it to the client.
If your register lists products rather than uses, you are governing the vendor's invoice, not the work.
5:00 – 10:00
Separate authorities, each accepting something specific
- A consequential use touches several competences, so the book establishes several distinct authorities, each accepting something specific.
Authority What it accepts or resolves Service owner Functionality and support Information owner The permitted processing Relevant engineering authority Technical use Commercial and legal owners Assessment of contractual consequences Operations Any interface with a live facility Finance Economic claims Executive sponsor Resolves priorities without overriding competence through enthusiasm - The last row deserves a moment. The sponsor resolves priorities between the other owners. The sponsor does not accept a technical use because the programme is behind. Enthusiasm is not a competence.
- When you fill this table for your own decision, an empty row is a finding, not a formality. Write it down as one.
Ask each owner what exactly they are accepting. If two give the same answer, one acceptance is missing.
10:00 – 15:00
Write the approval conditions before the results
- Define release conditions before the pilot produces results. Once a team has seen attractive numbers, it is hard to set a threshold that is independent of them.
- Conditions may include source traceability, acceptable errors by severity, permission enforcement, useful response time, reviewer capacity and recovery. Choose thresholds according to the task and consequence; no universal accuracy percentage fits every EPC use.
- THE DOCTRINE
Some conditions are gates. A service that discloses another client's restricted drawings should not proceed because its time savings are attractive.
- This is the Value versus Risk Map at work. Mandatory conditions stay separate from tradeable preferences, and financial benefit cannot offset an unacceptable engineering, legal or safety condition through a weighted average.
- Keep the failure categories visible. A drafting tool that invents inspection evidence has failed a different requirement from one that produces awkward prose. A single blended error rate hides the failure that matters.
Date the conditions and file them before the first result arrives. That date is part of your evidence.
15:00 – 20:00
The assurance argument, and how the service is changed or stopped
- For a consequential application state four things: the claim, the supporting evidence, the argument that connects them and the limitations. The book's example claim: the service may recommend which procurement exceptions require review, within one defined package population, using specified current records, while purchase approval remains manual.
- Support it with representative evaluation, challenge cases, shadow operation, permission tests and a workable fallback. Explain why the evidence applies to the intended population and identify what it does not establish. This is a management assurance structure, not a formal safety certification.
- AT THE WORKFRONT · THE WORKED CASE
- Workfront. A fictional EPC contractor's exception service correctly flags a late package, but the alert reaches someone without authority to act. A competent reviewer with insufficient time becomes a nominal control.
IN THE COMMITMENT · THE PARALLEL- Commitment. Seen from the commercial side: after an outage the support team cannot restore the source index, so staff keep using an obsolete answer. The same loop seen twice: assurance must challenge the workflow as well as the model.
- Reassess material changes in model, prompts, documents, interfaces, users and task. A vendor update can alter behaviour even if the product name remains constant. Preserve the previous accepted configuration and use a controlled release process.
- Define triggers for suspension: material unsupported claims, permission failure, unexpected execution, stale critical sources and unmanageable review queues. Investigate affected decisions, not merely the model log, and resume only after the responsible owners accept the correction.
- THE DOCTRINE
Withdrawal should be a normal operating capability. A service that cannot be stopped without interrupting essential delivery has created dependence that deserves separate assessment.
Know, before launch, how staff continue work, what records remain and who tells the affected teams on the day you switch it off.
20:00 – 25:00
What the board should ask, and your wrap
- The book gives the board five questions. Which uses have authority to act? Which mandatory conditions remain unresolved? What material incidents occurred? What changed after review? Which applications have been withdrawn?
- Policy documents alone cannot answer them. The evidence lies in decisions, controls exercised and consequences corrected. An intelligent EPC company makes those records accessible to the people who carry responsibility.
- If your company has never withdrawn a service, ask honestly whether that reflects success or the absence of any way to withdraw one.
- Before you close: write the use register entry for your Session 1 decision, the authorities who must each accept it, the approval conditions with the gates marked, and a short assurance argument. That is Section 6 of your 90-Day Intelligent EPC Programme.
Governance you can evidence from records is worth more than governance you can describe from a policy.
Key Terms
Use register
The record of each governed use: purpose, users, data population, outputs, permitted actions, excluded actions, owner and approved environment. A change in purpose needs review even if the model is unchanged.
Mandatory gate
A necessary condition for the proposed use or activity. An attractive average score or a time saving does not compensate for its failure.
Assurance argument
The claim, supporting evidence, argument and limitations for a consequential application, including what the evidence does not establish. A management structure, not a formal safety certification.
Suspension trigger
A defined event that stops a service, such as material unsupported claims, permission failure, unexpected execution, stale critical sources or unmanageable review queues.
Self-Check — Before You Submit
1. A fictional EPC contractor's assistant, approved for drafting internal technical queries, is now proposed for preparing client-facing commercial notices. The vendor confirms the model is unchanged. What should the head of commercial require?
- A. No new review, because the model is unchanged
- B. A review of the changed use, with its own register entry, owners and approval conditions
- C. A higher accuracy percentage on the original drafting test
- D. Approval from the executive sponsor alone
B. A review of the changed use, with its own register entry, owners and approval conditions — A change in purpose needs review even when the model is identical. The unchanged model is the trap: a commercial notice carries a different consequence from an internal draft.
2. Which of these is a gate rather than a tradeable condition?
- A. Response time slightly slower than the team hoped
- B. Drafts that read awkwardly
- C. Disclosure of another client's restricted drawings
- D. A reviewer's preference for a different layout
C. Disclosure of another client's restricted drawings — Disclosing another client's restricted drawings is a gate: attractive time savings cannot buy it back. Awkward prose is a real failure, but a different and tradeable one, which is why the failure categories must stay visible.
3. A suspension trigger fires because a critical source has gone stale. What should the investigation cover?
- A. The affected decisions, not merely the model log
- B. The model log only
- C. The vendor's release notes
- D. Only incidents already reported to the board
A. The affected decisions, not merely the model log — The book asks you to investigate affected decisions, because the harm sits in what people did with the answer. The model log is tempting because it is easy to read, but it cannot show which commitments relied on the stale source.
Today’s Assignment
Write Section 6 of your programme: the governed use, its approval conditions and its assurance argument, with change, withdrawal and the board's questions.
- Write the use register entry for your company's decision chain from Session 1: purpose, users, data population, outputs, permitted actions, excluded actions, owner and approved environment.
- Name each authority by role (service, information, engineering, commercial and legal, operations, finance and the executive sponsor) and what exactly each accepts. Mark any row your business cannot fill today.
- List your approval conditions, with thresholds chosen for the task and consequence, written before any result. Mark which are gates.
- Sketch the assurance argument: claim, evidence, argument and limitations, and what the evidence does not establish.
- State the suspension triggers, who suspends, how staff continue work after withdrawal, and your company's honest answers today to the five board questions.
- The honest part: where your company governs a product name rather than a use, or has no way to stop a service. If no AI is in use yet, that is normal; work from the proposal in front of you. Aim for 400 to 900 words.
YOUR 90-DAY PLAN
Section 6 — The governed use, its approval conditions and its assurance argument.
How this is marked — the rubric
| Writes a complete use register entry for one use, including excluded actions | 25 |
| Names each authority by role with what it accepts, and states the gaps honestly | 20 |
| Sets conditions before results, with gates marked separately from tradeable conditions | 25 |
| States claim, evidence, argument and limitations, plus specific suspension and withdrawal arrangements | 30 |
| Total · pass mark 70 | 100 |
Submitting session 6
Write your answer in Word or Google Docs. The first line must read
Write your answer in Word or Google Docs. The first line must read
Session: 6, or the submission is refused. Upload the Word file (.docx), or switch to the Google Doc tab and paste your document’s share link.Marked against the rubric above and returned as a written letter, saved to your progress page. Do not submit until you have passed the self-check above.Capabilities Covered
Use registersSeparated authoritiesApproval gatesAssurance argumentsControlled withdrawal
Part Two · Engineering and the Design CommitmentSESSION 7
Opportunity Selection, Tendering and Estimate Integrity
Why This Matters
The bid decision sets much of a project's future exposure before anyone mobilises. A proposal can look attractive because exclusions are omitted, quantities are immature, vendor quotes are incompatible or funding assumptions are unrealistic. Today you learn what a bid should make visible, how a traceable estimate is built, why margin and markup give different prices, and how to model exposure instead of hiding it in contingency. Then we open the book's teaching project, H-01, and recompute its initial planning cost model. If your company is a client, vendor, subcontractor or consultancy, read each step from your side of the contract.
25-Minute Module
0:00 – 4:00
What the contractor agrees to carry
- The plain idea: a bid is the set of commitments the company will carry for the life of the project. AI should improve what the contractor agrees to carry, not merely the speed of producing the offer.
- Create a bid basis: scope boundaries, deliverables, quantity maturity, schedule assumptions, subcontract strategy, quote validity, currency basis, tax treatment for review, client interfaces and acceptance criteria. Record unresolved points and the person who can accept each exposure, and keep qualifications linked to the commercial offer so they survive document preparation.
- Use AI to compare tender requirements with the response, find missing attachments and reveal inconsistent promises. Require evidence for claims about personnel, facilities, equipment ownership and previous work.
- THE DOCTRINE
A plausible capability paragraph is not evidence of capability. Faster tender drafting helps only when exclusions, quantity maturity, quote compatibility and funding assumptions remain visible.
Ask who in the room can accept each unresolved exposure.
4:00 – 9:00
Build the estimate from quantities, and name margin correctly
- A traceable estimate separates quantity, unit cost, productivity, indirect cost, contingency and margin, and shows how each assumption changes as the design matures. The GAO Cost Estimating and Assessment Guide (GAO-20-195G, March 2020) is a public reference for structured estimates and uncertainty analysis; it does not set a Nigerian EPC price.
- Margin is profit as a share of the selling price. Markup is profit added as a share of cost. The same fifteen per cent gives two different prices. The book's assumed teaching example, recomputed:
Step (assumed) Calculation Result Direct fabrication cost 1,200 tonnes × ₦1.8 million per tonne ₦2.16 billion Base cost ₦2.16 billion + ₦240 million indirects ₦2.40 billion Cost provision ₦2.40 billion + ₦180 million risk allowance ₦2.58 billion Price at 15% gross margin of sales ₦2.58 billion ÷ 0.85 Approximately ₦3.035 billion Price at 15% added to cost ₦2.58 billion × 1.15 ₦2.967 billion, a sales margin of approximately 13.04% - Check: ₦2.967 billion less ₦2.58 billion is ₦387 million, about 13.04% of price. These assumed values are not market rates; they exclude taxes, financing and contract-specific adjustments, and finance must verify the actual pricing basis.
When someone says fifteen per cent, ask: of price or of cost.
9:00 – 14:00
Model the exposure, and the bid committee record
- Separate quantity uncertainty, unit-rate uncertainty and discrete risks. If a design change can increase both quantity and installation duration, model that relationship: independent ranges can understate joint exposure.
- Do not count one event in the base estimate, a contingency percentage and a risk register allowance. State whether each amount covers expected expenditure, an uncertainty provision or a contractual price decision.
- THE DOCTRINE
Contingency is neither guaranteed profit nor permission for uncontrolled spending.
- AI can cluster prior estimate errors, but historical costs need adjustment for scope and basis before they become a training target.
- The bid committee record presents a base, downside and funding case: peak cash need, unpriced obligations, material exclusions, decisions required before submission, and qualifications the client may reject with the consequence of removing them. The committee should be able to decline or condition an attractive bid.
If no one can say which line holds a given risk, assume it sits in two of them.
14:00 – 21:00
The teaching project H-01: scope before the offer, and the cost model
- The book labels H-01 an original hypothetical teaching scenario: invented inputs, not facts about a Nigerian company, contract, verified price or completed project, with deliberate errors. It assigns Nigeria no universal permit, consumption, productivity or currency assumptions. Project H-01 replaces a utility-water pump and control package at an operating gas facility, from engineering to accepted testing and handover; the client retains the operating interface. Assumed planning price NGN 160 million; initial cost provision NGN 125 million; sixteen calendar weeks from notice to proceed; one installation crew. None is a benchmark.
- An AI service extracts hypothetical requirements R-01 to R-05 into a register: the pump and control package; foundations and installation; the client's operating interface; the agreed tests and handover evidence; and the accepted schedule and commercial conditions. Reviewers accept the interpretation before it becomes the quote basis.
- AT THE WORKFRONT · THE WORKED CASE
- Workfront. The equipment offer excludes one required document, so the requirement-to-response comparison marks R-04 only partly covered. Procurement obtains an accepted supplier response, or the bid retains a clear unresolved decision. It is a requirement gap, not an arithmetic error, and a model reading only the draft might miss it.
IN THE COMMITMENT · THE PARALLEL- Commitment. The AI draft promises an unqualified completion date while the operating access date is still provisional. The reverse check from promises to approved basis flags it, and commercial leadership revises the offer. A draft containing a date does not make the requirement covered.
Cost component Assumed provision, NGN million Evidence needed on a real project Engineering 12 Scope and reviewed effort basis Purchased equipment 55 Accepted current offer and scope Bulk materials 20 Quantity and delivered-rate basis Installation 16 Accepted method, resources and productivity Testing and handover 7 Required activities and evidence Site overheads 7 Duration and allocation basis Financing 3 Actual funding terms and timing Risk provision 5 Defined exposure without duplication - The lines sum to NGN 125 million. Price less provision is NGN 35 million; the pricing-model margin is 35 ÷ 160 = 21.875%. Not a claim about final profit: scope, expenditure, tax, finance and contract treatment can alter it. The quote tool computes totals deterministically; generative AI drafts narrative from the accepted basis, with no authority to invent availability claims or transmit the offer.
A more fluent quote cannot resolve a missing equipment offer.
21:00 – 25:00
Where each uncertain item sits, and your wrap
- The H-01 bid review asks whether each uncertain item sits in the base, the risk provision or an explicit qualification. The AI service can identify apparently duplicated allowances and unsupported rates; finance and commercial reviewers establish the accepted treatment. After award, transfer accepted assumptions into the project mandate and preserve rejected ones for learning.
- THE DOCTRINE
A tender intelligence service earns its value when it improves the contract the business can deliver, rather than merely increasing the number of bids submitted.
- Before you close: write what your company agrees to carry on one live or recent bid, its estimate logic, where each exposure sits and the bid committee record. That is Section 7 of your 90-Day Intelligent EPC Programme. A subcontractor, vendor or consultancy writes it for its own quotation; a client for the tender it evaluates.
A bid declined on a clear record can be worth more than one won without it.
Key Terms
Bid basis
The scope, quantity maturity, schedule, quote validity, currency, tax treatment for review, interfaces and acceptance criteria behind an offer, with unresolved points and who can accept each exposure.
Margin and markup
Margin is profit as a share of price; markup is profit added as a share of cost. In the book's assumed example, 15% on cost gives approximately 13.04% margin.
Contingency
An amount whose stated purpose is expected expenditure, an uncertainty provision or a contractual price decision. Neither guaranteed profit nor permission for uncontrolled spending.
Bid committee record
The base, downside and funding case with peak cash need, unpriced obligations, material exclusions and qualifications the client may not accept.
Self-Check — Before You Submit
1. In the book's assumed teaching example, the cost provision is ₦2.58 billion. A director prices the bid by adding 15% to cost. What sales margin results?
- A. 15%
- B. Approximately 13.04%
- C. Approximately 17.65%
- D. Approximately 21.875%
B. Approximately 13.04% — ₦2.58 billion × 1.15 is ₦2.967 billion, and ₦387 million of profit on that price is about 13.04%. Fifteen per cent is the trap: it is the markup on cost, not the margin on sales.
2. A fictional EPC contractor's bid team carries one site-access risk in the base estimate, the contingency percentage and the risk register, to be safe. What should the bid committee require?
- A. Accept it, because more provision is always prudent
- B. Remove the risk entirely to sharpen the price
- C. Move it all into margin
- D. Hold the event once, stating what each amount covers
D. Hold the event once, stating what each amount covers — The book forbids counting one event in the base, a contingency percentage and a risk register allowance. Extra provision looks prudent but misstates exposure and price.
3. In the H-01 walkthrough, why is R-04 marked only partly covered?
- A. The quote total was miscalculated
- B. The client rejected the test plan
- C. The equipment offer excludes one required document
- D. The draft promised an unqualified completion date
C. The equipment offer excludes one required document — The supplier's offer excludes a required document: a requirement gap, not an arithmetic error. The unqualified completion date was a separate flag.
Today’s Assignment
Write Section 7 of your programme: what your company agrees to carry, the estimate basis, the modelled exposure and the bid committee record.
- Choose one live or recent bid or quotation in your decision chain. Write its bid basis and the unresolved points, each with the role that can accept the exposure.
- Set out the estimate logic, separating quantity, unit cost, productivity, indirect cost, contingency and margin, and state whether you price on margin or markup.
- Show where exposure sits by type, with linked risks modelled together and no event counted twice.
- Draft the bid committee record: base, downside and funding case, peak cash need, unpriced obligations and exclusions.
- The honest part: where your company hides exposure in contingency or lets capability claims stand without evidence. If no AI is in use yet, that is normal. Aim for 400 to 900 words.
YOUR 90-DAY PLAN
Section 7 — What we agree to carry, the estimate basis, the modelled exposure and the bid record.
How this is marked — the rubric
| Bid basis names each unresolved point with the role that can accept the exposure | 25 |
| Estimate logic separates the six elements and names margin or markup correctly | 25 |
| Exposure is modelled by type, linked risks are joined and nothing is counted twice | 25 |
| Bid committee record includes downside, funding case, peak cash need and qualifications at risk | 25 |
| Total · pass mark 70 | 100 |
Submitting session 7
Write your answer in Word or Google Docs. The first line must read
Write your answer in Word or Google Docs. The first line must read
Session: 7, or the submission is refused. Upload the Word file (.docx), or switch to the Google Doc tab and paste your document’s share link.Marked against the rubric above and returned as a written letter, saved to your progress page. Do not submit until you have passed the self-check above.Capabilities Covered
Bid basis disciplineMargin and markupExposure modellingBid committee recordsScope before offer
Part Two · Engineering and the Design CommitmentSESSION 8
Contract Intelligence and Responsibility Boundaries
Why This Matters
Once a bid becomes a contract, commitments stop being proposals and become obligations with triggers, deadlines and recipients. The danger this chapter addresses is not only the clause nobody read. It is also a condition lost in a summary, a promise nobody tracked across an interface, a notice sent through the wrong process, or an assumption that a client approval moved responsibility. Today you start from the executed agreement, track one promise through its interfaces, control who may communicate, keep design responsibility specific and write the test a contract assistant must pass before anyone relies on it. Then you watch the H-01 award become controlled objects. Pop Quiz 2 opens at the end of this session. If you are not the main contractor, read each step from your own side of the contract.
25-Minute Module
0:00 – 5:00
Start from the executed agreement
- Build a controlled contract set: the signed agreement, schedules, incorporated documents, amendments and authorised clarifications. The order of precedence, which document governs when two conflict, is established through competent review. Do not let an assistant infer precedence from file names or recency.
- Extract obligations into records with responsible party, action, trigger, deadline, notice recipient, evidence, approval and source location. Preserve conditions and exceptions. A clause requiring notice after a defined event should not become a generic calendar reminder detached from that event.
- THE DOCTRINE
The service can retrieve and compare language. Interpretation remains with authorised commercial and legal professionals.
- Where meaning is disputed, retain the dispute and its current treatment rather than force one answer into the operational database. A tidy record that hides a live disagreement is less accurate than an untidy one that shows it.
Ask to see the trigger behind every reminder. A date with no event attached is a guess.
5:00 – 10:00
Track promises through interfaces
- Client-supplied equipment, access, design inputs and utilities each need their own interface commitment, linked to the affected work packages and the latest useful decision date. The contractor's internal schedule cannot establish that the client has accepted an assumed interface date.
Interface matrix field The question it answers Obligation What was promised, and by which party Evidence Which record shows its current state Owner Who is accountable for it Consequence What happens to the affected work if it is late or wrong - Distinguish promised, confirmed, delivered and accepted. A supplier email stating that equipment has shipped is not a receipt. A client email approving a drawing may have conditions requiring additional work.
- THE DOCTRINE
When AI summarises correspondence, preserve the conditions. The important sentence may be the qualification at the end rather than the approval word at the beginning.
Read the last sentence of every approval first.
10:00 – 15:00
Authority to communicate, and responsibility that stays specific
- A draft notice can have commercial value. Sending it can create contractual consequences. Restrict submission to the authorised process and recipient, and record the final approved version, supporting evidence, transmission and receipt where relevant. This is the Autonomy Ladder at the contract boundary: drafting for review is not bounded execution.
- Do not automatically classify every site instruction as a compensable variation. Its treatment depends on authority, scope, contract terms and evidence; the appropriate output is a potential change requiring review, with source records and deadline exposure. Likewise, a late activity is not automatically an entitlement to an extension of time. Cause, criticality, notice, mitigation and actual contract provisions need assessment, and a language model's confidence settles none of them.
- If the contractor has design responsibility, define who accepts the design basis and who reviews calculations. If the client provides a design, identify the contractor's actual review and execution obligations. Avoid the generalisation that a client approval automatically removes contractor responsibility.
- AT THE WORKFRONT · THE WORKED CASE
- Workfront. A fictional fabrication subcontractor proposes a material substitution its engineers judge technically acceptable. The technical deviations register records it, but nobody has obtained commercial approval.
IN THE COMMITMENT · THE PARALLEL- Commitment. The reverse case: a fictional contractor's commercial team favours a cheaper substitution that the engineering authority finds technically unsuitable.
- One register, one rule. The technical deviations register is linked to contractual acceptance, and both dimensions must reach the authorised decision.
Before any notice leaves the building, ask who approved this version and through which process.
15:00 – 21:00
Test the contract assistant, then transfer the award
- A contract assistant's acceptance test uses questions requiring the correct clause, conditions, party and amendment. Include conflicting versions, scanned annexes, tables, omitted pages and questions the contract does not answer. Test that restricted documents cannot be retrieved by unauthorised users.
- THE DOCTRINE
Measure material omission separately from wording quality. A summary that removes a condition can be more damaging than a slow response.
- Include reviewer time, and whether the final approved position matches the source. The service should leave the business with a dependable obligation record and a controlled communication process, including the explicit cases where it cannot answer.
- Back to H-01, still assumed. The parties execute an agreement on the accepted scope after tender review, and the project director reconciles it with the final offer. The service prepares links from R-01 to R-05 to engineering deliverables, purchase packages, work packages, completion records and invoice conditions.
Teaching label Controlled object E-01 The controlled package design set P-01 The equipment package, including accepted documentation C-01 Civil work providing foundations W-01 Installation work connecting the physical scope to the completion system S-01 The completion system - R-03 links the client's operating interface to W-01; R-04 links the required tests and handover records to S-01. The evidence register keeps the original requirement, accepted interpretation, current source revision and owner for each object, so a later change propagates as a review request without allowing the assistant to approve the consequence.
An assistant that says it cannot answer is passing the test, not failing it.
21:00 – 25:00
Your wrap, and Pop Quiz 2
- If your company is not the main contractor, a client writes this for what it must supply and approve, a vendor or fabricator for its purchase order promises, a consultancy for the design responsibility it holds.
- Before you close: write one obligation record, one promise tracked through its interfaces, who may communicate, who holds design responsibility and the acceptance test for a contract assistant. That is Section 8 of your 90-Day Intelligent EPC Programme.
- Pop Quiz 2 opens now: five questions on Sessions 6 to 8, closed book. Sit it before Session 9, while governance, the bid and the contract are fresh.
The contract is the one document every function in your company is working to, whether they have read it or not.
Key Terms
Controlled contract set
The signed agreement, schedules, incorporated documents, amendments and authorised clarifications, with the order of precedence established through competent review rather than file names or recency.
Obligation record
Responsible party, action, trigger, deadline, notice recipient, evidence, approval and source location for one contractual obligation, with its conditions and exceptions preserved.
Interface matrix
Obligation, evidence, owner and consequence for each interface commitment, distinguishing promised, confirmed, delivered and accepted.
Technical deviations register
The record of departures and substitutions, linked to contractual acceptance, so that both technical suitability and commercial approval reach the authorised decision.
Self-Check — Before You Submit
1. A fictional EPC contractor's contract assistant summarises a client email as drawing approved. The email's final sentence asks for an additional support detail. What should the project director require?
- A. Record the drawing as approved and proceed
- B. Ask the assistant to re-summarise until the wording is clearer
- C. Treat the approval as conditional, preserve the qualification and route the additional work for review
- D. Ignore the final sentence, because approval was given first
C. Treat the approval as conditional, preserve the qualification and route the additional work for review — The book warns that the important sentence may be the qualification at the end rather than the approval word at the beginning. Recording a clean approval is the trap: the condition requires additional work and must survive the summary.
2. The site team receives an instruction from the client's representative. What is the book's appropriate output?
- A. A potential change requiring review, with source records and deadline exposure
- B. An automatic compensable variation
- C. An automatic extension of time claim
- D. Nothing until the monthly report
A. A potential change requiring review, with source records and deadline exposure — Treatment depends on authority, scope, contract terms and evidence, so the output is a potential change for review. Classifying it automatically as a compensable variation is tempting, and it is exactly the generalisation the book rejects.
3. In H-01, what does the evidence register for each controlled object allow a later change to do?
- A. Approve itself once the assistant matches it to a previous package
- B. Propagate as a review request without allowing the assistant to approve the consequence
- C. Overwrite the accepted interpretation with the latest revision
- D. Bypass the project director's reconciliation
B. Propagate as a review request without allowing the assistant to approve the consequence — Keeping requirement, interpretation, source revision and owner for each object lets a change reach the right reviewers. The assistant gains no authority to approve the consequence; letting it approve, or bypassing the reconciliation, is the error the walkthrough guards against.
Today’s Assignment
Write Section 8 of your programme: the agreement, one promise tracked through its interfaces and the contract assistant's acceptance test.
- For one live agreement in your decision chain, list your company's controlled contract set and say who established the order of precedence.
- Write one obligation record: responsible party, action, trigger, deadline, notice recipient, evidence, approval and source location, with its conditions.
- Track one promise through its interfaces using obligation, evidence, owner and consequence, and state whether it is promised, confirmed, delivered or accepted today.
- State who has authority to send notices, how a potential change and a potential extension of time are routed, and who accepts the design basis and reviews calculations.
- Write five acceptance-test questions for a contract assistant, including a conflicting version, a scanned annex and a question the contract does not answer, and how material omission is scored separately from wording.
- The honest part: where your business currently loses conditions in summaries or lets the wrong person send. If no AI is in use yet, that is normal; the test still defines what you would accept. Aim for 400 to 900 words.
YOUR 90-DAY PLAN
Section 8 — The agreement, the promise tracked through interfaces and the contract assistant's test.
How this is marked — the rubric
| Obligation record keeps trigger, deadline, notice recipient, source location and conditions | 20 |
| One promise is tracked through its interfaces with its current state and an owner by role | 25 |
| Communication authority and design responsibility are named specifically, not assumed | 25 |
| Acceptance test includes the hard cases and scores material omission separately from wording | 30 |
| Total · pass mark 70 | 100 |
Submitting session 8
Write your answer in Word or Google Docs. The first line must read
Write your answer in Word or Google Docs. The first line must read
Session: 8, or the submission is refused. Upload the Word file (.docx), or switch to the Google Doc tab and paste your document’s share link.Marked against the rubric above and returned as a written letter, saved to your progress page. Do not submit until you have passed the self-check above.ASSESSMENT NOW OPEN
Pop Quiz 2 — Governance, Tendering and Contracts opens now. Sit it before you start the next session — it is how you find out whether the doctrine landed, and the practice papers may be resat as often as you like.
Sit Pop Quiz 2 →Closed book, no notes, and Coach Ritchie switches himself off while you sit it.Capabilities Covered
Controlled contract setsObligation recordsInterface trackingCommunication authorityAssistant acceptance tests
Part Two · Engineering and the Design CommitmentSESSION 9
Front End Definition and the Design Basis
Why This Matters
An apparently successful calculation on the wrong duty remains an engineering failure, and the commitment built on it inherits the failure. This session is about the front end, where the design basis is set and where a leader can be shown a percentage of drawings issued instead of the state of the inputs. Today you learn to ask what problem engineering is solving and how mature its inputs are, to treat configuration as the set of physical and documentary states that belong together, to bound any surrogate model to the domain where it was validated, and to link every accepted requirement to the evidence that will verify it. Your decision is the stage approval itself: whether to release on actual maturity and residual exposure. If you are a client, vendor or consultancy, apply it to the design inputs you supply or receive.
25-Minute Module
0:00 – 5:00
Establish the problem engineering is solving
- Design begins with an accepted basis: duty, fluids, conditions, interfaces, site information, applicable standards and client requirements. The basis needs maturity and ownership, not simply a document title. Identify which inputs are confirmed, provisional or awaiting competent acceptance.
- An AI assistant can compare a specification, process description, equipment list and interface register for inconsistencies. It should produce a precise query with source locations and affected decisions. It should not select the most convenient operating condition and silently rewrite the basis.
- For a hypothetical gas package, a discrepancy between normal flow and design flow can affect equipment selection, utilities and commercial commitments. The correct response is to establish the approved duty and assess the consequences.
- THE DOCTRINE
An apparently successful calculation on the wrong duty remains an engineering failure.
Ask which inputs are still provisional before you ask how much of the design is done.
5:00 – 10:00
Configuration: which documents belong together
- Plain language first. A configuration is not the latest file. It is the accepted combination of physical and documentary states relevant to a design, installation, test or operation: this equipment, with these calculations, drawings and vendor data, at these revisions, with these approved departures. Two genuine documents at different revisions can each be correct and still not belong together.
- Define the baseline for each stage and the change process. Retain the design basis, calculation revisions, drawings, vendor data and approved departures that support a released configuration. A single latest-file folder cannot establish which documents belong together.
- A changed equipment package can affect loads, foundations, pipe connections, power demand and control interfaces. Use dependency records to identify the review set. AI can propose the dependencies; engineering accepts them.
- Hidden dependencies should become learning items when discovered. That is the learning stage of the Operating Intelligence Loop applied to design.
If your team cannot say which revisions were released together, you have files, not a configuration.
10:00 – 15:00
Surrogate models with bounded validity
- Plain language first. Some engineering calculations take time to run. A surrogate model is an approximation used in place of a more detailed model for a defined purpose and accepted domain; the book describes a learned approximation to an engineering model, so many options can be screened quickly. Think of an estimator's rule of thumb: dependable for the kind of job it was formed on, unreliable outside it.
- A surrogate is useful only within an accepted domain and error tolerance. Record the training range, physical constraints, excluded conditions and reference calculations used for validation.
- Test near boundaries and in adverse combinations, not only at typical points. Separate interpolation, within the represented domain, from extrapolation beyond it.
- THE DOCTRINE
A low average error can conceal a material error at the condition that sets equipment size.
- Retain the engineering model or competent calculation as the reference where required. A surrogate used for option screening has not been accepted for final design certification. When it flags an apparently attractive option, that option still needs the required technical evaluation.
Ask for the surrogate's training range before you ask for its accuracy.
15:00 – 21:00
Requirements, verification and the leadership decision
- Translate accepted requirements into a verification matrix. A fictional illustration for one package requirement:
Field Fictional entry Requirement The package meets the accepted design duty Source Accepted design basis, at its stated revision Responsible discipline Mechanical engineering Deliverable Equipment sizing calculation Method Calculation review Acceptance criterion As stated in the accepted basis Reviewer Named competent engineer Status Open until the actual evidence is accepted - A document's existence does not prove that it verifies the requirement. An assistant can identify an apparently relevant calculation, but a competent reviewer establishes whether it addresses the correct case and criterion.
- Use the matrix for design reviews and later handover. It helps prevent a requirement from disappearing between tender, design and performance testing, and prevents late discovery that the contractor never collected the evidence required for acceptance.
- AT THE WORKFRONT · THE WORKED CASE
- Workfront. A fictional engineering consultancy reports a high share of drawings issued while the design flow is still provisional and two interface inputs await client acceptance.
IN THE COMMITMENT · THE PARALLEL- Commitment. The contractor's executive review is asked to approve the stage on that percentage. The book's answer is to approve on actual maturity and residual exposure, with unresolved inputs, their consequences and the latest useful resolution dates reported.
- Same loop seen twice: the drawing count describes activity on one side and misrepresents exposure on the other.
A requirement with no named reviewer will be closed by whoever is in a hurry.
21:00 – 25:00
Release discipline, and your wrap
- Management should approve a stage on its actual maturity and residual exposure. Do not replace that assessment with a percentage of drawings issued.
- THE DOCTRINE
AI improves consistency checking, retrieval and option evaluation. Leadership provides the release discipline that prevents a faster analysis from becoming a premature commitment.
- If you are not the main contractor, the same discipline applies to your side: a client to the basis inputs it owes, a vendor to the data that sets its package, a consultancy to the basis it accepts.
- Before you close: write the problem engineering is solving for your decision, which inputs are confirmed or provisional, what configuration must be retained together, the bounds on any surrogate, and one requirement traced to its verification. That is Section 9 of your 90-Day Intelligent EPC Programme.
Speed in analysis is welcome. Speed in commitment needs a reason.
Key Terms
Design basis
The accepted duty, fluids, conditions, interfaces, site information, applicable standards and client requirements, each marked confirmed, provisional or awaiting competent acceptance, with an owner.
Configuration
The accepted combination of physical and documentary states relevant to a design, installation, test or operation. A latest-file folder does not establish it.
Surrogate model
An approximation used in place of a more detailed model for a defined purpose and accepted domain. Valid only within its recorded range and error tolerance, and not accepted for final design certification by screening use.
Verification matrix
Requirement, source, responsible discipline, deliverable, method, acceptance criterion, reviewer and status, kept open until actual evidence is accepted.
Self-Check — Before You Submit
1. A fictional EPC contractor's assistant finds that normal flow and design flow differ across two basis documents and proposes adopting the lower value so the purchased equipment still fits. What should the head of engineering require?
- A. Accept the lower value, because it protects the procurement commitment
- B. Average the two values
- C. Let the assistant rewrite the basis and log the change
- D. A precise query with source locations and affected decisions, and the approved duty established by competent owners
D. A precise query with source locations and affected decisions, and the approved duty established by competent owners — The assistant should raise a query, not select the most convenient operating condition and silently rewrite the basis. Protecting the purchase is tempting, but a successful calculation on the wrong duty remains an engineering failure.
2. A surrogate model shows a low average error across its test points. Why is that insufficient for an equipment sizing decision?
- A. A low average error can conceal a material error at the condition that sets equipment size
- B. Average error is never reported correctly
- C. Surrogates may only be used after final certification
- D. The model needs more typical test points
A. A low average error can conceal a material error at the condition that sets equipment size — The condition that sets equipment size may sit near a boundary or in an adverse combination, where an average says little. More typical points is the trap: the book asks for boundary and adverse-combination testing, not more of the same.
3. On what basis should management approve a design stage?
- A. The percentage of drawings issued
- B. The number of AI checks completed
- C. Its actual maturity and residual exposure, with unresolved inputs and their latest useful resolution dates
- D. The consultant's confidence statement
C. Its actual maturity and residual exposure, with unresolved inputs and their latest useful resolution dates — The book says to approve on actual maturity and residual exposure and not to replace that with a percentage of drawings issued. The drawing count is tempting because it is easy to measure, but it says nothing about which inputs remain provisional.
Today’s Assignment
Write Section 9 of your programme: the engineering problem, the configuration retained and the bounds on any surrogate model, with requirements linked to verification.
- State the problem engineering is solving for your company's decision chain, listing the basis inputs and marking each confirmed, provisional or awaiting competent acceptance, with an owner by role.
- Describe the configuration that must be retained together: which basis, calculations, drawings, vendor data and approved departures, and who accepts the dependency records.
- If any surrogate or quick-screening model is used or proposed, state its training range, excluded conditions, reference calculations and boundary tests. If none is used, say what reference calculation governs instead.
- Trace one accepted requirement through a verification matrix to the evidence that will close it.
- The honest part: where your company approves stages on drawing percentages, or keeps a latest-file folder instead of a configuration. If no AI is in use yet, that is normal. Aim for 400 to 900 words.
YOUR 90-DAY PLAN
Section 9 — The engineering problem, configuration and bounded surrogate models.
How this is marked — the rubric
| Basis inputs are listed with maturity marked and an owner by role | 25 |
| Configuration is defined as documents and states retained together, with dependency acceptance named | 25 |
| Any surrogate is bounded by range, exclusions, reference and boundary tests, or a governing reference is named | 20 |
| One requirement is traced to verification evidence and a named reviewer, with honest current practice | 30 |
| Total · pass mark 70 | 100 |
Submitting session 9
Write your answer in Word or Google Docs. The first line must read
Write your answer in Word or Google Docs. The first line must read
Session: 9, or the submission is refused. Upload the Word file (.docx), or switch to the Google Doc tab and paste your document’s share link.Marked against the rubric above and returned as a written letter, saved to your progress page. Do not submit until you have passed the self-check above.Capabilities Covered
Basis maturityConfiguration controlBounded surrogatesVerification matricesStage release discipline
Part Two · Engineering and the Design CommitmentSESSION 10
Detailed Engineering and Multidiscipline Coordination
Why This Matters
A revision is not one document changing. It is a consequence moving through disciplines, packages and commitments, and counting issued documents does not show whether the combined configuration is consistent. This session closes Week 2. You learn to follow a revision's consequence, keep checking separate from generation, treat rework and reviewer capacity as relationship problems and release a coherent configuration. You then see the book's proposed revision impact service, its output contract and H-01's week-five revision, recomputed. Practice Exam 2 opens at the end. Vendors, fabricators and consultancies can originate revisions (vendor change is one of the causes the book classifies); read it from that side.
25-Minute Module
0:00 – 5:00
Follow the consequence of a revision
- Engineering quality depends on the relationship among disciplines. A change in process duty can affect equipment, piping, electrical supply, controls, civil loads and operating access.
- Create an interface register with originating requirement, receiving discipline, due date, accepted input and unresolved assumption. Identify which deliverables cannot be released until the interface is accepted. A model can flag a late input, but the engineering manager owns its treatment.
- For a hypothetical skid revision, a heavier assembly may need foundation and lifting reviews; a larger motor, electrical and control reviews; a changed nozzle location, piping and access reviews. The dependency service proposes this review set with references. It does not authorise the change or establish suitability by similarity to a previous package.
Ask where a revision went next, not only whether it was issued.
5:00 – 10:00
Checking is not generation; rework is a relationship problem
- An assistant can compare a datasheet with a specification, check tag consistency and identify missing values. Generating a new design is a separate use with different evidence requirements.
- THE DOCTRINE
A document comparison test cannot establish competence for engineering design. Agreement between two language models is not independent verification of the engineering basis.
- For calculations, retain inputs, units, method, software version, boundary conditions, result and reviewer, linked to the accepted design basis. A plausible equation can still have an incorrect unit basis or sign convention. Repeating the same generated code with a different prompt may reproduce the same assumption; a separate calculation or accepted reference case is a more useful challenge.
- Classify revision causes: incomplete input, client change, vendor change, design correction, constructability issue and documentation error. Keep cause separate from blame; a revision count without cause can encourage staff to delay necessary corrections. Treat reviewer capacity as a schedule constraint: faster generation can increase the review queue and reduce effective assurance.
When generation speeds up and review capacity does not, the queue grows and assurance thins.
10:00 – 15:00
Release a coherent configuration through a revision impact service
- At release, confirm that deliverables belong to the accepted configuration and unresolved conditions are controlled. Issued-for-construction needs an agreed meaning in the project's document controls. Record conditional releases with scope, expiry, follow-up and the work they permit and exclude.
- Where I would begin engineering AI: a controlled revision comparison, narrow enough to test and important enough to affect delivery. It receives two accepted versions of the same deliverable, identifies changed requirements and proposes the affected review set; the engineering manager decides what needs discipline assessment before release.
- Validate identities first, the Session 4 rule: an unofficial vendor file compared with an accepted baseline cannot be presented as an authorised change. Use exact comparison for identifiers, units and structured values, a language model to explain textual changes, and a dependency graph accepted by engineering to propose receiving disciplines. Word similarity can propose a relationship; it cannot establish one.
Output contract field What the service supplies What the reviewer establishes Compared objects Document identifiers and revisions That both versions are the intended comparison Change finding Old and new content with source locations Whether the interpretation is technically correct Proposed impact Receiving deliverable and dependency basis Whether the receiving discipline needs action Current limitation Missing source, extraction failure or uncertain link How the gap will be resolved Release consequence Proposed hold or review referral Actual release conditions and authority - A missing receiving object creates a query, not a guessed drawing number. An unreadable scan or absent annex makes the comparison incomplete, and the service says so.
A comparison that admits what it could not read beats a polished one that skipped it.
15:00 – 21:00
Evaluate the service, then H-01 at week five
- Evaluate on independently identified reference cases, including unchanged revisions, amended units, changed tags, superseded documents and poor scans. Measure change detection and impact quality separately, on the actual uploaded scans, with case families kept outside prompt development.
- THE DOCTRINE
After accepted use begins, inspect revisions the service did not flag as well as those it did. Sampling only alerts cannot establish missed-change performance.
- H-01, assumed. At week five the supplier proposes a revised package configuration; the scenario specifies no physical design value. The service proposes a receiving electrical record and the foundation and installation interface. Engineering reviews the dependencies, procurement checks supply scope and delivery, commercial leadership assesses the change procedure, and the AI engine assembles the review pack.
Assumed, NGN million At bid (Session 7) Change accepted at week six Revised Cost provision 125 +8 133 Price 160 +10 170 Price less provision 35 +2 37 As a share of price 35 ÷ 160 = 21.875% — 37 ÷ 170 = approximately 21.76% - AT THE WORKFRONT · THE WORKED CASE
- Workfront. Accepting the change does not prove every earlier test or drawing remains applicable. The configuration register identifies evidence needing reassessment, and the service retains revision A and accepted revision B.
IN THE COMMITMENT · THE PARALLEL- Commitment. The same retained revisions explain why a later cost forecast differs from the bid. The NGN 8 million and NGN 10 million are scenario inputs, not an entitlement calculation or reported negotiation. One preserved record serves both sides.
Never let a new revision erase the reason the numbers moved.
21:00 – 25:00
Retain engineering accountability, your wrap and Practice Exam 2
- Acceptance evidence for an AI-drafted calculation script includes equations, units, assumptions, test cases, numerical precision and independent comparison with an accepted reference. Keep generated text out of release fields until review is complete; record who accepted the finding and who accepted the design change.
- THE DOCTRINE
If the service is unavailable, engineers need the original source set and the existing coordination process. The contractor should be able to explain the design without reconstructing a conversation with an assistant.
- Before you close: follow one revision in your decision chain, state where your company checks and where it would generate, and write the output contract you would require. That is Section 10 of your 90-Day Intelligent EPC Programme.
- Practice Exam 2 opens now: fifteen questions across Sessions 1 to 10, closing Week 2.
Accountability is not a signature at the end; it is a record of who accepted what, and on which evidence.
Key Terms
Interface register
Originating requirement, receiving discipline, due date, accepted input and unresolved assumption for each engineering interface, showing which deliverables cannot be released until the interface is accepted.
Revision impact service
A proposed service that compares two accepted versions of a deliverable, identifies changed requirements and proposes a review set. A referral, not a finding of inadequacy or an approval.
Engineering output contract
The proposed fields a revision service returns (compared objects, change finding, proposed impact, current limitation, release consequence), each with what the reviewer establishes.
Conditional release
An authorised early release recorded with scope, expiry and follow-up, stating the work it permits and the work it excludes.
Self-Check — Before You Submit
1. A fictional EPC contractor's engineer drafts a calculation script with AI; a second language model agrees with the result. What should the engineering manager require before release?
- A. Release, because two models agree
- B. Run the same script again with a different prompt
- C. Release with a note that AI was used
- D. Equations, units, assumptions, test cases, numerical precision and independent comparison with an accepted reference
D. Equations, units, assumptions, test cases, numerical precision and independent comparison with an accepted reference — Agreement between two language models is not independent verification of the engineering basis. Re-prompting is tempting but may reproduce the same assumption; a separate calculation or accepted reference case is the useful challenge.
2. In the assumed H-01 scenario, after the change accepted at week six, what is price less provision as a share of revised price?
- A. 21.875%
- B. Approximately 21.76%
- C. Approximately 27.82%
- D. Approximately 23.13%
B. Approximately 21.76% — NGN 37 million ÷ NGN 170 million is approximately 21.76%. 21.875% is the bid-stage figure; 37 ÷ 133 gives about 27.82%, using cost rather than price as the base.
3. A revision impact service detects a changed motor power under the same tag and lists the datasheet, load list, electrical evaluation, control documentation and package interface. What is that list?
- A. A referral set for review, not a finding that any cable, protection or installation is inadequate
- B. A finding that the electrical design is inadequate
- C. Approval to proceed with the revised motor
- D. Proof that no other document is affected
A. A referral set for review, not a finding that any cable, protection or installation is inadequate — The book calls it a referral set; the responsible engineers assess actual values. Treating it as a finding of inadequacy is the trap; treating it as proof that nothing else is affected is equally unsupported.
Today’s Assignment
Write Section 10 of your programme: one revision followed, checking separated from generation and the engineering output contract your company would require.
- Follow one recent revision in your company's decision chain: the originating change, every discipline or package it reached, and any it should have reached but did not.
- State where your business uses or would use AI for checking and where for generation, and the evidence each requires.
- Classify the causes of your recent significant revisions and say whether reviewer capacity was the constraint.
- Write the engineering output contract you would require from a revision service, using the five fields, and how you would test missed changes as well as alerts.
- State how engineering accountability is retained: who accepts the finding, who accepts the design change, and how work continues if the service is unavailable.
- The honest part: where your company counts issued documents instead of following consequences. If no AI is in use yet, that is normal. Aim for 400 to 900 words.
YOUR 90-DAY PLAN
Section 10 — The revision followed, checking versus generation and the engineering output contract.
How this is marked — the rubric
| Follows one revision to its receiving disciplines and names a missed or late consequence | 25 |
| Separates checking from generation with the evidence each requires | 20 |
| Writes a usable output contract and a test for missed changes, not only alerts | 30 |
| Names who accepts findings and design changes, and the fallback without the service | 25 |
| Total · pass mark 70 | 100 |
Submitting session 10
Write your answer in Word or Google Docs. The first line must read
Write your answer in Word or Google Docs. The first line must read
Session: 10, or the submission is refused. Upload the Word file (.docx), or switch to the Google Doc tab and paste your document’s share link.Marked against the rubric above and returned as a written letter, saved to your progress page. Do not submit until you have passed the self-check above.ASSESSMENT NOW OPEN
Practice Exam 2 — Foundations and the Design Commitment opens now. Sit it before you start the next session — it is how you find out whether the doctrine landed, and the practice papers may be resat as often as you like.
Sit Practice Exam 2 →Closed book, no notes, and Coach Ritchie switches himself off while you sit it.Capabilities Covered
Revision consequence tracingChecking versus generationReviewer capacityOutput contractsRetained accountability