Skip to content
GullySales

Driving schools · Bid or no-bid decision framework

Decide which tenders deserve your team before anyone starts filling in forms.

A bid or no-bid decision framework is a written grid your firm uses to decide whether to pursue a tender or large request for quotation. GullySales builds the grid from your own past bids, sets who decides and how the decision is recorded, and keeps the review going, while your owner and commercial head make every decision.

Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

A driving instructor explaining mirror adjustment to an adult learner in a parked car

Start with the buying decision

Which opportunities deserve the team’s effort?

Industry membership alone does not establish fit. The service exclusions, your operating model, and the records available determine the scope after your requirements brief.

Your team approves the scope and any commitments to buyers. GullySales does not assume authority over pricing, staffing, or delivery promises unless a specific responsibility is agreed in writing.

The context for Driving schools

Start with the decisions in your own enquiry records.

Compare the stated requirement with completed work and the effort needed to deliver it. Keep assumptions about demand separate from evidence in the records.

How people choose in this industry

Learners choose on distance first. A school that is a ten minute ride away beats a better one across the city, because the learner has to turn up every morning for weeks. Google Maps ranking, the star rating and recent reviews that mention a named instructor decide who gets the call.

The second filter is fear. First-time drivers, women returning to driving after years, and people who failed the test once want to hear that the instructor will not shout. They also ask whether the school helps with the learner's licence application and the driving test booking on the Parivahan portal, and whether the fee covers the test day car.

A family makes the decision. A father pays for a son's two-wheeler course, a son books a car course for a mother, a company books a few drivers. The fee, the pick-up arrangement and the start date are agreed on WhatsApp before anyone visits.

The decision before implementation

The owner approves segment priorities and commercial boundaries before the team changes its approach.

Existing industry priorities to review

  • Google Business Profile with instructor names and real photographs
  • A page for each course, from two-wheeler to refresher
  • Reply routine for phone and WhatsApp enquiries
  • Reviews that mention the instructor and the area
  • Pages for the localities you pick up from

These describe the industry's wider priorities. The written scope identifies which this service will address.

Industry application review

Test the service against a problem in your own records.

These review scenarios connect the industry context to a possible output and a checkable next step. They are scope questions, not client results or a promise that every industry problem belongs in this engagement.

People ask only for the cheapest course

The first question is the rate, because our page lists no difference between a basic course and a full one with test preparation and extra practice hours.

Output to assess: Margin and exposure test

Review whether “Margin and exposure test” addresses this specific issue. Confirm that connection from the example before including the work in the scope.

What to bring

Bring a completed opportunity record, its requirement and outcome, and the assumptions used to prioritise it.

Proposed completion check

Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

Enquiries come in on the phone while the instructor is in the car

The call goes unanswered at nine in the morning, the learner tries the next school on the list, and nobody notes the missed number.

Confirm the scope first

Check whether this issue belongs in the bid or no-bid decision framework engagement or requires different work. The industry problem alone does not establish that this service will solve it.

What to bring

Bring a completed opportunity record, its requirement and outcome, and the assumptions used to prioritise it.

Proposed completion check

Record the scope decision and its reason. If the issue is outside this engagement, identify the responsible team or the separate work required.

The problem

What bid or no-bid decision framework is meant to address.

  • “We bid for everything and win little”

    Every tender gets a response because nobody has agreed what a good tender looks like. The estimating team is stretched thin across bids the firm was never likely to win.

  • “We found the disqualifying clause after we had finished the bid”

    A turnover requirement, a past-work condition or a missing authorisation surfaced on the last read. The work done before it was wasted.

  • “We won and lost money on the order”

    The price looked fine against the specification. The payment terms, penalty clause and site conditions had not been costed when the decision was made.

  • “Nobody remembers why we said no”

    A tender returns a year later and the argument starts again from nothing. The earlier decision and its reasons were never written down.

Who it is for

Check your operating model against the scope.

  • Manufacturers and suppliers who receive tenders and large requests for quotation from institutions and corporate buyers
  • Contractors and installers who bid for projects with fixed specifications and bid security
  • Service companies, such as facility, security and IT firms, answering formal procurement requests
  • Dealers and distributors who need a manufacturer's authorisation before they can bid at all
  • Owners who say yes to every tender because declining feels like losing
  • Sales heads who prepare bids that the owner later says should never have been chased

Before you decide

When this may not be the right fit.

  • Firms that bid so rarely that one conversation between owner and sales head settles each case
  • Businesses whose sales are walk-in, retail or small repeat orders with no formal buying process
  • Owners expecting GullySales to confirm legal eligibility or interpret tender conditions; those go to your own adviser

Choose the right scope

Start with the work your business needs.

  1. A grid built from your own past bids

    You have answered tenders for years without a common test. We read your wins, losses and declines, then set the knockouts and weights that would have predicted them. The grid reflects your firm, not a generic checklist.

  2. A margin test for tenders with heavy terms

    Payment conditions, penalties and bid security change what an order is worth. The margin and exposure page puts those terms next to the price before the decision, so a large order does not hide a thin one.

  3. Decision rights for a team that shares estimators

    Two live bids can draw on the same engineer. The pipeline view and escalation rule show the clash and send the choice to the person who can make it, rather than letting the louder salesperson win.

  4. A decision record that survives staff changes

    When a tender returns, the earlier scores and reasons are on file. A new sales head starts from your firm's judgement, not from a blank sheet.

What we do

Agree the outputs before work begins.

These are the bid or no-bid decision framework deliverables available for driving schools. Your written scope identifies the included work and responsibilities.

  1. Knockout checks

    A short list of conditions that end the discussion if they fail, such as the experience clause, the turnover test, a required licence or a manufacturer's authorisation. A failed check means no bid, whatever the order size.

  2. Weighted decision grid

    A scoring sheet covering margin, capability, likelihood of winning, cost of bidding, strategic value and workload. Weights come from your own history and your owner's priorities, not from a template.

  3. Margin and exposure test

    A page that tests the price against payment terms, bid security, penalty and warranty clauses, and the cost of site or logistics conditions. It shows where a profitable-looking order is not.

  4. Likelihood-of-winning questions

    The questions your team answers about the buyer: whether the specification was written around a competitor, whether you hold a prior relationship, and who else is likely to bid. Answers are recorded with the evidence behind them.

  5. Decision rights and escalation rule

    A statement of who may decide a bid, at what size it moves to the owner and what happens when scorers disagree. It is written so that the sales head is not the only voice.

  6. Decision record

    One entry per tender holding the scores, the decision, the decider, the date and the reason. A no-bid is recorded with the same care as a yes.

  7. Bid pipeline view

    A register in your CRM or shared sheet showing the tenders in play, their closing dates and the team members each would draw on. It exposes clashes before they happen.

  8. Review rule for the grid

    A trigger for revisiting the weights, such as after a set number of decisions or a major loss. The review compares scored expectations with what happened.

How the result is measured

  • Tenders received and the share assessed with the grid
  • Bids stopped by a knockout check before preparation began
  • Decisions recorded with a written reason
  • Bid or no-bid decisions reversed after preparation started
  • Bids won against the score the grid gave them
  • No-bid tenders later found to have been won by a competitor on terms you could have met

Recorded as a baseline before work starts, so every later report has an honest comparison.

Industry baseline

Keep the industry's wider measures beside the service measures.

Use the existing baseline to understand the context. These figures are not all targets for this engagement, and a change must not be attributed to the service without evidence.

  • Enquiries by source: Maps, search, WhatsApp, referral
  • Missed calls answered the same day
  • Enquiries that became a booked first session
  • Learners who completed the course
  • Reviews that name an instructor
  • Corporate and group batches enquired

This or a nearby service

Which piece of work fits your situation.

These services sit close to each other. The line between them, in plain words.

RFP and tender management
Choose RFP and tender management when you have decided to bid and need documents, approvals and submission tracked before the closing date. Choose the bid or no-bid decision framework when the open question is which tenders deserve a response at all, before anyone starts writing.
Win-loss analysis
Choose win-loss analysis when you want to learn why buyers chose you or a rival after a decision was made. Choose the bid or no-bid decision framework when you must decide before a bid is written, using the lessons of past bids as inputs to the grid.
Deal desk services
Choose deal desk services when discounts, credit or special terms on live sales need rules and an approval route. Choose the bid or no-bid decision framework when the question is whether to enter a tender or large request for quotation at all, before any pricing begins.

A sample of the output

A weighted decision grid turns a tender into a recorded bid or no-bid choice.

This is a grid for a contractor considering a supply tender. Each row is a question the decision group answers. Read across to see why it matters, what evidence is checked and how the answer is used.

Illustrative example, not client data. Yours is built from your own records.
QuestionWhy it mattersEvidence checkedHow the answer is used
Eligibility documents heldMissing papers rule a bid out before it startsRegistration and certificates in handKnockout: no bid if absent
Penalty and payment termsHeavy terms can remove the marginContract clauses read by the commercial headMargin and exposure test
Fit with past workFamiliar work is priced and delivered with fewer surprisesPast bids of the same kindScored in the weighted grid
Buyer relationshipA known buyer shapes how likely a fair evaluation isEarlier orders and contacts on recordScored in the weighted grid
Team capacityEstimators and engineers cannot cover every tenderCurrent bid pipeline viewEscalates to the owner if overloaded

Before we start

What we need from you.

The work depends on these. Each says why it is needed and what happens when it is missing.

Records of your past bids
The grid is weighted from tenders you actually entered, won, lost or declined. Quotations, tender folders and notes in any condition will do. Without them, the weights are guesses and the grid will not reflect how your firm really wins.
Your minimum acceptable margin, in principle
The margin test needs your owner to state the floor below which a tender is not worth bidding. It can be a rule of thumb, held privately. If it is missing, the test has no threshold and every tender looks acceptable.
Named decision makers for each size of tender
Decision rights say who may approve a bid, who may veto it and who is told. Agree the names before the grid is finished. Without them, decisions stall between the sales head and the owner and the decision record stays empty.
The current tender pipeline
The grid is trialled on tenders open now, so it meets real conditions rather than examples. A list of live tenders with their documents is acceptable. Without it, the trial is theoretical and weak criteria go unnoticed.

Marketing and sales together

Your sales team spends its bid effort where an order is worth having.

A bid draws on the same people who would otherwise follow up quotations, visit buyers and close the deals already in hand. The grid protects that time by turning down tenders that do not fit, and by naming the reason so the sales head can explain it to the buyer or the owner. It also feeds back: the record shows which kinds of tender your firm keeps declining and which it keeps losing, and that points your selling at buyers and specifications you can serve.

Decisions to make before the work starts

  1. What your firm decides

    Your owner sets the margin the firm will accept and the workload it can carry. Your commercial head and estimators answer the capability and cost questions. GullySales supplies the structure and keeps the record. It does not make the call on any tender.

  2. What affects the scope

    The range of buyers you bid to, the number of tender types and the quality of your past-bid records shape the work. A firm bidding to a few institutional buyers is a smaller job than one answering tenders across several sectors. Scope is written down after the requirements brief.

  3. Where this stops

    Preparing and submitting the response is rfp and tender management. Independent interviews on why you lost belong to win-loss analysis. Legal reading of tender conditions, eligibility opinions and bid security arrangements belong to your own adviser and your bank.

How it works

How bid or no-bid decision framework runs

The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.

  1. 1

    Past-bid review

    You share the tenders you answered and the ones you declined, with outcomes where known. GullySales finds the patterns in eligibility failures, margin surprises and wasted effort.

  2. 2

    Criteria and weights

    Your owner and commercial head agree which checks are knockouts and how the scoring criteria are weighted. They also decide the score at which the answer is yes, conditional or no.

  3. 3

    Grid and decision rights

    We draft the grid, the margin test and the decision rules in your trade's terms. You approve who decides and where the owner must step in.

  4. 4

    Trial on live tenders

    Your team scores tenders in hand with the grid, and the owner compares the result with the instinctive answer. Weights that gave a wrong answer are corrected before the grid is fixed.

  5. 5

    Recording and review

    Decisions go into the register as they happen. The two heads review the record against bid outcomes and agree any change to the grid.

Approval and acceptance

Use an observable check before accepting an output.

These are proposed review checks for the named outputs. Agree the final conditions in the written scope, then record any missing requirement before accepting the handover.

  • Knockout checks

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Weighted decision grid

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Margin and exposure test

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Likelihood-of-winning questions

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Decision rights and escalation rule

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Decision record

    Inspect a sample record against the original information. Check required fields, duplicate handling, the responsible owner, and who is permitted to access it.

  • Bid pipeline view

    Inspect a sample record against the original information. Check required fields, duplicate handling, the responsible owner, and who is permitted to access it.

  • Review rule for the grid

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

FAQ

Questions owners ask before they call.

Not here? More answers, or ask on WhatsApp.

How is bid or no-bid decision framework scoped for driving schools?
Industry membership alone does not establish fit. The service exclusions, your operating model, and the records available determine the scope after your requirements brief. The owner approves segment priorities and commercial boundaries before the team changes its approach.
Who should make the bid or no-bid decision?
The person who carries the margin and the workload: the owner, or the commercial head acting within a written limit. The sales head scores and proposes. A bid that draws on the same people as another live bid goes to the owner.
Will the grid tell us which tenders we will win?
No. It tells you which tenders fit your firm, your margin and your workload, and it makes the guess about winning explicit. The buyer decides the award.
Do you decide for us?
No. GullySales builds the grid and keeps the record. Every decision is made and signed off by your people, and eligibility questions go to your own adviser.
How is this different from rfp and tender management?
This service decides whether to bid. Rfp and tender management starts after a yes: it coordinates documents, queries, sign-off and submission. Some firms need both, and the decision record feeds the bid file.
What about declined bids?
They are recorded with the same fields as a bid. When a tender returns, or a competitor's win becomes known, the record shows whether your reasons held. Win-loss analysis can then study the pattern.

Continue your review

Compare the service scope and the related work.

The scope, responsibilities, fee, reporting frequency, and term are agreed in writing after the requirements brief and conversation. Tell us what you need.

Your brief

Tell us what you need, and we will read it before we call.

Eight short steps about your business, what you want and who decides. Most questions are a tap, and you can skip any you would rather answer on the call.