Codes referenced
Defines what constitutes admissible expert opinion in Indian courts.
Procedure for commissioning an expert opinion in civil cases.
Code basis for durability/cracking opinions.
NDT basis for in-place strength assessment.
Why defensibility matters
A technical opinion can be challenged in arbitration, court, or RERA. A weak opinion destroys credibility. A wrong opinion invites civil liability (compensation for losses caused) and, in extreme cases, criminal liability (Sections 191-193 IPC — false evidence). The defensibility test: another competent engineer, reading only the opinion, must be able to independently reach the same conclusion from the evidence cited.
7-section opinion structure
- Issue / opinion requested — the precise question. "Whether the M30 concrete supplied meets IS 456 Table 11 acceptance."
- Documents reviewed — every document relied upon, with date and source.
- Site inspections & tests — when, where, who attended, what was observed, test results.
- Code references applied — exact IS clause + version cited.
- Opinion with reasoning — the answer, with the logical chain from evidence to conclusion.
- Limitations — what the opinion does NOT cover.
- Conclusion & signature — signed statement of truth, post-nominals, date.
The 4 opinion categories
Whether work meets IS code requirements. Most common opinion type.
What caused the observed defect (cracking, low strength, leakage).
Whether the proposed/ executed repair is adequate for the defect.
Whether the structure is safe for continued use / occupation.
Burden of proof — 6 W's
Every opinion must address: WHAT (the specific issue), WHERE (location), WHEN (date of observation), WHY (causation based on evidence), by WHOM (the consultant's qualifications), with WHAT EVIDENCE (documents, photos, test results). Missing any of the six weakens the opinion.
Opinion vs testimony
A technical opinion is voluntary, written, and the consultant controls the content. Testimony is given under oath in court or arbitration — the consultant answers questions, often hostile ones, and is cross-examined. An opinion you write is what you stand behind. Testimony you give must align with your written opinion or your credibility is destroyed.
Worked example — opinion on low-strength cubes
| Section | Content excerpt |
|---|---|
| 1. Issue | Whether M30 concrete at Floor 5, Column C-7 complies with IS 456 Table 11 acceptance. |
| 2. Documents | Mix design MD-2026-M30; 12 cube test reports; delivery tickets; SVRs dated 2026-08-10 to 2026-08-15 |
| 3. Inspections & tests | Site visit 2026-08-15; observed cube storage in tank at 26°C; 3 cores extracted per IS 516 |
| 4. Codes | IS 456 Cl 16.1, Table 11; IS 516 Cl 7 (core testing); IS 13311 Pt 1 (UPV); IS 13311 Pt 2 (rebound) |
| 5. Opinion | Sample fails acceptance: mean 22.1 MPa < the Table 11 group-of-four mean requirement of 34 N/mm² (fck + 4 for M30). Core test results 24, 26, 25 MPa confirm in-place strength marginally adequate for the column loading |
| 6. Limitations | No structural re-analysis performed; column reinforcement as-built not verified; long-term durability not assessed |
| 7. Signature | A. Haridas, FIE, Chartered Engineer (India); Reg No IEI/M/12345 |
Common deviations seen on Indian sites
An opinion that does not include a site visit is hearsay. The consultant has not seen the condition and cannot testify to it. Always include Section 3.
"I think the structure will fail in 5 years" is speculation, not opinion. Stick to what the evidence supports. Speculation invites liability.
An opinion without code references is just personal opinion. The value of an opinion is the link from observed fact to IS requirement.
Every opinion has limits — what was not inspected, what was not tested, what is outside the consultant's competence. Stating limitations protects against claims of overreach.
Field-checklist blocks
A short questionnaire, an inspector's checklist, and three worked examples that show how the 7-section structure resolves into a conclusion another engineer can defend.
Questionnaire — asked before the opinion is signed and released
- Is the issue stated precisely, as a question that can be answered? Section 1, for example: whether the M30 concrete at Floor 5, Column C-7 complies with IS 456 Table 11 acceptance. Not "condition of the column".
- Does Section 3 record a site inspection? When, where, who attended, what was observed, and the test results. An opinion that does not include a site visit is hearsay: the consultant has not seen the condition and cannot testify to it.
- Are all the documents relied on listed with their date and source? Mix design MD-2026-M30, 12 cube test reports, delivery tickets, and the SVRs dated 2026-08-10 to 2026-08-15. Anything not listed is something the other side will say you never had.
- Does Section 4 cite the exact clause and version for every conclusion? IS 456 Cl 16.1 and Table 11, IS 516 Cl 7, IS 13311 Pt 1 (UPV) and Pt 2 (rebound). An opinion without code references is just personal opinion.
- Can another competent engineer reach the same conclusion from what you cite? That is the defensibility test: fact, clause, conclusion, with the arithmetic visible. The sample opinion shows 22.1 MPa against the fck − 3 floor of 27 MPa, a gap of 4.9 MPa.
- Are all six W's present? What, where, when, why, by whom, with what evidence. Missing any one of the six weakens the opinion, and it is easy to miss them when you are close to the problem.
- Does Section 6 state the limitations? What was not inspected, what was not tested, what sits outside your competence. Stating limitations protects against claims of overreach, and every opinion has limits.
- Is this one of the four opinion categories, and is Section 7 complete? Code compliance, defect causation, repair adequacy or structural safety. Then the conclusion, the signature, the statement of truth, the post-nominals, the registration number and the date.
Inspector's checklist — what to verify on site
- Section 1: the issue, phrased precisely enough that a yes or no is possible.
- Section 2: every document relied on, with date and source, and nothing listed that was not actually reviewed.
- Section 3: site inspections and tests, with the observations recorded rather than summarised. On the sample, the site visit on 2026-08-15, cube storage observed in the tank at 26 °C, and 3 cores extracted per IS 516.
- Section 4: the code references applied, exact clause and version, tied to the point each one supports.
- Section 5: the opinion with its reasoning, the logical chain from evidence to conclusion, and the numbers worked. For the sample, the cube average of 22.1 MPa against the 27 MPa floor, and cores at 24, 26 and 25 MPa, a mean of 25.0 MPa with a 2 MPa spread.
- Section 6: limitations, and nothing vague in them. No structural re-analysis performed, column reinforcement as-built not verified, long-term durability not assessed.
- Section 7: conclusion and signature, with the statement of truth, the post-nominals (FIE, Chartered Engineer), the registration number and the date.
- Defensibility checks before release: the six W's complete, the opinion category named, no speculation beyond the observed evidence, typically 5 to 15 pages including attachments, and any retraction written, signed, distributed to all original recipients, with both versions retained.
What happens if… three worked examples
What happens. The consultant has 12 cube test reports, a mix design and delivery tickets, and writes a conclusion without going to the structure. It is hearsay: the condition was never observed, so it cannot be testified to. Under the Indian Evidence Act §§45-51 the opinion has no observational basis to stand on, and the missing Section 3 is the first thing the other side finds. Then there is the cross-examination problem: testimony given in arbitration has to align with the written opinion, or the credibility is gone in a single session.
Likely outcome. The opinion is rebuilt before issue, with Section 3 filled in: the site visit on 2026-08-15, cube storage observed in the tank at 26 °C, and 3 cores extracted per IS 516. That is the difference between an opinion and an assertion, and it is the one section that cannot be written from the office.
What happens. That is speculation, not opinion, and speculation invites liability. So does the other failure mode: dropping the clause references and leaving the reader with a personal view rather than an engineering conclusion. The evidence here says something narrower and much stronger. The average 28-day strength of 22.1 MPa sits 4.9 MPa below the fck − 3 floor of 27 MPa in IS 456 Table 11, so the sample fails acceptance.
Likely outcome. The conclusion stays with what the evidence supports and the recommendation is the next test rather than a prediction: core testing per IS 516 and in-situ NDT assessment per IS 13311 Pt 1 and Pt 2. The cores come back at 24, 26 and 25 MPa, a mean of 25.0 MPa, and the opinion is that the in-place strength is marginally adequate for the column loading. Section 6 then carries the limits: no structural re-analysis performed, column reinforcement as-built not verified, long-term durability not assessed.
What happens. With no limitations section, every gap in the investigation becomes a claim of overreach. What was not inspected, what was not tested, what lies outside the consultant's competence, all of it sits there waiting. And when something later needs correcting, a retraction that is not written, signed and disclosed to every original recipient exposes the consultant to allegations of misleading conduct.
Likely outcome. Section 6 states the limits, Section 7 carries the signature, the statement of truth, the post-nominals, the registration number and the date. If a correction is needed later it goes out in writing, signed, to all original recipients; the corrected opinion supersedes the original and both are retained. That sequence costs a paragraph. Leaving the limitations out costs the opinion.
Frequently Asked Questions
Can a technical opinion be retracted after issue?
How detailed should a technical opinion be?
Who can give an expert opinion under Indian law?
Related articles
Amit Haridas
Founder & Proprietor, ConcreteInfo. 25+ years experience in construction QA/QC, concrete technology, RMC plant operations, consulting and technical training across India. For engagement-letter templates or consulting engagement setup, contact amit@concreteinfo.in.
Technical updates, not sales emails
One email when a new article goes out on concrete technology, QA/QC and construction quality. No promotions, and your address is never sold or passed to advertising networks. Subscribing is separate from making an enquiry.