Architecture Service Request Form
Purpose
The Service Request Form is used to request architecture services, guidance, or consultation from the Architecture Practice team. This form ensures all necessary information is captured for efficient triaging and fulfillment.
When to Use
- Requesting architectural guidance for new initiatives
- Asking for design review of existing architecture
- Seeking help with technology evaluations
- Requesting design patterns or best practices
- Asking for architecture mentoring or training
- Submitting issues or concerns about existing systems
Service Request Form
═══════════════════════════════════════════════════════════════════
ARCHITECTURE SERVICE REQUEST
═══════════════════════════════════════════════════════════════════
REQUEST INFORMATION
───────────────────
Ticket ID: [Auto-generated]
Submitter Name: ___________________________________
Team/Department: ___________________________________
Email: ___________________________________
Phone: ___________________________________
Date Submitted: ___________________________________
Priority: ☐ Low (Normal capacity planning)
☐ Medium (Important for roadmap)
☐ High (Time-sensitive)
☐ Critical (Blocking production)
═══════════════════════════════════════════════════════════════════
SERVICE TYPE
────────────
Select the type of service needed:
☐ ARCHITECTURE DESIGN
├─ New system/application design
├─ Architecture improvement/modernization
├─ System integration planning
└─ Performance optimization
☐ DESIGN REVIEW
├─ Architecture review
├─ Security architecture review
├─ Data architecture review
├─ API design review
└─ Technology stack review
☐ TECHNOLOGY EVALUATION
├─ Technology assessment
├─ Tool/platform evaluation
├─ Vendor evaluation
└─ Build vs. buy analysis
☐ GUIDANCE & CONSULTATION
├─ Best practices guidance
├─ Pattern selection
├─ Problem-solving
└─ Architecture coaching
☐ TRAINING & MENTORING
├─ Architecture training
├─ Team mentoring
├─ Workshop facilitation
└─ Knowledge sharing
═══════════════════════════════════════════════════════════════════
PROJECT INFORMATION
───────────────────
Project/Initiative Name: ___________________________________
Project Description:
[Provide 2-3 sentence description]
___________________________________________________________
___________________________________________________________
___________________________________________________________
Business Context:
- Business objective: ____________________________________
- Key stakeholders: _____________________________________
- Expected business impact: ______________________________
- Timeline/deadline: ____________________________________
Technical Scope:
- Systems involved: _____________________________________
- Technology stack (if known): ___________________________
- Scale/load requirements: ______________________________
- Integration requirements: ______________________________
Current State (if applicable):
- Current architecture: _________________________________
- Key problems/gaps: ____________________________________
- Existing constraints: _________________________________
═══════════════════════════════════════════════════════════════════
SPECIFIC REQUEST DETAILS
────────────────────────
What specific guidance or services do you need?
___________________________________________________________
___________________________________________________________
___________________________________________________________
What have you already tried or considered?
___________________________________________________________
___________________________________________________________
What is the expected outcome?
___________________________________________________________
___________________________________________________________
What are the success criteria?
___________________________________________________________
___________________________________________________________
What constraints or requirements must we consider?
☐ Cost constraints: Budget $ ______
☐ Timeline constraints: By ________
☐ Technology constraints: ________________________________
☐ Organizational constraints: ____________________________
☐ Security/compliance requirements: ______________________
☐ Other: ________________________________________________
═══════════════════════════════════════════════════════════════════
RESOURCE INFORMATION
────────────────────
Team size: ☐ 1-3 ☐ 4-10 ☐ 10-20 ☐ 20+
Team experience level: ☐ Junior ☐ Mid-level ☐ Senior ☐ Mixed
Architecture expertise in team: ☐ None ☐ Some ☐ Significant
Key contacts (beside submitter):
- Technical Lead: ________________________________________
- Business Owner: ________________________________________
- Decision Maker: ________________________________________
Preferred engagement model:
☐ Async (documentation, email, Slack)
☐ Synchronous (meetings, workshops)
☐ Hybrid (combination)
Preferred duration:
☐ Quick consult (< 1 hour)
☐ Short-term (1-4 weeks)
☐ Medium-term (1-3 months)
☐ Long-term (ongoing)
═══════════════════════════════════════════════════════════════════
ATTACHMENTS & REFERENCES
────────────────────────
☐ Current architecture diagrams
☐ Technical design documents
☐ Performance metrics/data
☐ Problem statements
☐ Requirements documents
☐ Previous evaluations
☐ Other: ________________________________________________
Attached files:
- File 1: ________________________________________________
- File 2: ________________________________________________
- File 3: ________________________________________________
Related links/references:
- Link 1: ________________________________________________
- Link 2: ________________________________________________
═══════════════════════════════════════════════════════════════════
ADDITIONAL INFORMATION
──────────────────────
Is this request related to:
☐ Cloud migration
☐ Modernization/refactoring
☐ New product/feature
☐ Performance improvement
☐ Security improvement
☐ Cost optimization
☐ Scalability/growth
☐ Operational excellence
☐ Other: ________________________________________________
Are there any related or dependent initiatives?
___________________________________________________________
___________________________________________________________
What is your preferred communication channel?
☐ Email
☐ Slack
☐ Meeting (scheduled)
☐ Whiteboard session
☐ No preference
Any other relevant information?
___________________________________________________________
___________________________________________________________
___________________________________________________________
═══════════════════════════════════════════════════════════════════
SERVICE REQUEST CHECKLIST
──────────────────────────
Before submitting, ensure:
☐ Service type is clearly selected
☐ Project/initiative is clearly described
☐ Business context is provided
☐ Specific request is articulated
☐ Expected outcome is defined
☐ Success criteria are identified
☐ Key constraints are listed
☐ Key contacts are identified
☐ Relevant documents are attached
☐ Timeline expectations are clear
☐ Preferred engagement model is selected
═══════════════════════════════════════════════════════════════════
ROUTING & ASSIGNMENT
─────────────────────
[Form Processing - Completed by Architecture Practice Team]
Primary Architect: _____________________________________
Secondary Architect: ___________________________________
Estimated Start Date: __________________________________
Estimated Duration: ____________________________________
Assigned Priority: ☐ Urgent ☐ High ☐ Medium ☐ Low
Risk Level: ☐ Critical ☐ High ☐ Medium ☐ Low
═══════════════════════════════════════════════════════════════════
ENGAGEMENT PLAN
────────────────
☐ Initial kickoff meeting scheduled: ____________________
☐ Requirements clarification completed
☐ Scope agreed upon
☐ Deliverables defined
☐ Communication plan established
☐ Timeline committed
═══════════════════════════════════════════════════════════════════
SUBMISSION INSTRUCTIONS
───────────────────────
1. Complete all applicable sections
2. Attach supporting documents
3. Submit via:
- Email: architecture-requests@example.com
- Slack: #architecture-requests channel
- Web form: https://example.com/architecture/request
4. You will receive a confirmation within 1 business day
5. Initial assessment within 5 business days
6. Engagement to begin within 10 business days (or as agreed)
═══════════════════════════════════════════════════════════════════
FREQUENTLY ASKED QUESTIONS
───────────────────────────
Q: How long does it typically take to fulfill a request?
A: Depends on request type:
- Quick consult: 1-3 days
- Design review: 1-2 weeks
- Full architecture design: 4-12 weeks
- Technology evaluation: 2-4 weeks
Q: Can I request a specific architect?
A: Yes, but availability may vary. We'll assign the best match.
Q: What if the scope grows during engagement?
A: Scope changes require agreement. We'll discuss options.
Q: Are there any costs for these services?
A: Architectural services are included in the Architecture Practice budget
for internal teams. External consultants may require different
arrangements.
Q: How do I escalate if I'm not satisfied?
A: Contact the Architecture Practice Lead or VP of Architecture.
═══════════════════════════════════════════════════════════════════
Service Types & Typical Timelines
Architecture Design Service
When to Request:
- Starting a new system
- Major refactoring/modernization initiative
- Complex integration project
Typical Deliverables:
- System context diagram
- Architecture decision records
- Technology recommendations
- Design patterns applied
- Implementation roadmap
- Risk assessment
Timeline: 4-12 weeks depending on complexity
Effort: 40-160 hours
Design Review Service
When to Request:
- Have draft design, want expert feedback
- Want to validate architecture decisions
- Before major commitment of resources
Typical Deliverables:
- Review comments and feedback
- Issues identified and prioritized
- Recommendations for improvement
- Decision support
Timeline: 1-2 weeks
Effort: 20-40 hours
Technology Evaluation Service
When to Request:
- Considering new technology/tool
- Need vendor comparison
- Want data-driven recommendation
Typical Deliverables:
- Evaluation criteria and scoring
- Comparison matrix
- Recommendation with rationale
- Risk assessment
- Implementation guidance if selected
Timeline: 2-4 weeks
Effort: 30-60 hours
Guidance & Consultation Service
When to Request:
- Need architectural advice on specific problem
- Want best practices guidance
- Seeking second opinion
Typical Deliverables:
- Verbal/written guidance
- Decision support
- Pattern recommendations
- Coaching for team
Timeline: 1-5 days
Effort: 5-20 hours
Training & Mentoring Service
When to Request:
- Want to upskill team in architecture
- Need mentoring for junior architects
- Want workshops on specific topics
Typical Deliverables:
- Training materials
- Workshop facilitation
- Coaching sessions
- Knowledge transfer
Timeline: Varies (can be ongoing)
Effort: 10-40+ hours
Related Resources
Status: Complete
Last Updated: November 2025
Version: 1.0
Contributors: Architecture Practice Team