Architecture Scope Change Request Manager

How It Works

Every architect knows the pattern: a client says "just a small tweak" and

three weeks later you've redesigned the kitchen for free. This recipe catches

change language in emails, tracks revision counts against your contract limits,

and generates a professional impact memo before the work starts — so the

conversation stays about scope, not about feelings.

What You Get

• Change request register: each change gets a CR number, date, requester, and phase tag
• Clarifying questions: 2–4 targeted questions to lock the change definition before any work begins
• Impact checklist: automatic scan across drawings, model, consultants, permit status, schedule, and CA implications
• One-page impact memo: client-ready document showing time + fee + schedule delta with approval signature block
• Decision register update: approved changes logged with consultant notifications triggered automatically

Setup Steps

1. Set your revision limits per phase (e.g., SD: 2, DD: 2, CD: 1)
2. Define your budget change threshold (e.g., 10% cost or area change triggers a CR)
3. Choose your memo style (concise-professional works for most practices)
4. Set approval mode (written confirmation required vs. verbal + follow-up)
5. Connect to email and messaging to catch change-language triggers automatically

Tips

• The biggest value is the impact memo — clients rarely push back when they see the numbers in writing
• Flag common trigger phrases ("just adjust", "small tweak", "last minute", "while you're at it") for automatic detection
• Keep the tone neutral and factual; the memo does the boundary-setting so you don't have to
• Review the revision counter at each phase transition to catch accumulated creep