ElevGrid / Project assurance
Quality &
Project Control
Control starts with a clear specification.
Quality control begins with technical clarification and a confirmed document baseline—not only with a check before shipment. Define what is required, what needs approval and what evidence is needed for release.
Discuss your project requirementsReview the planning checklist
Control logic / Illustrative
- 01Define the requirementSpecification · interfaces · standards
- 02Confirm the baselineRevision · approval · open points
- 03Agree the evidenceCheckpoints · records · release scope
Scope and responsibilities to be agreed for each project.
01 / Technical baseline
Control Starts with a Clear Technical Baseline
Bring the requirements into one reviewable set. Identify missing information and conflicting values before treating a specification as confirmed.
Define the duty
Capacity, voltage, frequency, impedance, loss requirements and insulation levels, where applicable. Separate reference values from contractual requirements.
Resolve the interfaces
Accessories, dimensions, connections, protection interfaces and installation limits. Include ambient conditions, altitude and any special environment.
Set the review basis
Applicable standards and editions, document precedence, acceptance criteria and approval responsibilities. Record exclusions and unresolved points explicitly.
A project baseline should identify the agreed document revisions and any accepted deviations. An enquiry document alone is not an approved production instruction.
02 / Document discipline
Document & Revision Control
Keep specifications, datasheets, drawings, single-line diagrams (SLDs), bills of quantities (BOQs) and approval records connected to the same equipment scope.
Each controlled document should have an identifier, revision, issue date, purpose and review status. Record who reviewed it and link comments to the revision they address.
Revision sequence / Example only
- For review
Issued revision
Log the issue and collect comments against that version.
- Approval recorded
Agreed revision
Identify the permitted use and any remaining conditions.
- Superseded
Previous revision
Retain the history and mark the earlier issue as no longer current.
A later issue date alone does not establish approval. Confirm the review status before use.
03 / Decision sequence
Project Control Gates
Use these gates as a discussion framework. The sequence, responsibilities and hold or witness points must be agreed for the actual supply scope.
- 01
Requirement Review
Check equipment scope, input documents and missing requirements.
Output / Input register - 02
Technical Clarification
Resolve conflicts, interfaces and proposed exceptions.
Output / Clarification log - 03
Approved Baseline
Record agreed revisions, acceptance criteria and approval conditions.
Output / Baseline record - 04
Production Checkpoints
Define relevant checks and required records within the agreed scope.
Output / Checkpoint record - 05
Inspection/Test
Review specified results against agreed acceptance criteria.
Output / Verification record - 06
Release Documentation
Review document status and unresolved conditions before release.
Output / Release register
04 / Verification scope
Inspection and Verification Points
Checks depend on equipment type, applicable standards and contract scope. Confirm the method, acceptance criteria, responsible party and required evidence before scheduling inspection.
Transformers
Possible review points include nameplate data, agreed ratings, accessories, dimensions and the electrical test records specified for the unit.
Distribution equipment
Possible review points include configuration, enclosure, connections, protection interfaces and functional or electrical verification defined in the contract.
Engineered components
Possible review points include drawing revision, material requirements, dimensions, interface fit and specified inspection records.
Factory acceptance testing (FAT), buyer witnessing, third-party inspection and additional tests are subject to technical feasibility and written agreement. Their availability or inclusion should not be assumed.
05 / Exception management
Deviations, Changes & Open Points
Make unresolved decisions visible. A useful issue register connects each question to its equipment tag, source document, owner, target response date and required decision.
For a proposed deviation or change, record the original requirement, proposed alternative and potential effect on performance, interfaces, cost, schedule and documents. Obtain the required written disposition before using the affected revision.
Issue lifecycle / Illustrative
- Open
State the question and identify the owner.
- Impact review
Assess the affected scope and document the proposed disposition.
- Decision recorded
Capture approval, rejection or conditions and update affected documents.
- Closed
Link the closure evidence and confirmation; keep any remaining conditions visible.
An unanswered point should remain open. Closure requires a recorded basis.
06 / Handover evidence
Deliverable Register
Agree the register early: document identifier, equipment reference, required format, language, planned issue stage and review status. Track preliminary and final issues separately.
Datasheets & confirmed specifications
Ratings, configuration and agreed requirements.
Provided as required by the project and contract.
Drawings & interface documents
Applicable arrangement, connection and approved revision records.
Provided as required by the project and contract.
Inspection & test records
Records for the checks and tests included in the agreed scope.
Provided as required by the project and contract.
Packing & shipment information
Applicable packing lists, package identification and handling information.
Provided as required by the project and contract.
Certificates & compliance documents
Applicable evidence, subject to confirmed availability and scope.
Provided as required by the project and contract.
Operating & maintenance information
Applicable installation, operation and maintenance instructions.
Provided as required by the project and contract.
07 / Prepare your enquiry
Buyer Inputs
Send the information already available and identify what still needs confirmation. The following inputs help define the technical and document review scope.
- Standards & specificationsApplicable editions, project requirements, SLD, BOQ and equipment tags.
- Approval processReviewers, approval authority, document precedence and comment cycles.
- Inspection & witness requirementsRequested tests, hold points, attendance arrangements and notice periods.
- Document format & languageFile formats, naming rules, templates and required final dossier structure.
- Project milestonesTarget approval dates, inspection windows and delivery requirements.
Connected project decisions
Keep the next steps connected.
Standards & Compliance
Clarify applicable standards before defining the test scope.
Before dispatchExport Packing & Delivery Coordination
Connect agreed release conditions with packing and dispatch planning.
Recommended Next StepTesting & Factory Acceptance
Define the inspection scope, witness arrangements and acceptance records.
Next step / Define the scope
Bring your requirements.
Identify the control points.
Share your specification and document requirements through the existing project enquiry route. Flag any mandatory inspection, approval or delivery conditions.