Implementation Change Request
What an Implementation Change Request Is
Why a Clear Implementation Change Request Matters
A properly completed ICR reduces misunderstanding, limits scope creep, and protects contractual and compliance obligations by documenting approvals, cost impact, and schedule adjustments in a single record.
Who Typically Prepares and Reviews an ICR
Project teams, change control boards, IT managers, and contracting officers commonly prepare or review Implementation Change Requests to govern scope adjustments and technical modifications.
- Project Managers and PMO staff who log, prioritize, and route change requests for approval.
- Technical Leads or Architects who estimate effort, identify dependencies, and define implementation scope.
- Procurement or Contract Managers who check contractual impact, budget allowances, and vendor approvals.
Clear role separation and signatory authority speed decisions and reduce rework during implementation.
Typical Signatories and Their Roles
Project Manager
Responsible for submitting the ICR, summarizing the change, and coordinating cost and schedule estimates. The PM ensures the request contains implementation steps, rollback options, and an initial risk assessment to support decision making.
Technical Approver
A technical lead or systems architect who validates feasibility, defines required work items, and certifies the implementation approach. Their approval documents technical acceptance and clarifies dependencies and testing requirements.
Step-by-Step: Completing the Implementation Change Request
-
01Draft the Request: Record title, requester, date, and a clear change description.
-
02Assess Impact: Estimate cost, schedule, resources, compliance, and testing needs.
-
03Prepare Attachments: Attach supporting diagrams, change logs, test plans, and budget worksheets.
-
04Route for Approval: Send to listed approvers and document each approval or rejection.
How to Configure an Online ICR Workflow
| Field | Configuration |
|---|---|
| Requester | Required; auto-fill from user profile |
| Priority | Dropdown: Low | Medium | High |
| Approver Sequence | Sequential routing with reminders |
| Attachments | Allow PDF, DOCX, PNG, max 25 MB |
Where to Send and How Routing Works
-
Submitter: Uploads ICR and supporting files to the project repository or eForms portal.
-
Technical Review: Technical approver validates feasibility and impact details.
-
Commercial Review: Finance or procurement evaluates cost and contract effect.
-
Final Approval: Authorized signer records acceptance and implementation date.
Distribution and eSubmission Options
Choose a distribution method that preserves an audit trail and meets organizational security policies.
- Email: Suitable for informal notices but weaker for audit and authentication.
- Project Repository: Central storage with version control and access logs.
- eSignature Platform: Enables authenticated signing, timestamp, and certificate of completion.
Use platforms that integrate with your systems and record each action to support compliance and post-implementation audits.
Typical Timelines and Processing Expectations
Initial Acknowledgment:
1–2 business days after submission
Technical Analysis:
3–10 business days depending on complexity
Commercial Review:
5–15 business days for budget and contract checks
Implementation Window:
Scheduled per release cycle or emergency change protocol
Post-Implementation Review:
Within 5 business days after deployment
Key Milestones in the ICR Lifecycle
Submission Complete
ICR filed with required fields and attachments recorded.
Impact Evaluation
Technical and commercial impacts assessed and logged.
Approval Decision
Formal accept, defer, or reject decision recorded.
Implementation and Closure
Change applied, tested, and final acceptance recorded.
Common Mistakes to Avoid
- Insufficient detail in the change description causes delays and rework.
- Missing cost or schedule estimates prevents timely approval.
- Failure to attach rollback or test plans increases operational risk.
- Routing to incorrect approvers delays the decision and implementation.
Risks and Liability from Incorrect or Incomplete Requests
eSignature Vendor Comparison for Implementation Change Requests
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day trial | Varies | Varies | Varies | Varies |
| Bulk Send | Yes | Yes | Yes | Yes | Varies |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes (BAA) | Yes | Yes | Varies | Varies |
Frequently Asked Questions and Troubleshooting
-
What if the approver is unavailable?
Designate alternate approvers in governance documents and include escalation rules in the workflow so the ICR progresses without undue delay.
-
Can I eSign an ICR?
Yes; electronic signatures are enforceable under ESIGN and UETA for most commercial transactions, provided intent, consent, attribution, and retention are documented.
-
When is notarization required?
Notarization is uncommon for internal ICRs but may be needed for contract amendments or legal documents depending on state or contract terms.
-
How should I document rollbacks?
Include a clear rollback plan and test criteria in the ICR so implementers can reverse changes safely if issues arise.
-
What if scope or cost estimates change mid-review?
Log any estimate revisions as an amendment to the original ICR and route the amendment through the same approval chain.
-
How long should I retain the ICR?
Keep the ICR through the project lifecycle plus a statutory retention period; follow industry rules such as HIPAA or IRS where applicable.