[{"data":1,"prerenderedAt":259},["ShallowReactive",2],{"\u002Fblog\u002Fcalibration-register-just-a-spreadsheet-validation":3},{"id":4,"title":5,"author":6,"body":7,"category":240,"date":241,"description":242,"draft":243,"excerpt":244,"extension":245,"heroImage":244,"heroImageAlt":244,"meta":246,"navigation":247,"path":248,"seo":249,"slug":244,"stem":250,"tags":251,"__hash__":258},"blog\u002Fblog\u002Fcalibration-register-just-a-spreadsheet-validation.md","My Calibration Register Is Just a Spreadsheet. Does It Really Need Validation?","QikSolve",{"type":8,"value":9,"toc":230},"minimark",[10,14,17,20,25,28,50,64,68,71,97,100,104,107,138,142,145,177,181,184,198,206,210,223],[11,12,13],"p",{},"\"It's just a spreadsheet\" is one of the most common phrases heard when discussing calibration\nregisters in GMP facilities. Usually it is true, in the sense that the file does not calculate\nanything or make a GMP decision. It simply records what has already happened.",[11,15,16],{},"That does not mean the register is automatically outside the scope of validation thinking. It\nmeans the validation approach can be proportionate to what the spreadsheet actually does.",[11,18,19],{},"This article is a practical interpretation of a common register scenario. It is not a validation\nprotocol or a determination that any specific spreadsheet is compliant. Your organisation's own\nrisk assessment, quality system, and the applicable regulatory expectations remain the controlling\nreferences.",[21,22,24],"h2",{"id":23},"the-scenario","The scenario",[11,26,27],{},"A typical calibration register spreadsheet contains:",[29,30,31,35,38,41,44,47],"ul",{},[32,33,34],"li",{},"Equipment ID",[32,36,37],{},"Last calibration date",[32,39,40],{},"Next due date",[32,42,43],{},"Certificate reference",[32,45,46],{},"Equipment location",[32,48,49],{},"Comments",[11,51,52,53,58,59,63],{},"There are no GMP calculations. There is no decision-making logic. The spreadsheet is a structured\nlist, what we describe in our\n",[54,55,57],"a",{"href":56},"\u002Fblog\u002Fhidden-validation-cost-of-excel-registers-in-gmp","maturity model for GMP spreadsheets"," as a\n",[60,61,62],"strong",{},"register spreadsheet",", the first and lowest-risk level.",[21,65,67],{"id":66},"what-inspectors-tend-to-focus-on","What inspectors tend to focus on",[11,69,70],{},"Regardless of whether a register is a spreadsheet or a formal system, the underlying data\nintegrity expectations are the same. An inspector reviewing a calibration register is typically\ninterested in:",[29,72,73,79,85,91],{},[32,74,75,78],{},[60,76,77],{},"Data integrity."," Can the organisation show the record has not been altered inappropriately?",[32,80,81,84],{},[60,82,83],{},"Accuracy."," Do the dates and references in the register match the underlying certificates?",[32,86,87,90],{},[60,88,89],{},"Traceability."," Can a specific piece of equipment be traced to its calibration history and\nsupporting certificate?",[32,92,93,96],{},[60,94,95],{},"Evidence."," Is there something to show, beyond \"we've always done it this way,\" that the\nregister is maintained and reviewed?",[11,98,99],{},"None of these questions require the register to have been through a full software validation\nlifecycle. They do require the organisation to be able to answer them with more than an assumption.",[21,101,103],{"id":102},"common-risks-in-a-register-like-this","Common risks in a register like this",[11,105,106],{},"Even a simple register carries recognisable risks:",[29,108,109,115,121,132],{},[32,110,111,114],{},[60,112,113],{},"Manual transcription errors",", where a date or reference is typed incorrectly when copying from\na certificate.",[32,116,117,120],{},[60,118,119],{},"Missing calibration certificates",", where the register shows a date but the supporting document\ncannot be located.",[32,122,123,126,127,131],{},[60,124,125],{},"Formula corruption",", if a due-date calculation (",[128,129,130],"code",{},"= [Last calibration date] + 365",", for example)\nis accidentally overwritten in a cell.",[32,133,134,137],{},[60,135,136],{},"Poor version control",", with several copies of the register circulating across email or shared\ndrives, each slightly out of date.",[21,139,141],{"id":140},"what-validation-evidence-may-be-needed","What validation evidence may be needed",[11,143,144],{},"For a register at this level, a pragmatic, risk-based approach is usually more appropriate than a\nfull software validation lifecycle. Evidence that is commonly useful includes:",[29,146,147,153,159,165,171],{},[32,148,149,152],{},[60,150,151],{},"Intended use",": a short statement of what the register is used for, and what it is not used\nfor (for example, it does not calculate pass\u002Ffail status).",[32,154,155,158],{},[60,156,157],{},"Risk assessment",": an assessment of what could go wrong (missing certificate, wrong date,\noverwritten formula) and how likely and significant that is.",[32,160,161,164],{},[60,162,163],{},"Formula verification",": where any calculation exists (even a simple due-date formula), a check\nthat it produces the expected result.",[32,166,167,170],{},[60,168,169],{},"Change control",": a record of how the register's structure, formulas, or fields are changed and\nby whom.",[32,172,173,176],{},[60,174,175],{},"Validation report or summary",": a short document that ties the above together and states the\nregister is fit for its intended use.",[21,178,180],{"id":179},"when-excel-may-still-be-acceptable","When Excel may still be acceptable",[11,182,183],{},"Excel is not automatically the wrong tool for a register like this. Where the register:",[29,185,186,189,192,195],{},[32,187,188],{},"only records dates, references, and status information;",[32,190,191],{},"has no formulas that determine equipment fitness for use or product disposition;",[32,193,194],{},"has a small number of controlled editors; and",[32,196,197],{},"is backed by a defined review and certificate-filing process,",[11,199,200,201,205],{},"a lightweight, proportionate validation approach can often be justified without moving to a new\nplatform. The risk changes materially once the spreadsheet starts calculating anything the\norganisation relies on to make a GMP decision. That scenario is covered in\n",[54,202,204],{"href":203},"\u002Fblog\u002Fwhen-your-spreadsheet-starts-making-gmp-decisions","When Your Spreadsheet Starts Making GMP Decisions",".",[21,207,209],{"id":208},"a-proportionate-next-step","A proportionate next step",[11,211,212,213,217,218,222],{},"Not sure whether your calibration register requires formal validation, or what level of evidence is\nenough? A structured ",[54,214,216],{"href":215},"\u002Fvalidate-quality-register","Annex 11 spreadsheet assessment"," can classify the\nrisk and recommend whether the register should be retained with light-touch controls, remediated\nwith formal evidence, or migrated to a governed SharePoint register. See\n",[54,219,221],{"href":220},"\u002Fblog\u002Fannex-11-in-plain-english","Annex 11 in Plain English"," for the underlying computerised-systems\nquestions this assessment draws on.",[11,224,225,229],{},[54,226,228],{"href":227},"\u002Fcontact","Book a discovery call"," to talk through your calibration register and the evidence you\nmay already have.",{"title":231,"searchDepth":232,"depth":232,"links":233},"",2,[234,235,236,237,238,239],{"id":23,"depth":232,"text":24},{"id":66,"depth":232,"text":67},{"id":102,"depth":232,"text":103},{"id":140,"depth":232,"text":141},{"id":179,"depth":232,"text":180},{"id":208,"depth":232,"text":209},"Compliance","2026-09-14","A calibration register that only tracks equipment IDs, dates, and certificate references is a different risk to a spreadsheet that calculates pass or fail. A practical, risk-based look at what validation it may actually need.",false,null,"md",{},true,"\u002Fblog\u002Fcalibration-register-just-a-spreadsheet-validation",{"title":5,"description":242},"blog\u002Fcalibration-register-just-a-spreadsheet-validation",[252,253,254,255,256,257],"calibration","excel","annex-11","validation","gmp","spreadsheets","SNW155ZKlBQMEWngyY8AjmmyJweg5L5lX6B3QOqyMuo",1789388497130]