Change Management

Change management provides detailed visibility into exactly what changed in your statements of work over time. See precise differences between versions, understand the impact of changes, and communicate modifications clearly to stakeholders.

What is Change Management?

Change management helps you:

See Exact Changes: Know precisely what was added, modified, or removed
Understand Impact: Assess how changes affect the project
Communicate Changes: Show stakeholders what's different
Support Approvals: Help approvers review only what changed
Track Evolution: Understand how requirements evolved
Maintain Accountability: Know who changed what and when
Enable Auditing: Demonstrate change control for compliance

How Change Tracking Works

Automatic Change Detection

Every version captures changes:

Added items, criteria, or tests (shown in green)
Modified content (shown in yellow/orange)
Removed content (shown in red)
Moved or reordered items
Status changes
Metadata updates

Changes are tracked at multiple levels:

SOW level (title, description, status)
Item level (work items added, modified, removed)
Criterion level (acceptance criteria changes)
Test level (test definitions)
Hierarchy level (parent-child relationships)

Change Types

Addition (New content):

+ New requirement: "Mobile-first responsive design"
+ New acceptance criterion: "Works on screens 320px-4K"
+ New test: "Verify on iPhone 12 and Samsung Galaxy"

Modification (Changed content):

~ Title changed:
  From: "Navigation menu"
  To: "Responsive navigation with mobile support"

~ Description updated:
  Added 127 characters about touch interactions
  Removed 45 characters about IE11 support

Removal (Deleted content):

- Removed requirement: "Internet Explorer 11 support"
- Removed task: "Test in IE11"
- Removed 3 acceptance criteria related to IE11

Move (Reordered content):

⬆ "Mobile UI requirements" moved from position 5 to position 2
⬇ "Admin features" moved from position 2 to position 7

Status Change (Progress updates):

✓ Status changed: "In Progress" → "Complete"
✓ Criterion marked as "Met"
✓ Test result: "Passed"

Viewing Changes

Change Summary

High-level overview of all changes:

Version 4 → Version 5
Created: Dec 15, 2024 at 3:45 PM
By: Jane Smith

Summary:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📊 12 total changes

Work Items:
  + 3 added
  ~ 2 modified
  - 1 removed

Acceptance Criteria:
  + 4 added
  ~ 2 modified
  - 0 removed

Tests:
  + 2 added
  ~ 0 modified
  - 0 removed

Detailed Change Log

See every individual change:

Open SOW
Click "Version History"
Select two versions to compare
Click "View Changes"

Detailed log shows:

━━━ Work Items ━━━

✓ ADDED: Requirement "Mobile-first design"
  Description: All interfaces must be designed for mobile first,
  then enhanced for larger screens.
  Added at: Dec 15, 2024 3:30 PM
  Added by: Jane Smith

✓ MODIFIED: Requirement "Navigation menu"
  Field: title
  From: "Navigation menu"
  To: "Responsive navigation menu"
  Changed at: Dec 15, 2024 3:32 PM
  Changed by: Jane Smith

  Field: description
  Added: "Must support touch gestures and work on all screen sizes"

✓ REMOVED: Task "IE11 compatibility testing"
  Reason: IE11 is no longer supported
  Removed at: Dec 15, 2024 3:35 PM
  Removed by: Jane Smith

━━━ Acceptance Criteria ━━━

✓ ADDED: "Menu opens with smooth 300ms animation"
  Parent: Requirement "Responsive navigation menu"
  Added at: Dec 15, 2024 3:40 PM

✓ MODIFIED: "Browser compatibility"
  From: "Works in Chrome, Firefox, Safari, IE11"
  To: "Works in Chrome, Firefox, Safari, Edge (last 2 versions)"

Change Filtering

Filter changes by type:

Show only additions
Show only modifications
Show only removals
Show only status changes
Show changes by specific user
Show changes in date range

Example filters:

Filter: Show only additions
Result: See what's new in this version

Filter: Show changes by Jane Smith
Result: See everything Jane modified

Filter: Show modifications between Dec 10-15
Result: See changes during specific period

Change Comparison Views

Side-by-Side View

Compare content side by side:

Version 4                    |  Version 5
─────────────────────────────┼────────────────────────────
Navigation menu              |  Responsive navigation menu
                             |
Desktop and mobile support   |  Mobile-first design
                             |  Desktop enhancement
                             |
                             |  + Touch gesture support
                             |  + Responsive breakpoints
                             |
Supports IE11                |  Supports modern browsers

Benefits:

Easy to spot differences
See before and after
Compare full context
Understand reasoning

Inline Diff View

Changes shown in context:

Requirement: Navigation menu → Responsive navigation menu

Description:
The navigation system must support desktop and mobile
[- devices, including legacy browsers like IE11 -]
[+ devices with mobile-first design and touch support +]

Acceptance Criteria:
  1. Works in all modern browsers [~ and IE11 ~]
  2. [+ Supports touch gestures +]
  3. [+ Responsive breakpoints at 768px and 1024px +]

Color coding:

Green: Added content
Red: Removed content
Yellow: Modified content
Gray: Unchanged content

Summary View

High-level changes only:

Version 4 → Version 5

Requirements:
  + 2 new requirements added
  ~ 3 requirements modified
  - 1 requirement removed

Tasks:
  + 5 new tasks added
  ~ 1 task modified
  - 0 tasks removed

Overall:
  • Scope increased by ~15%
  • 7 new acceptance criteria
  • 0 criteria removed
  • Net addition of work

Change Annotations

Adding Context to Changes

Explain why changes were made:

View specific change
Click "Add Context" or "Annotate"

Add explanation:

Removed IE11 support per architecture decision RFC-2024-042.
Modern browser focus aligns with 99% of our user base.
Reduces testing burden and allows us to use modern CSS.

Save annotation

Annotations appear:

Next to the change in diff view
In change logs
In exports and reports
For approvers reviewing changes

Linking Changes to Decisions

Connect changes to their rationale:

CHANGE: Added "Touch gesture support"

LINKED TO:
  • RFC-2024-038: Mobile-First Strategy
  • Client meeting notes: 12/10/2024
  • User research: 85% mobile traffic
  • Decision: Approved by Jane Smith on 12/12/2024

Benefits:

Future reference
Audit trail
Onboarding new team members
Explaining to stakeholders

Change Impact Analysis

Assessing Impact

For each change, see impact:

CHANGE: Added requirement "Mobile-first design"

IMPACT:
───────────────────────────────────────
Scope: +15% (significant increase)
Tasks: +8 new implementation tasks
Tests: +12 new test cases
Timeline: +2 weeks estimated
Dependencies: Requires mobile testing devices
Risk: Medium (new approach for team)
Approvals: Requires client sign-off

AFFECTED AREAS:
  • All UI components
  • Responsive layouts
  • Touch interactions
  • Performance requirements

Change Metrics

Track change patterns:

By type:

40% additions (scope growth)
35% modifications (refinements)
15% removals (scope reduction)
10% reorganization

By source:

50% from client feedback
30% from technical decisions
15% from testing insights
5% from compliance needs

By frequency:

Average 5 changes per version
Peak changes in v3-v4 (client review phase)
Fewer changes as project stabilizes

Use metrics to:

Identify scope creep
Plan for change cycles
Estimate review time
Improve change process

Communicating Changes

Change Highlights for Stakeholders

Create stakeholder-friendly summaries:

What's New in Version 5

🎯 Key Changes:
──────────────
1. Mobile-First Design Added
   Why: 85% of users access via mobile
   Impact: Better mobile experience

2. IE11 Support Removed
   Why: Less than 1% of traffic
   Impact: Faster development, modern features

3. Touch Gestures Added
   Why: Improve mobile usability
   Impact: More intuitive interactions

📊 By The Numbers:
──────────────────
  • 3 new requirements
  • 8 new implementation tasks
  • 2 weeks added to timeline
  • All changes client-requested

✅ Next Steps:
──────────────
  • Review and approve changes
  • Confirm timeline adjustment
  • Schedule design review

Email Change Notifications

When distributing new versions:

Include automatic change summary:

Subject: SOW v5 Ready for Review - Key Changes Highlighted

Hi John,

I've created version 5 of the Website Redesign SOW
incorporating the mobile-first requirements we discussed.

KEY CHANGES:
  • Added mobile-first design approach
  • Removed IE11 support (per our agreement)
  • Added touch gesture interactions
  • Updated acceptance criteria for responsive design

IMPACT:
  • Timeline: +2 weeks
  • Budget: No change (within contingency)
  • Quality: Improved mobile experience

You can review the full changes here: [Compare v4 to v5]

Please approve by Friday if this looks good.

Thanks!

Change Reports

Generate formal change reports:

For compliance:

CHANGE REPORT
SOW: Website Redesign
Versions: v4 to v5
Date: December 15, 2024
Prepared by: Jane Smith

SUMMARY:
12 changes made
- 5 additions
- 4 modifications
- 3 removals

APPROVALS:
Technical Lead: Approved 12/15
Product Owner: Approved 12/15
Client: Pending

IMPACT ASSESSMENT:
Timeline: +2 weeks
Budget: $0 (within contingency)
Risk Level: Low
Quality Impact: Positive

CHANGE DETAILS:
[Detailed list of all changes...]

Change Approval Workflow

Review Changes for Approval

Approvers see changes clearly:

Receive notification of new version
Click "Review Changes"
See highlighted differences from last approved version
Review each change:
- Read change description
- Understand impact
- See context
- Check annotations
Make decision:
- Approve all changes
- Request modifications
- Reject specific changes
- Add comments

Approver view includes:

Side-by-side comparison
Change highlights
Impact summary
Timeline adjustments
Budget implications

Selective Approval

Approve some changes, reject others:

Version 5 Change Review

✓ APPROVE: Mobile-first design [Accept]
  Comment: "Great idea, aligns with strategy"

✓ APPROVE: Touch gestures [Accept]
  Comment: "Essential for mobile experience"

✗ REJECT: Remove IE11 support [Reject]
  Comment: "Need to support enterprise clients on IE11"

? QUESTION: Additional 2-week timeline
  Comment: "Can we reduce this to 1 week?"

Result:

Approved changes stay
Rejected changes removed
Questions addressed
New version created with accepted changes

Change Control Best Practices

Managing Change Requests

Process for handling changes:

Document the Request:
- What needs to change
- Why it's needed
- Who requested it
- When it's needed
Assess Impact:
- Scope effect
- Timeline effect
- Budget effect
- Risk level
Get Approval:
- Technical approval
- Business approval
- Client approval (if needed)
- Budget approval (if needed)
Implement Change:
- Update SOW
- Create new version
- Document rationale
- Notify stakeholders
Track and Review:
- Add to change log
- Update metrics
- Review in retrospective

Change Freeze Periods

When to freeze changes:

During client approval
Before major milestones
During implementation sprints
Before delivery

During freeze:

Document requested changes
Queue for next change window
Only critical bugs allowed
Emergency process for urgent changes

Change Thresholds

Define when approval is needed:

Minor changes (no approval needed):

Typo fixes
Clarifications
Formatting updates
Non-functional changes

Moderate changes (team approval):

New acceptance criteria
Modified test cases
Reordered items
Status updates

Major changes (client approval needed):

New requirements
Removed requirements
Significant scope changes
Timeline impacts
Budget impacts

Troubleshooting

Changes Not Showing

If differences aren't visible:

Refresh the page
Clear browser cache
Try different comparison view
Verify versions are different
Check your permissions