This Change Requests Log Software Development document shows how Eduardo Montes tracked all four change requests submitted during the ProjectAdm SaaS platform development — from CR-001 (dark mode pulled forward) through CR-004 (WBS view added) — in a single Excel register that gave the team and steering committee a clear audit trail of every scope, cost, and schedule change made across 28 sprints and 13.5 months.

What Is a Change Requests Log?

A Change Requests Log is a PMBOK 8 output in the Planning Performance Domain that records all change requests submitted during a project, their evaluation status, approval or rejection decision, cost and schedule impact, and implementation status. It serves as the definitive audit trail for the integrated change control process — demonstrating that every change to the project baselines was formally evaluated, appropriately approved, and properly implemented. Without a change requests log, projects are vulnerable to scope creep, budget overruns, and disputes about what was agreed and when.

What This Change Requests Log Software Development Includes

The ProjectAdm Change Requests Log covers all four CRs with full lifecycle tracking:

• CR-001 — Dark Mode Pulled Forward — Submitted: Jan 28, 2025 (Sprint 2); Requestor: Henry Douglas; Type: Schedule (feature resequencing); Description: Move dark mode implementation from Sprint 24 to Sprint 16–18 based on beta user feedback; Cost impact: $0 (within existing capacity); Schedule impact: Swap with lower-priority feature; Status: APPROVED Feb 4, 2025; Delivered: Sprint 18 (2 weeks early due to Camila Rocha's design system documentation)
• CR-002 — Gantt Chart Module Added — Submitted: Feb 14, 2025 (Sprint 4); Requestor: Henry Douglas; Type: Scope + Cost; Description: Add fully interactive Gantt chart view with task dependencies, drag-to-reschedule, critical path, and PDF export; Cost impact: +$4,500 (contingency draw); Schedule impact: +2 sprints absorbed in buffer; Status: APPROVED Feb 21, 2025; Delivered: Sprint 14 (accepted M3); Contingency balance after: $37,500
• CR-003 — PagSeguro Integration Removed — Submitted: Mar 8, 2025 (Sprint 6); Requestor: Eduardo Montes; Type: Scope reduction; Description: Remove PagSeguro payment gateway integration from scope; Rationale: webhook reliability concerns and low projected LATAM transaction volume; Cost impact: -$3,200 (avoidance); Schedule impact: Freed 2 sprint stories for buffer; Status: APPROVED Mar 15, 2025; Scope Baseline updated v1.3; No implementation required (feature never started)
• CR-004 — WBS View Added — Submitted: Apr 2, 2025 (Sprint 8); Requestor: Henry Douglas; Type: Scope addition; Description: Add Work Breakdown Structure view (3-level hierarchy, expand/collapse, export) to compete with enterprise PM tools; Cost impact: $0 (within existing capacity — absorbed from CR-003 savings); Schedule impact: +1 sprint (Sprints 21–22); Status: APPROVED Apr 10, 2025; Delivered: Sprint 22 (accepted M4)
• Log Summary Statistics — Total CRs submitted: 4; Approved: 4 (100%); Rejected: 0; Net cost impact: +$1,300 (CR-002 +$4,500 – CR-003 -$3,200); Net contingency used: $4,500; Contingency remaining at closure: $37,500; Net schedule impact: 0 days (all absorbed in buffer or offset by scope reductions)
• CCB Decision Records — All 4 CRs evaluated by CCB (Eduardo Montes + Henry Douglas) within 5 business days of submission; all decisions documented in meeting minutes with rationale; no CCB escalations to ProjectAdm International Board required

How Eduardo Montes Used This Change Requests Log Software Development

Eduardo Montes used the Change Requests Log Software Development at every milestone gate to present the net impact of all approved changes. At M5 (Go-Live), the log clearly showed that four approved changes had a net positive effect: $1,300 added to cost (well within contingency), 0 days added to the schedule, and the Gantt chart (CR-002) and WBS view (CR-004) added significant product value that was already generating interest from enterprise beta users. The log transformed what could have been a "change management failure" narrative into a "effective change control" success story.

How to Use This Change Requests Log Software Development Document

When maintaining your own Change Requests Log Software Development, always record the "net impact" column showing cumulative cost and schedule effects of all approved changes together. Individual CRs may look costly in isolation; the net view shows whether change control is working effectively to keep the project within its overall constraints.

Download the Template and Deepen Your Knowledge

Ready to create your own change requests log? Download the blank Change Requests Log Template (PMBOK 8).

• Download the Change Requests Log Template — PMBOK 8 (blank, ready to use)
• Read the full guide: Change Requests Log in PMBOK 8

Want to go deeper? The PMBOK Guide 8th Edition is the definitive reference for modern project management. Get your copy and use it alongside these examples to build a solid, practical understanding of every performance domain.

Format: Microsoft Excel (.xlsx) | Project: Software Development (SaaS Platform) | PMBOK Edition: 8th (2025) | Domain: Planning