No matching fragments found in this document.
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO POLICY LETTER OF 17 NOVEMBER AD 14
Remimeo
Sthil Staff
OFFLINE AND OFFPOLICY
YOUR FULL IN BASKET
(HCO Sec. Hat Check on all Executives and send me a despatch
personally each time you have done so-1 despatch per checkout.)
These two data are paramount in handling Scientology Communication Lines
and
your own In Basket.
1. The first duty of an executive is routing properly and seeing that
others
route properly. If an executive does not do this, then the lines in his
or her area will
stack up and become so tangled that nobody can follow them or get
through them.
This reduces income and dissemination-producing traffic volume-and
general effec-
tiveness. By "routing properly" is meant to see that everyone around
them routes
properly. Forwarding something already improperly routed creates Dev-T
and fails to
handle misrouting where it is occurring.
2. Know and make known policy. The first thought of an executive in
handling
a despatch requiring a decision must be: "Is this already covered by
planning or
policy?" If the executive knows existing policy he or she will find that
99% of
despatches "requiring decisions or solutions" are already cared for by
policy and, the
policy being unknown or non-existent, only then require "special
handling". In short,
if the matter is (a) covered already by policy, (b) if the sender should
know that policy,
or (c) if the first executive receiving the despatch knows policy, then
the despatch
should stop right there. This leaves flowing only traffic where policy
does not exist or
despatches about specialized matters.
The answer to put on a despatch demanding something already covered by
policy
is not some unusual solution. The answer on the despatch should be of two
kinds-(a)
to a person outside who would have no clue of policy, or (b) to somebody in
an org
who should know policy. In the case where (a) originates a query, the
proper answer is
"Policy on this is ______ ." In the case of (b) originating a query already
covered by policy the answer is "Look up old (recent) policy on this."
To outside people, policy is largely unknown. Thus one has to look up
the policy
or recall it to handle. But such seldom have questions needing subtle
points and field
policy is very well known in orgs such as "Give them what we promised if it
was
promised." "Keep entheta to a minimum" etc, etc. A simple "Sorry, it's
against
policy," is the simplest (and usually best) solution to outside wild
queries or ideas. Why
explain? You're not training a staff member.
Where a staff member is involved, it is expected he or she will know
policy or can
look it up.
If an executive gives the despatch querying for policy an "unusual
solution"
where policy already exists, then a problem will occur as this solution
will clash with
the other existing policy and the staff member goes spinning off to no-
policy no-org.
And the organization eventually becomes paralyzed. Any org that has an
executive
who doesn't keep up with policy and general planning and who is always
replying to
queries with unusual solutions of his own will soon find its income
dropping out the
bottom as it's being stuck on the track with counter-solutions. Soon,
nobody will
know what policy is, so in disagreement the org disintegrates. It is no
longer an
org-only a bunch of individuals working at cross purposes.
MISROUTING
Routing consists of forwarding a proper communication to its proper
destination
or, more pertinent to an executive, indicating how types of despatches are
routed to
staff members who route org despatches.