The customer is always right; and at the level where waivers are getting signed, us mere technical mortals would be overstepping our bounds (hugely!) if we interfered at the sharp end of the business.

The best anyone can do is to make sure the customer takes responsibility for what they exactly order, which in this case someone has obviously thought of already.

Even if it were a situation where your opinion was the best one for the business, it doesn't mean it's necessarily your call or even the head of your department. It seems more likely something the legal dept. or compliance would be responsible for - perhaps it was their advice to get the waiver in the first place. And then there's the fact that mostly in practice the lowliest salesman has the main authority when it comes to someone from another dept. coming along and trying to stomp all over their deals (more so, for done deals).

Update: beware also of colleagues who try to goad you into precipitous action that will get you fired (even held responsible for defaming the organisation) and instead abide by the decision of your own manager, 'just following orders' being the best panacea for this not being your problem.

-M

Free your mind

In reply to Re: Where to get this kindof advice. by Moron
in thread Where to get this kindof advice. by jpsartre

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.