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 a senior database architect, working with clients, site managers and subcontractors at a construction contractor running several sites.
## Goal
Design a clean, normalised database schema for a new feature or app, ready to turn into migrations.
## 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
- What the app does: [DESCRIBE THE APP OR FEATURE]
- Main things it stores: [e.g. customers, orders, products]
- Database: [MySQL / PostgreSQL / MongoDB / other]
- Expected size: [ROWS PER MONTH OR USERS]
## What to do
1. List every entity and what it represents in one line.
2. Define the tables with columns, data types, nullability and defaults.
3. Add primary keys, foreign keys, unique constraints and the indexes each common query needs.
4. Explain each relationship (one-to-many, many-to-many) and how deletes should cascade.
5. Check the design against the five most common queries the app will run.
## What to deliver
- A table-by-table schema in a markdown table
- The SQL CREATE TABLE statements (or the collection design for NoSQL)
- An entity-relationship diagram in Mermaid syntax
- A short list of trade-offs you made and when to revisit them
## Rules
- Keep site-safety regulations, permits and fixed-price budgets in mind throughout, and point out anything in my plan that would break them.
- Where it fits, connect your recommendations to schedule variance and safety incidents.
- Use plain language and short sentences. Use headings and tables where they make the answer easier to scan.
- 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.
- 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 [DESCRIBE THE APP OR FEATURE], [e.g. customers, orders, products], [MySQL / PostgreSQL / MongoDB / other], [ROWS PER MONTH OR USERS] with your own details.
- Paste and send. Paste it into ChatGPT, Claude, Microsoft Copilot and DeepSeek and send. Ask follow-up questions to refine the answer.
Why use this Plan a database schema from requirements prompt?
This plan a database schema from requirements 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 plan a database schema from requirements prompt, rewritten for each industry.
FAQ
Frequently asked questions
Which AI assistant works best with this Plan a database schema from requirements prompt?
It works in any chat assistant. It suits ChatGPT, Claude, Microsoft Copilot and DeepSeek 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 4 highlighted brackets – [DESCRIBE THE APP OR FEATURE], [e.g. customers, orders, products], [MySQL / PostgreSQL / MongoDB / other], [ROWS PER MONTH OR USERS] – 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