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 field app designer.
I work in Construction: a construction contractor running several sites. This work matters to clients, site managers and subcontractors.
## Goal
Make site inspections fast on a phone.
## What matters in Construction
- How customers decide: clients choose on track record, price, committed timeline and quality; contracts are fixed-price or item-rate.
- 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.
- 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
- Inspection types: [INSPECTIONS]
- Inspectors: [USERS]
- Site conditions: [CONDITIONS]
- Reports needed: [REPORTS]
- Anything else you should know: [EXTRA CONTEXT, or "none"]
## How to work through it
1. Restate the users, their main task, the platform and the business goal. Note what research or analytics would sharpen the answer.
2. Map each inspection type and its checks.
3. Design one-tap pass, fail and not-applicable answers.
4. Design photo capture with notes and location.
5. Plan full offline use with later syncing.
6. Design reports that build themselves from the answers.
7. Design large controls for gloves and bright sunlight.
8. Test the app on a live site.
9. Check the result against accessibility basics: contrast, focus states, labels, touch targets and screen readers.
10. Say how to test it with five real users and what to watch for.
## What to deliver
- Checks
- Forms
- Photos
- Offline
- Test
## Expert rules
- Design for the user's goal first; remove anything that does not help them complete it.
- Follow established patterns unless there is a clear reason not to.
- Be specific: name components, states (empty, loading, error, success) and exact copy.
- 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
- Describe layouts top to bottom, section by section.
- Use tables for flows, states and copy.
- Give exact microcopy in quotes.
## Before you answer
Check your draft against this list and fix anything that fails:
- Recommendations meet basic WCAG accessibility and rest on a user need, not on taste.
- 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.
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 [INSPECTIONS], [USERS], [CONDITIONS], [REPORTS], [EXTRA CONTEXT, or "none"] with your own details.
- Paste and send. Paste it into ChatGPT, Claude and Gemini and send. Ask follow-up questions to refine the answer.
Why this prompt works
The “Design a site inspection app” prompt tells the assistant exactly what to hand back: checks; forms; photos; offline; and test. It makes the assistant work through 10 steps in order, starting with "restate the users, their main task, the platform and the business goal. Note what research or analytics would sharpen the answer", instead of jumping straight to an answer. Before replying, the assistant checks its draft against 3 tests and fixes anything that fails.
If an important detail is missing, the assistant asks you up to 3 short questions before it starts, so it does not build on guesses.
How to get the best answer
- Fill every bracket with real detail: [INSPECTIONS], [USERS], [CONDITIONS] and the rest should hold real names, numbers and dates, not 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: test what it builds or writes before you rely on it.
FAQ
Frequently asked questions
Which AI assistant works best with the “Design a site inspection app” prompt?
The “Design a site inspection app” prompt works in any chat assistant and suits ChatGPT, Claude and Gemini best. Paste it in, send it, and ask follow-up questions in the same chat to refine the answer.
What do I fill in before sending the “Design a site inspection app” prompt?
Replace the 5 highlighted brackets – [INSPECTIONS], [USERS], [CONDITIONS], [REPORTS], [EXTRA CONTEXT, or "none"] – with your own details. The more specific you are, the better the answer.
Who is the “Design a site inspection app” prompt for?
Anyone who wants a complete, working result from an AI assistant. Replace the brackets with your own project details.
Is the “Design a site inspection app” prompt free to use?
Yes. First AI Prompt prompts are free to copy and use in personal and business work, with no sign-up, no account and no daily limit.
Can I trust the answer the “Design a site inspection app” prompt gives?
Treat it as a strong first draft: the prompt tells the assistant not to invent facts and to mark its assumptions, but check figures yourself, especially anything with legal, financial or safety consequences.
Keep exploring