Desrochers Validation, Félix Desrochers Back to the offer

What I don't do, and where to check everything I claim

This page exists because I am asking you to send an internal file to a stranger. The only sensible response to that is suspicion, so here is the boundary of what I deliver, every source behind every claim on the other page, the free tools to do this work yourself, and who else does it.

Nothing here is a sales page. If you leave and go to ISOBudgets or download the NIST form and do it yourself, that is a fine outcome, and section 4 is written to make it possible.

1. The full checklist, all 47 checks

The record I produce is built around the NIST Office of Weights and Measures Software Verification and Validation form, published as GLP 15 (2019), Appendix A, free from NIST. Download it and hold it next to my sample. It is a federal document, not something I invented, and it is how you can judge my work without taking my word for anything.

It has 47 checks. Of those, 30 I answer from the file itself, 6 I gather the evidence for and leave the judgment to you, and 11 only you can answer. How many come back answered depends on the workbook: some checks will not apply to your file at all, and two need things I ask for separately, namely last year's version of the same workbook and your accredited scope.

Every one of the 47 appears in the record, including the ones I cannot answer. A checklist with the awkward rows quietly removed is worth nothing.

A. Software Inspection

CheckWhat it asksWho answers it
A1Spreadsheet is clear and makes senseI gather the evidence, you judge it
A2There are instructions for useI answer it from the file
A3Instructions and data input appear on the visible portion of the first worksheetI answer it from the file
A4Data-entry fields are labeled and color coded (avoiding red and green)I answer it from the file
A5The Standard Operating Procedure used is clearly specifiedI answer it from the file
A6The number of digits to be rounded to is specifiedI answer it from the file
A7The user is warned whenever data-entry fields are left blankI answer it from the file
A8Data-entry fields are blank when opened, so old data is not reusedI answer it from the file
A9The software opens at the right location within the fileI answer it from the file
A10Unused fields/cells are lockedI answer it from the file
A11Rows/columns the operator need not see are hiddenI gather the evidence, you judge it
A12Unused sheets are removedI answer it from the file
A13Worksheets are named appropriatelyI answer it from the file

B. Mathematical Specification

CheckWhat it asksWho answers it
B1The correct SOP is usedOnly you can answer it
B2The formulae and methods chosen from that SOP are specifiedI answer it from the file
B3Sources and references for formulae are specifiedI answer it from the file
B4The SOP, its methods and formulae are appropriate to the level of precisionOnly you can answer it

C. Code Review

CheckWhat it asksWho answers it
C1The formulae in the fields exactly match the procedureOnly you can answer it
C2Repeated calculations appropriately reference the correct cellsI answer it from the file
C3Calculations, tested with reference data, show appropriate accuracyI answer it from the file
C4Rounding is done at the appropriate locations in the fileI answer it from the file

D. Numerical Stability

CheckWhat it asksWho answers it
D1Calculations are stable with large numbers and small differencesI answer it from the file
D2Fields are categorized as Number and not General when appropriateI answer it from the file
D3Number cells are locked to an appropriate number of decimal placesI answer it from the file

E. Component Testing

CheckWhat it asksWho answers it
E1Conditional logic cells handle negative values properlyI answer it from the file
E2Conditional logic cells withstand a boundary value testI answer it from the file
E3Each macro used is functionalOnly you can answer it
E4Each command/button is functionalOnly you can answer it
E5Combinations of interdependent macros are functionalOnly you can answer it
E6Plotted graphs are accurateI gather the evidence, you judge it
E7Plotted graphs and their axes are properly labeledI answer it from the file
E8Worksheets/reports print properly, if needed toI answer it from the file
E9Conditional (color and non-color) formatting is functionalI gather the evidence, you judge it

F. Numerical Reference Results

CheckWhat it asksWho answers it
F1Look-up tables and lists match the latest calibration reportOnly you can answer it
F2Uncertainties match the latest ScopeI answer it from the file
F3Values that reference another workbook are datedI answer it from the file
F4Behaviour is as intended when a master list's date is updatedI gather the evidence, you judge it

G. Embedded Data Evaluation

CheckWhat it asksWho answers it
G1Embedded data (conversion factors, reference values) is correctI gather the evidence, you judge it
G2The evaluation of the embedded data is dated and documentedI answer it from the file

H. Back-to-Back Testing

CheckWhat it asksWho answers it
H1Newer and older spreadsheets agree down to intermediate calculations, datedI answer it from the file

I. Analysis Without Computer Assistance

CheckWhat it asksWho answers it
I1Hand calculations agree with the spreadsheet, or differ insignificantlyI answer it from the file

J. Security

CheckWhat it asksWho answers it
J1Equation and calculation cells are protected against inadvertent editingI answer it from the file
J2Cells are locked in place and cannot be moved or draggedI answer it from the file
J3Confidentiality of passwords is appropriateOnly you can answer it
J4Files are backed up automaticallyOnly you can answer it
J5Additional back-up is available at alternate facilitiesOnly you can answer it
J6Files on network drives cannot be accidentally deletedOnly you can answer it

2. What I do not do, and what that means for you

Read this column on the right rather than the one on the left. A list of things I refuse is only useful if it tells you what you are still on the hook for.

I do notWhich means
Decide which contributors your measurement needs I check your budget against the contributors ILAC P14 5.4 expects, which are repeatability, resolution, reference standard, drift and environment, and I report which are absent. Whether an absent one genuinely does not apply to your measurement is metrology judgment, and it stays with you. I show gaps. I do not decide which of them matter.
Answer 11 of the 47 checks Your record arrives with blanks in it: backups, password handling, macro behaviour, whether the correct procedure was chosen. It is not a finished document until you complete those. I leave them visible rather than filling them in, because no examination of a file can answer them.
Test macros, buttons, or printed output GLP 15 section E leaves those to the laboratory and so do I. I detect that macros are present; I do not run them or judge whether they work.
Know what your workbook was meant to do Section 3 of the record is a requirements specification I reverse-derived from the file, because almost no lab has one written down. If it misstates your intent, every test below it is measuring against the wrong specification. Reading that section is the one step you cannot delegate to me, and it is the single most important thing on this page.
Read legacy .xls files The formula layer of that format cannot be read reliably. Open it in Excel, Save As .xlsx, and nothing in the file changes. Ten seconds.
Validate your LIMS Waters, LabWare and LabLynx do that and they are good at it. I work on the side workbooks that feed it, which is a different problem.
Work under 21 CFR Part 11 or pharma CSV Different regulator, different liability, much heavier documentation. If that is your world, see section 5.
Certify, attest, approve, or accredit anything No body accredits validation providers. Not A2LA, not anyone. If a vendor implies otherwise, that alone should worry you. Your technical manager's signature is what gives the record standing, not mine.
Predict what your assessor will conclude I do not control your assessor, and anyone selling "guaranteed to pass" is selling something they cannot deliver.
Give an opinion on results you already issued I validate software. I do not bless data that has already left the building. If I find something that affects released results, I tell you and nobody else, and what you do about it is entirely your decision.
Have a track record No record I have produced has been through an accreditation assessment yet. I started in 2026. Being able to complete a NIST form is not the same as your assessor accepting it, and I have no evidence about the second thing. That is the honest reason the first file is free.

3. Where every claim comes from

The rule I work to is that I never state a fact I have not read the source for, and that I say which sources are primary and which are not.

ClaimSourceKind
Uncertainty must be evaluated for each measurement function ISO/IEC 17025:2017 clause 7.6. The standard is not free to redistribute, so I describe what it requires in my own words rather than quoting its text. The method I actually test against is the GUM, below, which is free and public. Paid standard
How an uncertainty budget is built and combined JCGM 100:2008, the GUM, free from BIPM. This is the method every budget implements and what I test against.Primary, free
Expanded uncertainty to at most two significant figures; coverage factor and coverage probability both stated ILAC P14, free. A2LA's R205 defers to it.Primary, free
A per-file software validation form exists and is expected NIST GLP 15, and NIST IR 8250.Primary, free
Uncertainty budgets missing required components rank second among cited A2LA deficiencies Heather Wade Group, corroborated by In Compliance Magazine. These are two secondary sources, not A2LA's own publication. I have not been able to verify the ranking against A2LA directly, and I would rather you knew that than took the number at face value.Secondary
ISO 17025 consulting commonly runs $100 to $250 an hour Published industry summary. A range, not a quote, and not a claim about any particular consultant.Secondary
Your accreditation scope and the range in my first email Your own certificate in the A2LA public directory, with the date I retrieved it recorded.Primary, free

4. How to do all of this yourself, for nothing

Every tool needed to do this work is free, and most labs simply do not have the hours. If you do have them, here is the path, in order.

  1. Download the form. NIST GLP 15. Appendix A is the checklist. That is the deliverable.
  2. Download the GUM. JCGM 100:2008. Sections 4.2 to 4.3 cover Type A and Type B evaluation, 5.1.2 the combination rule, 6.2 coverage factors. Those four sections are most of what matters.
  3. Read ILAC P14 sections 5 and 6 for the reporting rules, including the two-significant-figure limit that a lot of budgets quietly break.
  4. Take the NIST training. NIST OWM runs Software Verification and Validation, Parts I and II, aimed at exactly this work, with a laboratory spreadsheet as the coursework.
  5. Use NIST's own templates and NIST Technical Note 1297 for worked uncertainty guidance.
  6. Mine A2LA's free guidance at a2la.qualtraxcloud.com for what assessors are told to look for.

The honest catch: doing one file properly this way is most of a day the first time, and you have more than one file. That gap is the only reason I have a business, and I would rather say so than pretend the free path does not exist.

5. Who else does this, and when you should use them instead

Prices below were checked in July 2026 and will drift. Verify before you buy anything on my say-so.

ISOBudgets

Go to them, not me, if you do not have an uncertainty budget yet. They build budgets; I document and verify budgets you already have. Different product, same reader. They sell uncertainty calculators from $19 to $49, instrument-specific budget templates for particular calibrators and multimeters at $1,500 to $2,500, and a training bundle at $197. Consulting is quote-based with no public price. They say they have worked with more than 3,000 laboratories since 2011. isobudgets.com. Their blog is fifteen years of free writing aimed squarely at you and is worth reading whether or not you ever buy anything.

The 17025 Store, now trading as Uncera

Sells an Equipment Uncertainty Calculation Excel sheet at $49, reduced from $99, with a step by step guide. A template to build with, not a validation of what you have. uncera.com.

Pharma and 21 CFR Part 11 specialists

If you are FDA-regulated, I am the wrong supplier and you should not hire me. Ofni Systems sells ExcelSafe, which adds audit trails and electronic signatures to Excel, and does validation packages around it. That world is far heavier and considerably more expensive than anything on my price list, and correctly so, because the regulator is different. ofnisystems.com.

A general ISO 17025 consultant

Commonly $100 to $250 an hour. More expensive than me and much broader: a good one will make the metrology judgments I explicitly refuse to make, write your quality manual, and sit with you through an assessment. If what you actually need is someone to decide what belongs in your budget, hire one of them.

LIMS validation vendors

Waters, LabWare and LabLynx validate the central system. That is a real and different job. Nobody in that market is interested in the thirty side workbooks that feed it, which is the entire reason I exist.

Doing nothing

Sometimes the right answer. If your scope has three CMC lines, you have three budgets, and this is not a spreadsheet problem. The labs this helps are the ones with more calculation files than anyone can remember building.

6. What happens to your file

That last point deserves saying plainly, because it cuts against me: asking you to look inside a workbook is asking you to find out whether you have a problem. Some labs would rather not know. I would rather write that down here than discover you were worried about it after you had already decided not to reply.