PROMPT QUALITY DEMO — "The Same Question, Two Ways"
=====================================================

Try both of these prompts in Copilot using the project context below.
Notice how the output changes when you give AI something to work with.


── PROJECT CONTEXT (paste this before each prompt) ──────────────

Project: Seismic Retrofit of the Riverdale Community Bridge
Client: City of Riverdale Public Works Department
Budget: $4.2M | Timeline: 14 months (March 2026 – May 2027)
Team: 6 structural engineers, 2 geotechnical specialists, 1 project manager
Key deliverables: Site assessment report, retrofit design package,
construction oversight, final inspection and certification
Known risks: Permit delays (avg 6–8 weeks), discovery of legacy materials
(lead paint, asbestos), winter weather construction windows
Status: Site assessment complete. Design phase 60% done. Permit submitted.


── PROMPT A (Vague) ─────────────────────────────────────────────

Help me write a project summary.


── PROMPT B (Specific) ──────────────────────────────────────────

As a mechanical engineer presenting to a non-technical client,
summarize this project scope in 200 words. Focus on timeline,
deliverables, and risks. Use plain language.


── WHAT TO LOOK FOR ─────────────────────────────────────────────

After running both, compare:

  1. AUDIENCE FIT — Does it sound like it's written for the client,
     or for another engineer?

  2. STRUCTURE — Does it prioritize what matters (timeline, risks),
     or give a generic overview of everything?

  3. LENGTH — Is it concise and controlled, or did it ramble?

  4. USEABILITY — Could you paste it into an email right now,
     or does it need heavy editing first?

The difference isn't magic. It's context.
Role + audience + format + focus = better output on the first try.