Construction Project Management · Saeed Azarshab

Project Brief & Scope

Project Brief & Scope — Workflow image 1
Project Brief & Scope

My approach starts with a clear brief, defined work packages and a shared understanding of delivery constraints. My Tavanir and Niayesh records provide the project context; responsibility remains limited to my stated appointment and assigned workstreams.

England: regulatory context for delivery

For an England project, identify the planning and building-control routes separately, record applicable requirements and agree dutyholders before mobilisation. The brief must allow for competent appointments, sufficient information and realistic review time.

BIM-enabled coordination and repeatable controls

I connect scope, work packages, model information and decision owners in one coordination structure. Reusable briefing and issue templates are intended to reduce repeated entry and missed interfaces; scope changes still need an authorised decision.

Official references and scope

What I focus on

  • Clarify scope, exclusions, interfaces and decision owners.
  • Connect the work breakdown structure to programme and procurement.
  • Record constraints, actions and agreed changes before mobilisation.

Relevant project records

The records below show the stated role, scope and involvement. A project link does not prove every workflow or a quantified outcome.

Tavanir Office Building

Role
Construction Project Manager
Scale
10 offices / 36 parking spaces
Involvement
Oct 2019 — Aug 2022

Technical workflow in detail

Practical workflow reference. Project-specific roles and the current England regulatory context are described separately above.

• Work Breakdown Structure (WBS) Development

  • Accurate scheduling and resource allocation

  • Transparent delegation and scope tracking

  • Seamless integration with cost and procurement plans

• Contract and Document Review

  • Define the project scope precisely

  • Identify initial risks and compliance requirements

  • Ensure alignment with building codes, safety laws, and client objectives

• Regulatory Pathway and Authority Liaison

  • Obtain construction permits

  • Submit design documents for approval

  • Resolve zoning, code, or site access issues early in the project

• Stakeholder Briefings and Needs Analysis

  • Clients

  • Designers

  • Consultants

  • Contractors
    to ensure that all expectations and technical requirements are captured and documented.

Example workflow tools

Tool/Skill

Application

Microsoft Project

Creating master schedules and aligning with WBS

AutoCAD, Revit, Navisworks

Reviewing IFC drawings, detecting early design conflicts

Kickoff Meetings

Aligning multidisciplinary teams on scope and deliverables

Initial Risk Registers

Identifying delays, permit barriers, and regulatory gaps

Supporting visual material

Project Brief & Scope — Workflow image 2
Supporting workflow material. Select the image to view it in full.