1. Automotive Dealers CRM
  2. Features
  3. Proposal and Outcome Review
Feature · Proposal and Outcome Review

Proposal and Outcome Review

Review the exact proposal or customer outcome with a separate decision owner and a retained reason.

OverviewProposal Review Queue
Automotive Dealers CRM · Proposal and Outcome Review

Proposal Review Queue

Opportunities

New
Record numberSubjectCounterpartyExpected value USDExpected close dateRevision
OPP-96908Qualified opp-187ACC-11030018 Oct880
OPP-22469Qualified opp-359ACC-11053019 Oct830
OPP-26932Qualified opp-773ACC-15030021 Oct910
OPP-37309Qualified opp-613ACC-11087017 Oct210
OPP-93466Qualified opp-519ACC-12063021 Oct710
6 of 6 records
Qualified opp-187Opportunities · OPP-96908
Qualified
CounterpartyACC-110
Expected value USD300
Expected close date18 Oct
Revision880
Example screen with sample data

What you can do

Decide on the scope the customer actually considered

Relationship Owner prepares proposal scope and the next customer activity for an opportunity that has been qualified. Sales Manager independently reviews the eligible revision before the proposal transition. The decision history records the reviewer, source revision, reason and decision, so a later reader can identify the scope that was considered.

Customer closure follows the same responsibility split. The owner submits verified acceptance or loss evidence and the eligible independent reviewer checks the exact revision. Won includes the outcome date; Lost includes the loss reason. The previous expected value and activity evidence stay available after the decision so the dealership can explain both successful and unsuccessful customer conversations.

How the work is organized

  • Prepared scope. Collect the proposal context and next activity before requesting review. An attached file should be identified clearly enough that the manager knows which customer version it supports.
  • Independent review. Sales Manager checks the source revision and records an Approve, Reject or Return decision as appropriate to the action. Access to the record is separate from authority to approve a protected transition.
  • Outcome evidence. Use verified customer acceptance or a specific loss explanation for closure. Keep the earlier conversation and expected value intact when the opportunity reaches Won or Lost.

What to agree during setup

Agree who can act as the eligible independent reviewer and how the owner obtains a fresh decision after changing customer scope. Define the evidence required for proposal submission and for customer acceptance. A manager should be able to identify that evidence from the opportunity without relying on an undocumented verbal assurance.

Decide what marks the start of Negotiation and how a Return decision reaches the owner. Agree how the team checks an uncertain action result before submitting again. Protect the meaning of Won: it records the reviewed customer outcome, while delivery, payment and service execution follow their separately owned handoffs. Establish those connections where the dealership needs to coordinate them.

Check the handoff on an actual case

Use the qualified hatchback opportunity and attach the proposal evidence for the current customer request. Relationship Owner prepares the next activity and submits the scope. Sales Manager checks the current revision, records the decision reason and authorizes the eligible proposal transition. Confirm that the decision history and operation result point back to the same opportunity.

Now let the customer change the requested scope before closure. Attempt to use the earlier revision and confirm that the stale action is rejected. Prepare the fresh acceptance evidence and repeat the independent review. Inspect the Won date and retained expected value after a successful outcome. Rehearse a Lost outcome separately with a meaningful reason, then ask Auditor to explain the result from the activity and decision history alone.

What your team sees

  • Proposal Review Queue — Qualified opportunities whose proposal scope is being prepared for independent review.
  • Review Decision History — Decisions with the exact source revision and reviewer reason retained.
  • Internal Evidence — Internal supporting files linked to their customer opportunity.

Follow the work through

What it keeps track of

Data model
Opportunities
Vehicle sales and service opportunities with a guarded lifecycle.
Review decisions
Independent reviewer decisions on a frozen source revision.
Relationship activities
Calls, meetings, emails and tasks logged against an opportunity.
Record attachments
Evidence files attached to an opportunity with visibility scope.
Operation receipts
Durable receipts for guarded operations with stable operation keys.
Team members
Dealership staff with an authenticated platform identity and role.

Who uses it

Permissions
Relationship Owner
Prepares evidence.
Sales Manager
Independently approves eligible scope.
Auditor
Inspects the authorized decision history.
App Administrator
Maintains memberships without making operational approval decisions.

Set up Automotive Dealers CRM your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started