Generate Comprehensive Change Request Forms

This skill specializes in designing and implementing change request forms for project management and organizational governance, covering change control processes, impact assessment methodology, approval workflows, and the critical elements needed for effective project-scope change management. Its core components are a unique identifier scheme (sequential or coded, e.g. CR-YYYY-XXX), requestor information (name, role, department, contact, date), change classification across scope, schedule, budget, quality, and resource changes, a priority level (critical, high, medium, low) with clear criteria, a multi-dimensional impact assessment (technical, financial, schedule, resource, and risk consequences), and a tiered approval workflow based on the scale of the change. Change categories break down further - scope changes (feature additions/removals, requirement modifications, deliverable changes), schedule changes (milestone adjustments, timeline extensions, dependency modifications), budget changes (cost increases/decreases, resource reallocation, vendor/contract changes), and quality changes (standards modifications, acceptance criteria updates, testing requirement changes).

Use this skill when building a formal change request process for project or organizational governance that needs multi-dimensional impact assessment and tiered approval rather than an ad hoc sign-off. It defines a concrete four-tier approval matrix by cost and schedule impact: low-impact changes (under $5,000, under 1 week) need only project manager approval, medium ($5,000-$25,000, 1-4 weeks) adds a department head, high ($25,000-$100,000, 1-3 months) adds a steering committee, and critical (over $100,000, over 3 months) adds an executive sponsor. It is not meant for informal or low-stakes changes that don't need documented impact analysis and multi-level sign-off - its own best practices call for conditional field logic and real-time cost/schedule calculators, which is overhead a lightweight internal tweak doesn't need.

Given a proposed change, the skill structures a form covering current-state description (what exists today, current stakeholders), the proposed change with expected outcomes and acceptance criteria, and business justification (why the change is needed, business value, cost of not doing it). It produces a multi-dimensional impact assessment - technical impact (affected systems, integration points, risk level, a 1-10 implementation complexity scale), financial impact (estimated cost, cost breakdown by labor/materials/external, budget variance percentage, ROI timeline), schedule impact (additional time needed, critical-path effect, milestone and dependency adjustments), and resource impact (staffing needs, skill gaps, equipment, vendor involvement) - plus a risk matrix scoring technical complexity, resource availability, stakeholder resistance, and integration issues by probability and impact with mitigation strategies and a go/no-go recommendation. It also defines a status-tracking schema (Submitted, Under Review, Approved, Rejected, Implemented, Closed statuses with cost, hours, and completion dates), a stakeholder communication plan tied to notification triggers (submission, status updates, implementation milestones, completion), and an implementation checklist covering resource confirmation, technical solution approval, test planning, user training, launch date, and rollback plan.

PMOs and project managers building or standardizing a change control process who need the full lifecycle - form design, impact analysis, tiered approval, risk assessment, and implementation tracking - not just an intake form. It suits organizations that want automated routing based on impact thresholds, standardized cost estimation templates by change category, and integration with project management, financial, and resource management systems for dashboard-level portfolio analysis and compliance reporting.