BidTroller/User guide

Bid scores

If your company has scoring turned on, each open job gets a score from 0 to 100 and a band, BID, REVIEW or PASS, in a Score section on its job page, under the details. Companies without scoring don’t see this section. Everyone at your company sees the score, viewers included.

The bands

BID
70 or higher. A strong match for the work you go after.
REVIEW
45 to 69. Worth a look before you decide.
PASS
Under 45. Probably not worth your time. Jobs scored PASS get no deadline reminders. See Assignments and reminders.

These are the standard cut-offs. Your company’s owners and admins can set different ones on Admin > Scoring (see Tuning the scoring); the bands on every job page follow your company’s cut-offs.

A score is advice, not a filter. Nothing is hidden or removed because of its score.

On the dashboard

The score also shows on the Opportunities list, in the Score · Fence fit column, like 72 · BID. Under it, a short line still says whether the job includes fence work at all (Likely, Possible or Unlikely), because the two answer different questions: the score says whether the job is worth bidding, and the fit says whether your work is in it. A big job close to your office can score REVIEW even when your work is only Possible. Tap How? to open the same factor-by-factor breakdown the job page shows, with why the job got its fit grade under it. Tap any factor there to see how its points were worked out. A job not scored yet shows the fit grade with its percentage instead.

Pick Highest score first in the Order box, or click the column name, to put the highest scores on top. Jobs not scored yet come last.

The six factors

Under the score, each factor shows the points it earned out of its maximum, and a short line saying what BidTroller saw. A ✔ means the factor earned most of its points; ⚠ means it didn’t. (assumed) means the listing didn’t give that detail, so a middle value was used.

Click a factor, on the job page or in the list’s How? breakdown, to see how its points were worked out: what earned points, what didn’t, and the steps the factor uses. Under Fence potential it also shows what the fence check found: which of your keywords are in the listing and where, any keywords that count against it, and the check’s own reading of the project. Owners and admins get links there to change how much the factor counts (Admin > Scoring), the keywords (Admin > Keywords) or the offices and service area (Admin > Geography).

The number after each factor below is its BidTroller default weight: the most points it can earn out of 100. Your company’s weights may be different (see Tuning the scoring); each factor’s maximum on the job page always shows your company’s own weight.

Fence potential (30)
How likely the job includes your work, from the same check as the Fence fit column, plus extra points when it is the main scope or the job carries strong signs like perimeter security. A check of 90% or more counts in full (the check almost never says 100%), so a fence-only job with a strong sign earns every point.
Project type (20)
The kind of project, read from the title and agency: data centers, airports and correctional facilities score highest, then industrial and utility work, then schools, municipal, park and military work. Residential work scores low. A job whose main scope is chain link or ornamental fence earns full points whatever the project is.
Distance (20)
The driving time from your nearest office, compared with how far the job is worth driving. A bigger package justifies a longer drive: about 1.5 hours for a small one, up to 6 hours for the largest.
Project size / value (15)
The estimated size of your package. When your work is only part of a bigger project, BidTroller estimates your share and says it is an estimate. When the listing gives no dollar value at all, this factor is left out: it reads no value listed: not counted for or against, takes the average of the other five factors, and moves the score neither way.
GC / customer (10)
Whether the GC or customer is on your company’s lists, whether it is a public agency, and any jobs you recorded as won or lost with them before.
Bid timing (5)
Business days left until bids are due. Two or more is full points, one is half, due today is none.

How the fence package value is worked out

Project size / value scores the size of your package, not the whole project:

  • Fence is the main scope (the job is a fence job): the listing’s value is your package.
  • Fence is part of a bigger project (a school, a plant, a GC’s whole bid): BidTroller takes 1.5% of the project’s value as your share, at least $10,000 and at most $400,000, and marks it (estimate). A $20 million school reads as a $300,000 fence package; a $40 million project hits the $400,000 cap.
  • No dollar value listed: the factor is left out (see above). The one exception is a listing whose documents show large fence quantities: it is treated as a $250,000 package, marked (assumed).

The package value then earns a share of the factor’s points:

$1,000,000 or more
100%
$250,000 to $999,999
87%
$75,000 to $249,999
73%
$25,000 to $74,999
47%
Under $25,000
20%

The same package value sets how far a job is worth driving in the Distance factor: 1.5 hours for $50,000 or less, rising to 4.5 hours at $500,000 and 6 hours from about $2 million.

Click Project size / value on a job to see the value it used and how it got there. The 1.5% share and the $400,000 cap are the same for every company today. If they don’t fit your work, say so on the Feedback page as an Idea or request.

Red flags on the job show in red under the factors as warnings. They don’t change the score.

Tuning the scoring (owners and admins)

Owners and admins control the scoring for their company on Admin > Scoring (/app/admin/scoring). Other team members can’t change it; see Roles and permissions. Every change applies to the whole company, and your open jobs are re-scored right away.

How your scores are made

  • Weights: how much each factor counts. Each factor gets a number of points from 0 to 100, with a slider or by typing it. The six must add up to exactly 100: the page shows the running total and won’t save until it reaches 100. For example, a company that cares more about the size of the job than the drive can raise Project size / value and lower Distance.
  • Cut-offs: the score a job needs for BID and for REVIEW; below REVIEW is PASS. Whole numbers from 0 to 100, with BID higher than REVIEW. The line under the boxes spells out the three bands.
  • AI second look: how much of the final score comes from the AI’s reading of a job, when it has one, as a percentage. The rest comes from the six factors. BidTroller’s default is 30%; 0% turns the blend off, so the score is the factors alone.
  • Preview shows how many of your open jobs would be BID, REVIEW and PASS with the settings on the form, next to how many are now, without saving anything.
  • Save and re-score saves everything on the form and re-scores your open jobs right away. Everyone at your company sees the new scores.
  • Reset to BidTroller defaults fills in the default weights above, the standard cut-offs (70 and 45) and the default 30%; press Save and re-score to use them.
  • Re-score now re-scores your open jobs with the settings already saved, for example after recording a batch of bid results. It can be used six times an hour; scores also refresh on their own through the day.

How your scores are doing

The chart and table under the form compare each band with what your team actually did: the share of its jobs you pursued (set to Reviewing, Pursuing, Bidding or Submitted, or given a result), bid on (Bidding or Submitted), and won (of won + lost), plus the Good fit and Never for us answers. A score is doing its job when BID jobs are pursued clearly more often than REVIEW jobs, and REVIEW more than PASS.

Each decision is measured against the score and band the job had when your team made it, not the score it has today. Until your team has decided on 20 jobs (pursued them, or passed on them with No bid or a Never for us answer), the page says there is too little data and the rates mean little.

Suggested changes

Once a month, and whenever an owner or admin presses Suggest changes now (once a day), BidTroller compares your scores with your team’s decisions and may suggest a change: moving weight toward the factors that agree with your estimators, at most 5 points each with the same total, and raising the BID cut-off by at most 5 when BID jobs aren’t pursued clearly more often than REVIEW jobs. It needs 20 decided jobs; with fewer, or when nothing would change, the page says so instead.

A waiting suggestion shows the changes it proposes and, under Why, the evidence. Nothing changes until you decide:

  • Approve and re-score saves the suggested numbers and re-scores your open jobs.
  • Edit, then approve lets you change the suggested weights and cut-offs first (weights must still total 100), then saves your numbers.
  • Decline keeps your settings as they are.

Add a note for your records if you like. Only one suggestion waits at a time, and Earlier suggestions lists the last few decisions, who made them and when. If the settings were changed by hand after a suggestion was made, it can’t be approved: decline it and ask for a new one.

Driving time

The Distance factor says something like about 2.4 h drive (by road). Driving times by road come from openrouteservice, with its credit line under the factor. When a road time isn’t available yet, the factor says it was estimated from the straight-line miles instead. The Distance row in the job’s details, the dashboard’s Miles column and the miles filters stay straight-line miles.

AI second look

For jobs the rules can’t settle, mostly ones near a cut-off, BidTroller also has AI read the job. Its result shows under the factors as AI second look, with its own score, a recommendation, how confident it is, the reasons for and against, and similar past jobs it weighed. The line Rules · AI second look · blended shows that the final score mixes the two; how much of it the AI carries is set by your admin (30% by default) on Admin > Scoring.

Estimators, admins and owners can ask for it on any scored job: press Get the AI second look at the top of the Score section (or Get the AI second look again to refresh one). It takes a few seconds and the page updates. A company can ask up to 30 times every 10 minutes.

Scores in your notifications

With scoring on, each person can set a Minimum score on the Notifications page: Any score, BID and REVIEW, or Only BID-band jobs. The digest and alerts then leave out jobs below it. A new job not scored yet waits for its score and comes through if it qualifies.

When scores change

Scores are refreshed through the day while a job is open, so a score can move when a bid date, value or location is updated, or as the bid date gets closer. Your team’s “Worth our time?” answers and the bid results you record are stored with the score the job had at the time, and feed the suggested changes your admin sees on Admin > Scoring.

If a score looks wrong, click Something wrong with this job? Tell us on the job page. See Feedback and sign-offs.