Editorial draft / Design engineering

What should be resolved before construction?

This placeholder checklist helps organize a design review. It does not certify that a design is complete, coordinated, compliant, or ready for construction.

A decision register

Make open questions visible.

“For construction” should not hide unresolved assumptions. A practical review can separate what has been confirmed, what is pending, what is excluded, and what must be verified during later work.

The register should name the information used, the responsible party, the effect of delay, and the document that will carry the final answer. That gives the team a clearer basis for sequencing work and managing changes.

01

Design basis

Record the brief, occupancy, operating intent, survey information, environmental assumptions, client criteria, and limits of the agreed scope.

02

Loads and selections

Check that calculations, equipment selections, capacities, utility information, and major dimensions use an identified and current input set.

03

Interfaces

List dependencies between disciplines, packages, suppliers, existing services, temporary works, controls, testing, and builder’s work.

04

Approvals and constraints

Identify submissions, reviews, permits, owner decisions, access constraints, shutdowns, and long-lead information without implying an approval that has not been received.

05

Issue set

Confirm drawing and specification revisions, cross-references, schedules, details, scope boundaries, open-item notes, and the agreed distribution record.

Draft status

A checklist is not an approval.

  1. 01

    The final review criteria must come from the actual contract, project brief, applicable requirements, and responsible professionals.

  2. 02

    This draft avoids naming codes, authorities, or acceptance thresholds until Kyriarch supplies reviewed source material.

  3. 03

    A technical reviewer should decide which items are mandatory, conditional, or outside Kyriarch’s scope before publication.