Documented Pipe-Organ Project Delivery and Closeout

The written project documents control the scope and price of accepted work. Preliminary discussions, an inspection, a diagnosis, or a preliminary range help with planning, but none of them is a binding proposal and none of them is acceptance. Travel, mobilization, scope, price, and change control are likewise governed by the project-specific written documents for that instrument rather than by a published formula.

The scope is settled before it is written. The information an owner supplies routes the inquiry, but a presenting symptom alone does not determine the service category; the instrument, its condition, the owner’s goal, access, and the required scope are reviewed before the work is categorized and proposed. The written scope that results is the document every later record is measured against: findings are recorded against it, work performed is recorded against it, and the closeout documentation is sized by it.

Changed conditions or additional work require the applicable written approval process before they become part of the accepted scope. Opening a windchest or a console can reveal conditions an inspection could not see, and the right response is to document what was found, state what addressing it would involve, and wait for written approval rather than absorb the work silently into the project. Whether a change is priced as an addition or handled within the existing scope is a matter for the written project documents, not for a general rule.

The approval record then travels with the closeout documentation. A later reader can see not only what was done but why the scope grew and that the change was agreed in writing, which is the difference between a file that explains the instrument and one that only lists dates.

The record should keep three things separate: what was found, what was agreed, and what was actually done. Findings describe the instrument’s condition as observed, including conditions that fall outside the accepted scope. Agreed work is the written scope together with any approved changes. Work performed is what was carried out against that scope. Keeping the three distinct is what makes the file useful later, because a future technician can see which conditions were observed and left alone and which were addressed.

The record should also make clear what class of work was done. Guidance published in 1998 by the NSW Heritage Office with the Organ Historical Trust of Australia treats maintenance and repair as separate categories. Tuning, keeping air humidity at the necessary level, and renewing perishable materials such as leather, felt, and key coverings fall under maintenance. Thorough cleaning throughout the organ, rounding out crushed or dented pipes, regulation and re-bushing of the action, and measures against wood-damaging insects, oxidation, and deterioration fall under repair. A record that names the category as well as the date tells the next reader whether the work renewed a consumable or corrected a fault.

Because the instrument stays and the people change. The Organ Historical Society’s Guidelines for Conservation and Restoration, adopted in 2008, define documentation as recording in a permanent format the information derived from conservation activities, and state that copies of examination and treatment records should be given to the owner or authorized agent. The American Institute for Conservation’s Code of Ethics and Guidelines for Practice says the same for cultural property generally. Documentation should be produced and maintained in as permanent a manner as practicable, copies of examination and treatment reports must be given to the owner, custodian, or authorized agent, and the recipient should be advised to keep those materials with the property. That is guidance from conservation bodies, not a warranty. Its point is that the file belongs with the instrument and its owner, whoever did the work.

A staged service history shows what that continuity looks like in practice. The institutional record for Skinner Opus 769 of 1929 lists console releathering in 2004, chest releathering in 2007, blower and motor restoration in 2011 after flooding, rewiring in 2014, and reed restoration in 2019 to 2020. Spread across two decades, a history like that is legible to a later technician only because each stage left a record, and the closeout documentation an owner keeps from each project is what builds it.

Enough for the owner to know what was configured, which firmware revision is running, and where any backup of the configuration is kept, without confusing those records with the authority to change the configuration. Manufacturer documentation draws that line consistently. Across four generations of Peterson products the same division of authority appears: operation belongs to the organist, configuration to the organ builder or technician. Peterson’s 2024 ICS-4000 user manual places folder creation, configuration, and software updates in a Supervisor Mode gated by a changeable four-character password held by the organ builder or another authorized person.

Syndyne’s MS8400 builder manual lists firmware update alongside backing up and restoring the system’s cards and displays firmware revisions under its diagnostics, and the MS8400 configuration manual recommends a firmware update only when it addresses a particular bug or a desired feature. For an owner, the useful record is therefore which system is installed, which firmware revision it carried at handover, and whether a configuration backup was made and where it is kept.

Receiving those records is a different question from holding configuration authority. Whether the owner also holds the credential that opens configuration is a separate, project-specific matter settled in the written project documents, and the closeout record does not change what the manufacturer’s documentation reserves to the organ builder or an authorized credential holder.

It contains the documentation the accepted written scope calls for: the findings, the agreed work, the work performed including any approved changes, and the closeout requirements the written project documents set for that project. Because the written scope controls it, the package for a tuning and regulation visit is short and the package for a rebuild is long, and neither follows a universal deliverable list. Where warranty applies, its terms are provided in the written proposal or project agreement, and eligible third-party components may carry separate manufacturer warranties; keeping those documents with the closeout documentation puts the terms and the record of work in the same file.

An open recommendation is recorded as a finding, not as accepted work. Conditions observed during the project but outside the written scope belong in the documented findings so the owner can plan for them, but a recommendation, a preliminary range, or a conversation at handover is not a binding proposal. It becomes work only through written project documents of its own, with scope and price stated there. Recording open recommendations this way keeps the file honest about what the instrument still needs and gives the owner a starting point for the next scope, whoever is engaged to carry it out.

This page covers documentation and closeout only. Who performs the work and how it is supervised, including disclosed outside domain expertise, is covered at Direct-Workforce Service. What manufacturer independence means for an owner is covered at Manufacturer Independence. How recurring and multi-instrument work is structured is covered at National and Multi-Instrument Programs.