Wednesday, November 18, 2026

Using AI to Analyze BC Public Tree Planting Bid Results

For this morning's entertainment, I decided to use AI to analyze some bid results.  Here are some of the background parameters that I adhered to:

- I wanted to use the data that has been posted on the Replant.ca forums over the past decade or so.  I could have used the original data source (BC Bid) but I figured that going to BC Bid would be much more resource-intensive, since agents would need to repeatedly crawl through thousands of unrelated non-planting bids on that site.

- I have the Replant.ca website set up with Cloudflare geo-restrictions, so it can only be accessed by people in certain countries.  I have the main Replant.ca website visible to visitors from twenty countries, but the forums are only visible to people in Canada, Great Britain, Australia, and New Zealand.  This was to prevent server overload from AI agents scraping data.  Earlier this year, the server was sometimes getting 1.5 million hits per day, almost entirely from AI training hits to the forums, and it was limiting access to the board.  I could have temporarily turned the Cloudflare protection off for this task, but instead I decided to change a board setting that limited the number of posts per page (I changed it from 50 to 250).  This allowed each "year" of posts to be displayed on a single respective web page.  Then I visited each year's page and used the Print dialog to save the page to PDF, thereby capturing all data.  Incidentally, if anyone tries this, using "Save to PDF" embeds the data differently than "Microsoft Print to PDF" - which is more image-oriented and less easy to read effectively.

- I uploaded all of my PDFs (one each for 2009 through 2025) into ChatGPTs Work tab.  I asked it first to read and analyze the PDFs, and to make sure it understood the data contained therein.  I then told it that I was going to ignore 2009 to 2014 PDFs for now, and only concentrate on the period from 2015 to 2025 inclusive.  I didn't include 2026, because we're only partway into the bidding season right now.

- I frequently asked Chat to ignore Coastal bids in my various queries. 

- I was using ChatGPT 6.1 Terra on High intensity, even though 6.2 Astra and 6.2 Sol are now available.

- I went into this with the mindset that Chat would probably make mistakes, and since this is just a casual experiment, I wasn't going to go through and replicate the work by hand to verify all results.  I'd do that if this was some sort of critical task, but this is just a fun experiment. 

Now that I've added all of these PDFs to Work, I'm able to analyze them with tons of different queries, over and over again, without Chat needing to scrape data every time.

 

For my first query, I asked Chat to create a chart to graph all bids over time.  Again, I restricted the chart to the period from 2015-2025.  I asked Chat to ignore all bids which didn't have price data.  In order to "clean up" the data somewhat and ignore lottery bids and unrealistically high bids that would throw off averages, I asked Chat to ignore any bids which worked out to greater than $1.50 per tree.

This is the chart that was generated:

 

 

Anyone who is familiar with the bidding over the past decade will probably look at this closely and have two questions:

1.  "Why are there so few bids in 2021 compared to other years?" - This was the second year of Covid, and the government wasn't releasing data right away.  So we just waited until each bid closed, then I collected bid data from each individual contractor so we all had a full set of results behind-the-scenes.  However, we didn't want to share most of that data publicly.

2.  "Why is there a dot in 2025 which looks like a stupidly low price, is that an error by the AI?" - No, that was Marlo's bid in Fort St. John, which ended up being disqualified.

The value of this graph, even if it isn't perfect, is that it gives us a good understanding of how bids have trended upward over time, which is not surprising considering inflation.  And it also shows us years when the herd moved upward or downward.  This probably shows us that planting companies feel the hit of unsustainable pricing in unison.

---

Next, I asked Chat to generate a series of charts for individual companies, to show how each of their bidding attempts evolved over time.  Here are half a dozen examples, picking some of the larger companies or more frequent bidders, presented in alphabetical order:


 

 








Fun stuff.

---

Next, I asked Chat to summarize which companies had been putting in a lot of bids.  This is the query that I used:

Can you provide me a text list itemizing how many bids each company has submitted during the period from 2015 to 2025 inclusive?  Do not include bids above $1.50/tree.  Do not include bids for which no price per tree was provided in the PDF.  Rank the list from the company with the most bids down to the company with the fewest bids.

I got the following list, which I then amended by grouping companies that had fewer than 20 bids over that 11-year period:

 


That's a lot of bids.  I'm not surprised by the high number at Folklore ... I've driven a lot of miles during viewing season over the past decade and I've walked around blocks which were prescribed for hundreds of millions of trees (also, I was just one of several people doing the viewing work).  Incidentally, when I count up all the blocks that I've visited while viewing, and all the blocks that I was responsible for during my 35 years as a camp supervisor, I estimate that I've visited/seen blocks all over BC and Alberta that added up to more than three hundred and fifty million trees.

---

My next query was about spring versus summer trees.  I wanted to estimate the overall difference between spring and summer trees.  This was my query:

Ignoring any coastal contracts, what do you think the overall weighted average price is in the BC Interior from 2015-2025 for spring trees versus summer trees?  Ignore contracts where there are both spring and summer trees on the same contract.  Ignore Fall contracts.

This was the result:

This result actually surprised me, because there's generally more competition for summer trees, as there are fewer summer trees on the market each year.  However, it's a reassuring result - a lot of summer trees in BC, which are usually in the northern half of the province, are a lot uglier than spring trees due to green-up.

---

Next, let's look back at some of the jobs where the lowest two bids were pretty close:


 

---

 

I think the main thing that everyone needs to remember is that this collection of data is fairly substantial, but it is not complete.  We were missing a few bids each year, we didn't share a significant portion of the 2021 bids, and I probably have a bunch of typos scattered throughout the data.  Also, ChatGPT and other AI's can make mistakes.  I would not place much trust in the complete accuracy of the responses that were generated.  Chat itself frequently pointed out various weaknesses in the underlying data that I provided.

It was a fun exercise, nonetheless.

I'll leave you with some final food for thought.  If you were to do some analysis yourself, what would you ask?  I asked ChatGPT Work to give me some ideas.  This was my query:

I'm thinking about all of the data contained in the 2015-2025 PDFs.  What interesting analysis tasks can you think of, which might provide some fun or interesting insights into the data contained therein?

I got a VERY long answer.  I'll share that in a second, for anyone looking for some data mining inspiration.  But first, if you'd like the collection of PDFs that I used, here's a quick download link to save you some time:

   www.replant.ca/docs/Public_Bid_Results_Archives_2009-2025.zip     (158MB) 

 

I'm out of here for today, it's time to go outside and touch grass, but here's where Chat would like to take you next:

 

There is enough material in those PDFs to explore much more than whether bid prices increased. The most interesting questions, in my view, concern competition, bidding behaviour, regional differences, and how often a contractor’s assessment of a job differs sharply from everyone else’s.

I’d group the possibilities into several broad themes.

1. How competitive were public planting bids?

Number of bidders per contract, over time

For each year, calculate the average and median number of companies bidding on a public contract. We could show the individual contracts as dots and identify years when competition became noticeably stronger or weaker.

Questions this could answer:

  • Did the increase in tree volumes around 2018–2021 lead to fewer bidders per job?
  • Did the number of bidders recover or decline as volumes changed?
  • Were some districts consistently more competitive than others?
  • Were large contracts more likely to attract a crowd than small contracts?

Important detail: For this particular analysis, I would count bidders whose names are listed even when their prices are missing. We would still follow your $1.50 rule where a price is known, but a bidder with no published price could not be classified against that ceiling. I would therefore show those bidders separately or exclude them from the filtered count. That distinction matters especially in 2021.

Does more competition lead to lower bids?

For each contract, compare the number of bidders with:

  • The lowest posted bid.
  • The average bid.
  • The difference between the lowest and second-lowest bids.
  • The spread between the lowest and highest bids.

A scatterplot might reveal, for example, whether jobs with ten or more bidders tended to have tighter pricing than jobs with only two or three.

The challenge is separating cause from correlation. Easy, desirable jobs might attract more bidders and command lower prices because they are easier. Ideally, we would compare contracts within similar regions, seasons, years and size ranges.

How often was there only one bidder?

We could identify every contract in the PDFs that attracted a single bidder and examine:

  • Who submitted the bid.
  • The price per tree.
  • Where and when the work was located.
  • Whether the contract had difficult access, special qualifications or other unusual requirements.
  • How the price compared with similar contracts that attracted multiple bidders.

This could produce a useful catalogue of situations where the public tender process generated little direct competition.

2. What do the bids reveal about company behaviour?

A head-to-head comparison between companies

Pick two companies—say, Folklore and Seneca—and identify contracts on which both submitted bids.

For each shared contract, calculate:

Folklore’s bid per tree minus Seneca’s bid per tree

We could then report:

  • Number of head-to-head bids found.
  • How often each company bid lower.
  • The median difference in cents per tree.
  • The largest differences in each direction.
  • Whether the relationship changed over time.

This is potentially more informative than comparing each company’s overall average. If two companies bid on different mixes of coastal, Interior, spring and summer work, their overall averages are not directly comparable. Looking at the same contracts controls for many of those differences.

We could repeat this for any pair:

  • Folklore versus Dynamic.
  • Seneca versus Brinkman.
  • Torrent versus Coast Range.
  • Spectrum/Wright versus Dynamic.
  • Windfirm versus Whanau.

A head-to-head matrix for the major companies

We could expand the preceding idea into a table or heatmap. Each cell would answer:

When both companies bid on the same job, how often did the company in the row submit the lower bid?

For example, a cell might show 60% over 20 shared bids. The number of shared bids is essential: a 100% rate based on two encounters is far less informative than a 60% rate based on fifty.

We could also express the result as the median cents-per-tree difference rather than simply who was lower.

This would probably be one of the most interesting analyses in the collection.

Who bid most often—and who won most often?

For each company:

  • Number of bids found.
  • Number of times it submitted the lowest posted price.
  • Number of apparent awards, where the PDF confirms the award.
  • Number of times it ranked in the top three.
  • Median bid rank.
  • Percentage of its bids that were lowest.

I would keep “lowest bid” and “awarded contract” separate. The contractor rating system, eligibility decisions, withdrawals and other factors mean those are not always the same thing.

This could show the difference between a company that bids frequently and selectively prices high versus one that bids less often but places near the bottom of the price list.

How selective were different companies?

A company’s bidding pattern could be profiled by:

  • Regions where it bid.
  • Average and median contract size.
  • Spring versus summer work.
  • BCTS versus Ministry or other public clients.
  • Coastal versus Interior work.
  • Percentage of bids where it ranked first, second, third, and so on.

For instance, we might find that one company tended to target large northern Interior programs while another appeared more often on smaller coastal contracts. That would help explain why their overall price averages differ.

We could present this as a set of company profiles, with one page per major contractor.

Which companies showed the greatest variation in bidding?

For each company, measure the spread of its own bids:

  • Lowest and highest qualifying bids.
  • Median bid.
  • Middle 50% of bids.
  • Range after adjusting for year and region.

A company bidding between 40¢ and 90¢ may simply have bid on very different ground. A more useful version would compare how far above or below the other bidders it tended to be on the same job.

For example:

On its shared contracts, did Company A usually stay close to the middle of the pack, or did it alternate between very aggressive and very high bids?

3. Where was money left on the table?

Largest gaps between first and second bids

This is an obvious and entertaining one: rank the contracts by how much the lowest bidder left on the table compared with the second-lowest bidder.

We could measure the gap three ways:

  1. Total dollars: second-lowest bid minus lowest bid.
  2. Cents per tree: second-lowest unit price minus lowest unit price.
  3. Percentage: the difference expressed relative to the lowest bid.

Each metric tells a different story. A 5¢ gap on five million trees is financially much larger than a 20¢ gap on a small contract.

The list could include:

  • Contract number and location.
  • Tree count.
  • Lowest and second-lowest bidders.
  • Their bid amounts and prices per tree.
  • Dollar gap and percentage gap.
  • Any relevant commentary from the post, such as difficult access or an unusual tender specification.

We would identify these as gaps in the posted bids, not money that the winning company necessarily could have captured. Raising its bid might have changed the ranking or the award.

How common were large gaps?

Rather than only highlighting dramatic cases, show the distribution:

  • What percentage of contracts had a first-to-second gap under 2%?
  • How many had a gap under 5%?
  • How many exceeded 10%, 20%, or 50%?
  • Did the typical gap change over the years?

We could make a separate comparison for big jobs versus small jobs and for coastal versus Interior jobs.

Which companies most often submitted a bid far below the field?

For every bid, compare the company’s price with the median of the other bids on the same job.

For example:

A company bid 45¢; the median of its competitors’ bids was 60¢. Its bid was 15¢, or 25%, below the competitors’ median.

We could then identify:

  • The most extreme individual examples.
  • Companies most frequently below the field.
  • Companies most frequently above the field.
  • Whether those patterns changed by year.

I would require a minimum number of competitors—perhaps three other priced bids—before calculating the comparison. Otherwise, one unusually high or low competitor can distort it.

This would need careful language: a low relative bid could reflect better knowledge of the ground, a different operating model, an error, a desire for summer work, or a number of other factors. The numbers alone cannot tell us which.

The closest finishes

At the other extreme, rank the tightest bids:

  • Smallest dollar gap between first and second.
  • Smallest difference in cents per tree.
  • Smallest percentage gap.
  • Closest cluster of the top three or top five bidders.

Your 2025 Terrace example, where Sapling and Summit were separated by $68, would be a strong contender for one of these lists.

For a particularly fun version, we could calculate how many trees would account for the gap at a given price. That would be a descriptive illustration, not a suggestion that contract pricing literally works one tree at a time.

4. How did prices vary by location and job type?

Coastal versus Interior prices

Produce separate annual weighted-average lines for:

  • Interior contracts.
  • Coastal contracts.
  • Possibly a third category for northern and remote coastal work.

This would show whether the gap between coastal and Interior bidding widened or narrowed over the period.

However, “coastal” is not a single operating environment. A Vancouver Island road-access job and a remote inlet contract requiring a boat or helicopter can have very different economics. I would also retain the $1.50 ceiling, which may remove a larger share of the most difficult coastal bids and therefore bias a coastal-versus-Interior comparison. We should report how many bids the ceiling removes from each group.

Prices by district or timber sales office

For locations with enough observations, compare annual weighted averages and distributions for areas such as:

  • Prince George.
  • Mackenzie.
  • Fort St. James/Vanderhoof.
  • Burns Lake/Houston.
  • Quesnel.
  • Williams Lake.
  • Kamloops/Merritt.
  • Cranbrook and the Kootenays.
  • Port McNeill, Campbell River and other coastal offices.

We could make this either a table or a set of small charts. A map could be useful, though the geographic assignment would normally represent the administering office or stated work area, not the exact locations of every block.

Spring versus summer prices

Using contracts clearly identified as spring-only or summer-only, compare the price distributions within the same year and region.

This could test the familiar idea that summer work often sells at a discount because companies want to retain crews after the main spring season.

Potential results:

  • Median spring bid versus median summer bid.
  • Difference between spring and summer lowest bids.
  • Whether the gap changed between, say, 2015 and 2025.
  • Whether the gap was larger in some regions than others.

Mixed spring/summer contracts would need their own category unless the PDFs provide separate volumes and prices for each season.

Does contract size affect price?

Group contracts by the size categories already used in the charts:

Size categoryTrees
SmallFewer than 500,000
Medium500,000–1.5 million
LargeMore than 1.5 million

We could compare prices, bidder counts and first-to-second gaps across those groups.

An interesting question is whether larger contracts generally attract lower prices per tree because fixed costs are spread over more trees—or whether they sometimes attract fewer bidders because fewer companies can take on the volume.

We should compare within the same year and region where practical. A large, straightforward Interior job and a small, complex coastal job are not directly equivalent.

Summer work and the “crew retention discount”

A more targeted version would focus on companies that bid on both:

  • A spring contract; and
  • A summer contract in the same region and year.

We could ask whether the same company tended to bid lower on its summer job. It still would not be a controlled experiment, but it would be more informative than comparing every spring contract with every summer contract.

5. What effect did the contractor rating system have?

How often did the lowest dollar bid fail to rank first?

The posts sometimes explicitly note when contractor ratings changed the order of bidders. We could catalogue those contracts and record:

  • Lowest dollar bidder.
  • Bidder ranked first after the rating adjustment.
  • Difference between their posted bid amounts.
  • Region and year.
  • Whether the PDF confirms the eventual award.

This could show how often rating adjustments visibly affected rankings within this collection. It would not establish the rate across all BCTS contracts, because not every post may identify every adjustment.

Closest decisions affected by ratings

A related list could identify contracts where:

  • The lowest dollar bid was overtaken by a slightly higher bid after ratings; or
  • Ratings moved a bidder several places up or down the award order.

We could look for the largest observed dollar difference between the lowest bid and the first-ranked bid, while being careful to use the actual posted amounts and to distinguish ranking from confirmed award.

For years in which the published prices were described as adjusted prices, we would need to identify that explicitly rather than mixing them silently with original tender amounts.

6. What changed over time?

Inflation-adjusted bid prices

The charts we have made so far use nominal cents per tree: 40¢ in 2015 is compared directly with 40¢ in 2025.

We could adjust the annual figures for inflation and show both:

  • Nominal prices, as posted.
  • Inflation-adjusted prices, expressed in a common year’s dollars.

That would help answer whether bids increased faster than general consumer prices. We could also use a more industry-specific cost measure if we find a suitable one, though no single index perfectly captures planting costs such as wages, food, vehicles, insurance and camp expenses.

This would require external data and a clear choice of inflation index.

A before-and-after view of the volume expansion

We could compare bidding patterns across periods such as:

  • 2015–2017.
  • 2018–2020.
  • 2021–2023.
  • 2024–2025.

For each period, show:

  • Prices.
  • Number of bidders.
  • First-to-second gaps.
  • Regional mix.
  • Contract sizes.
  • Share of bids from each company.

The periods could reveal changes around the beetle, wildfire and increased-reforestation years. They would not, by themselves, establish what caused those changes.

Did bid prices rise at the same pace for all companies?

A multi-line chart could compare companies’ annual tree-weighted averages, but I would also build a stronger same-contract comparison to control for differing work mixes.

That could reveal whether, on jobs where they competed directly, the relative gap between two companies became wider, narrower or reversed over time.

7. Unusual contracts and interesting stories

The PDFs contain your descriptions and discussion, not just bid tables. That makes some more qualitative analyses possible.

A catalogue of unusually difficult specifications

Search the posts for references to:

  • Helicopter access.
  • Boats and barges.
  • Long quadding or walk-in distances.
  • Remote camps.
  • Numerous small blocks.
  • Fill planting and burned ground.
  • Fertilizer requirements.
  • Unusual stock types.
  • Steep or rocky ground.
  • Tight completion windows.
  • Extra survey or supervision obligations.

We could then list the associated contracts and their bids. The result might become a fascinating “why this job priced differently” reference.

Some of those categories would need manual review. A post mentioning a helicopter does not necessarily mean that every block, or even the majority of the trees, required helicopter access.

The biggest disagreements over the same ground

Rank contracts by the difference between the lowest and highest qualifying bid, in both dollars and cents per tree.

A wide range can signal very different assumptions about access, production, logistics, risk or the value of keeping a crew employed. The most interesting cases would pair the numbers with whatever you wrote after looking at the blocks.

Because the $1.50 ceiling removes high bids, it would truncate the spread on some jobs. We could still apply your default ceiling, but flag contracts where at least one higher bid was excluded.

Contracts where nearly everyone agreed

Find jobs where several bidders—perhaps at least five—were clustered within a narrow band. Examples could include:

  • All qualifying bids within 10% of the lowest.
  • At least five bids within 5¢ per tree.
  • The smallest range among jobs with six or more bidders.

This would complement the “largest disagreements” list and might identify jobs where companies had unusually similar expectations.

Your historical predictions versus later results

Your posts often include comments about where you thought prices were headed, whether a job looked attractive, and whether a bid seemed low.

A fun retrospective would collect a selection of those comments and compare them with later information in the PDFs:

  • Predictions that were borne out.
  • Predictions that turned out differently.
  • Jobs where the forum discussion identified a risk that later became relevant.
  • Comments about future industry conditions that look particularly interesting in hindsight.

That would be partly editorial and would need care: the PDFs may not tell us whether a contractor actually made or lost money on a job.

The analyses I would prioritize

If you wanted the most informative first batch, I would start with these:

  1. Head-to-head company comparisons, because they compare bids on the same ground.
  2. Largest and smallest gaps between first and second bids, with contract details.
  3. Number of bidders per contract over time, including a clear treatment of missing prices.
  4. Regional and spring-versus-summer price differences.
  5. Contractor-rating reversals, where the posts provide enough detail.
  6. Inflation-adjusted annual bid prices.

Before doing a large series of comparisons, I would rebuild the underlying bid records into a single auditable table with the source PDF and page for every entry. The work we have already done exposed enough missed entries, repeated posts, name variations and inconsistent figures that it would be unwise to treat the existing chart extractions as a finished database. That table would make it much easier to check any surprising result and would give us a dependable foundation for all of the analyses above.

 

 

 

No comments:

Post a Comment