Final
Generated YesterdayGolden Hour — Assumption Log
Project: Golden Hour Divestiture
Executive Summary
This assumption log documents the key assumptions used in the Golden Hour Separation Economics analysis. It is designed to make the model auditable by linking source inputs, assumptions, calculation references, confidence levels, and scenario impact.
Key Metrics / Facts
Purpose
Traceability
Project
Golden Hour Divestiture
Assumptions tracked
5
High-impact assumptions
3
Validated
1
Open / Needs diligence
4
Main Report Body
Assumption Log
| ID | Category | Source Input | Assumption | Calculation Reference | Confidence | Scenario Impact | Status |
|---|---|---|---|---|---|---|---|
| A-001 | HR / People | HR census | 25% of shared roles remain partially stranded for 12-24 months | HR stranded cost range | Medium | High | Needs validation |
| A-002 | IT / Technology | ERP dependency map | ERP separation requires 18-36 month TSA support | IT stranded cost range | Low-Medium | High | Open |
| A-003 | Finance | Finance operating model | RemainCo retains reporting, close, controls, and budgeting support | Finance support estimate | Medium | Medium | Validated |
| A-004 | Contracts / Procurement | Vendor contract list | Volume reduction may trigger repricing for top vendors | Procurement dis-synergy estimate | Low | High | Needs diligence |
| A-005 | Revenue Dis-Synergies | Customer relationship data | Reduced cross-sell access creates revenue leakage during transition | Revenue dis-synergy range | Low | Medium | Open |
Traceability Flow
| Input | Assumption | Calculation | Output |
|---|---|---|---|
| HR census | Partial retained roles | HR stranded cost | Net proceeds bridge |
| ERP map | TSA support period | IT separation range | Downside case |
| Vendor contracts | Repricing risk | Procurement impact | Data gap flag |
| Customer data | Cross-sell leakage | Revenue dis-synergy | Recommendation |
Open Items
- Validate HR stay/go classification
- Confirm ERP TSA duration
- Review top 12 vendor contract repricing terms
- Validate customer cross-sell dependency
- Assign functional owners to remaining assumptions
Recommendations
- Require owner sign-off for high-impact assumptions
- Separate validated assumptions from placeholders
- Use confidence badges in all report outputs
- Maintain assumption change history before final delivery
Synthetic data for capstone demonstration. Not a valuation opinion, fairness opinion, legal advice, tax advice, or financial due diligence conclusion.