SmartERP Documentation An Ashewa Technology Solutions Platform

Task estimation and approval chain

How SmartERP enforces engineering estimation rigor through a multi-tier review chain connecting Developers, Team Leaders, Technical Leads, and Project Managers.

Accurate effort estimation is critical for cost baseline integrity and sprint predictability. SmartERP Project Estimation Approval (smarterp_project_approval) introduces a structured four-stage governance workflow that ensures technical sanity and management sign-off before effort is committed to task budgets.

Swimlane diagram of the estimate approval chain. The developer enters an estimate and submits it. The ERP Team Leader approves, then the Tech Lead approves, then the Project Manager approves for development, and the approved hours are copied to Allocated Time. At any of the three review stages the reviewer can request a revision, which returns the task to the developer, who enters a revised estimate and submits again from the first stage.
The estimate approval chain and the revision loop.

The four-tier approval workflow#

Task 4-Tier Estimation & Approval Workflow

When estimation governance is active on a project, effort hours move through distinct review stages:

Status diagram of an estimate. Draft goes to ERP Team Leader Review with Submit Estimate, then Tech Lead Review, then Project Manager Review, then Approved for Development. From any review stage Request Revision leads to Revision Requested, and Submit Estimate returns to ERP Team Leader Review. Reject leads to Rejected, which has no way back in the screens.
The estimate status values. Rejected is final in the screens; Request Revision and Reject work the same way at every review stage.
StageResponsible roleEvaluation focusNext valid actions
Draft (draft)Developer / AssigneeBreaks down requirements and inputs initial estimated hours and breakdown rationale.Submit Estimate
Team Leader Review (tl_review)ERP Team LeaderVerifies workload balance, functional accuracy, and adherence to delivery patterns.Approve, Request Revision, Reject
Tech Lead Review (tech_review)Technical Lead / ArchitectEvaluates architectural complexity, technical risks, and non-functional requirements.Approve, Request Revision, Reject
PM Review (pm_review)Project ManagerValidates budget alignment, client milestones, and resource capacity constraints.Approve, Request Revision, Reject
Approved (approved)System (Automated)Locks estimated hours and automatically copies approved hours into allocated_hours.Task ready for sprint inclusion

Submitting and reviewing an estimate#

  1. The developer opens the task, navigates to the Estimation tab, and inputs:
    • Initial Estimate (Hours): Expected effort.
    • Estimation Rationale: Breakdown of effort across backend, frontend, unit testing, and documentation.
  2. The developer clicks Submit Estimate. The task state transitions to tl_review, and an approval notification is routed to the designated Team Leader's approval queue.
  3. Reviewers evaluate the task from their My Approvals menu:
    • Clicking Approve advances the estimate to the next sequential tier.
    • Clicking Request Revision prompts for feedback notes and returns the task to the developer in the revision state. The developer updates the hours and resubmits.
    • Clicking Reject terminates the estimate. Rejected tasks cannot proceed to development without a new task or PM re-evaluation.

Synchronization with Allocated Time#

When the Project Manager completes the final approval:

  • SmartERP automatically updates the native Odoo field Allocated Time (allocated_hours) with the approved estimate.
  • The approval timestamp and authorized PM user are indelibly stamped in the task record.
  • In Agile projects, this approved estimate satisfies the Definition of Ready estimation requirement for sprint inclusion.

Note

Subsequent changes to the scope of an approved task require resetting the estimate through a formal Change Request or PM re-approval to maintain historical baseline integrity.

Last updated: 2026-10-16