Table of contents
At a glance
How do you distinguish a validated Excel template from completed working copies?
The approved Excel template defines formulas, structure and intended use. Each completed working copy also contains a specific dataset. Control changes to and distribution of the master separately from identification, review and retention of each working copy. A newly approved template must not silently replace existing result records.
Scope and Applicability
This article addresses the lifecycle of work folders. Formula errors and limit tests are further discussed in the linked specialist article. A specific folder structure or particular document management system is not prescribed as a universal solution.
Draft, working copy, and record differ
A template contains the approved logic and structure. A working copy is used for a specific process. The completed record documents inputs, calculations, and decisions made during that process. All three may utilize the same file format, but they serve distinct purposes. Clear naming and storage practices should make these differences readily apparent.
Start with an inventory of the actually used templates. Capture purpose, responsible party, storage location, version, critical formulas, and external dependencies. Also inquire about local copies and email attachments. A central file is not automatically the sole version in use. The inventory should reflect actual work practices, not just the officially designated storage path.
Define how a new working copy is created and ensure that the original template version remains identifiable within it. Visible versioning helps, but is alone insufficient to prevent unauthorized replacement. Appropriate rules for release, distribution, write access, and version supersession are required. The suitability of a technical solution depends on scope, risk profile, and existing document management capabilities.
Establish a controlled release and distribution chain
Separate editing a template from using its approved version. Make changes in a controlled draft, assess their effects, run appropriate tests and obtain approval from the responsible roles. Only then make the new version available for new work. Editing the sole production copy makes the history difficult to establish.
Determine the handling of open work copies. A new template does not need to automatically replace all previously initiated activities. It may be appropriate to complete existing work under the current status, provided that further use of such work is professionally justified. In the case of a detected calculation error, an evaluation of previously generated results may become necessary. The reason for the change determines the transition requirements.
| State | Permitted use | Information needed |
|---|---|---|
| Draft | Development and controlled testing | Author, Reason for Change and Reference Base |
| Approved template | New procedures in the specified application | Version, Efficacy and Release |
| Working copy | Designated procedure following transition rule | Template used and processing status |
| Final record | Traceability and retention | Inputs, Results, Decision and Context |
| Retired template | Historical statement, no uncontrolled nine-use | Withdrawal date and associated activities |
Software version changes and retention of previous work copies
When transitioning between versions, it must be determined at what point new work copies are generated from the new master. Ongoing evaluations may require a special handling approach. Assess whether a new formula has an impact on previous results; a cosmetic change and a corrected calculation are professionally distinct.
Historical work copies require contextual relevance. Those who retain only a PDF version after years may no longer be able to reconstruct relevant calculations or underlying data. The formats to be retained should be determined by the required content and actual documentation function, not by convenience of storage.
Example: Version 3 replaces a flawed calculation rule
Template V2 uses a wrong conversion factor in an auxiliary cell. V3 corrects it. It is not enough to place V3 in the central folder. First, the affected calculations, processes and time periods are delimited. Then, it is assessed which results and decisions already generated can be affected.
For V3, appropriate nominal and boundary cases are independently calculated and verified. The test documents inputs, expected values, actual values, and the correct decision. Thereafter, the distribution is monitored. Searches for known storage locations, clear communication to users, and technical limitations may collectively contribute. No single step individually proves that any local copy has been eliminated.
Open processes are handled according to a predefined decision. When a process is transferred to V3, any imported inputs and newly calculated results must remain traceable. Blanket overwriting of the original file without comments would obscure the original state. Closed records are not silently replaced; any required corrections follow the prescribed controlled procedure.
| Case | In-house verification | Expected finding |
|---|---|---|
| New working copy | Create the template through the approved workflow | V3 is detectable and correct logic is present |
| Old local copy | Call V2 in the known alternative pathway | Proposed distribution and blocking checks or findings |
| Open process | Inputs controlled according to V3 are accepted. | Values and changes remain traceable |
| Historical Process | Reconstruct results from V2 | Previous calculation basis is justifiable |
| Unauthorized change | Attempt to change the formula in the working copy | Selected protection and review control responds |
Correctly categorize safety functions
Sheet protection may complicate unintended editing of critical cells. Folder protection may impact document structure. File access and encryption address different concerns. Microsoft differentiates these features and cautions against treating sheet protection as a security function. Therefore, a concept must define which control limits which error or access.
Evaluate alternative approaches. Users can copy, rename, export files, or transfer content into new workspaces. Depending on usage, macros, external links, or manual inputs may introduce additional changes. Describe authorized work methods and assess how deviations are detected. A technical restriction without appropriate distribution can merely shift the problem to another location.
Version histories of a document management platform can be helpful but do not replace professional release decisions. Verify whether a previous version was identified, whether a relevant difference was explained, and whether the actually used version of a process can be assigned. A list of change timestamps does not automatically confirm that a formula change was authorized or adequately reviewed.
Maintain usable change and handover records
The change record should link the rationale, affected logic, implications, validation evidence, and release. A comparison of critical formulas and named areas can support the evaluation. Also document external dependencies: an unchanged template may yield different results if a referenced file or data source has been modified.
Operations need an owner, deputy and access to the evidence. Define who may request, edit and approve a new version. Control template retirement so historical records remain understandable. Deleting a master file that is no longer in use may remove needed context.
Test the document routing with a simple traceability case. Select a completed record and allow an authorized employee to locate the template version, the prevailing rule at the time, and the associated audit evidence. If only the original developer can access these, there may be a lack of appropriate handover. This test evaluates usability and personnel dependency, not merely file existence.
Worksheet for controlled replacement with a new master template
Treat detachment as a transition between two logically explainable states. In the example, V2 is replaced by V3. Document the rationale, critical changes, and affected processes. For a correction error, additionally assess whether previous results may be impacted. For a planned technical change, a different transition rule may be applicable.
Practically go through a user's path: find a template, create a working copy, collect data, complete results and search later. At each point, the used stand should be recognizable. A central release list only helps if the actual work path fits it and alternative copies are treated appropriately.
After transition, review a new and a historical process. This enables a joint assessment of current distribution and storage conditions. If an older version remains professionally required, specify its intended purpose. Historical availability must not create ambiguity regarding release for new processes.
| Handover field | Example entry | Required statement |
|---|---|---|
| Reason for the change | V3 corrects a specified conversion. | The affected calculation is clearly identified. |
| Distribution | New working copies are derived from the controlled master pathway. | Users receive the correct status. |
| Open procedures | V2 cases are individually evaluated according to established criteria. | No comments attached to overridden results. |
| History | Closed V2 records remain attributable. | Previous formula basis and decision traceability. |
| Alternate copies | Known local and consigned versions will be treated. | No unfounded claim of completeness. |
| Closure | Release, testing, and actual availability are linked. | Document decision and implementation align. |
Next steps
- Master, work copy, and result documentation clearly defined.
- Define release, distribution, and access to templates.
- Review version changes including ongoing activities.
- Organize archiving and, if applicable, retrospective evaluation of results.
Project experience and collaboration
Check the effect of a template change on existing working copies
We place an approved template alongside a completed working copy. With the people who use it, we establish how they recognise the version and what should happen to existing records after a change. A distribution and filing rule may suffice for a few controlled files. Numerous templates or workstations may need more control. We test the change against known copies and open transactions to check that new formulas do not silently change the meaning of historical results.
Frequent Questions about Excel Templates and Worksheets
Must each completed copy be revalidated?
Is a PDF output sufficient for retention?
Can a SharePoint library help?
Must completed Excel files be recalculated upon every template modification?
Not at all. Evaluate the reason and effect of the change. Editorial adaptation has different consequences than correcting an incorrect calculation. Affected historical results and decisions are to be examined in a targeted manner. Required corrections should be made intelligibly without implicitly overwriting the original recording level.
Is a version number in the filename sufficient?
It supports orientation but provides neither release nor unaltered content. Link version, controlled storage, change history, and actual usage. Specifically verify local copies and open activities. A file may be correctly named and still contain different formulas or originate from a non-released source.
Can a document management platform fully replace Excel template guidance?
It can support versioning, permissions, and release steps. However, always verify the actual working copy, local storage, and connectivity to the calculation logic. A platform audit trail does not automatically demonstrate that each user employed the correct template or that a critical formula remained unchanged.
How do we handle an accidentally overwitten master file?
Ensure the known state is preserved and identify the timing, changes, and affected usage. Recreate the appropriate state under controlled conditions and verify critical functions. Assess previously generated results where a professional evaluation is feasible. Simply copying data does not automatically conclude this investigation.
Sources and review date
The sources provide the technical foundation. Tables, checklists, and examples are derived methodological tools, not verbatim regulatory requirements. Manufacturer information must be referenced to the specific version and configuration in use.
- European Commission: EU GMP Annex 11, Computerised Systems (2011)Current version as per EudraLex inventory as of 14.10.2026. Application, risks, operation, and data lifecycle; specific testing proposals are derived independently.
- European Commission: EU GMP Chapter 4, Documentation (2011)Document control, inspection, distribution, and retention of documents and records.
- Microsoft: Protection and security in ExcelSupplier source for product functionalities. Availability and behavior depend on version, edition, license, and configuration; no general compliance certification.
Sources checked: .
So your team can safely plan the next step.
We support you in assessing the current situation, clarifying responsibilities, and implementing appropriate evidence within operations. The type of support that is most effective depends on your system, your team, and the specific objective.
- Computer system validation →
Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

