# Elora Grid

> Elora Grid is an AI-first bid management platform for power solution companies and electrical engineers. AI reads tender documents, builds supplier packages and levels incoming bids in one connected workflow.

Elora Grid is a quoting assistant, not a chatbot. Teams hand it tasks from their quoting workflow; it returns deliverables with citations, flags judgment calls to humans, and never sends or writes anything without approval.

## Key facts

- What it is: an AI quoting assistant for engineering project companies, EPC contractors and high-mix (engineered-to-order) manufacturers.
- What it does: reads the documents a tender arrives as — RFQs, scopes of work, specifications, drawings and blank client templates — and returns the deliverables behind a quote: clause-by-clause compliance checklists, populated returnable schedules, conflict & variation registers, and a current price book.
- How it works: every line is cited to its source document and page; it never invents prices (pricing is flagged for humans); nothing is sent, written or submitted without approval; a timestamped backup is taken before any write.
- Data handling: your documents produce your deliverables only and are not used to train AI models; an NDA is available on request.
- Who it is for: bid and tender teams, precon, business development, and engineers pulled into bids — across Australia, the United States, Europe and Asia.
- Getting started: implementation is typically 1–6 weeks and works from your existing documents; cost is a fraction of a new hire.

## Example tasks (each page includes an interactive demonstration)

- [Bid management](https://eloragrid.ai/): AI reads tenders, prepares supplier enquiries and levels bids.
- [Electrical drafting](https://eloragrid.ai/drawings): electrical drawings and linked 3D models for switchboards, switchrooms and microgrids.

- ["Complete our tender returnables"](https://eloragrid.ai/tasks/tender-returnables): Your standard answers, filled into any client's schedules, cited and ready for review.
- ["Find any contradictions within the RFQ documents"](https://eloragrid.ai/tasks/sow-compliance): Reviews entire RFQ, finds if there are any contradictions between SoW, Site specs, and engineering diagrams, drafts and RFI to send and loads it in your email
- ["Keep our parts price book current"](https://eloragrid.ai/tasks/price-book): Supplier quotes read and matched into your workbook, suspicious prices flagged before they reach a bid.
- ["Find our most similar past projects"](https://eloragrid.ai/tasks/similar-projects): A new RFQ and drawings in, your most similar past projects out, with the reasons why.
- ["Customized AI agents built for your process"](https://eloragrid.ai/tasks/custom-tasks): Through deep experience we have built up modules that accelerate development of AI agents for your quoting team

## Who it is for

- [Electrical drafters and designers](https://eloragrid.ai/for/electrical-drafting): Elora Grid drafts single line diagrams (one line diagrams), control schematics, wiring diagrams and general arrangement drawings from the tender pack, in your title block and drafting standards.
- [Generator enclosure manufacturers](https://eloragrid.ai/for/generator-enclosures): Elora Grid drafts general arrangements and schematics for acoustic generator enclosures straight from the customer's spec, so the drawings go out with the quote.
- [Electrical engineering consultants](https://eloragrid.ai/for/engineering-consultants): Elora Grid drafts general arrangements and schematics from your engineers' design intent, so senior hours go into engineering instead of redrawing.
- [Electrical project engineering firms](https://eloragrid.ai/for/electrical-projects): Elora Grid reads hundreds of tender documents, drafts general arrangements, builds scope of works checklists, packages enquiries for suppliers and benchmarks the quotes that come back.

## Free tools & templates

- [Returnable schedule completeness checklist](https://eloragrid.ai/tools/returnable-schedule-checklist): 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.
- [Conflict and variation register template](https://eloragrid.ai/tools/conflict-and-variation-register-template): 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](https://eloragrid.ai/tools/supplier-rfq-pack-generator): 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 (SDRL) checklist](https://eloragrid.ai/tools/tender-deliverables-checklist): 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.
- [Tender clarification (RFI) register template](https://eloragrid.ai/tools/tender-clarification-register-template): 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.

## Guides

- [How to build a scope-of-work (SoW) compliance matrix](https://eloragrid.ai/guides/how-to-build-a-sow-compliance-matrix): A step-by-step method to turn a tender scope of work into a clause-by-clause compliance matrix: extract requirements, set IDs, record compliance status, cite evidence and flag conflicts.
- [Why generic LLMs hallucinate tender estimates (and what to use instead)](https://eloragrid.ai/guides/why-generic-llms-hallucinate-tender-estimates): Generic LLMs like ChatGPT invent prices and compliance claims because they predict text, not verified facts. Why that breaks tender estimating, and the safer alternative.
- [A tender re-issued mid-bid: how to find what changed without re-reading 1,000+ files](https://eloragrid.ai/guides/how-to-compare-tender-revisions): A tender re-issued mid-bid? Compare revisions by diffing which documents, clauses and bid responses changed, instead of re-reading 1,000+ files. The method.
- [Why CPQ and ERP quoting modules fail for engineered-to-order project bids](https://eloragrid.ai/guides/why-cpq-erp-quoting-fails-for-engineered-to-order): CPQ and ERP quoting modules price configurable catalogue products, not one-off tenders. Why they fail for engineered-to-order project bids, and what fits instead.
- [Tendering under EN/IEC: the compliance evidence a European bid must carry](https://eloragrid.ai/guides/en-iec-tender-compliance-evidence-eu): A European bid must prove EN/IEC compliance with evidence: CE marking, an EU Declaration of Conformity, type test certificates and EN 10204 material certificates.
- [The hidden cost of reformatting the same answers into every client's template](https://eloragrid.ai/guides/cost-of-reformatting-tender-responses): Reformatting the same answers into each client's returnable template is a hidden tender cost. Where the time and error risk hide, and how to cut it safely.
- [Order of precedence: who wins when the scope of work and drawings contradict](https://eloragrid.ai/guides/order-of-precedence-in-tender-documents): Order of precedence is the contract rule that decides which document wins when a tender's scope of work, specification and drawings contradict. How it works, by region.
- [The hidden cost of re-keying supplier quotes into your estimate](https://eloragrid.ai/guides/cost-of-re-keying-supplier-quotes): Re-keying supplier quotes into your estimate hides real cost: transposed digits, misplaced decimals, stale rates and dropped exclusions. Where the errors come from, and how to cut them.
- [How to triage a tender document pack in the first 48 hours](https://eloragrid.ai/guides/how-to-triage-a-tender-document-pack): How to review tender documents quickly: read the instructions to bidders first, register every file, extract the governing dates, and find deal-breakers early.
- [Bidding into IEC-based Asian power projects: the documentation that travels](https://eloragrid.ai/guides/iec-tender-documentation-asia): What documentation an IEC-based tender requires across Asian power markets: type test certificates, accreditation, service conditions and local overlays.
- [The seven most common errors in tender responses, and the clause behind each one](https://eloragrid.ai/guides/seven-common-errors-in-tender-responses): Seven errors get bids set aside before the price is read: missing returnables, forbidden qualifications, unacknowledged addenda. Each traced to its clause.
- [The first 48 hours with a new tender: the ten clauses to read before anything else](https://eloragrid.ai/guides/first-48-hours-with-a-new-tender): In the first 48 hours you read ten clauses, not the whole pack: precedence, validity, liquidated damages, security, payment, liability and the rest.
- [Bid/no-bid scorecard for engineering tenders](https://eloragrid.ai/guides/bid-no-bid-scorecard): Six weighted criteria and three decision bands, scored in the first days of a tender so estimating effort is committed by criteria rather than by reflex.
- [Buyers are starting to evaluate tenders with AI: what that changes about your returnables](https://eloragrid.ai/guides/ai-tender-evaluation-and-your-returnables): Buyers increasingly extract bidder answers with AI before a panel scores them. What breaks extraction, why cross-references fail, and how to survive the pass.
- [Colour team reviews (Pink, Red, Gold) adapted to engineering tenders](https://eloragrid.ai/guides/colour-team-reviews-for-engineering-tenders): Pink, Red and Gold reviews adapted for tenders that are mostly not prose: what each one opens in an engineering bid, and how to schedule them backwards.
- [The 600 line BOQ problem: what high line count tenders do to an estimating team under deadline](https://eloragrid.ai/guides/high-line-count-boq-tenders): Why a large bill of quantities takes days rather than hours, where the time actually goes, and how to sort the lines into three bands before pricing anything.
- [Tender kick-off checklist: from pack download to compliance plan](https://eloragrid.ai/guides/tender-kick-off-checklist): The fixed agenda a bid team runs before pricing starts: what a tender kick-off covers, who needs to be in the room, and the four artefacts it has to produce.
- [Win/loss review template that feeds the next bid](https://eloragrid.ai/guides/win-loss-review-template): The five areas a tender debrief has to cover, what to ask the client, and the three places the output has to go before the review changes anything.
- [The estimate's assumptions die at handover: carrying tender knowledge into delivery](https://eloragrid.ai/guides/tender-to-delivery-handover): What is lost between the estimate and the project team, why it decides variation claims, and the six things a handover record has to carry.
- [How tender evaluation and scoring actually works: weighted criteria, price and non-price](https://eloragrid.ai/guides/how-tender-evaluation-and-scoring-works): The three stages of a weighted tender evaluation, how price and non-price scores interact, and where bids quietly lose marks without ever failing.
- [Supplier quote validity vs tender validity: where a winning margin quietly expires](https://eloragrid.ai/guides/supplier-quote-validity-vs-tender-validity): Why a winning bid loses margin before award, where the validity mismatch hides in a tender pack, and the four treatments for a quote that expires first.
- [Writing a technical response that scores against the evaluation criteria](https://eloragrid.ai/guides/writing-a-technical-response-that-scores): What evaluators actually score, the difference between an assertion and an evidenced answer, and the four moves that work for every criterion.
- [Process or luck: a maturity self-check for tendering teams](https://eloragrid.ai/guides/bid-process-maturity-self-check): Five markers that show whether a tendering process runs on method or on whoever picked the tender up, and why the cheapest fixes sit at the two ends.
- [Rise and fall clauses in long duration energy projects](https://eloragrid.ai/guides/rise-and-fall-clauses): How escalation is actually calculated, why the base date decides what you recover, and the six things to check before relying on a rise and fall clause.

## Glossary

- [Returnable schedule](https://eloragrid.ai/glossary/what-is-a-returnable-schedule): A returnable schedule is a structured form a buyer issues with a tender that the bidder must complete and return as part of their submission, capturing one part of the response (price, technical compliance, capability, or supporting evidence) in the exact format the buyer will evaluate.
- [BAFO (best and final offer)](https://eloragrid.ai/glossary/what-is-bafo): BAFO (best and final offer) is a buyer's formal, late-stage request for shortlisted bidders in a competitive tender to submit one final, revised offer (sharpened price, confirmed terms and answered clarifications) after which no further changes are accepted.
- [Submittals](https://eloragrid.ai/glossary/what-are-submittals): Submittals are documents a contractor provides for the design team to review during a project, proving that the materials, equipment and methods it will use comply with the contract: in US construction the term most precisely covers post-award shop drawings, product data and samples. At bid time, the forms a bidder must complete and return are usually called bid forms, proposal forms or exhibits, which are the US counterpart to what Australian and UK tenders call returnable schedules.
- [ITP vs ITC](https://eloragrid.ai/glossary/itp-vs-itc): An inspection and test plan (ITP) is the document that plans the quality checks for a scope of work, listing each inspection and test, its acceptance criteria, its hold and witness points and who is responsible; an inspection and test checklist (ITC) is the completed record that evidences those checks were actually carried out, capturing the date, the result, any defect and the sign-offs. In short, the ITP is the plan and the ITC is the proof: one ITP defines the inspections, and each time the work is built it generates the ITCs (also called inspection and test records, ITRs) that show the plan was followed.
- [SDRL (supplier data requirements list)](https://eloragrid.ai/glossary/what-is-an-sdrl): An SDRL (supplier data requirements list) is the buyer-issued list, attached to a tender or purchase order, of every document and data deliverable a supplier must produce alongside the physical scope, with each line carrying a title, a document-type code, the required format, the review class it needs, and the milestone or date it is due by. It is the contractual master checklist of a supplier's paperwork obligations; the same list is often written as a VDRL or VDR (vendor data requirements list), and the supplier's reply committing to deliver each item is the supplier document list (SDL).
- [RPEQ sign-off](https://eloragrid.ai/glossary/when-is-rpeq-required): RPEQ sign-off is the certification of an engineering deliverable by a Registered Professional Engineer of Queensland (RPEQ), the engineer who then carries professional and legal responsibility for it. An Australian tender needs RPEQ sign-off when the professional engineering services are carried out in or for Queensland, which is a statutory requirement under the Professional Engineers Act 2002 (Qld), or when the contract or specification calls for it as a condition of the deliverables. Under that Act, anyone providing a professional engineering service in or for Queensland must either be registered as an RPEQ or work under the direct supervision of one.
- [PE stamp (professional engineer seal)](https://eloragrid.ai/glossary/when-is-a-pe-stamp-required): A PE stamp (also called a PE seal) is the mark a licensed Professional Engineer applies to an engineering document, with their signature and state license number, certifying that they prepared or directly supervised the work and take legal responsibility for it. A US bid needs a PE stamp when the engineering deliverables will be submitted for a building permit or other government or utility approval, or are otherwise offered to the public, in which case they must be sealed by a PE licensed in the state where the project is located. Many states also apply an industrial exemption that lets a company's own employees engineer its own products and facilities without a seal, so not every engineered deliverable in a bid has to be stamped.
- [Price book](https://eloragrid.ai/glossary/what-is-a-price-book): A price book is a maintained library of unit rates an estimator prices from, holding a cost for each defined unit of work (and often the labor, material and equipment that make up that cost), so a new estimate is built by pulling proven rates rather than deriving every price from scratch. It is also called a rate library, cost library, pricing database or, in US construction, a unit price book (UPB). A price book can be a company's own rates distilled from past jobs, or a published commercial dataset such as RSMeans; either way it is the single source of truth for what a unit of work costs, kept current so every bid starts from the same trusted numbers.
- [RFI vs clarification vs departure vs qualification](https://eloragrid.ai/glossary/rfi-vs-clarification-vs-departure-vs-qualification): An RFI, a clarification, a departure and a qualification are four different exchanges in a tender, and they are not interchangeable. An RFI (request for information) is a question raised to close an information gap, either a buyer's pre-tender approach to the market or a bidder's formal query about the tender documents during the bid period. A clarification is an explanation of something already stated, given without changing the offer: the buyer's answer to bidders' questions, or the buyer's request that a bidder explain part of a submitted bid. A departure is a stated non-compliance against a specific clause or specification, recording exactly where your offer does not meet what was asked. A qualification is a condition you attach to your offer that changes the basis of your price, such as an exclusion, an assumption or a limit of liability. The short test: an RFI asks, a clarification explains, a departure declares non-compliance against a clause, and a qualification changes what your price actually covers.
- [BOQ vs schedule of rates vs lump sum](https://eloragrid.ai/glossary/boq-vs-schedule-of-rates-vs-lump-sum): A lump sum price is one fixed amount for a defined scope. A bill of quantities prices measured quantities line by line, so the total follows from rates applied to quantities the client has measured. A schedule of rates fixes the rates but not the quantities, and the final sum follows from what is actually done.

The difference that matters is who carries the risk that the quantity is wrong. Under a lump sum, you do. Under a schedule of rates, the client does. A bill of quantities sits between them, and exactly where depends on whether the contract makes the quantities binding or indicative.
- [Provisional sums, PC items and contingency](https://eloragrid.ai/glossary/provisional-sums-pc-items-and-contingency): A provisional sum is an allowance included in the contract sum for work that is not yet defined well enough to price, adjusted later against what the work actually costs. A prime cost item is an allowance for supplying an item that has not yet been selected, with your installation, attendance and margin priced separately.

Contingency is different in kind: it is money set aside against risk, and depending on whose contingency it is, it may sit inside the contract sum, inside your margin, or in the client's own budget where you never see it.

## How it compares

- [Elora Grid vs CPQ software](https://eloragrid.ai/compare/cpq-software): CPQ tools quote configurable products from a catalog. Elora Grid reads the documents an engineering tender arrives as and drafts the deliverables. How they differ, and where they fit together.
- [Elora Grid vs Procore, Aconex & InEight](https://eloragrid.ai/compare/construction-platforms): Procore, Aconex and InEight store and control project documents. Elora Grid reads them and drafts the quoting deliverables. Why they're different categories, and how they work side by side.

## Company & contact

- [About Elora Grid](https://eloragrid.ai/about): the company, its founder and the engineering teams the product is built for.
- [Join the waitlist](https://eloragrid.ai/contact): sign up for early access; a person emails you when your place opens.
- Email: contact@eloragrid.ai

For full page content in one file, see https://eloragrid.ai/llms-full.txt.