Schedule Documentation and Control
How to Create a Schedule Assumption Log
Identify every uncertain planning statement supporting the schedule, assign an owner, establish a validation deadline, measure the effect if it proves false, and keep hidden assumptions from silently becoming schedule delays.
Purpose
A schedule assumption is provisional information—not an invisible fact
Schedules are often developed before every decision, quantity, supplier date, resource commitment, technical detail, approval condition, and external dependency is known. Planning still needs to proceed, so the team uses assumptions. The problem is not the existence of an assumption. The problem is allowing it to remain hidden, ambiguous, ownerless, or untested.
A Schedule Assumption Log is a living register of uncertain statements that materially support schedule dates, logic, durations, calendars, resources, milestones, or dependencies. It records what is being assumed, why planning requires it, who must validate it, what evidence will confirm or reject it, when that validation is needed, which schedule elements depend on it, and what action follows if it proves false.
An assumption is not the same as a confirmed fact, approved decision, active issue, or risk. It may later become any of those. The log provides the transition record so the schedule can be updated deliberately rather than surprised by an assumption that quietly expired.
Clear boundaries
Distinguish assumptions from related schedule records
| Record type | Meaning | Example | Required treatment |
|---|---|---|---|
| Fact | Verified information supported by evidence | The permit was issued on May 12 | Use the confirmed information and retain its source. |
| Assumption | Planning statement accepted temporarily without complete confirmation | The permit will be issued by May 12 | Assign validation evidence, owner, and required-by date. |
| Risk | Uncertain event or condition that may affect objectives | The permit may arrive after May 12 | Assess probability, impact, response, owner, and trigger. |
| Issue | Condition that has already occurred or is presently true | The permit decision is overdue | Assign resolution action and reflect current schedule consequences. |
| Constraint | Limit that restricts available choices | Work cannot begin before the legally permitted date | Represent it appropriately in the plan and document its basis. |
| Decision | Authorized selection among alternatives | Management approved the alternate permitting sequence | Record authority and implement the approved schedule effect. |
These categories may change over time. An assumption can be validated and become a fact, rejected and become an issue, remain uncertain and be managed as a risk, or require a formal decision. The log should preserve that history instead of deleting the original record.
Log structure
Fields every useful Schedule Assumption Log should contain
Identification
- Unique assumption ID
- Concise title
- Detailed testable statement
- Date raised and originator
- Category or workstream
Schedule connection
- Affected activity IDs
- Affected milestone or handoff
- Logic, duration, calendar, or resource effect
- Current path and float context
- Potential consequence if false
Control information
- Accountable validation owner
- Evidence required
- Validation deadline
- Trigger and fallback action
- Status, decision, and closure history
Write one assumption per record. Combining several statements makes ownership, validation, and closure unclear. “Design, procurement, and testing will all finish on time” should be separated into distinct assumptions tied to their own evidence and deadlines.
Working method
A ten-step Schedule Assumption Log process
Collect assumptions from the actual schedule basis
Review duration estimates, logic discussions, planning workshops, supplier inputs, calendars, resource plans, scope documents, interface records, risks, and decision minutes. Ask what must be true for each important date to remain credible.
Rewrite each statement so it can be tested
Replace vague wording such as “resources should be available” with a precise statement: “Two qualified reviewers will be available for the five working days beginning June 8.” Include quantity, timing, capability, location, and acceptance condition where relevant.
Separate assumptions from facts and commitments
Check whether evidence already confirms the statement or an authorized party has committed to it. Do not weaken an approved commitment by relabeling it as an assumption. Equally, do not present an unconfirmed expectation as a committed fact.
Map the assumption to schedule elements
Identify affected activities, milestones, dependencies, durations, resources, calendars, and paths. A schedule reference turns a general concern into a usable control record and makes impact analysis possible.
Estimate the consequence if the assumption is false
Describe what changes—not merely that “the schedule may be delayed.” Identify the alternate duration, required resequencing, blocked successor, lost resource window, milestone movement, or new decision likely to result.
Assign one validation owner
The owner is accountable for obtaining evidence and updating the record, even when another party supplies the information. Avoid assigning a department name without a responsible individual.
Set an evidence requirement and validation deadline
Define what will prove or disprove the statement and when the answer is needed. The deadline should precede the point at which the schedule loses useful response options—not merely the activity start date.
Define trigger and fallback action
State what happens if evidence is missing, late, or unfavorable. The response may include escalation, alternate resource, schedule scenario, risk activation, dependency change, re-estimation, or formal change control.
Review assumptions at every relevant update
Check proximity to the validation date, changed evidence, path importance, and possible downstream effect. An assumption that was harmless three months ago may become critical as work approaches.
Close without deleting history
Record whether the assumption was validated, invalidated, superseded, converted into a risk or issue, or resolved through a decision. Include evidence, decision date, schedule change, and any lesson for future planning.
Writing quality
Turn weak expectations into controlled assumptions
| Weak wording | Controlled assumption | Validation evidence |
|---|---|---|
| The supplier will deliver on time. | The supplier will deliver all accepted units to Site A by August 14. | Approved production plan, shipping confirmation, and acceptance record |
| Testing should take two weeks. | Twenty test cases will be executed in ten working days using two available environments. | Test inventory, throughput evidence, and environment booking |
| Management will approve quickly. | The review board will issue a decision within five working days of a complete submission. | Board calendar, service standard, and confirmed submission criteria |
| The team is available. | Three named specialists are allocated at least 75 percent from July 1 through July 19. | Approved resource assignment and conflict check |
| No rework is expected. | The submitted design will satisfy documented entry criteria before detailed review begins. | Completed entry checklist and reviewer acceptance |
Interactive worksheet
Schedule assumption record generator
Enter one assumption. The tool creates a structured log entry locally in the browser. Review the wording and connect it to the actual schedule before publishing or relying on it.
Prioritization
Review assumptions according to exposure—not age alone
An assumption deserves closer attention when it affects a critical or near-critical path, supports an external commitment, has a near validation deadline, influences several activities, lacks an accountable evidence source, or would require substantial replanning if false.
Avoid using a simple high-medium-low label without criteria. A low-probability assumption can still deserve urgent validation when the impact is severe and the decision window is closing. Likewise, a highly uncertain statement may be manageable when an inexpensive fallback remains available.
A practical review order considers validation urgency, schedule consequence, available response time, path sensitivity, and evidence quality. Document why priority changes so later reviewers can reconstruct the decision.
Worked example
How an assumption becomes a controlled decision
A project schedule assumes that a specialist test environment will be available on September 3. Integration testing begins that day and sits on the path controlling customer acceptance. The environment is shared with another project, but no confirmed reservation exists.
The assumption record identifies the environment manager as validation owner, the signed booking confirmation as required evidence, and August 6 as the validation deadline. If the booking is not confirmed by that date, the team must evaluate an alternate environment and a phased test sequence. The record references the testing activity IDs and acceptance milestone.
On August 4, the environment manager confirms that the facility will not be available until September 12. The assumption is marked invalid—not deleted. The condition becomes a current issue, the alternate-environment action is activated, and the schedule is recalculated. The resulting forecast and required changes proceed through the applicable control process.
Because the assumption had an early validation deadline and fallback, the team retained options. Without the log, the missing environment could have remained an informal expectation until the planned testing start.
Failure prevention
Common Schedule Assumption Log mistakes
| Mistake | Why it fails | Better practice |
|---|---|---|
| Writing vague assumptions | The statement cannot be objectively validated. | Include quantity, timing, capability, and acceptance condition. |
| No schedule reference | The consequence cannot be traced through the plan. | Reference activities, milestones, paths, and dependencies. |
| Owner listed as “team” | No individual is accountable for validation. | Assign one accountable owner, even when others contribute. |
| Validation date equals activity start | Response options may already be lost. | Validate before the last responsible decision point. |
| Assumption treated as confirmed | The schedule appears more certain than its evidence. | Label provisional information clearly. |
| Invalid assumption deleted | Decision history and lessons disappear. | Close it with outcome, evidence, action, and schedule effect. |
| Every uncertainty left in the log | Known risks and active issues escape their proper controls. | Convert records as their status changes. |
| Log not reviewed with schedule updates | Expired assumptions continue supporting forecast dates. | Include assumption review in the update cycle. |
Quality checklist
Verify every assumption before relying on the schedule
- Each record contains one clear, testable planning statement.
- The assumption is not already a confirmed fact, approved decision, active issue, or identified risk.
- Its source and planning rationale are documented.
- Affected activities, milestones, handoffs, and paths are referenced.
- The consequence of failure is specific enough for impact analysis.
- One accountable validation owner is named.
- The required evidence is objectively described.
- The validation deadline preserves useful response time.
- A trigger and practical fallback action are defined.
- Status is reviewed during relevant schedule updates.
- Invalid assumptions are converted into the appropriate issue, risk, decision, or change process.
- Closure retains evidence, outcome, schedule effect, and lessons learned.
Frequently asked questions
Schedule Assumption Log FAQs
What is a Schedule Assumption Log?
It is a living register of unconfirmed planning statements that materially support schedule dates, durations, logic, calendars, resources, milestones, or dependencies. It assigns validation ownership and records what happens when evidence becomes available.
How is it different from a Schedule Basis of Estimate?
The Basis of Estimate explains the rationale and evidence behind schedule development and duration estimates. The assumption log controls individual provisional statements through validation, conversion, action, and closure during execution.
Should every assumption become a risk?
No. Some assumptions can be validated before they create meaningful exposure. Convert an assumption into a risk when uncertainty requires active probability, impact, trigger, response, and ownership management.
Who should own an assumption?
Assign the person accountable for obtaining or coordinating the validation evidence. That person may not control the external outcome, but must maintain the record and trigger the defined response.
When should assumptions be reviewed?
Review them during relevant schedule updates and more frequently as validation deadlines, affected activities, or decision points approach. High-impact assumptions may need dedicated interim checks.
Should invalid assumptions be removed?
No. Close them with the evidence, outcome, conversion, decision, and schedule effect. Preserved history supports accountability, lessons learned, and future estimating.
Can an assumption remain open after its validation date?
It can only with an explicit escalation or revised decision. Do not silently extend the date. Record why evidence is unavailable, what exposure now exists, and which fallback or risk response applies.
Where should the assumption log be linked?
Connect it to the schedule basis, affected activity identifiers, applicable risk or issue records, change decisions, and update narrative. Maintain one controlled source rather than disconnected copies.
Build practical schedules with the verified Weekly Schedule Builder. Explore other focused methods in ScheduleFlowLab Guides.