Installed System Configuration Baseline Register

Record the verified installed configuration and its controlled change references for a defined system baseline.

This Excel template contains prepared working sheets and completion notes on a separate sheet. Enter your project data and review the completed workbook before use.

Prepare project brief

The form prepares a separate brief; it does not fill the Word or Excel file.

Read product descriptions in your language. The Word and Excel template files are in English.

Installed System Configuration Baseline Register · Document preview — Selected page preview · XLSX

Learning

How to use this template

When you need it

Use this baseline when the project needs a controlled record of approved and installed equipment, software, or system configuration, particularly before testing, handover, modification, or investigation of a configuration discrepancy.

What it helps you decide

It makes the relationship between approved configuration and installed evidence explicit, allowing reviewers to identify unauthorized differences and assess later changes without relying on memory, obsolete drawings, or unverified equipment lists.

How to complete it

Populate Item / tag ID, System / function, Item type, and Model / version from the actual system inventory and controlled technical records.
Reference Approved configuration reference and Installed configuration evidence separately, then record Baseline date and Change reference so the status of each item is traceable.
Set Verification status based on completed comparison and describe Open discrepancy precisely, referring unresolved differences to the authorized technical or change decision process.

Who prepares and reviews it

A configuration or systems engineer usually coordinates discipline leads, commissioning staff, suppliers, and operations contributors. The designated technical authority controls baseline decisions, while competent reviewers verify installed evidence and resolve discrepancies through the project change process.

A mistake to avoid

Overwriting the approved configuration with the installed value hides the discrepancy and removes the evidence needed to decide whether a change was authorized.

Illustrative example

Illustrative example: a building-management controller arrives with a firmware version different from the approved configuration. The baseline records both the approved reference and installed evidence under the controller tag. The technical authority assesses compatibility and records the required change decision before final system acceptance.

Explore the wider topic

Document contents

Item / tag ID
System / function
Item type
Model / version
Approved configuration reference
Installed configuration evidence
Baseline date
Change reference
Verification status
Open discrepancy

Required inputs

Project name, location, company, document number and revision
Actual project scope, source records and responsible roles

Practical tools.
Professional judgment.

Confirm the adopted edition, local amendments, National Annex where relevant, and contract requirements.