Showing fragments matching your search for: <strong>""</strong>

No matching fragments found in this document.

Misrouting would be misrouting indeed if one forwarded an improper despatch
to
anyone else and failed to shoot it back to its originator.

    An improper despatch is one which hasn't any business on the lines. This
is the
soul of Dev-T (Developed Traffic)-the  forwarding  of  improper  despatches.
One can
forward all the proper despatches in the world without  causing  Dev-T.  The
moment
one forwards an improper despatch to anyone  but  the  originator,  one  has
involved
other terminals and blocked their lines too.

    When you forward a despatch which should never  have  been  written  you
become
a party to the original Dev-T. Because the despatch is improper it  will  do
nothing but
snarl up In baskets all the way along the line. The ONLY correct  action  is
to send it to
the originator as improper.

                                  IMPROPER


    By improper we don't mean insulting or obscene. We mean:

    (a)     Has nothing to do  with  the  person  to  whom  it  is  sent  or
    forwarded, or

    (b)     Is already covered by  policy  which  should  be  known  to  the
    originator or the
    forwarding person.

    Under (a) we get nonsense despatches, despatches to  the  wrong  people,
obvious
lies, "everybody  says"  despatches,  despatches  calculated  only  to  make
trouble, useless
entheta and so on.

    Under (b) we have (A-HA! discovered!) the staff member who  is  ignorant
of
what's going on or what policies  cover  his  or  her  post.  We  reasonably
expect that, let us
say,  a  Registrar  has  read  those  policies,  old  and  new,  that  cover
registration. From a
general staff member we expect general planning to  be  at  least  known  as
general policy
letters all go into his or her basket and so have been available.

                                   OFFLINE


    A despatch is offline when it is sent to the wrong person.

                                  OFFPOLICY


    A despatch is offpolicy when originated by or forwarded by  someone  who
should
know that the matter is already covered by policy.

                                    DEV-T


    Traffic is  developed  (developed  traffic,  Dev-T)  by  originating  or
forwarding an
offline or offpolicy despatch to  anyone  but  the  sender.  This  may  seem
obscure when
we say a person originating an offpolicy despatch  should  not  send  it  to
anyone but the
sender-i.e. himself. He has the policy letters and general planning just  as
available to
himself as they are to anyone in Scientology orgs. So querying  by  despatch
about a
policy that can be looked up is just being too lazy to  look  it  up,  isn't
it? And putting
the load on one's seniors to do one's own work.

    When you forward an offpolicy despatch to anyone but the sender, you, if
you're
an executive:

    (a)     Involve other lines and

    (b)     Fail to take the opportunity to spot  a  staff  member  weak  on
    policy.

    Your duty as an executive is to send the despatch  to  its  source  with
orders to look
up policy on this. Your duty  is  not  to  quote  policy.  He  or  she  (the
originator) is the
one in mystery. Let the originator do the  work.  Nay,  worse,  prowl  about
that person a
bit and see how bad it is and order if  needed  a  full  check  out  of  the
person on policy
letters applying  to  his  or  her  post.  That's  one's  job  as  a  senior
executive. Not being a
computer for the org that turns out answers.

    Those  staff  members  who  habitually  forward  queries  or   something
adequately
covered in write-ups of their own  duties  to  others  are  DYNAMITE  in  an
organization.