Remote Triage: What to Record Before Calling a Technician

Identify the note by division, key number, pitch and stop, not by note name alone. “D is dead” could be any D on any keyboard on any stop; one documented fault-reporting convention, published on the organbench site, writes it instead as “Swell D27 8′ Oboe Horn.” The division names the keyboard. The key number counts chromatically up from the lowest C on that keyboard as key 1, so that under this convention middle C is key 25 and the D above it is 27. The pitch is the footage on the stop knob or tab, and the stop name says which stop was drawn when the note failed.

That is one practitioner’s convention rather than an industry standard, and the numbering has to be explained to anyone who has not met it. Even so, a report carrying those four pieces of information has removed the ambiguity a technician otherwise has to reconstruct on arrival.

Record what you heard or saw, when, and under what conditions, and stop short of what you think it means. For a note that will not stop sounding, a cipher, note which division and, if you can tell, which stop, and whether it started while you were playing or on its own. For an unusual noise, note where in the building it seems to come from, whether it is present whenever the organ is switched on or only while playing, and whether it changes with what you play. For anything intermittent, note the date and time and whether the church heating was on.

Notes not working and unusual noises are the examples diocesan guidance gives of what belongs in a console fault record. The point of writing them down is that the technician arrives with every fault reported since the last visit, not with the one you happened to remember.

For a note that does not sound, you can tell from the console whether the fault belongs to one stop or to the whole division. On any console where stops can be drawn and cancelled individually, draw one stop at a time on the affected division and play the note. If it fails on every stop of that division, the problem is common to the division; if it fails only when one particular stop is drawn and sounds on the others, it belongs to that stop.

David E. Wallace of Wallace & Company Organ Builders describes this as a scoping step, and that is what it is. It narrows the family of systems that could be responsible, so the technician arrives knowing where to start; it does not identify the failed part. Which part has failed is established at the instrument, not from the bench. Write down which result you got and which stops you tried, and stop there.

The words organists use for faults, cipher and dead note among them, describe what the instrument did, not why. Published institutional guidance uses both as symptom terms, shows that either can have more than one cause, and sends a minor note that will not sound or will not stop to the tuner rather than treating the symptom as proof that one component has failed.

Failing leather, to take one example, shows itself at the console as loud wind leaks, drastic drops in pitch and volume, an unresponsive organ, dead notes, inoperative stops, or a tear that blows out a reservoir or bellows. That is how firms that releather organs describe it to owners, and none of it is leather anyone can see from the bench. Record the symptom in the form it took. Reading a symptom into a likely cause is the job of our problem-diagnosis guidance and, finally, of the visit.

Reporting an instrument’s condition is an organist’s job; diagnosing it is not. The 1998 New South Wales Heritage Office and Organ Historical Trust of Australia guide expects an appointed organist to be able to assess and report the instrument’s condition, and reporting condition is a different thing from diagnosing it or authorizing work.

Read together, published owner-facing guidance from church bodies and conservation authorities asks four kinds of task of an owner: observing and reporting from the console or the room, keeping the environment and the space around the instrument right, keeping records between visits, and light exterior and keyboard cleaning. No one of those sources sets out the four categories on its own, and they were written for different jurisdictions and instruments. In all of them, every instruction that involves entering the organ, adjusting or handling pipework, or working on wiring or the blower is assigned to a specialist.

Gather information by watching and listening, not by experimenting on the instrument. The Canadian Conservation Institute’s keyboard-instrument guidance states three prohibitions: do not operate an instrument unless you are certain it is in working condition, never remove covers or components without the relevant expertise, and never casually touch organ reeds, because even the slightest contact can produce an audible change. That is conservation guidance for collections, which may be stricter than the practice of a parish instrument in weekly use, but the direction is the same. Wallace adds an ordinary playing habit to avoid: drawing couplers while holding notes, especially pedal keys on older tracker organs, is a documented precipitant of a mechanical-action cipher. If a fault only shows under conditions that make you uneasy about playing at all, stop using the organ and go back to Pipe Organ Repair and Emergency Guidance.

A new or louder noise from the blower area cannot be sorted out from a recording or a verbal description. Bearing noise, fan imbalance, motor electrical noise and leakage downstream in a reservoir or wind line can each produce it, and telling them apart requires someone attending the blower while it runs. That is an inference drawn from published accounts of how blowers are built and how they fail, rather than a rule any of those accounts states outright.

For the record, note when the noise began, whether it is constant or only while playing, and whether it has changed. Add a recording if you have one, but treat it as a timestamp rather than an answer. Work on the blower belongs to a specialist, so do not go in to investigate.

Whether an expression fault lies at the console or inside the box cannot be settled from the bench. In an electrically controlled system, the chain runs from the shoe at the console through the control system to an operator motor and the shade linkage; some older instruments instead use a mechanical linkage that transmits force. A console symptom can identify a nonresponse without proving whether the fault is at the shoe, control output, operator or linkage. Control-system and shade-operator documentation describes the electrical chain, and the New South Wales heritage guide restricts interior access; together they set the limit on owner-side observation without turning one mechanism into a universal model. Record what the shades do and do not do, on which division, and whether it happens every time.

An out-of-tune complaint may not be an instrument fault at all, and the console cannot settle that either. Pipes speak at the temperature of the air around them, and in one case measured by the Institute of British Organ Building the air at the Swell division fifteen feet above the player was 15 degrees Celsius warmer than at floor level. That is a single reported measurement, not a typical value, but it shows that a thermometer at the console can be far from the temperature at the pipework. Record the console reading and whether the heating was on, and give it as context rather than as evidence that the organ has gone out of tune. Whether the instrument needs tuning at all is a question for our tuning pages.

A good report routes your inquiry; it does not produce a diagnosis or a price. As of August 31, 2026, Craftsman Pipe Organs uses the information an owner supplies to route an inquiry, but a presenting symptom alone does not determine the service category the work is finally proposed under; the instrument, its condition, the owner’s goal, access and the required scope are reviewed before the work is categorized and proposed. As of the same date, inspection, diagnosis, assessment, document review or site evaluation may be required before a detailed estimate or proposal is prepared. A clear record gives that review something to start from; it does not replace it.

A written fault record kept at the console is the documented normal way an owner passes fault information to a technician. Guidelines approved in 2019 by the Diocesan Councils of the United Dioceses of Dublin and Glendalough recommend that a log-book be kept at the organ console in which users of the organ record faults, notes not working and unusual noises being the examples given, so that the benefit of a service visit is maximized. The same guidance asks the organ builder to supply a brief written report with each invoice and expects the Select Vestry to review it.

That is denominational guidance for one jurisdiction; it does not prescribe a format or a retention period, and the logbook records reported symptoms, not a technical assessment. Whether your own diocese, denomination or jurisdiction requires anything similar is a question for it.

The record works best when the technician closes each entry. David Knight, writing for the Council for the Care of Churches in 2003, recommended a tuner’s log book in which the organist records any faults and the tuner notes that he or she has attended to them. The advice dates from 2003 and is framed for the Church of England, and the Council has since been reconstituted as the Church Buildings Council. What it describes still does two things a phone call cannot: it shows the technician every fault reported since the last visit, and it shows the owner which reported faults were attended to and which were not. Keep the record between visits, whoever attends, and have it at the console before you call.