<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><DIV>Wim,</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>One of the weaknesses of this program (or maybe it's a strength) is that you are making a set of service recommendations in a vacuum. It's interesting to see which members recognize that their approach to the instrument would be influenced by who's playing it, at what level, possible budget constraints, piano's fair market value, sentimental attachment, etc. In both cases, as I recall, there was a piano discussed that in fact was on its way to the dumpster! Most, but not all, figured that out before being told. . . but maybe it could have gone to a beginning technician as a "practice" piano. It's rarely a black and white issue.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Carl</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><BR class="khtml-block-placeholder"></DIV><BR><DIV><DIV>On Oct 25, 2007, at 6:36 PM, Willem Blees wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><WBR>So what happened at the meetings? How different were the resutls?<BR> <BR> <DIV style="CLEAR: both">Wim</DIV> <BR> <BR> -----Original Message-----<BR> From: Carl Root <<A href="mailto:carldroot@comcast.net">carldroot@comcast.net</A>><BR> To: College and University Technicians <<A href="mailto:caut@ptg.org">caut@ptg.org</A>><BR> Sent: Thu, 25 Oct 2007 7:36 am<BR> Subject: Re: [CAUT] CAUT testing model<BR> <BR> <DIV id="AOLMsgPart_0_0de61ed5-0a7f-4f1b-a686-297f9bfcd397" style="FONT-SIZE: 12px; MARGIN: 0px; COLOR: #000; FONT-FAMILY: Tahoma, Verdana, Arial, Sans-Serif; BACKGROUND-COLOR: #fff">(Wim just posted while I was writing this . . .) <BR> <BR> I've always felt that diagnosing a piano's problems, coming up with recommendations that are consistent with the piano's use, budget, and time constraints, then being able to communicate all of this to the client is at the heart of good piano service. <BR> <BR> Here's a format for a chapter tech session that I did years ago in both DC and Baltimore: Assemble a half dozen pianos - the more variety in terms of age, conditions, etc, the better. Divide the attendees into teams. Give them time to look over their assigned piano, agree on the recommended work, then report their findings. <BR> <BR> Ideally, you would have each member look at each piano independently and write out a report. (not enough time, of course . . . . maybe an all-day seminar!) <BR> <BR> Then watch the fur fly! <BR> <BR> Carl <BR> </DIV> <DIV class="AOLPromoFooter"> <HR style="margin-top:10px;"> Email and AIM finally together. You've gotta check out free <A href="http://o.aolcdn.com/cdn.webmail.aol.com/mailtour/aol/en-us/index.htm?ncid=AOLAOF00020000000970" target="_blank">AOL Mail</A>!<BR> </DIV></WBR></BLOCKQUOTE></DIV><BR></BODY></HTML>