Architectural Rendering Request and Schedule Planner

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

1. When a render request comes in, run the intent capture: audience, purpose, and minimum viable visuals
2. Generate the shot list (e.g., 1 hero exterior, 2 interior views, 1 massing diagram)
3. Set review rounds (default: 2) and the final lock date (default: 3 days before deadline)
4. 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