Use case

Build the compliance matrix

General Inference reads the tender, technical specification and general conditions, splits them into clauses, and checks each one against your data sheets, certificates and standard terms. It drafts a comply, deviate or clarify sheet with the source page for every line, and flags conflicts between documents. Your bid owner signs off every deviation.

Talk to us about thisAll use cases

Who it is for

Equipment makers bidding to EPCs and utilities

Valve, pump, transformer and switchgear specifications run to hundreds of clauses, and the buyer wants a reply to each one.

EPC and project contractors

Owner specifications, general conditions and project standards must be answered clause by clause before the technical bid is opened.

Bid and proposal teams in defence and public work

Evaluators reject a bid with a material deviation, so every exception has to be visible and deliberate.

How it is done today

Clauses are copied by hand into Excel

An engineer pastes the specification into a sheet, line by line, and types comply next to most of them. On a 300-clause spec, that is two or three days of work.

Comply is written where it should not be

Under deadline, a clause on material, testing or warranty gets a comply that your product or terms do not meet. The buyer holds you to it after the order.

Deviations hide in the general conditions

Liquidated damages, performance security, payment terms and governing law sit in a separate document. A deviation there can make the whole bid non-responsive.

What you get

  • A clause-by-clause matrix: comply, deviate or clarify, with the source page for each clause
  • The evidence for each comply, from your data sheet, certificate or standard terms
  • A short list of deviations and clarifications for the bid owner to decide
  • Conflicts between the specification, data sheets and drawings, named by clause
  • The matrix in the buyer's format, or in yours if none is given

How it works

1. Share the tender and your references

Upload the tender, specification and conditions. Connect your data sheets, certificates, standard terms and past matrices.

2. It splits and checks every clause

Each clause is read, including scanned pages and tables, and checked against what your product and terms actually offer.

3. It drafts the matrix

Each clause gets a proposed comply, deviate or clarify, with the reason and the page it relies on. Deviations are listed first.

4. Your bid owner decides

Exceptions are flagged first, and a person still reviews every line. The bid owner accepts, changes or rejects each deviation before the matrix goes into the offer.

An example

Example: a transformer maker in Nashik answers a 410-clause specification from a state power utility for 12 distribution transformers.

Clauses read410, across the specification, GCC and SCC
Proposed comply381, each with the data sheet or certificate it relies on
Proposed deviate9, including a no-load loss limit below your standard design
Proposed clarify20, such as a test standard named two ways in two sections
Conflict foundSpecification asks for copper windings; the price schedule says aluminium
Waiting on youWhether to accept the 10% liquidated damages cap in the SCC

Illustration with a made-up company, not customer data.

What it reads, and what you decide

It works from

  • The tender, RFP or enquiry
  • Technical specifications and data sheets from the buyer
  • General and special conditions of contract
  • Your own data sheets, drawings and certificates
  • Your standard terms and past compliance matrices

You still decide

  • Every deviation and how it is worded
  • Which clauses to raise as clarifications before the bid
  • Commercial terms you will accept or reject
  • The final matrix that goes into the offer

Worth knowing

Questions

Who approves the matrix?

Your bid owner. Each deviation and clarification is a proposal until a named person accepts it. Every decision is recorded with who made it and when.

Does it send the matrix to the buyer?

No. It drafts the matrix for your team. Your staff put it into the offer and submit it through your own process. Nothing is sent or submitted by the system.

Does this replace our document system?

No. It reads your data sheets, certificates and terms where they already sit. Your document system stays the record.

How do I know a comply is true?

Every line shows the page of the tender and the page of your own file it relies on. If there is no evidence in your files, the line is marked for a person instead of comply.

Related

Turn an RFQ into a quotation

Reads an RFQ and its attachments, matches each line to your catalogue, prices it from your own price list and drafts the quotation. Your team approves it.

Raise pre-bid queries and track corrigenda

Drafts pre-bid queries in the buyer's format before the cut-off and tracks replies, corrigenda and addenda against your offer. Your bid owner approves each one.

Check the bid before it goes

Checks every mandatory document, certificate, declaration, EMD and signature against the tender before you submit, and names each gap. Your signatory approves.

All use cases

Talk to us

Tell us about one job your team still does by hand.

Email us

Or write to anirudh@generalinference.co