Estimation Workspace

Darwin’s estimation workspace is where an estimate becomes a governed working object rather than a static output.

In the request-to-baseline workflow, the estimation workspace sits between clarification and approval:

clarify → estimate → review → approve

What the Workspace Brings Together

An estimation workspace can include:

• summary and cost review
• reports and exports
• linked work requests
• comparison against sibling revisions
• workflow activity history
• estimation analysis and review findings
• approval context

Why This Matters

Most estimating tools stop at producing totals.

Darwin keeps the estimate inside its operational context so teams can:

• request changes
• compare revisions
• explain deltas
• preserve review history
• understand whether the estimate is ready to become a baseline

Recommended Use

Use the estimation workspace when:

• an estimate is under review
• a revision is requested
• an approval is pending
• a comparison between alternatives is needed
• the team needs to understand what changed and why
• recommendations or findings need to become governed change requests

Best Practices

• use the workspace as the canonical place to review revisions
• create requests instead of relying on informal side conversations
• compare revisions before approving major changes
• keep reports tied to the current estimation context
• do not treat approval as a report export; approval is a baseline decision