Submission and approval
Submission is a controlled transition, not another draft save. Quote Control runs server-side preparation checks, records the company control versions used and then decides whether the revision needs an independent checker.
Preparation checks
Section titled “Preparation checks”The Review step separates blocking findings from advice. Resolve every blocking finding before submission. Typical blockers include missing customer details or site evidence, scope, pricing cost pairs, required caveats, obsolete-component decisions, catalogue-price explanations or a non-positive commercial value.
When the company policy allows it, Not applicable site status requires a human reason before submission. You can save an incomplete draft and return to finish its reason later. A catalogue-price explanation is a human review action; it is not provided by a report or AI suggestion. Internal reasons, catalogue source values, costs and margin evidence stay out of the customer PDF. Each catalogue review card identifies the affected quotation line by its description so it can be matched to the pricing table.
Approval authority
Section titled “Approval authority”- A submitted total strictly above the configured threshold, or a configured minimum-margin or catalogue policy trigger, enters the Approval queue.
- A submitted total at or below the threshold is approved automatically when no other independent-review policy applies.
- The owner and anyone recorded as a contributor cannot independently approve it, including after a change of owner or role.
- A checker can approve or return the revision with a reason, but cannot edit it.
- A returned revision goes back to the estimator for correction and resubmission.
A decision applies to the submission shown in the queue. If the estimator edits and resubmits while you are reviewing, refresh the queue and review the current submission before deciding. People with identical display names can still provide independent approval: Quote Control checks their accounts.
Submission also checks that the saved quotation has not changed in another session. Follow the save-conflict guidance if the current draft needs to be reloaded.
Older quotations may need an Administrator to resolve missing contributor history before submission, approval or issue. A revision or duplicate retains that history and cannot clear the restriction. Approved content stays locked; create a new revision when further preparation is needed.
Controls stay with the revision
Section titled “Controls stay with the revision”Company controls and operational preferences are versioned. The submitted revision keeps those versions even when an administrator publishes new settings later. If a checker returns the same revision for correction, it also keeps its site policy. A future revision uses the newly active versions.
This protects the reason for an earlier approval decision and prevents administrative changes from silently altering work already under control.
Company administrators can review how to publish commercial controls without changing a submitted revision.
Resolve preparation checks
Section titled “Resolve preparation checks”In Review, choose Resolve beside an editable preparation check to open its quotation step. Your unsaved changes stay in the editor. Independent approval remains a separate controlled decision.
Retry workload requests
Section titled “Retry workload requests”Loading and failed requests do not mean the queue is empty. Choose Retry after a load failure. If a refresh fails, previously loaded records remain visible with a warning.
Unsent approval comments
Section titled “Unsent approval comments”Each pending submission keeps its own unsent decision comment while you open a quotation and return to Approvals. A successful decision clears that comment; a failed decision keeps it for retry. Reloading or signing out clears these temporary drafts. A new submission starts with an empty comment.