In another thread I suggested making an editable "boilerplate" for an instruction/operating guide. Whether you do that or not is your business, but if you do you could reference the fact that "operating instructions have been provided" somewhere within the boilerplate of your contract, specifically your disclaimer area. Kind of an "I told you so" up front. That way if they kybosh something by going contrary to your intructions you have more ground to stand on when you say "pay me, or learn to fly". I'm in the IT industry and once in a while you just have to push someone out of the nest after repeat episodes of supporting the same (self-induced) problem. Your main problem is going to be with people who "fib" about what they've done. They will be (and probably already are) showing their stripes.
It goes like this: Did you reboot the computer? "NO, it was like this when I walked up to it." Did you see a blue screen for moment? "Yes, I did. What was that about" (They obviously rebooted the computer.)
Did you reset the Pronto ?? "No, it was....."
This message was edited by Sheik_Yerbouhti on 05/26/02 10:56.13.
You are transparent! I see many things; I see plans within plans. The Spice must flow!
