Estimation Workspace

Darwin’s estimation workspace is the revision-level screen for inspecting, defending, and moving one estimation toward a decision.

In the request-to-baseline workflow, it carries:

estimate → review → approve

Open it from the project’s Estimations tab. Use Estimation Details for line-level work such as adding modules, editing quantities, and changing direct costs; use the workspace to review the revision as a whole.

Read the Revision State

The header shows the current approval state for this revision:

State	What it means
Not requested	The revision has not entered the approval path yet.
Pending	An approval decision is still required.
Rejected	The decision is recorded; use a request or later revision to address the outcome.
Approved - active baseline	This is the revision Cost Control tracks.
Approved - superseded	This revision was approved, but a later revision is now the active baseline.

An approved active revision is not the place to make a quick line correction. Its line editor is read-only; work in a later revision when the estimate needs to change.

Use the Workspace Tabs

Tab	Use it to
Summary	Review the cost roll-up, sections, margins, grouping, and scenarios.
Reports	Generate or access estimation reports and exports.
Proposal	Build the client-facing proposal from this revision.
Estimate Review	Resolve review findings before a decision.
Bid Leveling	Manage bid packages, received proposals, clarifications, and leveling decisions.
Requests	View or raise work requests tied to this estimation.
Audit	See who changed the estimation and when.
Comparison	Compare this revision with another revision side by side.
Activity	Review the revision’s activity history.

Badges on Estimate Review and Bid Leveling indicate open items that need attention.

Move a Revision Toward a Decision

1. Review the Summary and open Estimation Details when line-level changes are needed.
2. Resolve findings in Estimate Review.
3. Use Requests to create a clarification, change, price refresh, alternate, or approval request with the estimation already in context.
4. Use Comparison to explain meaningful differences from another revision.
5. Return to the project summary for the approval decision.

The workspace helps prepare an approval, but it does not own the final decision. Requesting and recording approval happen through the project-level workflow.

Best Practices

• Review a revision in the workspace before treating it as ready for approval.
• Raise a work request instead of relying on an informal side conversation.
• Use Approved - superseded as history, not as the current cost-control baseline.
• Keep reports, proposals, bid decisions, and review findings tied to the revision they describe.