Review and drawing quality process
Our Engineering Methodology
A process built so that calculations are traceable, drawings agree with each other and review comments are closed on record. It is described as working practice, not as a certified management system.
The process
Seven steps from inputs to final submissions
Select a step to read what happens, the inputs it uses, the outputs it produces and the record we keep.
01 · Inputs
The package starts when the project documents arrive: the technical specification, the single-line diagram, any approved basic design, the master deliverable list (MDL), the bay list and equipment GTPs, and the site constraints. We log what has been received and what is still missing.
Evidence kept: an inputs log with document numbers and revisions.
02 · Design basis
Design criteria are set before calculation starts. Owner or client approved criteria and the applicable latest regulations take priority. Every assumption that has to be made is entered in an assumptions register, with the person who must confirm it.
Evidence kept: design basis report and assumptions register.
03 · Calculations
Initial calculations and design studies are prepared with traceable technical inputs and a stated formula basis. Independent internal checks are applied as appropriate to the calculation and the contract before issue.
Evidence kept: calculation reports with input references, method and results.
04 · Drawings
Discipline drawings and sections are developed from the calculated results and the approved layout, on one coordinate and level reference so that sheets agree with each other.
Evidence kept: drawing set under revision control.
05 · Multidisciplinary checks
Equipment, foundation, load, level and dimension interfaces between electrical, civil, structural and transmission designs are cross-checked, and designs are adjusted to approved vendor documents and GTPs. Outstanding information and design risks are recorded rather than assumed away.
Evidence kept: interface check record, vendor review sheets and open-information log.
06 · Comment resolution (CRS)
Documents are submitted under the revision convention the client requires; we do not assume a universal Rev-0 practice. Each comment is logged in a comment resolution sheet, answered and closed in a revised submission.
Evidence kept: drawing register, transmittals and CRS.
07 · Final submissions
When comments are closed, documents are issued in the status the project formally authorises: issued for approval, approved or issued for construction, as defined by the project. We do not claim client acceptance before it happens.
Evidence kept: closed CRS and final register status.
Practices, not performance claims
What the process is intended to achieve.
Fewer unresolved assumptions
Assumptions go into a register with an owner, so open points are visible and are confirmed or closed.
Coordinated interfaces
Loads, levels and dimensions are checked across electrical, civil and transmission designs before issue.
Traceable calculations
Each result shows its inputs, method and acceptance limit, so a reviewer can follow it from specification to answer.
Disciplined revisions
One register records every issue, revision and transmittal, in the client’s own convention.
Reviewable drawings
Drawings use a common reference and are checked internally, so reviewers spend their time on engineering rather than inconsistencies.
Clear BOQ
Quantities state their basis and what they exclude, so estimators and procurement teams know what they are using.
These are design practices that we follow. We do not publish speed or cost improvement figures because they depend entirely on the project.
What each document status means
CoreGrid uses status terms as the client or project defines them.
Submitted for the client’s or consultant’s review. It is a proposal for acceptance, not an approved document.
The formal response of the approving party, which may carry comments. Only the client, owner’s engineer or consultant can give it.
Released for use at site, in the status and under the convention the project defines. Revision labels differ between projects.
Status names and revision conventions differ between projects. The project’s own definitions always apply.
Related
Share your SLD, technical specification or MDL for an engineering proposal
Send us the tender extract, single-line diagram, master deliverable list or the specific calculation you need. We will confirm scope, inputs and a realistic submission sequence before any work starts.