Render Request Intake & Deadline Plan
Photoreal asks without last-minute chaos
Standardizes visualization requests by capturing scope, audience, and purpose up front, then generates a production plan — assets needed, shot list, review dates, and a change-lock deadline — so renders get done on time instead of at 3 AM.
INGREDIENTS
PROMPT
Create a skill called "Render Request Intake & Deadline Plan". When someone asks for renderings or visuals, you should: 1. Capture the intent: who is the audience, what's the purpose (sell / approve / permit / public presentation), and what's the minimum set of visuals needed? 2. Generate a shot list with an input checklist: model state required, entourage, materials, and site context for each shot 3. Create a review calendar: draft delivery → review round(s) → final lock date (default: 3 days before the external deadline) 4. Draft an expectation-setting note for the client: when changes stop, what late changes cost, and how many review rounds are included Default output: 1 hero exterior, 2 interior views, 1 massing diagram. Default review rounds: 2.
How It Works
Someone says "we need renderings" and suddenly it's a week before the
deadline with no shot list, half the materials unmapped, and three rounds of
"can we just try a different angle?" ahead of you. This recipe captures the
intent and scope of a visualization request up front, generates a realistic
production plan, and sets a clear change-lock date — so everyone knows when
changes stop and what late changes cost.
What You Get
- Intent capture: is this to sell, get approval, support a permit, or present to the public? The answer shapes everything else
- Shot list + input checklist: specific views needed, plus model state, entourage, materials, and site context requirements
- Review calendar: draft → review → final lock dates, with buffer built in
- Expectation-setting note: a client-ready message explaining when changes stop and what late changes mean for the schedule
Setup Steps
- When a render request comes in, run the intent capture: audience, purpose, and minimum viable visuals
- Generate the shot list (e.g., 1 hero exterior, 2 interior views, 1 massing diagram)
- Set review rounds (default: 2) and the final lock date (default: 3 days before deadline)
- Send the expectation-setting note to the client or stakeholder before work begins
Tips
- The expectation-setting note is the most important deliverable — it prevents revision spirals by making the rules explicit
- "Minimum viable visuals" is a powerful framing; it stops scope from expanding to "one more view" indefinitely
- Lock the model state before rendering begins; mid-render model changes are the #1 cause of wasted time
- For public meetings (planning, neighborhood), images often need to be more neutral than marketing renders — capture that intent early