Engineering Sarathi publishes original, Nepal-focused explanations and working tools. The aim is to help readers understand a rule, calculation or field issue while keeping the controlling source and professional limits visible.
1. Editorial responsibility
Er. Keshav Giri, Founder and Technical Editor, is responsible for the platform’s technical direction. His background includes civil engineering, earthquake engineering, structural assessment and retrofitting, construction supervision, QA/QC, public procurement and contract administration.
Published material is prepared for engineers, contractors, consultants, public entities, students and project teams. Authorship does not turn general information into a project-specific design, approval, certification or legal opinion.
2. Source hierarchy
Where a subject is governed by law, contract or standard, we work from the strongest available source. The normal order is:
- Acts, regulations, Gazette amendments and official directives;
- current standard bidding documents, specifications, codes and manuals issued by the responsible authority;
- the executed contract and project-specific documents when discussing an actual case;
- recognised technical references and professional guidance; and
- clearly identified worked assumptions or editorial interpretation.
Official text remains controlling. A translation, summary, checklist or tool on this website is a navigation and learning aid.
3. How technical content is prepared
Articles are structured around the practical decision a reader needs to make. Relevant provisions and technical principles are compared, inconsistencies are flagged, and the result is explained through tables, checklists, calculations or project workflows where useful.
We aim to distinguish clearly between a legal requirement, a contract condition, a common industry practice, a worked illustration and an editorial recommendation. Publication and material update dates are retained so readers can judge whether a later amendment or standard may apply.
4. Calculations, examples and tools
Worked examples use stated inputs and assumptions. Calculators and templates are tested against their documented rules, but they remain decision-support tools. Users must check units, formulas, dates, thresholds, drawings, quantities and project conditions before relying on a result.
Illustrative quantities, prices and scenarios are labelled as examples unless they come from an identified source. Project-specific engineering conclusions require the relevant survey, investigation, design information and professional review.
5. Notices and external resources
Public notices and document directories are provided to help readers locate timely official information. They are kept distinct from editorial articles. Each notice should identify its issuing authority and date, link to or preserve the official source where available, and add only the explanation needed to understand its practical effect.
An external link does not imply ownership or endorsement. Readers should confirm that the linked version is current and complete before using it for a procurement or project decision.
6. Corrections and updates
Technical and legal information can change, and errors should be corrected transparently. Material corrections or updates are incorporated into the relevant page and reflected in its update date where appropriate.
If you identify an inaccurate clause reference, broken source, calculation issue or technical ambiguity, email info@engineeringsarathi.com with the page link, the point requiring review and the strongest supporting source available.
7. A responsible starting point
Use Engineering Sarathi to understand the issue and organise the next step. Use the applicable law, contract, approved design, current standard and authorised professional decision to conclude an actual case.