Design
CHECK 01Is the design developed enough for the next decision?
ENGINEERING APPROACH
Technical information should support project decisions
YDC's approach connects engineering, programme, cost, quality and documentation so project decisions are made with a clearer understanding of their wider effect.
TechnicalProgrammeCostQualityInformation
Coordinated project information
01Technical
02Programme
03Cost
04Quality
05Information
Technical, programme, cost, quality and information controls are reviewed as connected parts of the same project record.
The YDC Standard
A disciplined approach to project information.
Verify what is issued, control what changes, and keep technical, cost and programme decisions connected.
01Verify before issuing
Check that information is current, coordinated and ready for its intended use.
02Track every revision
Make changes identifiable so teams can distinguish superseded information from the current issue.
03Quantify before deciding
Understand quantities and measurable impact before committing to a technical or commercial direction.
04Coordinate before construction
Resolve interfaces between disciplines while changes are still easier to control.
05Document every change
Keep instructions, approvals and decisions traceable throughout the project record.
06Control cost and time together
Review technical decisions with their programme and commercial consequences in view.
01
Verify before issuing
Check that information is current, coordinated and ready for its intended use.
02
Track every revision
Make changes identifiable so teams can distinguish superseded information from the current issue.
03
Quantify before deciding
Understand quantities and measurable impact before committing to a technical or commercial direction.
04
Coordinate before construction
Resolve interfaces between disciplines while changes are still easier to control.
05
Document every change
Keep instructions, approvals and decisions traceable throughout the project record.
06
Control cost and time together
Review technical decisions with their programme and commercial consequences in view.
Project lifecycle
The information changes. The control should not.
Different stages need different decisions, reviews and outputs. Select a stage to see how the emphasis changes from early review through close-out.
Feasibility & Due Diligence
Define the decision basis
Clarify requirements, existing conditions, constraints and technical risk before design effort accelerates.
Typical focus
Requirements
Existing conditions
Risk review
Connected project controls
Control through connected project information
Programme, cost, technical status and project records should be reviewed together. A delay may affect cost. A design change may affect programme and procurement. A commercial decision may affect technical scope.
01Technical
Design status, coordination, constructability and technical decisions.
02Programme
Sequencing, milestones, dependencies and the effect of change on time.
03Cost
Quantities, valuation, variations and commercial impact.
04Quality
Review, inspection, compliance and close-out requirements.
05Information
Drawings, RFIs, submittals, instructions, approvals and revisions.
Pre-construction
Resolve more before construction begins
Pre-construction review focuses on whether design, quantities, cost, programme, coordination and tender information are sufficiently developed for the next project stage.
DesignCHECK 01
Is the design developed enough for the next decision?
CoordinationCHECK 02
Are major interfaces between disciplines resolved?
QuantitiesCHECK 03
Can the current scope be measured consistently?
CostCHECK 04
Are cost implications visible before commitment?
TenderCHECK 05
Is the information clear enough for comparable bids?
ProgrammeCHECK 06
Are key dependencies and lead times understood?
RiskCHECK 07
Are unresolved technical and delivery risks identified?
Coordination
CHECK 02Are major interfaces between disciplines resolved?
Quantities
CHECK 03Can the current scope be measured consistently?
Cost
CHECK 04Are cost implications visible before commitment?
Tender
CHECK 05Is the information clear enough for comparable bids?
Programme
CHECK 06Are key dependencies and lead times understood?
Risk
CHECK 07Are unresolved technical and delivery risks identified?
These are review questions, not project status scores. The answer depends on the project stage, scope and available information.
Information control
Maintain one current project record
Drawings, revisions, RFIs, submittals, instructions and approvals should remain identifiable and traceable throughout the project.
DrawingsRFIsSubmittalsInstructionsApprovals
01Issue
Information enters the project record with a defined purpose and revision.
02Review
Technical and project stakeholders review against current requirements.
03Revise
Comments and decisions are incorporated into a controlled update.
04Approve
The accepted issue is identified for its intended use.
05Current record
The team can distinguish the current issue from superseded information.
Construction support
Technical support through execution
Construction-phase support remains structured around current information, traceable decisions and coordinated technical review.
01Technical review
Shop Drawing Review
Technical Submittal Review
RFI Review / Response
02Progress & controls
Progress Monitoring & Reporting
Schedule Review
03Quality & site
Site Inspection
Quality Oversight
04Change & close-out
Variation / Change Review
Snagging / Punch Lists
Handover / Close-Out
Technical review
01Shop Drawing Review
Technical Submittal Review
RFI Review / Response
Progress & controls
02Progress Monitoring & Reporting
Schedule Review
Quality & site
03Site Inspection
Quality Oversight
Change & close-out
04Variation / Change Review
Snagging / Punch Lists
Handover / Close-Out
Bring the approach into the project