[{"data":1,"prerenderedAt":514},["ShallowReactive",2],{"\u002Fblog\u002Fexcel-register-intended-use-and-ownership":3},{"id":4,"title":5,"author":6,"body":7,"category":494,"date":495,"description":496,"draft":497,"excerpt":498,"extension":499,"heroImage":500,"heroImageAlt":501,"meta":502,"navigation":503,"path":504,"seo":505,"seoTitle":498,"slug":498,"stem":506,"tags":507,"__hash__":513},"blog\u002Fblog\u002Fexcel-register-intended-use-and-ownership.md","How to Define Intended Use of a Computerised System","QikSolve",{"type":8,"value":9,"toc":478},"minimark",[10,14,17,26,31,34,37,40,56,59,63,66,69,72,80,84,87,97,105,114,117,121,145,149,152,204,208,211,222,227,233,236,240,243,369,372,376,379,435,438,442,445,448,451,455,463,475],[11,12,13],"p",{},"To define the intended use of a computerised system, describe the process it supports, who uses\nit, the information it handles and the decisions people may rely on it to support. State its\nboundaries, including what it must not decide, which records are authoritative and who owns\nits use and controls. Write this before selecting features or planning verification.",[11,15,16],{},"This guide provides a reusable statement template and a fictional Excel quality register\nexample. It is an assessment aid for quality-system work, not a complete Annex 11 guide,\nvalidation protocol or compliance determination.",[11,18,19,20,25],{},"This is a practical follow-on to\n",[21,22,24],"a",{"href":23},"\u002Fblog\u002Fannex-11-in-plain-english","Annex 11 in Plain English",": that article explains the broader\ncomputerised-system control themes; this guide focuses on defining what a system is for and\nturning that purpose into a statement your team can review.",[27,28,30],"h2",{"id":29},"what-belongs-in-an-intended-use-statement","What belongs in an intended-use statement?",[11,32,33],{},"An intended-use statement describes the system's purpose and permitted reliance in a named\nprocess. \"We use Excel\" names a tool; \"we track deviations and report overdue actions, but do\nnot approve closure\" describes a use and its boundary.",[11,35,36],{},"Start with the process owner and people who perform the work. Gather the current procedure,\nsystem or configuration description, representative records and reports, and known interfaces.\nFor a proposed system, distinguish planned use from how the current process actually operates.",[11,38,39],{},"Capture these elements:",[41,42,43,47,50,53],"ul",{},[44,45,46],"li",{},"The named process, system scope and user groups.",[44,48,49],{},"Inputs, activities, outputs and interfaces.",[44,51,52],{},"Decisions supported, authoritative records and explicit exclusions.",[44,54,55],{},"Accountable owners, discrepancy handling and review triggers.",[11,57,58],{},"Use the statement to develop detailed requirements and acceptance checks; do not treat a short\nparagraph as a replacement for them or for executed validation evidence.",[27,60,62],{"id":61},"start-with-the-process-not-the-platform","Start with the process, not the platform",[11,64,65],{},"A register can begin as a list of identifiers and dates, then become part of how a team monitors\nopen work, escalates delays or reports quality trends. That reliance matters even when the\nregister does not contain the full investigation or its approvals.",[11,67,68],{},"In this example, the register identifies deviations, tracks status and supports workload\noversight. The controlled deviation record remains the source for the investigation, its\nconclusions and authorised closure. The register does not approve an investigation, release a\nbatch or independently decide that a quality event is complete.",[11,70,71],{},"That boundary is not a claim that the register has no quality impact. Missing or misleading\nmetadata could still affect oversight. The organisation must assess how people actually use the\ninformation, including reports, copied data and manual hand-offs.",[11,73,74,75,79],{},"The ",[21,76,78],{"href":77},"\u002Fblog\u002Fbeyond-excel-gxp-quality-registers-sharepoint-lists","quality-register overview","\nexplains the register\u002Frecord distinction; this article adds a copyable intended-use statement\nand ownership challenge.",[27,81,83],{"id":82},"define-applicability-before-naming-requirements","Define applicability before naming requirements",[11,85,86],{},"Regulatory applicability depends on the organisation, product, activity, jurisdiction and actual\nuse of the system. Do not treat every spreadsheet or SharePoint List called a “Good Manufacturing\nPractice (GMP) register” as automatically subject to the same requirements.",[11,88,89,90,96],{},"At the 29 October 2026 source check, the ",[21,91,95],{"href":92,"rel":93},"https:\u002F\u002Fwww.tga.gov.au\u002Fproducts\u002Fmedicines\u002Fmanufacturing\u002Fmanufacture-medicine\u002Fgood-manufacturing-practice-gmp\u002Fcomplying-pics-guide-good-manufacturing-practice-medicinal-products",[94],"nofollow","TGA's GMP guidance","\nstates that the current manufacturing principles specify PIC\u002FS Guide PE 009-17, dated\n25 August 2023, with Annexes 4, 5 and 14 not adopted in Australia. Check the TGA's linked\nguidance and current instrument for applicability and transition conditions before applying a\nclause to a system. This is not an applicability decision for a particular site, product or\nregister.",[11,98,74,99,104],{},[21,100,103],{"href":101,"rel":102},"https:\u002F\u002Fhealth.ec.europa.eu\u002Fconsultations\u002Fstakeholders-consultation-eudralex-volume-4-good-manufacturing-practice-guidelines-chapter-4-annex_en",[94],"European Commission's Annex 11 consultation page","\nidentifies revised Chapter 4 and Annex 11 material as consultation drafts. A proposal is not\nautomatically an effective Australian requirement. This example does not use draft text to set\ncurrent obligations.",[11,106,107,108,113],{},"For further reading alongside the worked example, see the\n",[21,109,112],{"href":110,"rel":111},"https:\u002F\u002Fwww.pharmout.net\u002Fwp-content\u002Fuploads\u002F2026\u002F03\u002FSion-Wyn-GxP-Annex-11-Annex-22-Regulations-Plenary-Pharma-Device-Forum-March2026.pdf",[94],"PharmOut-hosted presentation on Annex 11 and Annex 22 (PDF)",".\nTreat this as supplementary presentation material, not the adopted regulatory text or evidence\nthat a proposed revision applies to an Australian site.",[11,115,116],{},"Use the edition adopted for the relevant jurisdiction, not the newest publication or a\nconsultation proposal by default. Cite an Annex 11 locator only after checking it against the\napplicable official text. Where that verification is missing, leave the obligation unresolved\nrather than filling the gap with an assumption.",[27,118,120],{"id":119},"how-to-define-intended-use-seven-steps","How to define intended use: seven steps",[122,123,124,127,130,133,136,139,142],"ol",{},[44,125,126],{},"Name the process, system boundary and user groups; inventory inputs, outputs, reports and\ninterfaces.",[44,128,129],{},"Trace how important information is created, changed, linked to source records and used.",[44,131,132],{},"State the decisions and permitted reliance, including what the system must not decide.",[44,134,135],{},"Assign accountable roles for process definitions, system control, quality oversight and\nplatform support.",[44,137,138],{},"Draft the intended-use statement and challenge it with missing information, conflicting\nrecords and unavailable-service cases.",[44,140,141],{},"Compare the current or proposed configuration against the defined use; turn gaps into\nrequirements, acceptance checks and decisions about whether to retain or change the system.",[44,143,144],{},"Obtain the approvals required by the organisation's procedures, record residual risks and\nrevisit the statement when the process or reliance changes.",[27,146,148],{"id":147},"map-the-information-and-decisions-a-quality-register-example","Map the information and decisions: a quality register example",[11,150,151],{},"Trace important data from entry through reports, email hand-offs and decisions to its source\nrecord. Include copies, integrations, connectors and service identities: establish what each can\nread or change, who controls it and which write paths need verification. A column inventory alone\nwill not show how a decision relies on the information.",[153,154,155,168],"table",{},[156,157,158],"thead",{},[159,160,161,165],"tr",{},[162,163,164],"th",{},"Question",[162,166,167],{},"Example boundary to test",[169,170,171,180,188,196],"tbody",{},[159,172,173,177],{},[174,175,176],"td",{},"What does the register identify?",[174,178,179],{},"A deviation ID, owner, dates, status and reference to its controlled record",[159,181,182,185],{},[174,183,184],{},"Which record is authoritative?",[174,186,187],{},"The controlled deviation record holds the investigation and authorised closure",[159,189,190,193],{},[174,191,192],{},"What may a user rely on the register for?",[174,194,195],{},"Tracking and oversight in this example; not approval or batch release",[159,197,198,201],{},[174,199,200],{},"What can change that use?",[174,202,203],{},"A new automated decision, approval, signature or replacement of the source record",[27,205,207],{"id":206},"intended-use-statement-template","Intended-use statement template",[11,209,210],{},"Use the answers to write a short statement. Keep it specific enough that a new user can tell\nwhat the system does, which decisions it supports and when to seek an authoritative record.\nAdapt the prompts to the system rather than assuming every system is a register.",[212,213,219],"pre",{"className":214,"code":216,"language":217,"meta":218},[215],"language-text","Intended use:\nThe [system name and configuration\u002Fscope] supports [named process].\nIt is used by [user groups] to [activities] using [inputs and interfaces].\nIt produces [outputs\u002Frecords] to support [named decisions].\nThe authoritative record for [investigation, approval or other controlled detail] is [record].\nUsers may rely on the system for [bounded uses], but not for [explicit exclusions].\nWhen information conflicts with its source or the system is unavailable,\n[role] initiates [reconciliation or continuity procedure].\nThe Process Owner reviews [scope, definitions and fit] when [triggers] occur.\n","text","",[220,221,216],"code",{"__ignoreMap":218},[223,224,226],"h3",{"id":225},"worked-statement-an-excel-deviation-register","Worked statement: an Excel deviation register",[228,229,230],"blockquote",{},[11,231,232],{},"The Example Quality Team uses its Excel deviation register to identify deviation records,\ntrack assigned owners and dates, and support oversight of open work. Assigned editors enter\nidentifiers and status information from controlled deviation records; Quality reviewers use\nthe register's open-item and overdue reports. The controlled deviation record remains\nauthoritative for the investigation, its conclusions and authorised closure. The register does\nnot approve closure or release a batch. A mismatch between the register and its referenced\nrecord is recorded for reconciliation before the register is used to report that event as\nclosed. If the register is unavailable, the Process Owner follows the team's documented\ncontinuity procedure. The Process Owner reviews this scope when reporting, interfaces or\ndecision-making responsibilities change.",[11,234,235],{},"This is a fictional example, not an approved organisational statement. Replace the roles,\nrecords, decisions and escalation path with the actual process and approved procedures.\nThe continuity procedure mentioned in the example must exist and be assessed in the real\norganisation; writing it into the statement does not establish that it works.",[27,237,239],{"id":238},"assign-accountability-as-well-as-tasks","Assign accountability as well as tasks",[11,241,242],{},"Titles such as “Process Owner” and “System Owner” need assigned people, authority and escalation\npaths. This matrix is illustrative, not a universal role model or regulatory assignment.",[153,244,245,258],{},[156,246,247],{},[159,248,249,252,255],{},[162,250,251],{},"Activity",[162,253,254],{},"Illustrative accountable role",[162,256,257],{},"Supporting roles and evidence",[169,259,260,271,282,293,303,314,325,336,347,358],{},[159,261,262,265,268],{},[174,263,264],{},"Define the process, register purpose, data definitions and permitted reliance",[174,266,267],{},"Process Owner",[174,269,270],{},"Quality reviews the quality-system boundary; retain the approved statement",[159,272,273,276,279],{},[174,274,275],{},"Maintain the configured system baseline and change evidence",[174,277,278],{},"System Owner",[174,280,281],{},"IT\u002FMicrosoft 365 administrator supports platform operations; retain configuration, change and operating records",[159,283,284,287,290],{},[174,285,286],{},"Assess supplier and external-service responsibilities",[174,288,289],{},"System Owner or role named by the organisation",[174,291,292],{},"IT and the supplier provide service evidence; retain reviewed scope, limitations and open actions",[159,294,295,298,300],{},[174,296,297],{},"Plan and assess verification",[174,299,278],{},[174,301,302],{},"Process Owner defines intended-use checks; authorised Quality role reviews acceptance; retain protocols, actual results and deviations",[159,304,305,308,311],{},[174,306,307],{},"Set quality oversight, escalation and risk-acceptance decisions",[174,309,310],{},"Authorised Quality role",[174,312,313],{},"Process Owner supplies the impact assessment and discrepancy examples",[159,315,316,319,322],{},[174,317,318],{},"Enter and reconcile register information",[174,320,321],{},"Assigned editor or process role",[174,323,324],{},"Follow the controlled procedure; retain the record reference and correction trail",[159,326,327,330,333],{},[174,328,329],{},"Provide identity, access and service support",[174,331,332],{},"IT\u002FMicrosoft 365 administrator",[174,334,335],{},"System Owner defines required access; verify the organisation's actual service arrangements",[159,337,338,341,344],{},[174,339,340],{},"Handle incidents affecting register data or service",[174,342,343],{},"Roles named in the organisation's procedures",[174,345,346],{},"Record the event, assess affected entries and reports, and retain reconciliation and escalation evidence",[159,348,349,352,355],{},[174,350,351],{},"Plan recovery and continuity for the service and its records",[174,353,354],{},"System Owner or other role named by the organisation",[174,356,357],{},"IT supports service arrangements; retain approved recovery requirements and executed recovery evidence",[159,359,360,363,366],{},[174,361,362],{},"Decide whether the configured solution is fit for its intended use",[174,364,365],{},"Decision-maker authorised by the quality system",[174,367,368],{},"Process Owner and System Owner provide assessment and verification evidence; retain the approved decision and residual-risk record",[11,370,371],{},"Confirm who may approve intended use and accept residual risk. A role label here is not an\nappointment, approval or evidence.",[27,373,375],{"id":374},"challenge-the-statement-with-failure-cases","Challenge the statement with failure cases",[11,377,378],{},"Walk through realistic discrepancies before choosing an implementation. Define the expected\nresponse and the evidence that would show the process works. The checks below are proposals;\nthey have not been executed in a tenant or against a customer system.",[153,380,381,394],{},[156,382,383],{},[159,384,385,388,391],{},[162,386,387],{},"Scenario",[162,389,390],{},"Expected handling",[162,392,393],{},"Evidence to plan",[169,395,396,413,424],{},[159,397,398,407,410],{},[174,399,400,403,404],{},[220,401,402],{},"DEV-2026-0001"," has no link to controlled record ",[220,405,406],{},"CR-0001",[174,408,409],{},"Flag the missing reference; do not assume the entry is complete or traceable",[174,411,412],{},"Exception record, assigned owner and documented resolution",[159,414,415,418,421],{},[174,416,417],{},"The register says “Closed” while the controlled record remains open",[174,419,420],{},"Route the discrepancy for reconciliation; do not use the register status as closure approval",[174,422,423],{},"Reconciliation record, authorised correction and retained rationale",[159,425,426,429,432],{},[174,427,428],{},"A new workflow automatically approves closure",[174,430,431],{},"Reassess intended use, risk and authority before enabling it",[174,433,434],{},"Updated scope, requirements, risk assessment and approved verification plan",[11,436,437],{},"Record each check's input, expected and actual results, deviations and authorised assessor. Until\nperformed and documented in the relevant environment, its result is “not executed”.",[27,439,441],{"id":440},"decide-whether-to-retain-assess-or-change-direction","Decide whether to retain, assess or change direction",[11,443,444],{},"An intended-use statement should help the team compare options, not predetermine a move to\nSharePoint. Retaining a controlled Excel register may be reasonable if its use, ownership,\naccess, evidence and ongoing controls remain suitable. A SharePoint List may be assessed when\nits proposed configuration and service arrangements can support the defined process. Another\nsolution may be more appropriate when required controls or responsibilities cannot be justified.",[11,446,447],{},"Before deciding, identify the relevant needs for data meaning, ownership, access, source-record\nlinks, change control, reporting, recovery and retention. Verify them against local procedures\nand the actual environment; do not infer a capability from a product name or demonstration.",[11,449,450],{},"Reassess the boundary before adding an approval, electronic signature, automated classification,\nproduct-release decision, system integration or replacement of the authoritative record. These\nchanges can alter who relies on the information and what evidence is needed.",[27,452,454],{"id":453},"put-the-statement-to-work","Put the statement to work",[11,456,457,458,462],{},"Review the statement with process users, the system owner and the authorised Quality role.\nFor each permitted use, identify the requirements, controls and evidence needed to justify\nreliance. For a wider verification plan, see\n",[21,459,461],{"href":460},"\u002Fblog\u002Fpractical-risk-based-computerised-system-validation","practical risk-based computerised system validation",".",[11,464,465,466,470,471,462],{},"For the quality register example, assess whether the present register meets the defined need,\nidentify the gaps and decide whether a controlled change is justified.\nThe ",[21,467,469],{"href":468},"\u002Fvalidate-quality-register","quality-register assessment pathway"," is the next step for teams\nthat need help assessing fit and evidence. For broader context, see ",[21,472,474],{"href":473},"\u002Fblog\u002Fwhen-your-spreadsheet-starts-making-gmp-decisions","how a spreadsheet's role can\nchange when it starts influencing GMP decisions",[11,476,477],{},"The goal is not to move every register or produce a large package by default. Make purpose,\ndecision boundaries, responsibilities and residual risks clear enough to choose and maintain a\nsuitable approach.",{"title":218,"searchDepth":479,"depth":479,"links":480},2,[481,482,483,484,485,486,490,491,492,493],{"id":29,"depth":479,"text":30},{"id":61,"depth":479,"text":62},{"id":82,"depth":479,"text":83},{"id":119,"depth":479,"text":120},{"id":147,"depth":479,"text":148},{"id":206,"depth":479,"text":207,"children":487},[488],{"id":225,"depth":489,"text":226},3,{"id":238,"depth":479,"text":239},{"id":374,"depth":479,"text":375},{"id":440,"depth":479,"text":441},{"id":453,"depth":479,"text":454},"Compliance","2026-10-29","Define a computerised system's purpose, users, data and decision boundaries with a reusable intended-use template and an Excel quality register example.",false,null,"md","\u002Fimages\u002Fblog\u002Fqiksolve-blog-intended-use-abstract-1200x900.webp","Abstract geometric hero image for How to Define Intended Use of a Computerised System",{},true,"\u002Fblog\u002Fexcel-register-intended-use-and-ownership",{"title":5,"description":496},"blog\u002Fexcel-register-intended-use-and-ownership",[508,509,510,511,512],"computerised-systems","intended-use","quality-register","gmp","process-ownership","yOhfanrzh1_9TrMkEVmt_LgR1LqhabHL64rnWNovaFs",1793270106367]