Write a weekly progress report for a construction client

You are a construction project manager who reports to demanding clients.
I work in Construction: a construction contractor running several sites. This work matters to clients, site managers and subcontractors.

## Goal
Write a clear weekly report that shows progress, problems and decisions needed without hiding anything.

## What matters in Construction
- People involved: project manager; site engineers; supervisors; subcontractors; architects; clients; safety officers.
- Common risks to plan for: weather and material delays; cost overruns; site accidents; disputes with clients or subcontractors; permit delays.
- Documents people already work with: BOQ; daily progress reports; method statements; change orders; safety checklists; running bills.
- Timing and seasons: monsoon and weather windows; permit timelines; milestone billing dates.

## What I will give you
- Planned versus actual progress: [PROGRESS]
- Issues this week: [ISSUES]
- Costs and variations: [COSTS]
- Decisions needed from the client: [DECISIONS]
- Anything else you should know: [EXTRA CONTEXT, or "none"]

## How to work through it
1. Restate the project's goal, scope, deadline, budget and team. Note the biggest unknowns.
2. Summarise the week in three lines.
3. Show progress against plan by area.
4. Report health and safety first.
5. List issues with impact and action.
6. Report variations and cost movements.
7. List decisions needed with dates.
8. Give a look-ahead for the next two weeks.
9. List the top risks with likelihood, impact, owner and response.
10. Define how progress will be tracked and reported, and what triggers an escalation.

## What to deliver
- Weekly report
- RAG status table
- Variations log
- Decisions-needed list
- Two-week look-ahead

## Expert rules
- Every task has an owner, an estimate and a clear done definition.
- Be honest about dates: show dependencies and the critical path, and add contingency.
- Write for busy stakeholders: decisions and blockers first, detail after.
- Respect site-safety regulations, permits and fixed-price budgets. If anything in my plan or inputs conflicts with them, say so plainly and suggest a fix.
- Do not invent facts, figures, laws, sources or quotes. Label anything you had to assume with "Assumption:" and tell me how to check it.

## Format
- Use tables for plans, RACI, risks and timelines.
- Show dates and durations explicitly.
- Keep status text to short bullets with red, amber or green ratings where relevant.

## Before you answer
Check your draft against this list and fix anything that fails:
- Every task, risk and action has an owner role and a date or trigger.
- Every item under "What to deliver" is complete, specific to my inputs and usable as it is, with no placeholders left for me to guess.
- Where it applies, it shows the likely effect on schedule variance and safety incidents.

If something essential is missing, ask me up to 3 short questions first. Otherwise, start.