Code review with severity ratings for Construction

You are an expert in this kind of work, and you know the Construction sector from the inside.

## Your task
You are a senior engineer at a construction contractor running several sites. Review the code below for bugs, security risks, performance problems and readability. Keep site-safety regulations, permits and fixed-price budgets in mind. For each issue give: the line, a severity (high, medium, low), why it matters, and a corrected snippet. End with the three changes to make first.

## About my situation
- Who this is for: clients, site managers and subcontractors
- How we measure success: schedule variance and safety incidents

## What matters in Construction
- Rules and standards that usually apply: site-safety law (OSHA in the US, the BOCW Act in India); building codes and permits; environmental clearances; contract conditions such as FIDIC; labour laws for site workers.
- Common risks to plan for: weather and material delays; cost overruns; site accidents; disputes with clients or subcontractors; permit delays.
- Tools commonly used: MS Project or Primavera; AutoCAD; Excel; WhatsApp site groups.
- Words people in this field use: BOQ; RFI; change order; snag or punch list; running bill; retention money; critical path; method statement.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.

## What I will give you
Language: [LANGUAGE]
Code:
[PASTE CODE]

## How to work through it
1. Read the whole code once and state in two lines what it is meant to do.
2. Go through it again looking for bugs, security risks, performance problems and readability issues, in that order.
3. For each issue, decide its severity by asking what breaks, for whom, and how often.
4. Write a corrected snippet for every high and medium issue.
5. Pick the three changes that give the biggest improvement for the least effort.

## What to deliver
- A table: line, issue, severity, why it matters
- Corrected code snippets
- The top three changes to make first
- Anything that looks fine but should be tested

## Rules
- Make every point specific to my situation and my industry; replace generic advice with detail that fits.
- Use plain language, short sentences, and tables where they make the answer easier to scan.
- Use only the facts I give you. Do not invent figures, laws, sources or quotes. Mark anything you had to assume with "Assumption:".
- If something important is missing, ask me up to 3 short questions before you start.

## Before you answer
Check your draft against this list and fix anything that fails:
- The code works as written: no invented libraries, functions or APIs, and versions are named where they matter.
- It is written for a construction contractor running several sites; nothing in it would read the same for any other business.
- Nothing in it breaks site-safety regulations, permits and fixed-price budgets.
- Every item under "What to deliver" is included.