Guides for bid & tender teams
Practical how-tos and explainers for engineering tendering — written for the people who actually run the bid, and cited so you can trust them.
Supplier bid levelling checklist: compare quotes consistently
Compare supplier quotes against one package scope and commercial basis. Check price, exclusions, lead time and missing items before treating offers as comparable.
Returnable schedule checklist: what to include in a tender
A returnable schedule completeness checklist is a list of the schedules and supporting documents a tender submission must include, so a bid is not set aside for a missing or wrongly formatted return. Work through each group below before you submit.
How to keep a conflict and variation register
A conflict and variation register is a single log of every contradiction, ambiguity or gap found across a tender's documents (scope, specifications, drawings and schedules), so each one becomes a deliberate clarification, qualification or priced allowance instead of an absorbed cost. Set up the columns below, then log each issue as you read.
Supplier RFQ pack template: what to send suppliers
A supplier RFQ pack is the bundle of scope, technical and commercial information a bidder sends to each equipment supplier during a tender, so the quotes that come back are complete, comparable and traceable to the project. Build one pack per equipment package using the groups below, then issue the same pack to every supplier on that package.
Tender deliverables checklist: plan your SDRL
A tender deliverables checklist is the list of engineering and project documents a bid commits to producing and submitting, drawn from the tender's supplier data requirements list (SDRL). Each deliverable carries a category, an owner, a submission stage (for approval, for review, for construction, or as-built) and a due date tied to a milestone. Work through the groups below to confirm every deliverable the tender demands is captured, scheduled, resourced and owned before you commit to it in your bid.
How to keep a tender clarification register
A tender clarification register is a single log of every question you raise with the tender issuer during a live bid, capturing the clause it relates to, the question asked, the response or addendum received, and how that answer changes your bid. It keeps two threads in one place: your own outbound clarifications (RFIs), and the issuer's published question-and-answer addenda that bind every tenderer. Set up the columns below, log each query as you raise it, and reconcile the issuer's published responses against it before you submit, so no binding answer is missed.
How to build a scope-of-work (SoW) compliance matrix
A scope-of-work compliance matrix is a clause-by-clause table that maps every obligation in a tender's scope to your response, your evidence and a compliance status. To build one: extract every requirement, give each a stable ID, record a compliance position and its evidence, and flag any gaps or contradictions between the scope, specifications and drawings.
A tender re-issued mid-bid: how to find what changed without re-reading 1,000+ files
When a tender is re-issued mid-bid, you compare revisions in three narrowing passes (which documents changed, which clauses inside them changed, and which of your bid responses are affected) rather than re-reading the whole pack. Build a document register for both the original issue and the re-issue to isolate the handful of files that actually moved, diff each changed document clause-by-clause against the version you already responded to, then trace every material change through to the returnable, price line and compliance position it touches. Do not rely on the addendum note alone: it is a summary written by the issuer, not the binding change. This is exactly the kind of document-intensive work you can hand to Elora Grid and have done for you: send both issues and it returns the document register, a clause-level diff and a cited change-impact list, so your team reviews decisions instead of re-reading files.
Why CPQ and ERP quoting modules fail for engineered-to-order project bids
CPQ and ERP quoting modules fail for engineered-to-order (ETO) project bids because they are built to price configurable catalogue products from a pre-modeled option list, while an ETO bid is a one-off engineered response assembled from unstructured tender documents. A CPQ engine needs the product, its options and its pricing rules defined in advance; an ETO tender has no product yet, arrives as an RFQ, scope of work, drawings and blank returnable schedules, and must be answered clause-by-clause in the client's own format. That is a different problem: not selecting and pricing a known configuration, but reading documents, deciding compliance, and writing the answer into someone else's template. This is the work Elora Grid is built for: hand it the documents a tender arrives as, and it returns the compliance response and deliverables with every line cited to its source, while pricing and judgment stay with your team.
Tendering under EN/IEC: the compliance evidence a European bid must carry
A European tender requires you to prove compliance with EN and IEC standards through documented evidence, not just a statement that you comply. The core evidence a bid must carry is the EU Declaration of Conformity and CE marking for any equipment placed on the EU market, type test certificates to the relevant harmonised EN/IEC standard, material certificates to EN 10204 (typically type 3.1, sometimes 3.2), and the technical documentation that backs each claim. EN standards are the European versions of IEC standards (often identical, with national or European deviations), and a harmonised EN listed in the Official Journal of the EU gives a presumption of conformity with the relevant directive or regulation. The practical task in any EU bid is to attach the right certificate to the right clause: a compliance matrix that maps each requirement to its EN/IEC reference and the document that evidences it.
The hidden cost of reformatting the same answers into every client's template
Reformatting the same answers into every client's template is a hidden cost in tendering because every tender arrives with its own blank returnable schedules, and substantially the same content (your compliance positions, capability statements, equipment datasheets and standard terms) has to be re-keyed into a different structure for each bid. The work is not writing the answer; it is pouring an answer you already have into someone else's forms, line by line, in their wording and their order. It stays invisible because it never appears as a line item: it hides inside estimator and engineer hours, it scales with how many bids you submit rather than their value, and every manual re-key is a fresh chance to transcribe a wrong rating or drop a qualifier. Elora Grid removes this work directly: hand it your source answers and the client's blank returnables, and it completes each schedule in the client's format with every value cited to its source, while the compliance and pricing judgment stays with your team.
Order of precedence: who wins when the scope of work and drawings contradict
Order of precedence is the contractual rule that decides which document controls when a tender's documents contradict each other. When the scope of work (or specification) and the drawings disagree, the winner is whichever document the contract's order-of-precedence clause ranks higher, not whichever you read first or would prefer. Most standard forms rank the negotiated agreement and any addenda at the top, then the conditions of contract, then the specification, then the drawings, with schedules below, but the exact order varies by contract form and region, so you read the actual clause before deciding. Where there is no precedence clause (as under AIA contracts, which treat every document as complementary), a contradiction is resolved by interpretation and, in practice, by a written direction, not by silently choosing. For a bid, the safe move is never to price around a contradiction quietly: log every conflict to a register and raise it as a clarification, because a discrepancy you resolve in your own favour without confirmation becomes a variation you absorb after award.
The hidden cost of re-keying supplier quotes into your estimate
Re-keying supplier quotes into your estimate is a hidden cost because the price a supplier sends (in an email, a PDF or their own quote form) has to be transcribed by hand into your estimate's structure, and every manual transcription is a fresh chance to transpose a digit, misplace a decimal, carry a stale rate, or drop an exclusion. The cost is invisible because it never appears as a line item: it hides inside estimator hours and inside the estimate's own accuracy, where a single mis-keyed unit rate quietly moves your bottom line. It compounds because one project can carry dozens of supplier quotes across many packages, each in a different format, each re-entered under deadline. Elora Grid removes this work: hand it the supplier quotes and your estimate structure, and it extracts each line and places it against the matching scope item with the source quote and page cited, while the leveling and the rate decisions stay with your estimator.
How to triage a tender document pack in the first 48 hours
In the first 48 hours after a tender lands you triage the pack rather than read it, working in order of decision value: register every document, read the instructions to bidders first, extract the governing dates, list every returnable, then sweep the commercial conditions for deal-breakers. The goal of the first two days is not to understand the whole scope; it is to establish what is binding, what you must produce, what could disqualify or sink you, and whether to bid at all. Reading a large pack front to back is the common mistake, because the documents that decide the bid (the conditions of tender and the commercial terms) are rarely the ones you open first. Elora Grid runs this first pass for you: hand it the pack and it returns the document register, the deliverables and dates, and the clauses that carry commercial risk, each cited to its source document and page, so the bid decision is made on facts rather than on a skim.
Bidding into IEC-based Asian power projects: the documentation that travels
An IEC-based tender requires documentation that proves each compliance claim rather than asserting it: the standards list with editions, a type test certificate from an accredited laboratory covering the actual rated values, design verification or routine test records for the units being supplied, material certificates, inspection and test plan (ITP) and factory acceptance test (FAT) records, and the full vendor data set the SDRL calls up. IEC is the technical baseline in most Asian power markets, which is why one evidence pack can travel across the region, but almost every market layers its own regime on top: GB in China, JIS in Japan, KS in Korea, IS in India, SNI in Indonesia, TIS in Thailand, and an electrical code derived from the US NEC rather than IEC in the Philippines. Two failures sink technically sound IEC bids more than any others: a certificate that does not cover the rated values or the site service conditions the specification demands, and a document set submitted in the wrong language, seal or format. Elora Grid builds the evidence map for you: hand it the specification, the standards list and your certificate pack, and it returns a compliance matrix pairing every clause with its IEC reference and the document that proves it, each line cited to its source and page.
The seven most common errors in tender responses, and the clause behind each one
A bid can be technically excellent, competitively priced, and set aside before anyone reads the number. Sound familiar? Seven errors account for most of it, and none of them is an engineering failure. A missing or incomplete returnable, a qualification where the conditions forbid one, an answer given in the wrong place, a price submitted in a structure other than the one instructed, an expired certificate, an unacknowledged addendum, and a lodgement that misses the method or the deadline. Every one traces to a clause in the conditions of tender, which means every one is findable before you submit. Checking a submission against those clauses is the sweep Elora Grid runs, each finding cited to the clause and the page it comes from. Deciding what to do about a finding is your bid manager's call.
The first 48 hours with a new tender: the ten clauses to read before anything else
In the first 48 hours with a new tender you read ten clauses, not the whole pack. They are the ones that decide whether you should bid at all, what the submission must physically contain, and what it will cost you if a position turns out to be wrong. Those ten are the order of precedence, the tender validity, liquidated damages, security, payment terms, limitation of liability, the variation mechanism, the programme and separable portions, the conformance and qualification rules, and the submission mechanics. Read in that spirit, the pack stops being a thousand files and becomes about forty pages that matter first. Finding and quoting those ten across a large pack is reading work. Elora Grid returns them with each clause quoted and cited to its document and page. What they mean for your risk appetite is your team's call.
Bid/no-bid scorecard for engineering tenders
A bid/no-bid scorecard turns the decision to pursue a tender into a short, weighted assessment made in the first days of the tender period, so the team commits estimating effort by criteria rather than by reflex. Score the opportunity against six weighted criteria. Apply thresholds the team agreed before any tender was on the table. Record the outcome either way, including the declines. The scorecard itself takes minutes; what feeds it is the first-pass read of the conditions of tender, and that reading is the part you can hand to Elora Grid so the team scores from evidence rather than memory.
Buyers are starting to evaluate tenders with AI: what that changes about your returnables
Your last submission answered a schedule with "refer to Section 4.2 of our technical proposal". A human evaluator would have turned the page. Would a machine? Buyers are increasingly using AI assistance to read and compare submissions, usually to extract each bidder's answers against the evaluation criteria before a person scores them. That does not change what wins a tender. It changes how harshly a submission is punished for putting the answer somewhere other than where the question was asked. The fix is the oldest advice in tendering, enforced more strictly than before: answer in the box, restate the question, and never make the evaluator go looking. Checking a submission for answers that are not where their question is, is work Elora Grid does; what those answers say stays yours.
Colour team reviews (Pink, Red, Gold) adapted to engineering tenders
Colour team reviews are staged bid reviews held at fixed points in the tender programme: a Pink Team tests the response plan and early content while there is still time to change course, a Red Team scores the near-final bid the way the client's evaluators will, and a Gold Team is the executive sign-off on price, risk and the decision to submit. The method comes from text-heavy proposal writing. An engineering tender is mostly not text. What wins or loses an EPC bid lives in the compliance matrix, the returnables, the technical schedules and the price, so that is what each review has to open. The working rule is simple: every colour review reads the same documents the client's evaluators will score, in the order they will score them. Preparing that reading, the state of every returnable and the compliance position clause by clause, is work you can hand to Elora Grid. The scoring judgment stays in the room.
The 600 line BOQ problem: what high line count tenders do to an estimating team under deadline
Six hundred priced lines, three tenders open, and the client wants the number on Friday. Sound familiar? A large bill of quantities is not slow because of the arithmetic. It is slow because most lines need a decision before they can carry a rate: which rate applies, whether the line as written matches the scope, and whether the supplier quote in front of you covers the same thing the line describes. Hundreds of lines price themselves in minutes. The week goes to the handful that cannot be priced at all. Sorting the lines into those that price from a known rate, those waiting on a supplier, and those that cannot be priced as written is mechanical reading. Hand the BOQ and the quotes to Elora Grid and it returns that split with each line cited to its source. Which rate to apply stays with your estimator.
Tender kick-off checklist: from pack download to compliance plan
A tender kick-off checklist is the short, fixed agenda a bid team works through in the first days after a tender pack lands, before any pricing starts. It turns an unread pack into four things: a document register, a dated deliverables list, the clauses that carry commercial risk, and a compliance plan with an owner against every line. Run it once, properly, and the rest of the bid is execution against a plan. Skip it and the pack gets read in fragments by whoever happens to open it first. Producing those four outputs is reading work you can hand to Elora Grid; who owns each line stays with your bid manager.
Win/loss review template that feeds the next bid
A win/loss review is a short structured debrief run after every tender outcome, win or lose, that records what moved the result and files it where the next bid will use it. It covers five areas: price, compliance, technical response, relationship and process. The review takes an hour and produces three corrections: to the weights on your bid/no-bid scorecard, to the answers you reuse, and to the rates you price from. Ask the client for a debrief, but do not wait for one to start. Most of what you need is already visible in your own submission read against the issued pack, and Elora Grid returns that reading cited to source.
The estimate's assumptions die at handover: carrying tender knowledge into delivery
Six months into delivery, the project team asks why the switchroom was priced without a spare cubicle. The estimator who knew has been on the next three bids since. Sound familiar? What transfers at award is usually the price and the scope. What rarely transfers is everything underneath the price: the exclusions, the assumptions about site access and free issued equipment, which supplier quote each rate came from, and which clarification answer the team relied on. That knowledge is exactly what a variation claim is argued with later. A handover record fixes it, and it is assembled from documents that already exist. Elora Grid pulls the qualifications, priced assumptions and clarification answers out of the submitted bid and returns them in one record, each cited to its source. What the project team does with them is a delivery decision.
How tender evaluation and scoring actually works: weighted criteria, price and non-price
Tender evaluation usually runs in three stages: a conformance check, then scoring against non-price criteria, then price, combined into a weighted total that ranks the bidders. Bids that fail the conformance check can be set aside before anything else is read. The weights are the whole game. A tender weighted seventy per cent price rewards a different submission from one weighted forty, and the conditions of tender usually publish either the weights themselves or the criteria in descending order of importance. Reading that before writing a word of response is what separates a bid written to the criteria from a bid written to impress. Extracting the criteria, their weights and every stated requirement into one structure is reading work Elora Grid returns cited to source. What you choose to emphasise against each criterion is a bid strategy decision.
Supplier quote validity vs tender validity: where a winning margin quietly expires
You priced the job in March off a transformer quote that was valid for thirty days. The client awarded in June. Sound familiar? That is a winning bid losing its margin before the contract is even signed, and nobody made a mistake. The conditions of tender make you hold your price for months. Your suppliers hold theirs for weeks. Nobody writes down what happens in between. The fix is boring and it works: a validity register. List every supplier quote and its expiry, compare each one against the tender validity and the client's right to extend it, and choose a treatment for every quote that dies first. Finding the mismatches, cited to the quote and the clause they collide with, is document work you can hand to Elora Grid. Deciding what to do about each one stays with your estimator.
Writing a technical response that scores against the evaluation criteria
A technical response scores when it answers the criterion in the criterion's own terms, in the place the schedule asked for it, with evidence attached to every claim. It loses marks when it describes the company instead of the work, or covers the subject without answering the question. The structure that scores is consistent: restate the question, answer it directly, show the evidence, then state what it means for this client's project. Four moves, in that order, for every criterion and every sub-criterion. Checking that every criterion and sub-criterion has an answer in the right place is mechanical, and Elora Grid returns that map cited to source. Writing the engineering content is your team's work, and should be.
Process or luck: a maturity self-check for tendering teams
Ask two people on your bid team when the compliance matrix gets started, and see whether you get the same answer. Sound familiar? A tendering process is mature when the same tender would be run the same way regardless of who picked it up. Five markers show whether yours is: a bid/no-bid made against criteria, a kick-off that produces artefacts, one named owner per obligation, review milestones fixed in the programme, and a feedback loop that changes the next bid. Score each as absent, ad hoc or standing. Most teams are strong in the middle and weak at both ends, which is also where the cheapest fixes are. The reading load is usually why: when the pack takes days to understand, the kick-off gets skipped. Elora Grid removes that load by returning the register, dates and risk clauses cited to source; the process itself is yours to run.
Rise and fall clauses in long duration energy projects
A rise and fall clause, also called escalation or price adjustment, moves the contract price up or down over the delivery period to track movements in the cost of specified inputs. The adjustment is calculated by formula from published indices, not from your actual costs, and only the portion of the price the clause names is adjusted at all. On a two or three year substation or battery storage project, that clause is often the difference between a viable price and a bet on the copper market. Four details decide how much protection it really gives: the base date, which indices apply, how much of the price is adjustable, and whether a cap or a deadband applies. Finding the clause, its formula and its base date across a large pack is reading work Elora Grid returns quoted and cited. Whether that protection is enough to bid on is your commercial judgment.
Latent conditions and brownfield risk: pricing what you cannot see
A latent condition is a physical condition on or under the site that a competent contractor could not reasonably have anticipated from the information provided and a reasonable site inspection. Standard contracts deal with it in a dedicated clause, and that clause decides whether the cost of the surprise sits with you or with the Principal. The test almost always turns on two things: what you were given, and what you could reasonably have found out. That makes the site information in the tender pack the boundary of your entitlement, and reading it closely decides whether a later claim has anything to stand on. Extracting the latent conditions clause, the site information provided and every disclaimer attached to it is reading work Elora Grid returns quoted and cited. What allowance to carry against what remains is your estimator's decision.
Reading a single line diagram to scope a switchroom or substation
A single line diagram (SLD) shows an electrical installation as one line per circuit: where the power comes in, how it is transformed, which switchgear it passes through, how it is protected and metered, and where it goes. For a tender it is the fastest route to the scope of a switchroom or substation, because almost everything that drives the price is on it: the number of tiers and panels, the voltage levels, the fault rating, the protection scheme and the incomers and feeders the switchboard has to carry. What the SLD does not show is also what you need to know before you price. It carries no dimensions, no cable lengths and no room layout, so the SLD gives you the equipment count and the general arrangement gives you the building. Read in the order below, the diagram yields a scope list in under an hour. Reading the SLD against the specification and the equipment list, and returning the counts and ratings with the drawing reference beside each, is work Elora Grid does; what to allow for the parts the drawings leave out stays with your estimator.
What a tender GA has to show, and what it doesn't
A tender general arrangement (GA) shows the client that the equipment you are offering fits, where each item goes, how it is reached and how cables get to it. It carries the overall footprint and height of each item, its position with key dimensions, the access and maintenance clearances, the cable entry and trench routes, any future space, and equipment references that match the single line diagram. It leaves out what a fabrication drawing needs: internal busbar arrangements, sheet metal details, fixings, tolerances and a full bill of materials. The line matters because a tender GA is read twice. The evaluator reads it to decide whether your offer fits the room and meets the specification, and later, if the submission becomes a contract document, someone reads it to decide what you promised. Elora Grid drafts a first tender GA from the specification and the equipment list, in your title block and with a 3D view to check clearances; your engineers decide what goes out with the bid.
Generator enclosure GA: the six lines in the spec that size the box
You open the enquiry for a 1,000 kVA set in an acoustic enclosure, and the first question is how big the box will be. Six lines in the specification decide it: the generator rating, the fuel autonomy, the noise limit, the ambient and cooling conditions, the exhaust silencer grade, and the access and transport limits. Read those six before drawing anything, because together they fix the length, width and height of the enclosure general arrangement (GA), and most of its price. Everything else in the specification adds detail inside an envelope these six have already set. Reading an enclosure enquiry and returning each of the six with the clause it came from is work Elora Grid does, and it drafts the first GA from them; the engineering judgment on the design stays with your team.
Type-tested or verified: what AS/NZS 61439 means in a switchboard tender
A switchboard specification that asks for a type-tested board is using the language of AS/NZS 3439, the standard AS/NZS 61439 replaced. Under 61439 a board is proven in two steps. Design verification proves the assembly system once, by test, by calculation or by comparison with a tested reference design, and the original manufacturer holds the record. Each board built from that system then gets its own routine verification, which the switchboard builder carries out before it leaves the workshop. The tender question is which of those records you can return, against the edition the specification cites. Reading the switchboard specification and listing every 61439 requirement with its clause, beside the evidence the returnable asks for, is work Elora Grid does. Whether a design is verified for the ratings you are offering stays with your engineers.