Configuration Specification for Computerized Systems
Connect intended use to documented software settings, verification evidence, and controlled changes while keeping review and approval with accountable people.

On this page · 10 sections
- 1What a Configuration Specification defines
- 2Contents of a usable configuration baseline
- 3US and EU expectations by source type
- 4Trace requirements to settings and evidence
- 5Control changes and configuration drift
- 6Interfaces, identifiers, and exception recovery
- 7Verify effective settings and acceptance criteria
- 8Ownership, evidence, and operational review
- 9Failure modes and targeted controls
- 10Implementation and review checklist
How does Configuration Specification apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What a Configuration Specification defines
A Configuration Specification is a controlled description of the selected settings, parameter values, permissions, workflows, and interface rules that implement intended use in a configurable computerized system. Common aliases are CS and configuration spec. It describes the choices that turn configurable software into a defined implementation for a particular process.
Configuration Specification is industry terminology associated with GAMP-oriented validation practice, not a regulatory document title or a universally prescribed standalone deliverable. Its practical purpose is to make configuration decisions explicit enough for process owners, administrators, and reviewers to understand the intended setup without relying on administrator memory.
The following distinctions reflect common validation practice. Organizations may combine documents, provided their purposes remain identifiable; a document’s title matters less than whether readers can distinguish needs, implementation choices, operating instructions, and evidence.
| Artifact | Primary question | Typical content | Relationship to the CS |
|---|---|---|---|
| URS | What do users need? | Intended use and user needs | Provides the needs configuration supports |
| Functional specification | What behavior is required? | Functions, rules, expected responses | Defines behavior realized through selected settings |
| Design specification | How is it technically realized? | Architecture, components, technical design | Places configuration within the wider solution |
| CS | Which configurable behavior is selected? | Settings, values, permissions, workflow choices | Defines the intended configuration |
| Configuration record | What was applied? | Captured implementation state | Supports comparison with the specified state |
| SOP | How do people operate it? | Human tasks and operating procedures | Explains activities around configured behavior |
| Test protocol and results | How is it checked, and what happened? | Verification method and observations | Evaluate implementation against intended configuration |
The central boundary is between intended and observed state. The CS describes the intended configuration; implementation records and verification evidence establish what was actually applied and observed. Approval of a specification alone is not evidence that the running system matches it. For example, a specified permission restriction records a decision; evidence from the implemented system establishes whether that restriction is present and behaves as intended. Keeping these roles distinct prevents a signed document from being mistaken for confirmation of system behavior.
02Contents of a usable configuration baseline
A usable configuration baseline records the choices that determine intended system behavior, not every available preference. The following is a suggested industry-practice structure, not a prescribed regulatory template. Select settings by their effect on process execution, records, decisions, and recovery; use risk-based validation to guide the depth of documentation.
Document structure
- Baseline identity: system name and identifier, intended-use boundary, application version, environment, configuration owner, and approval responsibilities.
- Configuration register: requirement references, setting definitions, approved values, dependencies, rationale, and verification references.
- Supporting references: custom-code components and infrastructure dependencies, identified separately rather than presented as ordinary application settings.
- Revision history: what changed, why, affected baseline entries, and the associated change record.
Setting-level detail
For each relevant setting, record its stable identifier or path, purpose, approved value and data type, unit where applicable, allowed values or range, scope, default or inheritance behavior, rationale, and verification approach. Distinguish the application's allowable range from the narrower range selected for the intended process.
Group entries by configurable behavior: permissions, workflow transitions, calculations, limits, record-status rules, signature configuration where applicable, interfaces, reports, and recovery behavior. This grouping lets reviewers examine related decisions without searching an indiscriminate settings export.
Separate global, site, product, equipment, and user-level values. Document the actual precedence rules, including conflicting overrides and fallback behavior, so a reviewer can determine the expected effective value for a named transaction with known context. Do not assume that the most specific value always wins.
An explicitly accepted default identifies the default value, applicable version and scope, and acceptance rationale. An omitted setting communicates no such decision: it may be irrelevant, overlooked, or inherited. Record exclusion reasons where silence would leave the baseline ambiguous.
Accompanying evidence model
An illustrative evidence structure—not a V5 application schema—links requirements to baseline-specific setting entries, entries to verification observations, and changed entries to change records. Each observation identifies the baseline and environment examined, preserving the distinction between an approved value and an observed value. This supports data integrity by design. Keep passwords, access tokens, and other secrets outside the CS; reference their controlled management arrangements instead.
User Requirement
Defines intended use and acceptance basis.
- requirement_id
- intended_use
- gxp_impact
- risk_reference
- acceptance_basis
Configuration Baseline
Identifies the configuration and its context.
- baseline_id
- system_id
- environment_id
- application_version
- approval_record
Specified Setting
Links a selected value to intent.
- setting_id
- baseline_id
- requirement_id
- setting_path
- specified_value
- value_unit
Verification Evidence
Records observed state and test outcome.
- verification_id
- setting_id
- baseline_id
- effective_value
- result
- evidence_uri
Controlled Change
Connects baseline revisions and decision records.
- change_id
- prior_baseline_id
- new_baseline_id
- impact_record
- approval_record
03US and EU expectations by source type
Configuration Specification (CS) is an industry-practice document name, not a regulatory term. Map the underlying control and its evidence to the applicable source, rather than treating approval of a document called CS as the compliance objective. The configuration-relevance column below gives practical implementation suggestions, not prescribed document contents.
| Jurisdiction and product scope | Source type | Provision | Supported expectation | Configuration relevance |
|---|---|---|---|---|
| EU medicinal-product GMP systems | Official guidance | Annex 11, section 4.4 | Expects user requirements to remain traceable throughout the lifecycle. | Link each relevant requirement to its implementing setting and test evidence. |
| EU medicinal-product manufacturing | Official guidance | Annex 15, section 11.4 | Expects quality risk management to evaluate planned changes for their potential impact on product quality. | Identify affected settings and quality risks when assessing a proposed configuration change. |
| US finished pharmaceuticals | Binding regulation | 21 CFR 211.68(b) | Controls must assure that changes to master production and control records or other records are instituted only by authorized personnel. Computer-system input and output involving formulas, records, or data must be checked for accuracy. Verification degree and frequency must be based on system complexity and reliability. | Describe record-change permissions, relevant input/output checks, and the rationale for their extent and frequency. |
| US drug CGMP systems | Official guidance | FDA Data Integrity guidance, question 4 | Recommends technical means, where possible, to restrict changes to specifications, process parameters, data, and manufacturing or testing methods. | Identify permissions governing these changes and the evidence used to demonstrate their operation. |
Industry practice: connect the control to evidence
A practical CS connects intended controls to identifiable settings; the evidence demonstrates whether those controls work. A CSV traceability matrix can carry requirement-setting-test links, while change control can carry the impact assessment and approval decision. These are documentation choices, not additional regulatory deliverables inferred from the mappings above. Keep the distinction visible when reviewing data integrity: a permission listed in a specification and a permission demonstrated in operation answer different questions.
Software support and scope boundary
Treat software functionality as an implementation mechanism, not evidence of site-wide compliance. Human reviewers retain the approval and release decision; configuration documentation supports that decision rather than replacing it. For supplements, food, devices, and chemicals, assess the applicable product-specific and jurisdiction-specific rules separately. Do not extend these drug and medicinal-product mappings to those sectors.
04Trace requirements to settings and evidence
As industry practice, a configuration specification connects intended use → URS requirement → failure consequence → configuration decision → acceptance criterion → executed verification → discrepancy disposition. Requirements traceability makes those connections navigable. Identifiers locate records; they do not prove that a requirement is clear, a setting implements it, or a test challenges the relevant failure.
Risk-based validation commonly sets verification depth by considering the effect of an incorrect setting, how readily the error would be detected, shared dependencies, and alternate access paths. Apply that reasoning within the regulatory context mapped above, rather than treating every setting as equally consequential.
Worked case: execution without configuration authority
Assume operator and configuration-administrator roles, with user-interface and service access. Measurement units are not applicable to permission decisions. Intended use is execution of an approved process. The URS permits operators to execute it but prohibits changes to configured acceptance limits; unauthorized changes could allow unacceptable results to pass.
The CS translates this requirement into a role-based access model: operator execution allowed, operator limit editing denied, and configuration-administrator limit editing allowed. Record permission settings, inherited group memberships, and the identities used for service access. Evaluate effective permissions, not just the named role.
Acceptance criteria cover successful operator execution, denied operator limit changes through both access paths, and permitted administrator changes. Executed verification records the identity, configuration baseline, attempted action, observed outcome, and resulting stored value. A read-only screen demonstrates only that screen's behavior; it does not establish that service requests cannot change the same limit.
Suppose execution succeeds, but inherited group membership permits a prohibited service change. Record a discrepancy and assess other identities sharing that group. Trace the correction to the approved permission model, reconcile the CS with the corrected configuration, and rerun affected allow/deny tests. Preserve the failed result alongside correction and retest evidence. A reviewer dispositions the discrepancy; editing the original test result would not demonstrate resolution.
Operational lifecycle: approved baseline → operation → proposed change or detected discrepancy → impact assessment → configuration update → verification → human approval → revised baseline.
- Define useIdentify users, process boundaries, requirements, and configuration risks.
- Specify SettingsRecord chosen values, units, dependencies, roles, and interface behavior.
- Approve baselineResolve review comments and identify the configuration authorized for implementation.
- Implement settingsApply the approved baseline in the named system and environment.
- Verify behaviorRead effective values and execute positive, negative, and recovery tests.
- Accept EvidenceHave designated reviewers resolve discrepancies and authorize the intended use.
- Control changesAssess changes, reverify affected behavior, and update baseline history.
05Control changes and configuration drift
In configuration-management practice, a baseline is an identified configuration associated with a system version, environment, approval state, and implementation context. Identify the applicable modules, deployment, and dependencies so that reviewers can distinguish a document revision from the system state it describes.
- Proposed revision: the intended change, still subject to assessment and authorization.
- Approved target baseline: the configuration authorized for implementation in the named environment.
- Last verified operating state: the configuration supported by completed checks in that environment; it may differ from the approved target while deployment remains incomplete.
For EU medicinal-product manufacturing, official guidance in Annex 15, section 11.5 expects changes to be authorized and approved by responsible persons or relevant functional personnel under the pharmaceutical quality system.
A practical change-control package records the reason, affected settings, prior and proposed values, impacted requirements, and dependent interfaces and reports. Use that impact assessment to define the verification plan, implementation instructions, rollback or forward-recovery approach, and closure evidence. Name dependencies explicitly: a local setting change can alter downstream interpretation even when the receiving application is unchanged.
After deployment, reconcile the approved change against the configuration actually applied in the target environment. Include environmental substitutions and overrides, not just values in the deployment file. Record each difference, its explanation, and its approval status. An authorized environment-specific substitution is an approved difference; an unexplained mismatch is potential configuration drift, not an implicit amendment to the baseline. Route unresolved discrepancies through the site's deviation process where appropriate.
Assess recovery before implementation. Restoring a setting may not reverse records already created, transactions already transmitted, or data transformations already performed. Include reconciliation of affected records and external transactions in the proposed recovery assessment. For closure, link the applied configuration, verification results, discrepancy dispositions, and human approval decision. Advance the verified operating baseline only when that evidence supports it; a new revision number alone does not demonstrate successful implementation.
06Interfaces, identifiers, and exception recovery
As industry practice, an interface-specific CS commonly documents both data meaning and delivery behavior. A useful baseline includes source and destination systems; business event; schema or message version; field mappings and units; identifier authority; status mappings; time-zone handling; validation rules; acknowledgement behavior; retry handling; and reconciliation ownership.
Assign a process or master-data owner to approve data meanings and a reconciliation owner to resolve unmatched outcomes. For material, lot, equipment, and process references, document the authoritative system, lookup key, cross-system mapping, and response to missing or ambiguous matches. Identically named records are not sufficient evidence of equivalence; explicit production context references keep results attached to the intended operation.
Distinguish the business identifier, which identifies the relevant entity or transaction, from its human-readable display label. A transport-message identifier identifies a transmission; a durable source-event identifier identifies the business occurrence across retries. Define their scopes and persistence separately.
Worked retry and recovery case
Assume an inbound batch-result interface carries net mass in kilograms and a durable source-event identifier. The destination saves the result, but its acknowledgement is lost. The source retries the unchanged event. For this design, expected recovery is to recognize the repeated event, avoid another business transaction, record the retry outcome in a process event log, and return the committed outcome so the reconciliation owner can align source and destination status.
A changed payload using the same event identifier is a conflict, not an ordinary retry. Define payload comparison and route the conflict for disposition rather than silently overwriting the saved result. Keep recovery paths distinct:
- Quarantine blocks further posting pending investigation.
- Controlled reprocessing resubmits an eligible event after its failure cause is resolved.
- Manual correction changes the business record through an authorized, documented correction workflow.
Observable acceptance criteria for this hypothetical interface are no duplicate business result, traceable retry handling, explicit disposition of conflicting payloads, reconciled statuses, and evidence identifying the affected event and configuration baseline.
07Verify effective settings and acceptance criteria
In configuration-verification practice, readback and behavior testing answer different questions. Inspecting a configured value addresses the setting itself; exercising the process demonstrates its effective behavior in context. Use complementary evidence where dependencies, overrides, or alternate execution paths could change the result. A settings export alone does not demonstrate that an execution path applies those settings.
Select coverage by consequence
Use intended use and identified failure consequences to select coverage through risk-based validation. Consider approved values, defaults, inheritance, role restrictions, state transitions, calculation settings, relevant record histories, interface exceptions, and restart or recovery behavior. Document why each selected check matters and define its expected result before execution. These checks can support operational qualification without treating every available setting as equally significant.
Worked case: stored mass versus rounded display
Assume a weighing step stores mass in kilograms (kg), rounds the display to the nearest display increment, and compares stored mass against site-approved inclusive limits L and U. Let δ be the smallest supported stored-mass increment in kg. Assume inward boundary increments remain within the permitted range. These limits and resolutions are process assumptions, not regulatory thresholds.
| Stored mass (kg) | Expected comparison decision |
|---|---|
| L − δ | Reject: below lower limit |
| L | Accept: inclusive lower limit |
| L + δ | Accept: within limits |
| U − δ | Accept: within limits |
| U | Accept: inclusive upper limit |
| U + δ | Reject: above upper limit |
For the rounding challenge, assume U is exactly displayable and δ is small enough that U + δ rounds down to displayed U. Submit stored mass U + δ. The expected decision remains rejection: the configured rule compares stored mass, not its apparently acceptable display. Acceptance would contradict the stated requirement, even if the screen looked correct.
Retain the requirement reference, configuration baseline, effective comparison and rounding settings, stored input with units, displayed value, expected decision, actual decision, and discrepancy disposition. Together, these make the boundary result interpretable and distinguish a display effect from a comparison defect.
Assess supplier evidence for relevance
Compare supplier test evidence, including relevant factory acceptance testing, with the site's selected configuration, intended use, environment, and interfaces. Identify matching conditions, differences, and untested paths; use that assessment to select supplemental site checks. Generic supplier testing is not interchangeable with verification of the implemented site configuration. Site reviewers assess applicability and approve the evidence decision.
08Ownership, evidence, and operational review
A practical governance model assigns responsibility for the configuration specification separately from permission to edit the system:
- Process owner: defines intended use, operational consequences, and suitability for the process.
- Configuration owner: maintains the specification, baseline references, and links between settings and supporting evidence.
- Technical administrator: implements authorized settings and records the resulting configuration; implementation access does not confer acceptance authority.
- Test executor: records observed behavior, test conditions, and departures from expected results.
- Designated reviewer: evaluates evidence and unresolved issues, then documents acceptance or rejection within delegated authority.
Assess supporting tools for controlled storage, configuration capture, traceability, and evidence retrieval. A linked CSV traceability matrix can organize relationships, but the application is not the decision-maker. Acceptance of a system configuration is distinct from product-quality assessment and batch release; those decisions remain with accountable people.
Through upgrades and retirement, preserve enough context to interpret prior baselines: system and environment identity, setting meanings, verification observations, configuration differences, and approvals. Keep evidence linked to the version it describes, with readable exports or a suitable viewing method where needed. Test retrieval after migration rather than assuming stored files remain usable. Determine retention through applicable obligations and site policy, not a universal CS duration.
Use risk-based review frequency and event-driven triggers: unexplained configuration differences, changed intended use, supplier changes affecting defaults, incidents involving configured behavior, and recurring exceptions. Feed relevant findings from audit trail review into that review, assigning an owner to each resulting action.
09Failure modes and targeted controls
The following operational-practice checks complement document control and failure-mode analysis. They target gaps between the configuration specification, deployed settings, and verification evidence.
| Failure mode | Why it matters | Targeted control | Evidence to inspect |
|---|---|---|---|
| Screenshot-only specification without stable setting identifiers | Reviewers cannot reliably locate the same setting after interface changes. | Pair screenshots with identifiable setting paths and object identifiers. | Setting register matched to screens or exports. |
| Copied specification retains another environment’s assumptions | Endpoints, roles, or defaults may describe the wrong deployment. | Reconcile environment-dependent entries against the target environment. | Environment comparison with resolved discrepancies. |
| Linked tests do not exercise configured behavior | Traceability exists without demonstrating the intended restriction or outcome. | Have reviewers inspect acceptance criteria against each relevant setting. | Test inputs, expected outcomes, and execution results. |
| Undocumented overrides | A local value can defeat the specified global setting. | Define explicit precedence rules and inspect active overrides. | Override inventory and effective-value readback. |
| Updated specification without implementation evidence | An approved document can describe an undeployed state. | Reconcile implementation readback to the approved revision. | Dated readback identifying environment and configuration revision. |
For the access, retry, and rounding cases covered above, apply these checks to the specific settings and observed outcomes—not merely to linked document titles.
10Implementation and review checklist
Use this review aid to decide whether a configuration is ready for its intended use, not to certify compliance. For each gate, identify the supporting record and any unresolved action.
Specification readiness
- Confirm that intended use and the target environment are identifiable.
- Check that relevant settings, retained defaults, units, and precedence rules are explicit.
- Locate requirement links, interface ownership, and measurable or otherwise observable acceptance criteria. Use the CSV traceability matrix to navigate between these records.
Implementation readiness
- Identify the approved target baseline and controlled implementation instructions.
- Review dependency assessments and access arrangements for implementation and subsequent operation.
- Confirm an appropriate rollback or forward-recovery plan, including who decides when to invoke it.
Verification completion
- Locate reconciliation of the implemented configuration against the target baseline.
- Review executed tests, including selected failure conditions, and evidence that identifies the environment and observed result.
- Check documented disposition of discrepancies rather than treating test execution alone as acceptance.
Operational handover
- Confirm named owners, accessible baseline history, applicable procedures, and recovery responsibilities.
- Identify the route for subsequent configuration changes, including how supporting records remain accessible.
- Record the responsible reviewer's decision, its basis, and any actions that prevent handover.
Can the reviewer trace a relevant requirement through the effective setting to its verification evidence—and use that chain to justify the configuration decision?
Frequently asked questions
Q.Can a shared CS cover sites with different local configurations?+
Yes. A practical structure is a shared baseline plus controlled site-specific schedules. Identify each setting’s scope, approved value, local owner and applicable environment; distinguish inherited defaults from deliberate overrides. Link local differences to the relevant URS and verification evidence. For example, sites may share workflow logic while using different role-based access assignments. Each site’s approval should identify the baseline and local schedule used together, so reviewers can reconstruct its effective configuration without assuming that corporate approval covers every local variation.
Q.When is a supplier configuration export sufficient as the CS?+
An export can serve as the CS when it is readable, version-controlled, scoped to the deployed environment and supplemented with intended values, rationale, approvals and requirements traceability. An export of current values alone does not establish intended configuration or successful operational testing. For EU medicinal-product GMP systems, Annex 11, section 3.3 recommends reviewing documentation supplied with commercial off-the-shelf products to check that user requirements are fulfilled. A practical acceptance check also examines export omissions, inherited settings and whether values are raw or effective.
Q.Can structured records replace a standalone configuration specification document?+
Yes. In industry usage, configuration specification describes a controlled specification of settings, not necessarily a standalone narrative document. Structured records can hold setting identifiers, intended values, applicability, requirement links, verification references and approval history. The practical test is whether document control preserves an identifiable approved baseline and its superseded states. In a paperless validation approach, distinguish editable working records from approved records, and provide a readable view of the complete baseline. Human reviewers still evaluate and approve the configuration.
Q.How should emergency configuration changes be documented and reconciled?+
For EU medicinal-product GMP systems, Annex 11, section 10 recommends controlled configuration changes under a defined procedure. A practical emergency change-control record captures the incident, authorization, affected settings, previous and temporary values, implementation time, containment and rollback decision. Preserve supporting audit-trail records where available. Reconciliation then compares the live state with the approved baseline, evaluates affected operations, completes proportionate testing and records whether the temporary change was retained or reversed. Record later approvals as later approvals, rather than backdating them.
Q.Does every software patch call for a new CS revision?+
Not necessarily. A practical revision decision turns on whether the patch changes specified settings, their meaning, available options, defaults or configuration-dependent behavior. Record the patch and impact assessment even when the CS remains unchanged. Under a risk-based validation approach, examine supplier release information and targeted checks rather than treating an unchanged version of the CS as proof of no impact. Revise the CS when its content becomes inaccurate; update the software inventory separately when only the installed software version changes.
Q.Where should recipe parameters sit relative to the CS?+
Common practice separates platform configuration from product- or process-specific recipe content. The CS can describe parameter handling: units, permitted data types, editing permissions, approval workflow and how recipe versions are selected. Controlled recipe records typically hold product-specific targets and operating ranges, with references to the applicable process justification. Keep material master data separately identifiable where it supplies recipe inputs. If a recipe parameter directly changes system-wide behavior, document that dependency in the CS rather than maintaining conflicting values in separate records.
Q.How can settings be verified without a configuration export?+
Use a documented comparison of intended settings with observable system evidence. Practical methods include witnessed navigation through administration screens, contextual screenshots, supported read-only queries and behavioral challenges. Record the environment, software version, setting identifier, observed value, reviewer and result. For inherited or hidden settings, test effective behavior as well as any displayed value. During site acceptance testing, distinguish evidence that a setting exists from evidence that it works; an enabled permission flag alone does not demonstrate the intended access restriction.
Q.How should an undocumented live setting discovered during review be handled?+
Treat it initially as an unexplained configuration discrepancy, not as permission to rewrite the baseline. Preserve the observed value and context, then use the site's deviation process to investigate origin, duration and potential effects on records or operations. Compare available change history and approved intent before deciding whether to restore the baseline or propose a justified change. Avoid changing the setting merely to make the review pass. Document the investigation, disposition, verification and any retrospective impact assessment, including uncertainties that remain.
Primary sources
Want to see how Configuration Specification could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
