Section 4
Implementation Approaches
Common capitalization models with Dotwork
Dotwork supports a range of capitalization approaches that reflect the diversity of organizational environments. These approaches exist along a spectrum that ranges from lightweight estimation to highly detailed tracking.
| Model | Allocation Level | Effort Signal | Scope of Allocation | Precision and Defensibility | Operational Overhead |
|---|---|---|---|---|---|
| High-Level Periodic Allocation | Manager and team high-level allocation | Judgment informed by initiative participation and general work patterns | Across initiatives and broad buckets such as capitalizable work vs reactive or maintenance work | Defensible when teams work on a small number of initiatives and allocation reflects a reasonable representation of time spent | Very low |
| Proxy-Based Estimation | Typically team or initiative level | Operational proxies such as story points, ticket counts, or pull requests | Across initiatives using proxy totals to estimate effort distribution | Defensible when proxies correlate consistently with engineering effort | Low |
| Lightweight Individual Reflection | Individual level | Self-reported estimates of time allocation | Across multiple initiatives or categories of work | Defensible when individuals periodically allocate their effort and the process is repeatable | Moderate |
| External Time Tracking Integration | Individual level | Actual recorded hours | Often tied to specific project codes or job codes | Highest precision because effort is recorded directly against initiatives or projects | High |