GENERAL NON-REMIMEO

1. mimeo distribution based on one copy for master files, one copy to LRH Comm, one copy to the Guardian or A/G, one copy each to the FR, ED(CO), HES and OES, one CODV to the Qual Library reference files and one copy to the reference files of all bulletins and PLs kept in reception for staff, one copy to the div head(s) and the department head(s) concerned and one copy to the post(s) in the department(s) concerned. (BPL 14 Apr 69R) 2. key personnel and orgs get copies of it. Limited number of copies. (SH Spec 54, 6503CO9) 3. there are two classes of non-remimeo. One is limited non-remimeo meaning distribution is: master files, HCO Secretary, and Assn/Org Secretary. The other is general non-remimeo, meaning master files, HCO Secretary, Assn/Org Secretary, reception reference files, and department head and post concerned to whom the data applies. (HCO PL 2 Jul 64) 4. the same as limited non-remimeo but somewhat broader. These usually deal with broader points of admin or tech of interest to one or two production departments as well as the HCO Secretary and Assn/Org Secretary. They are never strewn about or broadly republished as they could be misunderstood. (HCO PL 2 Jul 64)

a code indicating an issue should not b e mimeoed again when received but should be limited in its distribution. These issues usually deal with broader points of admin or tech of interest to one or two production departments as well a s the org senior execs. They are never strewn about or broadly republished as they could be misunderstood. See also mimeograph in this glossary. —New Organizational Structure Approved 5.3.91

a code indicating an issue should not be mimeoed again when received but should be limited in its distribution. These issues usually deal with broader points of admm or tech of interest to one or two production departments as well as the org senior execs. They are never strewn about or broadly republished as they could be misunderstood. See also mimeograph in this glossary. So what I'm doing is that I put a lot of this stuff on what's called the General Non-Remimeo line - that is to say, key personnel and orgs get copies of it - so that the technology does exist, see? And that lets, of course, Mimeo here simply type them out from the written notes, type them directly onto a stencil, run them off, don't you see, and make this limited number of copies and so forth and distribute them.

a code indicating an issue should not be mimeoed again when received but should be limited in its distribution. These issues usually deal with broader points of admin or tech of interest to one or two production departments as well as the org senior execs. They are never strewn about or broadly republished as they could be misunderstood. See also mimeograph in this glossary.a code indicating an issue should not be mimeoed again when received but should be limited in its distribution. These issues usually deal with broader points of admin or tech of interest to one or two production departments as well as the org senior execs. They are never strewn about or broadly republished as they could be misunderstood. See also mimeograph in this glossary. So what I'm doing is that I put a lot of this stuff on what's called the General Non-Remimeo line-that is to say, key personnel and orgs get copies of it-so that the technology does exist, see? And that lets, of course, Mimeo here simply type them out from the written notes, type them directly onto a stencil, run them off, don't you see, and make this limited number of copies and so forth and distribute them.