Key takeaways
- Triage first: sort by estimated contract volume and hide duplicates — otherwise the team works the queue at random.
- Then bid/no-bid: fit, position and economics decide whether you quote.
- Gut feel does not scale: criteria must be visible, transferable and reviewed quarterly against outcomes.
- Per the product page, Scalera sorts by estimated contract volume and flags duplicates; processing-time figures come from published case studies.
As of 6 November 2026 · Expansion of the existing resources article
Disclosure: Scalera builds software for tenders and quotes; this guide is ours. Features refer to the public product page; figures to published case studies. Corrections: info@scalera.ai.
Quoting teams at manufacturers and distributors rarely start the day with an empty inbox. Dozens of new PDFs, GAEB files and spreadsheets are waiting — and the temptation is to open the oldest request first. That is where margin leaks: time goes into duplicates and hopeless cases while winnable projects wait. The hidden costs of manual tender processing start with the wrong order of work, not only with retyping.
This guide replaces the thin legacy bid/no-bid article. New is the operational triage Scalera describes on the product page: sorting by estimated contract volume and flagging duplicates (Scalera, Product Matching). For formats and import see GAEB, ÖNORM and NPK; for reading the BoQ itself see analyze bills of quantities with AI.
Why gut feel and oldest-first do not scale
Individual salespeople develop a feel for which tenders are worth the effort. That feel does not transfer, does not scale, and is invisible to management.
Two people looking at the same tender decide differently — and nobody learns from either decision. At ACO, about 80% of incoming tenders were technically fairly straightforward, yet processing was still time-consuming (ACO case study). Without prioritization, routine work eats the capacity needed for the few cases that really need advice and speed.
- No shared definition of «worth it» across the team
- Duplicates and forwards get processed twice
- Win rate and effort are never checked against the bid decision
What is tender triage — and what comes first?
Triage is sorting the queue before anyone reads line items. The goal: filter noise and open the opportunities with the highest expected value first.
On the product page, Scalera describes the «new way» as auto-sorting by estimated contract volume and flagging duplicates (Scalera, Product Matching). You do not start with the oldest email, but with what matters commercially and operationally.
Estimated contract volume
Volume is an estimate from line-item count, trades and known price history — not a guarantee of the eventual order. It is enough as a sort signal: large, fitting requests before small scatter positions.
Duplicates and repeats
The same tender often reaches you several times: from the general contractor, from the specialist designer, and again as a PDF with a new deadline. Without duplicate detection, effort doubles without doubling the win chance.
| Step | Question | Outcome |
|---|---|---|
| 1. Intake | Is the request new or a duplicate? | Process once or merge |
| 2. Volume | What estimated contract volume? | Processing order |
| 3. Bid/no-bid | Fit, position, economics? | Bid, review or decline |
Source: triage description on scalera.ai/en/product-matching; bid criteria from this framework.
The three questions behind bid/no-bid
After triage comes the actual decision. Most bid decisions reduce to three questions.
01
Fit
What share of the bill of quantities can your portfolio cover — and with what confidence?
Portfolio coverage instead of gut feel
02
Position
Do you know the buyer, designer or project, and were you specified?
Relationship and specification
03
Economics
Do expected margin, effort and risk profile justify the work?
Expected value, not revenue alone
The fit question used to require reading the full tender. With automated position extraction and product matching by specification, use case and standard, coverage can be estimated faster (Scalera, Product Matching). How manufacturers measure this in practice is summarized in the hub Quoting software in construction: results.
How to estimate fit in minutes instead of hours
Portfolio coverage bridges triage and quoting. ACO cut processing of a 300-page bill of quantities from 30–45 to 10–15 minutes (ACO case study). Frauenthal reaches over 90% matching precision on structured bills of quantities (Frauenthal case study).
For the bid decision you do not need a finished price calculation. You need a solid answer to: «Can we cover the core of the BoQ — and is the rest worth it?» Low-confidence positions go to manual review; missing accessories belong in the economics check, not in a blind quote.
Teams that systematically include accessories avoid change orders and under-quotes — see accessories and complements in quotes. Generic chat tools do not replace domain matching; for the boundary see ChatGPT for bills of quantities and quotes.
Saying no professionally — and learning from it
A fast, polite decline protects the relationship better than a late or half-hearted quote. Buyers remember suppliers who respect deadlines — including those who occasionally sit out.
- Document the reason in one sentence (fit / position / economics)
- Send the decline the same day, with an option for future fitting lots
- Review decisions quarterly against win rate and effort
Teams that sort by volume and duplicates first, then check fit, position and economics, put their energy into tenders they can actually win.
What a day with triage looks like
The product page contrasts the old and new morning: manually sifting about 30 new tenders by gut feel versus a strategic start with volume sorting and duplicates filtered out (Scalera, Product Matching).
| Phase | Old way | New way |
|---|---|---|
| 07–09 | Oldest first, duplicates unnoticed | Volume sort, duplicates flagged |
| Morning | Hunt PDFs, type SKUs | Validate suggestions, clarify fit |
| Afternoon | Backlog and late quotes | Customers, site, strategic cases |
Source: day-in-the-life on scalera.ai/en/product-matching.
What you can still define today
A framework only works when criteria and thresholds are written down. Start small and measure.
- Minimum fit percentage for «review» instead of «auto-bid»
- Duplicate rule (project ID, hash, sender chain)
- Who approves a no-bid — and how declines are worded
- Quarterly review: win rate and effort per bid decision
More than 150 manufacturers, distributors and general contractors across Europe use Scalera (Scalera, Product Matching). To connect the flow to your catalogue and systems: book a demo or read the FAQ on countries, languages and integrations.
Key takeaways
- Triage (volume, duplicates) and bid/no-bid (fit, position, economics) are two steps — not the same moment.
- Gut feel does not scale; criteria must apply team-wide and be checked against outcomes.
- Fit can be estimated faster with position extraction and matching than by reading every PDF end to end.
- Saying no is part of the process — documented and polite.
Next steps
- Write the three bid criteria and one duplicate rule on a single page.
- Score the next ten incoming tenders deliberately in this order.
- Check whether triage and matching fit your catalogue — start at Product Matching and Demo.
Frequently asked questions
What does triage mean for tenders?
Triage means sorting incoming requests by urgency and value before the team reads line items and matches products. On the product page, Scalera describes exactly that start: auto-sorting by estimated contract volume and flagging duplicates (Scalera, Product Matching).
How is triage different from bid/no-bid?
Triage orders the queue: what first, what later, what to merge as a duplicate. Bid/no-bid then decides whether you quote at all. Both steps need clear criteria, or chance and gut feel decide.
What three questions sit behind bid/no-bid?
Fit: what share of the bill of quantities does your portfolio cover? Position: do you know the buyer, designer or project, and were you specified? Economics: do expected margin, effort and risk justify the work?
Why are gut feel and oldest-first not enough?
Two people score the same tender differently, and nobody learns systematically from either decision. At ACO, about 80% of incoming tenders were technically fairly straightforward but still time-consuming (ACO case study) — without prioritization, effort lands in the wrong place.
How do you spot duplicate tenders?
Per the product page, Scalera flags duplicates automatically (Scalera, Product Matching). Organizationally, clear rules help: same project number, same BoQ hash, same tender ID, or a repeated PDF with only a new deadline — process once, decline once, or merge.
How long should a qualified bid decision take?
With automated position extraction you can estimate portfolio coverage in minutes instead of reading the full BoQ. ACO cut processing of a 300-page BoQ from 30–45 to 10–15 minutes (ACO case study) — the bid decision sits before that and needs its own criteria.
What should you do after a no-bid decision?
A fast, polite decline protects the relationship better than a late or half-hearted quote. Document the reason (fit, position, economics) so the team can learn from decisions each quarter.
How does prioritization connect to product matching and ERP?
After triage comes matching positions to products (Scalera, Product Matching). The product page describes hand-off without retyping: export as CSV, XML or GAEB, or via API into ERP, CPQ or CRM (Scalera, Product Matching). More: ERP integration for tenders and quotes.
Sources
- Scalera, Product Matching — triage (volume, duplicates), supported formats, export paths, 150+
- ACO case study — 30–45 to 10–15 minutes, ~80% technically fairly straightforward
- Frauenthal case study — over 90% precision on structured bills of quantities
- Construction quoting software results — cluster and metrics context
- ERP integration — export and connectivity