A completed project is often remembered through photographs. The construction team remembers the work behind them: drawings reviewed, activities coordinated, quantities checked, and problems resolved.
For me, the Dharahara Reconstruction project in Sundhara, Kathmandu, represents that connection between the finished structure and the everyday effort needed to deliver it.
My involvement in the project from 2018 to 2025 included construction planning, site coordination, supervision, documentation, procurement support, and progress reporting. Looking back, it provides a useful starting point for this blog: what does delivering a major project teach us beyond the drawings?
Looking beyond the main structure
The tower is the visual centrepiece, but a project is not only its most recognisable structure. It also includes the spaces, interfaces, and supporting work around it.
For an engineer, that means looking beyond an individual activity and considering how it connects with the next trade, the surrounding area, and the overall delivery sequence.
Planning must stay connected to site conditions
My responsibilities included planning, scheduling, and coordinating daily activities against drawings, specifications, and contract requirements.
That experience is the basis for one of the themes I want to explore through this blog: the relationship between a programme and the work happening on site.
A schedule sets out an intended sequence. Site coordination asks more immediate questions:
- Is the work area ready?
- Are the relevant drawings and information available?
- Are materials, labour, and equipment aligned?
- What needs to be completed before the next activity begins?
- What could prevent the team from progressing?
These are the kinds of questions I would like to examine in future posts—not as a single formula for every project, but as practical prompts for thinking about delivery.
Documentation is part of the construction story
Alongside site activities, my work included progress reports, Interim Payment Certificates, variation information, and claim records.
These documents represent another side of project delivery. Photographs show what a project looks like; records explain what work was completed, how progress was reported, and what information supported commercial discussions.
For this blog, I want to give documentation the same attention as visible construction work. Quantity records, progress reporting, and clear supporting information were all part of my project responsibilities, and they deserve a place in conversations about engineering practice.
Coordination connects the different parts of delivery
My involvement also included coordination with consultants, clients, contractors, procurement teams, and site personnel.
That range of interfaces is an important part of how I think about construction management. A site activity sits within a wider chain of decisions and information: drawings, approvals, materials, equipment, labour, supervision, and reporting.
The subject I want to explore is not simply how each function works separately, but how they connect. Where does information need to move? Who needs to act on it? What needs clarification before work proceeds?
Those questions provide a useful lens for reflecting on project experience.
Why I’m starting this blog
Through Civil Engineer Diary and this website, I want to create space for practical engineering conversations.
My planned topics include:
- Construction planning and site coordination.
- Quantity take-offs and construction documentation.
- Progress reporting and project controls.
- Digital tools and BIM learning.
- Professional development and reflections from project work.
Some posts will focus on technical processes. Others will reflect on the responsibilities and decisions that sit between drawings and completed construction.
The aim is to share thoughtfully, keep learning, and connect project experience with useful questions for other engineers.
A starting point for the next chapter
Dharahara Reconstruction forms an important part of my professional experience. It provides a starting point for reflecting on that work—not just through the finished appearance, but through the planning, coordination, supervision, and documentation behind it.
That is the perspective I hope to bring to this blog: looking beyond the visible result to understand the work that helped shape it.