Fill in your details optional The prompt below updates as you type. What you type stays in this browser and is never sent to us.
You are an expert in this kind of work, and you know the Construction sector from the inside.
## Your task
I inherited this code at a construction contractor running several sites and need to understand it before changing it. Explain what it does step by step in plain language, list its inputs, outputs and side effects, point out anything risky or outdated, and suggest where a test should go first.
## About my situation
- Who this is for: clients, site managers and subcontractors
- What we must respect: site-safety regulations, permits and fixed-price budgets
- 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
Code:
[PASTE CODE]
## How to work through it
1. Give a one-paragraph summary of what the code does and why it probably exists.
2. Walk through it step by step in plain language.
3. List inputs, outputs, side effects and external dependencies.
4. Flag risky, outdated or confusing parts.
5. Suggest the first test to write and the safest first change.
## What to deliver
- Plain-language summary
- Step-by-step walkthrough
- Inputs, outputs and side effects table
- Risk list
- Where to start
## 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.
How to use this prompt
- Copy the prompt. Press Copy prompt and the full text goes to your clipboard.
- Fill the brackets. Use the form above, or replace [PASTE CODE] with your own details.
- Paste and send. Paste it into ChatGPT, Claude, Gemini and Microsoft Copilot and send. Ask follow-up questions to refine the answer.
Why use this Explain legacy code in plain language prompt?
This explain legacy code in plain language prompt is written for a construction contractor running several sites. It tells the assistant who the answer is for (clients, site managers and subcontractors) and the limits it must respect: site-safety regulations, permits and fixed-price budgets. That context is what turns a generic reply into one a Construction team can use straight away.
Most people type a single line and get a generic answer back. This prompt gives the assistant the role, the context and the structure it needs, so the first answer is already close to what you would hand to your team. Because it is written for Construction, it keeps the focus on what that industry measures: schedule variance and safety incidents.
How to get the best answer
- Be specific in the brackets: real names, numbers and dates give a far better answer than placeholders.
- Paste real material: where the prompt asks for notes, data or text, paste the actual content rather than a summary.
- Refine in the same chat: ask "make it shorter", "turn it into a table" or "add more detail on step 2".
- Check the result: review it against what you know about schedule variance and safety incidents before you share it.
Other industries
Same prompt for other industries
The same explain legacy code in plain language prompt, rewritten for each industry.
FAQ
Frequently asked questions
Which AI assistant works best with this Explain legacy code in plain language prompt?
It works in any chat assistant. It suits ChatGPT, Claude, Gemini and Microsoft Copilot best. Paste it in, send it, and ask follow-up questions in the same chat.
What do I need to replace before sending it?
Replace the highlighted bracket – [PASTE CODE] – with your own details. The more specific you are, the better the answer.
Is this prompt only for Construction?
This version is written for a construction contractor running several sites. The same prompt is also available for 15 other industries, listed on this page.
Is it free to use?
Yes. Copy it as often as you like and use it in your own work. No sign-up is needed.
Can I trust the answer?
Treat it as a strong first draft. Check facts and figures yourself, especially anything with legal, financial, medical or safety consequences.
Keep exploring