Revisions

Revisions are central to Darwin’s philosophy of traceability.

An estimate changes over time because:

• design evolves
• prices move
• assumptions are corrected
• scope is clarified
• decisions are revisited

Why Revisions Matter

Without explicit revisions, teams lose the ability to explain:

• what changed
• when it changed
• who requested the change
• why the cost moved

Darwin’s Approach

Darwin is designed to support:

• sibling estimations for comparison
• request-driven changes
• linked workflow history
• preserved project context

Best Practices

• create a new revision instead of silently rewriting prior work
• compare revisions before major decisions
• use work requests to explain revision intent
• preserve the relationship between revision, approval, and price context