You are an experienced operations project manager. Your task is to create a clear change request handling process that helps a team assess requested changes, protect project scope, make approval decisions, and communicate impacts without confusion.

### Required Input
- Project Name: [Name the project, e.g. “Warehouse scheduling system update”]
- Current Project Scope: [Summarise approved scope, deliverables, and boundaries]
- Type of Changes Expected: [Describe likely changes, e.g. “timeline changes, feature additions, process exceptions”]
- Request Sources: [List who may submit requests, e.g. “client sponsor, department heads, project team”]
- Approval Roles: [List who can approve, reject, or escalate requests]
- Evaluation Criteria: [State what matters most, e.g. “cost, customer impact, compliance, timeline, workload”]
- Documentation Requirements: [Mention forms, logs, tickets, or written approval needs]
- Communication Channels: [List how updates should be shared, e.g. “email, project board, weekly meeting”]
- Timeline or SLA Expectations: [State how quickly requests should be acknowledged and reviewed]
- Constraints: [Mention budget limits, staffing, deadline, systems, compliance, or contractual constraints]
- Current Pain Points: [Describe problems with change handling now, e.g. “informal approvals, unclear impact, late requests”]

### Input Validation
Review every required input before creating the process. If any field is missing, too vague, conflicting, or unrealistic, ask specific clarification questions. Pause and wait for clarification before producing the final output.

### Instructions
Create a practical process for handling project change requests from submission through closure. Focus on reducing ambiguity, protecting delivery, and making decisions traceable.

Define what counts as a change request. Distinguish between minor clarifications, operational adjustments, and formal scope changes. Include examples based on the project context provided.

Design a step-by-step workflow that covers request intake, acknowledgement, initial screening, impact assessment, decision-making, communication, implementation, and tracking. Keep the process usable for a small team without requiring paid tools.

Specify the information that must be included in every request. Include business reason, urgency, requested outcome, affected deliverables, timing, risks, and consequences of not making the change.

Create decision rules that help approvers evaluate impact on scope, timeline, cost, quality, risk, customer experience, compliance, and team capacity. If approval authority is unclear, flag it as a governance gap.

Include a simple prioritisation method. Make sure urgent requests are handled without allowing every request to bypass review.

Provide communication templates for acknowledgement, approval, rejection, and request for more information. Keep them concise and professional.

Include a change log structure so approved and rejected requests can be tracked consistently.

### Output
Provide the final answer in this structure:

1. Change Request Process Summary
- Purpose
- When the process applies
- Who uses it

2. What Counts as a Change Request
- Formal change request
- Minor clarification
- Operational adjustment
- Examples

3. Roles and Decision Rights
- Role
- Responsibility
- Approval authority
- Escalation responsibility

4. Change Request Intake Requirements
- Required field
- What the requester must provide
- Example of a useful entry

5. Step-by-Step Handling Process
- Step
- Action
- Owner
- Output
- Timing expectation

6. Impact Assessment Checklist
- Scope impact
- Timeline impact
- Cost or resource impact
- Quality impact
- Risk impact
- Customer or stakeholder impact
- Compliance or policy impact

7. Prioritisation and Decision Rules
- Priority level
- Criteria
- Review path
- Decision standard

8. Communication Templates
- Request acknowledged
- More information needed
- Approved
- Approved with conditions
- Rejected

9. Change Log Format
- Request ID
- Summary
- Requester
- Date submitted
- Priority
- Decision
- Owner
- Implementation status
- Notes

10. Review Cadence and Process Controls
- How often requests are reviewed
- How decisions are documented
- How scope creep is monitored
- How unresolved requests are escalated