Purpose
The Assumptions & Constraints Log Template provides a structured format for capturing, reviewing, and monitoring the underlying conditions that shape project execution. Its purpose is to ensure lean PM teams (1–3 members) can explicitly document factors that are accepted as true (assumptions) and factors that restrict or limit choices (constraints). By recording these elements early and monitoring them throughout the lifecycle, Project Managers reduce ambiguity, manage risk proactively, and prevent untested assumptions from derailing the project.
Many projects fail not because of flawed execution, but because key assumptions proved false or constraints were underestimated. This template mitigates that risk by making all critical conditions visible, testable, and traceable. It also supports informed decision-making during planning and scope control by distinguishing between negotiable assumptions and non-negotiable constraints.
For Memorres projects, where teams often operate with lean resources, the ability to quickly validate assumptions and plan around constraints is essential. This template provides a repeatable structure that ensures accountability by assigning ownership and status to each entry. It also enables sponsors and stakeholders to challenge or validate project conditions before committing resources.
Scope
This template applies to all projects managed by the Memorres Project Management Department. It is mandatory during the Requirements & Scope Baseline phase and must be completed alongside the Requirements Specification. The log must be updated throughout the project lifecycle whenever assumptions change or new constraints are identified.
The scope of this template includes recording business, technical, operational, and external assumptions, as well as fixed constraints such as budget caps, deadlines, compliance obligations, or resource limits. It supports planning, risk management, and change control by linking each entry to objectives and monitoring methods.
The template excludes detailed technical limitations or solution-specific design constraints, which are owned by delivery teams. The Project Manager is responsible for maintaining the log, with stakeholders accountable for validating assumptions and sponsors accountable for approving constraints that impact budget, scope, or schedule.
Main Section
Table 1: Header Fields
| Field | Description | Example |
| Project Title | Name of the project | “Client Portal Modernization” |
| Version | Document version | v1.0 |
| Prepared By | Project Manager | [PM Name] |
| Date | Date of preparation | 12-Sep-2025 |
| Approved By | Sponsor/PMO | [Sponsor Name] |
| Approval Date | Date of sign-off | 14-Sep-2025 |
Table 2: Assumptions & Constraints Log
| ID | Type (Assumption/Constraint) | Description | Impact if Invalid | Validation/Monitoring Method | Owner | Status | Example |
| A-001 | Assumption | Client will provide SMEs for requirements workshops | Delays in capturing requirements | Confirm SME availability via email before workshops | Project Manager | Open | SME confirmation requested |
| A-002 | Assumption | Third-party APIs will be stable and accessible | Integration delays if unstable | Validate via test calls before development | Tech Lead | Open | API test scheduled |
| C-001 | Constraint | Project must complete by 30-Nov-2025 | Cannot extend schedule beyond date | Monitor schedule variance weekly | Sponsor | Approved | Deadline fixed by contract |
| C-002 | Constraint | Budget capped at 300 hours effort | Cannot exceed resource allocation | Monitor hours via time tracking policy | PMO | Approved | Budget envelope logged |
Table 3: Approval Record
| Approver | Role | Signature/Date | Example |
| [Sponsor Name] | Project Sponsor | [Signed 14-Sep-2025] | CIO sign-off |
| [PM Name] | Project Manager | [Signed 12-Sep-2025] | PM sign-off |
Closing Note & Cross-References
The Assumptions & Constraints Log Template ensures that project teams do not rely on undocumented conditions or overlook critical restrictions. It provides visibility, accountability, and monitoring for factors that directly influence project feasibility and planning. By requiring explicit documentation, ownership, and status tracking, the template safeguards projects against surprises and unmanaged risks.