DESCRIPTIVE PROJECT CHANGE WORKSHEET Enterprise Data Partnership Preparation guidance only: not a Micro1 requirement, data transfer request, valuation, or acceptance decision. Company/project label: Workflow owner/role: Historical period and estimated coverage: Project Reference — The link between the brief, tasks, and reviews Your notes: Milestone Definition — What a planned checkpoint meant Your notes: Change Event — The revision and the reason recorded for it Your notes: Dependency Record — What had to happen before the task could proceed Your notes: Accepted Outcome — How completion was reviewed rather than merely marked Your notes: Comparison examples (illustrative, not customer cases): More informative: A project history preserves an initial milestone, a documented scope change, the dependency that caused it, and the final review. The owner can distinguish completed work from administratively closed tasks. Questions remain: A task board shows only current status and due date. Closed tasks include completed work, duplicates, and abandoned tasks without clear distinctions. Next decision: Identify which status definitions and historical changes survive extraction before describing a board as a complete project history. Internal reviewer and unresolved questions: Next action and review date: