<?xml version="1.0" encoding="UTF-8"?>
<itemContainer xmlns="http://omeka.org/schemas/omeka-xml/v5" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://nam.maydayrooms.org/items/browse?output=omeka-xml&amp;page=14" accessDate="2026-04-15T09:57:58+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>14</pageNumber>
      <perPage>10</perPage>
      <totalResults>310</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="285" public="1" featured="0">
    <fileContainer>
      <file fileId="295">
        <src>https://nam.maydayrooms.org/files/original/54cf8c44baba1264819f4933ad17fb61.pdf</src>
        <authentication>134374e531addfbafecb2e5e5331c4d0</authentication>
      </file>
    </fileContainer>
    <collection collectionId="4">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="7">
                  <text>Professional Issues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="8">
                  <text>A cohort of NAM members became engaged with the professional registration body, standing&#13;
as elected councillors on the Architects Registration Council and its various committees. Hitherto entirely dominated by&#13;
the RIBA bloc, the Council began to yield to a new dynamic through NAM's involvement, enabling fresh perspectives on&#13;
such issues as mandatory fee scales, greater lay representation on the body, ethically-based standards of professional&#13;
conduct, etc.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1580">
                <text>Correspondence with ARCUK Registrar on Professional Conduct</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1581">
                <text> K J Porder Registrar ARCUK&#13;
73 lem&#13;
.&#13;
-&#13;
Street&#13;
Roath Cardiff&#13;
196 Albany Road&#13;
(c) I need ct rification on the following questions:&#13;
I an attempting to draft a response to your letter Of 13 April re Limited Liability. However, before £ Can answer the issuas Yaised under (a) to&#13;
1. What reference does the Act make to Professional Misconduct or Code of Conduct? :&#13;
2. Since no definition of "professional misconduct! appears to be offered in the Act, what legal Standing does any definition inplicit in the rules and Principles of the Code of Conduct shave? eas&#13;
&amp;- Has this ever been put to the test? !&#13;
5- Where, when, by whom, and on what Criteria was the Code brought into being? 6 Was recourse to the Privy Council made for the adoption of the Code?&#13;
Yours Sincerely&#13;
e&#13;
8. Ina Situation where the Act and the Code might be interpreted to be contradictory, wnat legal Standing does the Code have?&#13;
3. Would a legal interpretation o£ ‘misconduct! in a ‘court of law conform to that enshrined in the Code of Conduct?&#13;
7. Has recourse to the Privy Council been made for any alterations or acditions to the Code?&#13;
9. Has the Situation described in 8 €ver been put to the test, i-e., has ARCUK'S decision On misconduct ever been apnealed against ina court of law2 r&#13;
= apologies for imposing such heavy demands on you but I would appreciate an €erly response since you have asked for replies by 31 May.&#13;
fane Delaney (Ms)&#13;
+eeeserene&#13;
&#13;
 Ms Anne Delaney 196 Albany Road&#13;
Roath Cardiff&#13;
Yours sipcerely,&#13;
12'May 1978 =&#13;
4. Architects Registration Council of the United Kingdom&#13;
CRTABUUSHED UNDER THE ARCHITECTS IMEGISTRATION! ACTS 1931 To 1038&#13;
73 Hallam Street London WiN 6EE Tel: 01-580 5861&#13;
Registrar:Mrs-NockDawsene MBE KENNETH J.FORDER, M.A&#13;
Dear Ms Delaney, =. ° pact Xt&#13;
Thank you very much for your letter of 10 May. I think it might help&#13;
if I reply immediately on the more straightforward&#13;
issues that you raise, and I will write to you further on other points as soon as I have managed&#13;
to carry out the research. : : i&#13;
ear face&#13;
I think many of your points are answered in the enclosed copy Ofmauens summarised history of the ARCUK Code, together with a copy of the first edition in 1936. The following are my preliminary observations on your: questions:&#13;
- 1. The only reference to disgraceful conduct is contained in ; Section 7 of the principal Act (copy enclosed). There is&#13;
no reference to a Code in any of the legislation.&#13;
3. It is my view that disgraceful conduct has never been formally&#13;
4. interpreted legally but I will look into this. :&#13;
_5. The enclosed history will tell you all you need to know. 6. No.&#13;
Yo Bo&#13;
8. The question is a little too sweeping. If a situation arose&#13;
where the Act and the Code appeared to be in conflict then clearly ~ theCode would have to give way but only to the extent that the Act takes precedence. -&#13;
2. I find myself in some difficulty here because of the wording&#13;
you use. The Code has no ‘legal standing’ but it is a guide which the profession follows. Strictly speaking one can&#13;
be guilty of disgraceful conduct without breaking the terms&#13;
of the Code and conversely there are circumstances in which&#13;
one can break the terms of the Code without committing disgraceful conduct.&#13;
f&#13;
9. The usually quoted case where an appeal was lodged to the High Court against a decision of the Council was the Hughes v ARCUK&#13;
in 1957. I enclose herewith a copy of the relevant passage from the Judgment. I will check whether there have been any other cases.&#13;
&#13;
 =aeita ates&#13;
/&#13;
ye&#13;
advising against.&#13;
etc.&#13;
History of the ARCUK Code&#13;
On 11 March, 1932, the Council received a report of the Committee of Ways and Means which contained, inter alia, a recommendation that a Code of Professional Conduct was desirable despite having received Counsel's Opinion&#13;
to the undesirability of advertisements by surveyors who were also architects.&#13;
The Council, in debating the matter, considered — if there was to be a&#13;
Code - that it could be built up gradually by means of the precedents from the Discipline Committee; or the Council could give architects proposing to register&#13;
It was agreed at this meeting to defer a recommendation to draft a Code, partly because there were a number of other tasks urgently needing action and partly because in any event the Discipline Committee could not be appointed for some months. ‘ :&#13;
In March 1934 the PPC recommended the Council to inform an architect "that it is unprofessional and contrary to 2stablished custom to advertise". This was&#13;
Another architect at the same time was seeking information about his position with regard to advertising, hidden commissions; soliciting and trading, and pointing out that the Act made no provision for a Code. He was told that, in general,&#13;
these were matters of unprofessional conduct and contrary to established custom&#13;
but it was for the Discipline Committee to decide what was disgraceful. The&#13;
architect challenged this reply, pointing out that no Code had been approved by the Privy Council, and asked if the RIBA Code "with all its loose application" was accepted in the Courts.&#13;
Another architect was informed it was not in accordance with established&#13;
custom for an architect to trade as a builder. It was for the Discipline Committee&#13;
It was also "not in accordance with established custom for an architect to engage in trade”. (Very broad statement‘)&#13;
Other cases dealt with alleged supplanting (referred to D.C.) and soliciting and supplanting; and the Chartered Surveyors were asked to refer in their Code&#13;
some idea of what they must not do.&#13;
to stop newspaper advertisements.&#13;
&#13;
”&#13;
 spirit common to the codes."&#13;
2.&#13;
There was however a hold up with regard to referring cases to the Discipline Committee because they had no regulations yet.&#13;
After a motion had been received from an architect which ended with the following words&#13;
"That this Council give a ruling that may serve as a guide to the public and the profession as to what may be considered ‘established custom’ and what conduct would normally lie outside such ‘established custom’. (Code of Practice) That sanction&#13;
be obtained from the Privy Council for such regulations”&#13;
the PPC approved the principle of a Code of Professional Conduct which banned architects from advertising "his architectural services publicly", "receiving commission not disclosed" and "soliciting work by means of Ppaid agents"&#13;
In due course however, and before any ARCUK Code had been formulated, the Discipline Committee had heard its first case, where mention was made to two&#13;
Codes - that of the RIBA and that of the TAAS, and the Discipline Committee Report contains the following paragraphs: é cs&#13;
"(g) Each code must embody, its existence would be meaningless unless it did embody, those rules of conduct which its framers and administrators hold to be binding on themselves as practitioners of an honourable calling, while every professional man knows that many such rules express the solution of doubts which have arisen in practice. A practitioner who has any cause to doubt what his own course of action ought to be can seek guidance in the solutions tested by experience (or formulated by expen oos persons), and set forth in the codes,&#13;
The essential features of both codes, it must be believed, would in spirit be accepted by the architectural profession even had they remained unwritten, and the Committee conceives itself entitled to apply these codes in the interpretation of Section 7 of the Act and to find a registered person guilty of conduct disgraceful in an architect if he be shewn to have contravened the&#13;
The Council received a further Counsel's Opinion dated August 1934 which ~ contained a preference to "allow a code as to professional conduct to grow up gradually by means of publication and circulation from time to time” of Discipline Committee decisions. This view was based on the idea that it would leave the Council "unfettered by definitions of professional misconduct" whereas a "specified and definite code” would make it difficult for the Council to&#13;
remove a man from the Register "unless his conduct were ‘shown to fall within&#13;
&#13;
y.&#13;
the four corners of the code".&#13;
 pursue”.&#13;
comments.&#13;
to approve the draft Code.)&#13;
remained unaltered until 1945.&#13;
However, the Opinion did state that the Council could, without statutory authority, publish and send to registered persons "a statement enumerating practices or modes of conduct which they consider it undesirable for registered persons to&#13;
A copy of the March 1936 Code is attached from which it will be seen that it&#13;
Again the Council were reminded that the Act contained no express power to formulate a code as to professional conduct or misconduct. The Council was also advised that the Privy Council "would probably be reluctant -to give their Sanction to a code of professional conduct dealing (of necessity) with matters as to which a wide diversity of views might be held.&#13;
This statement should contain no reference to Section 7 of the Act and should show on the face of it that it was published merely for guidance.&#13;
In June 1935 the Council were informed that the PPC were drawing up a draft statement as referred to in the above paragraphs’ A suggestion/that che Draft Code, together with Scale of Fees and Conditions of Engagement, be submitted to all bodies mentioned in the First Schedule, and to every registered person for&#13;
On 20 March 1936 the Council had before it a "draft Code of Professional Conduct for Registered Architects" for the guidance of architects which was submitted by the PPC who had resolved unanimously that it be submitted to Cannes "as an agreed document".. In submitting the Draft the Committee said since it&#13;
had received unanimous approval in Committee to refer it to the constituent bodies would cause unnecessary delay. They proposed however to send copies to all registered persons but without inviting comments, but to invite-the Unattached architects to forward comments to one of the Council members they had elected.&#13;
(One Council member elected by the Unattached dissented from the decision to&#13;
In December 1944 the PPC recommended that the Code be revised generally. This arose from Counsel's Opinion obtained to assist in dealing with questions concerning architects inyolved in property development - buying and selling land and buildings.&#13;
&#13;
 registered person.&#13;
branches to discuss the new Principles.&#13;
4.&#13;
In February 1945 the Council had a draft revised Code before them in a totally&#13;
In November 1945 the PPC reported to Council on the comments received from the RIBA on the draft, but some of the RIBA suggestions were not accepted. One&#13;
different format and it was agreed that the draft be submitted to the constituent bodies and to the representatives of the Unattached architects for observations. This draft Code consisted of a Preamble, Principles and Examples.&#13;
Counsel was asked to vet the final version; and in March 1946 the Council&#13;
Early in 1960 the Code was reprinted in a new format; and because there had been a number 6f amendments made to it since 1955, a copy was sent to every&#13;
Again the Code was subject to a number of amendments/clarifications and in June 1969 the PPC were again asked to review the Code as a whole and to report back to the Council. As the RIBA were also looking at their Code as a whole&#13;
it was agreed in October 1969 to set up an ad hoc joint working group to enable&#13;
the zwo bodies to proceed in step. By March 1970 a preliminary draft of the Principles and Rules of Professional Conduct was ready and it was agreed it be circulated to the architectural constituent bodies for discussion. In June 1970 the Council were informed that meetings were being held in the RIBA Regions and&#13;
or two comments had also been received from the ABT and AA.&#13;
In December 1948 the Code was amended to give a time limit after which architects could not be house agents or auctioneers. The RIBA, IAAS, AA and ABT approved; FAS had made no comments and the Unattached had divergent views, but agreed to go along. :&#13;
at&#13;
After the Code had been amended a number of times, on 17 October, 1952, the&#13;
Council resolved that the PPC should review the Code "as a whole in its relation to the Codes of any of the constituent bodies of the Council", if necessary conferring with such bodies. A Sub-Committee of the PPC was set up and in October 1954 a draft new Code was submitted to ‘Council and finally approved in December 1954 for circulation to the profession with the 1955 Annual Report. Its format was not dissimilar from the previous Codes.&#13;
were informed that a new Code had been published.”&#13;
The work on amending the Code was then taken over by the RIBA but in March 1975 the Council were informed that the PPC had asked the Registrar to send&#13;
&#13;
T’.copies of the draft Code to the other architectural constituent bodies.&#13;
Eventually a new Code, different in form and format but not greatly different in meaning was published on 1 January 1976.&#13;
 a&#13;
&#13;
 ©&#13;
'&#13;
©&#13;
F&#13;
Architects’ Registration Council of the&#13;
United Kingdom 68, PORTLAND PLACE, W.1.&#13;
Code of Professional Conduct for Architects&#13;
The following Rules have been drawn up for the guidance of architects.&#13;
While it is not intended to lay down a hard-and-fast line between what is, and what is not, legitimate, the object of the Rules is to provide a general standard of professional practice, the breach of which} by an architect, may render him liable to be adjudged, by the Council, guilty of disgraceful conduct.&#13;
1= (1) Reniuneration in respect of architectural work consists (a) in the case of an employee,&#13;
of salary, and (6) of architects in private practice, of protessional fees. In the case of (6) the client should be informed at the outset of the rules of employment of architects and the scule of charges upon which remuneration is based.&#13;
N.B.--For the purpose of this Code the Conditions of Engagement and Scale of&#13;
Charges published by the R.I.B.A. or other constituent body is recommended. 4&#13;
(2) Au architect MUST NOT:— / o&#13;
(a) Accept any work which involves giving or recviving discounts or commissions, nor&#13;
may he accept any discount, gift or commission fron: Contractors or Tradesmen whether employed upon the works or not.&#13;
(b) Advertise or offer his services by means of circulars or otherwise, nor may he make paid announcements in the Press.&#13;
(c) Attempt to supplant another architect, nor must he compete with another architect by means of a reduction of fees or by any other inducement.&#13;
(d) Permit the insertion of any clause in tenders, bills of quantities or other documents which provide for payment to be made to him by the Contractor whatever may be the consideration, unless with the previous knowledye and approval of his client.&#13;
(ce) Carry on or act us principal, partner uv «anager of a company or firm trading in materials used in building, or whose activities are connected with the building industry.&#13;
(/) Permit the business of auctioneering or house ugency to form part of his practice.&#13;
NUTE to Parageaph .(f)&#13;
Extract jrom Counce Motates of June 24ynt, 1936:—&#13;
RESOLVED thar&#13;
Where busine: us au Auctioneer or House Agent was being carried on at the time of registration no uction be taken in the matter, but that any Kexisterad Architect attempting to, or who has attempted to, start any business as Auetivieer or Huse clvent after the date of his registration be informed that such action is not in accordance with the rocoguisal custom of the Architectural&#13;
profession. .&#13;
;&#13;
&#13;
 (3) An arcisitect MUST:--&#13;
(a) Be remunerated solely in the cuse of an employee by his salary and in the case of a&#13;
(4) An architect MAY:—&#13;
(g) Act us architect or joint architect tor a work which ts or has been the subject of a competition, in which he is or has been engaged as an assessor.&#13;
(A) Act as architect or joint architect for a work which is or has been the subject of an abandoned competition, if he is or has becw viticially nominated as assessor, or approached by the promoters for the purpuse of acting as such. Z&#13;
practising awchitect by professional fees, und must not accept remuneration from auy other source in connection with the works and duties entrusted to him.&#13;
(b) Before accepting an appointment or instructions to proceed with any work upon which it is obvious another architect has been employed, communicate with the architect last employed with a view to ensuring that his engayement has been properly terminated.&#13;
(a) Be architectural consultant or adviser to building contractors, decorators, furniture designers, estate development firms or companies or firms or companies trading in materials used in or whose activities are otherwise connected with the building industry, provided that:— : ,&#13;
(1) He is paid by fee and not by commission on sales or profits thereon. (2) He docs not solicit orders for the firm or company. “5&#13;
(b) Use the word “* Architect ” in connection with his appointment, and his name may appear on the stationery of the firm or company as architectural consultant or adviser. :&#13;
(c) Be a Director of any company (except those. excepted in Clause 2 {e)), including a building society registered under the Building Societies Act, and may allow his name and the word ‘' Architect ’ to appear on the notepaper of the company.&#13;
(d) Sign his buildings and may exhibit his name outside his office and on buildings in the course of construction, alteration and/or extension, provided that it is done in an unostentatious manner, If a client so desires, the architect’s name may remain upon the building for a period not exceeding twelve months after its completion provided that the board does not display ‘ fo Let’’ or “ For Sale ’” or similar notices.&#13;
(5) Although there is no objection to an architect allowing signed illustrations and descrip- tions of bis work to be published in the Press, with reference to such illustrations or descriptions it in contrary to professional custom to give monetary consideration for such insertions or to allow such insertions to be used by the publishers for obtaining advertisements from unwilling contributors.&#13;
&#13;
/&#13;
(6)&#13;
(7) When architects are ucting as surveyors or town planners in connection with the development of land, announcements may be made in the Press and on notice boards in connection with such development, provided that such announcements are made in ath unostentatious manner.&#13;
(8) In all questions arising between the employer und contractor an architect must act in an impartial manner. He must at all tics interpret the conditions of the contract with entire fairmess as between cmployer and contractor.&#13;
(9) Quantities—It is desirable that in cuses where an architect takes out quantities for buildings he should be paid directly by the client and not through the contractor.&#13;
y&#13;
7&#13;
 Note: —&#13;
March 20th, 1936. Reprinted April 1st, 1g4T.&#13;
By Order of the Council,&#13;
a PEMBROKE WICKS&#13;
: Pr Registrar. |&#13;
f‘&#13;
Architects who are appoitited surveyots lo recoguiscd estates muy announce land or sites or premises tor sale or letting in conteciion with their uppoininents.&#13;
Architects are recommended to bring this Code to the notice of their employees.&#13;
&#13;
 7&#13;
Dissraceful Conduct as defined by Mr. Justice Devlin in his Judgment in Hughes v A.R.C.U.K.&#13;
7, 731/59&#13;
The Architects (Registration) Act 1931 Section 7 gives the Council power to strike the name of an architect from the register if he has been "suilty of conduct disgraceful to him in his capacity as an architect". I cannot accept the argument that the term "diseraceful” is&#13;
in any sense a term of art. In accordance with the usual&#13;
rule it is to be given its natural and popular meaning. But&#13;
it is qualified by the phrase "in his capacity as an architect". The effect of that qualification is twofold. First, the&#13;
conduct must not only be what would ordinarily be considered&#13;
aeerecesale but it must also be a disgrace which affects hin professionally; to that extent the qualification diminishes&#13;
the term. sgoondlky, conduct which is not disgraceful for an )&#13;
ordinary man may be disgraceful for a professional man: to that extent the qualification amplifies the term. But the amplification does not require that "disgraceful" is to be given any technical meaning: it requires only that the ordinary meaning of the word should be applied in relation&#13;
to the special obligations and duties of a professional man. It must not be forgotten that if the finding of the Committee stands, anyone may hereafter say of Mr. Hughes with impunity that he was struck off the register for disgraceful conduct&#13;
and may add that that means what it says.&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1582">
                <text>AD/ ARCUK Registrar</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="1583">
                <text>John Murray</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1584">
                <text>May 1978</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2335">
                <text>Correspondence with ARCUK Registrar on Professional Conduct</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="283" public="1" featured="0">
    <fileContainer>
      <file fileId="293">
        <src>https://nam.maydayrooms.org/files/original/689c65412a67b4ce1c4467e7c7d6da94.pdf</src>
        <authentication>3028a6765814c68ab09a6014283e77f6</authentication>
      </file>
    </fileContainer>
    <collection collectionId="4">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="7">
                  <text>Professional Issues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="8">
                  <text>A cohort of NAM members became engaged with the professional registration body, standing&#13;
as elected councillors on the Architects Registration Council and its various committees. Hitherto entirely dominated by&#13;
the RIBA bloc, the Council began to yield to a new dynamic through NAM's involvement, enabling fresh perspectives on&#13;
such issues as mandatory fee scales, greater lay representation on the body, ethically-based standards of professional&#13;
conduct, etc.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1570">
                <text>Letter from Sally Oppenheim, July 1979</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1571">
                <text> John Murray Esq Unattached Architects ARCUK&#13;
75 Hallam Street London wW1&#13;
‘ Cer Als FM abi&#13;
DEPARTOMFETNRATDE&#13;
1VICTORIA STREET (&#13;
LONDON SWI1H OET&#13;
TELEPHONE DIRECTLINE 01215 2©62&#13;
y&#13;
w/ July 1979&#13;
Private Secretary&#13;
V3975&#13;
Fromthe SWITCHBOARD 012157877 Minister of State&#13;
for Consumer Affairs&#13;
The Rt Hon Sally Oppenheim MP&#13;
I am writing to thank Mr Koebuck for his letter of 12 July to the Minister of State for Consumer Affairs Summariisng the position of the Unattached Architects. (Mr Roebuck asked that any further&#13;
correspondence should be addressed to you).&#13;
Mrs Oppenheim has asked me to say that she too found the meeting on&#13;
10 July a very useful one, and that in considering what action is necessary following the Monopolies &amp; Mergers Commission report on architects' scale fees, she and the Secretary of State will take fully into account the points that you, Mr Roebuck and the other representatn of the Unattached Architexts have made.&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1572">
                <text>Ken Thorpe</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="1573">
                <text>John Murray</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1574">
                <text>07/06/1978</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2334">
                <text>Letter from Sally Oppenheim, July 1979</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="282" public="1" featured="0">
    <fileContainer>
      <file fileId="292">
        <src>https://nam.maydayrooms.org/files/original/f18c2a4a700912a94b5dbb547d779b99.pdf</src>
        <authentication>bfbd1c1a3189d7613223bfea7b9da0ac</authentication>
      </file>
    </fileContainer>
    <collection collectionId="4">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="7">
                  <text>Professional Issues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="8">
                  <text>A cohort of NAM members became engaged with the professional registration body, standing&#13;
as elected councillors on the Architects Registration Council and its various committees. Hitherto entirely dominated by&#13;
the RIBA bloc, the Council began to yield to a new dynamic through NAM's involvement, enabling fresh perspectives on&#13;
such issues as mandatory fee scales, greater lay representation on the body, ethically-based standards of professional&#13;
conduct, etc.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1565">
                <text>Letter to Sally Oppenheim, Minister for Consumer Affairs, July 1979</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1566">
                <text> The Rt Hon Sally Oppenhéem MP Minister of State for Consumer Affairs Department of Trade&#13;
1 Victoria Street&#13;
LONDON sw1&#13;
Dear Minister&#13;
(i) (ii)&#13;
(iii)&#13;
(iv)&#13;
(v)&#13;
(vi) (vii)&#13;
ARCUK oe 73 Hallam Street LONDON w1&#13;
12 July 1979&#13;
UNATTACHED ARCHITECTS&#13;
PROPOSALS TO INCREASE COMPETITION IN ARCHITECTS! SERVICES&#13;
We would like to thank you for Tuesday's very useful meeting to discuss the abandonment of architects' mandatory fee scale and I would like to summarize our position as follows&#13;
The Mandatory Minimum Fee having been abandoned, architects should be free to compete in terms of fee as well as quality of service&#13;
The removal of the Fee Scale's mandatory status can be speedily and simply achieved by requiring ARCUK to amend its rules (as scheduled in Way Ahead). This would enable all architects who wish to depart from the Monopiy to do so&#13;
Any new recommended fee systems should be based on ranges of architects' own costs instead of the discredited 'ad valorem! method&#13;
It may be considered simplest for the Government (DoE) to prepare the primary recommended fee scale for its own use in assessing value for money in public sector commissions thus avoiding the additional administration and expense of a new agency&#13;
Recommended fee scales may be prepared by other bodies both&#13;
within and outside the profession provided the following conditions are observed&#13;
a) Copies are deposited with Minister for Consumer Affairs ° b) ‘The non-mandatory status is clearly printed on all&#13;
documents in which reference to the fee scale is made&#13;
The Government should conduct periodic reviews (the first within&#13;
3 years) to ensure that a de facto monoyiy is not being established through RIBA dominance . It may be appropiate to consider providing the&#13;
OFT with these review powersein the proposed Competition Bill. The apparently enhanced competative conditions arising from architectural design competitions must be set against the disadvantages of considerable abortive work and time and reduced client influence in the development of the brief and we feel&#13;
that design competitions would thus continue to be of benefit in only limited circumstances&#13;
&#13;
 A&#13;
(pit(4 DAVID ROEBUCK&#13;
On Behalf Of JOHN ALLAN ROBERT MALTZ&#13;
JOHN MURRAY&#13;
Yours sincerely&#13;
Our proposals now combine the benefits of competition in both quality and fee in suggesting that architects in competing for a commission should include a fee quotation alongside full information as to their experience, resources and capabilities. Quotations should be explicit as to architects costs and could be presented in the format drafted in Appendix I of our report.&#13;
(vidi) Fee quotation and then negotiation would probably be the most effective method given the obvious disadvantages of straight ES tendering.&#13;
As agreed, a straight tendering system apart from being vulnerable&#13;
to the dangers of "ringing" would reduce the client's opportunity&#13;
to take into account considerations of quality when assessing commissions in terms of value for money. Conversely negotiation alone with a selected architect does not meet the criteria of increased competition&#13;
(ix) We consider it most unlikely that architects would be tempted to work uneconomically for the temporary advantage of obtaining commissions but we would expect that the enhanced climate for competition would encourage a considerably greater diversity of services available to the consumer&#13;
With regard to your question as to the possible RIBA response to the adoption of these proposals we consider this less likely to be a bang than a whimper.&#13;
We should be glad to assist in any costing exercise that the Government may initiate and trust that in the event of any further discussions on this or related matters with your department, the OFT or the DoE we hope that the&#13;
'Unattached' representing nearly 20% of the profession continue to be consulted.&#13;
Pls.se address ory eee ai CPrveoperoleQc hkfor eG.&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1567">
                <text>DR</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="1568">
                <text>John Murray</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1569">
                <text>July 1979</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2333">
                <text>Letter to Sally Oppenheim, Minister for Consumer Affairs, July 1979</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="281" public="1" featured="0">
    <fileContainer>
      <file fileId="291">
        <src>https://nam.maydayrooms.org/files/original/d6aa81f51c8f6bfe73d15c29d6553166.pdf</src>
        <authentication>f4c92e84142809e5c2d55881ed77b90d</authentication>
      </file>
    </fileContainer>
    <collection collectionId="4">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="7">
                  <text>Professional Issues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="8">
                  <text>A cohort of NAM members became engaged with the professional registration body, standing&#13;
as elected councillors on the Architects Registration Council and its various committees. Hitherto entirely dominated by&#13;
the RIBA bloc, the Council began to yield to a new dynamic through NAM's involvement, enabling fresh perspectives on&#13;
such issues as mandatory fee scales, greater lay representation on the body, ethically-based standards of professional&#13;
conduct, etc.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1560">
                <text>Correspondence, etc re …Unattached Representation; also notes on meeting with OFT on Monopolies Report</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1561">
                <text> To Un attacteool Peps .&#13;
Deav&#13;
J tndine a eoty of bly sot f Fadiv te MeCUK CGwumllies ¢&#13;
There ee be a mol Thee ygay)ara lat Your | L (&#13;
Unattached Mepiecetitnes at lardan /|eeu /4-Mare,&#13;
“ACU , 73 ttallan, Sheot mele Gai&#13;
TheCailepsathcouldawlPeantink ak CnC aangp ‘&#13;
fue Ssa&#13;
ical ae&#13;
e bySCAG&#13;
&#13;
 To UnattachedPepe- 5 Uilbr Anewt Z1 feb 7%&#13;
Deav&#13;
The Cucldf eps ash coulda we Pe ieed an DY qa a change,&#13;
feay (ee ort&#13;
Ez h slATE&#13;
a cise&#13;
%&#13;
Jo enclme a copy of elles sont fe Farciv te ACU Cums,&#13;
€ gee oll hoa oad Ths yganard last&#13;
Unattached ey)at oeWS(oe lApe SeanaeeMine“ateAiea.&#13;
&#13;
 Kennett\.) FevelovC4/ hegjohan/&#13;
Arecvild&#13;
73 balla Sheet&#13;
lrdo~ Wl.&#13;
“4A.&#13;
5 hulfor Aven lnotix WG&#13;
a O ie&#13;
Deny Mul Frvett|y&#13;
Ro: Atecuk Grwwillus 1970-FO.&#13;
‘Gpoillemers Agreemont? JFtansconstleMlpuceietadliiénofteUnabtchedt&#13;
people dinky te Gentlernans Aypeomendt&#13;
tour&#13;
4 Achiecine, opts OSniatlee&#13;
Etucahiar&#13;
&gt;Cee&#13;
Alar upman ,&#13;
SC Susan dackon Eatisrod Walbey,&#13;
branes and GoutrekPeopeses Qrumileo? (Marian fetrots lan Tod.&#13;
ProfessianakMgaeComvullee &gt; (delbnMan&#13;
a|&#13;
Bch ise ShowtAtho&amp;bafeSpee mae]&#13;
&#13;
 KounalhOFaceyExy/HA 5MilbrAwe&#13;
Ay2cUK werefallanr Stet&#13;
lado wi.&#13;
Dory KV Foveboy,&#13;
Pe! ¥RCUK Commitims 1979-¥o. Candidaltz, de Fro Eloctian|&#13;
oe SSfe&#13;
to beard d Archulicluyal Eetucakinr, lan Coopey&#13;
4 Flot&#13;
1072)&#13;
Vanes Las David Robson&#13;
Bio Aawatcsne Oneega Robert Malte&#13;
Thavas Leallor,&#13;
SO ern cow&#13;
\lelin Alay Thauas LJrolloy&#13;
Puspeaeo Quwilla&#13;
Bur Tec lan Tod&#13;
Peta)Cupmere&#13;
lan Ted lanTsd&#13;
[arnTod lantel&#13;
lan Tee&#13;
40 Professianack[LespereoQuamillae Reboort Malte&#13;
eae eefee Grdproud&#13;
&#13;
 Candidcles fv Fee Ehootinn (cort.)&#13;
é 5:0 Diciblinn Conmultia&#13;
Michagk Broad&#13;
€| forsco,&#13;
\ln Hane&#13;
Gp attached tubuseniedines)&#13;
Wounalad \ohn Adan&#13;
Seco dod&#13;
Yelm are ;&#13;
Pra ee ee a ee Oo"&#13;
&#13;
 Nee&#13;
Ye Wine&#13;
SMl Ave, NC&#13;
19.29 7.2&#13;
Ls&#13;
Rpt preparabylastuserUnattocladKops,&#13;
Ue Offore ee ge eotal the Mtn ile&#13;
Sf&#13;
Sas SdRoeland ao‘tadNecewedGur&#13;
+&#13;
Theewuttole onTres lo oe&#13;
ap tears&#13;
a ees aul be&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1562">
                <text>JM</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="1563">
                <text>John Murray</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1564">
                <text>Feb 1979</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2332">
                <text>Correspondence, etc re …Unattached Representation; also notes on meeting with OFT on Monopolies Report</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="279" public="1" featured="0">
    <fileContainer>
      <file fileId="289">
        <src>https://nam.maydayrooms.org/files/original/7a4cd30287ec8c89c340f2fa70090396.pdf</src>
        <authentication>cd593d2491d465f62db270185b0dbd02</authentication>
      </file>
    </fileContainer>
    <collection collectionId="4">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="7">
                  <text>Professional Issues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="8">
                  <text>A cohort of NAM members became engaged with the professional registration body, standing&#13;
as elected councillors on the Architects Registration Council and its various committees. Hitherto entirely dominated by&#13;
the RIBA bloc, the Council began to yield to a new dynamic through NAM's involvement, enabling fresh perspectives on&#13;
such issues as mandatory fee scales, greater lay representation on the body, ethically-based standards of professional&#13;
conduct, etc.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1550">
                <text>Letter from ARCUK Registrar re Unattached Election timetable</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1551">
                <text> 8&#13;
I have just come back from holiday and I see from my notes&#13;
that you had a strong viewpoint to put in the course of the June&#13;
Council meeting regarding the timetable for the Unattached election.&#13;
The Chairman of the Finance Conmittee and I are at present trying&#13;
to hammer out a more concentrated formula but I do recall that you felt that you might have suggestions to put to the Finance and General Purposes Committee and for this reason I am enclosing herewith a copy&#13;
of the present timetable which we have to follow each time there is an election.&#13;
I think you will find it helpful and I look forward to hearing from you on the subject.&#13;
Architects Registration Council of the United Kingdom ESTAQLIBHEOS UNOE® THE ARCHITECTS (MNEGIBTMATION!) ACTS 188! TO 1838&#13;
73 Hallam Street London W1N 6EE Tel: 01-580 5861 Registrar: Kenneth J. Forder M.A,&#13;
Dear Mr. Maltz,&#13;
10 July 1979&#13;
Robert Maltz Esq. 14 Holmdale Road London N W 6&#13;
Yours sincerely,&#13;
a nree&#13;
&#13;
 November 7&#13;
November 13&#13;
(16 November in 1978)&#13;
October 31&#13;
Send Forms A &amp; B to printer for setting as far as possible. Specimens attached&#13;
Last date for receiving membership details from constituent bodies Printout of the names of over 4000 Unattached in numerical order,&#13;
TIMETABLE FOR UNATTACHED ELECTION&#13;
October 1&#13;
Ask Unattached representatiyes if they are willing to serve again if nominated and elected&#13;
&amp;&#13;
November 20&#13;
Let printer have outstanding details to complete Forms A &amp; B&#13;
Ask constituent bodies to let us have membership details as at&#13;
as well as the count of membership of constituent bodies have to be obtained from computer bureau in time to report to the November meeting of the F&amp;GPC. We might be able to get these details in slightly earlier from the bureau but we have to supply data as at 31 October, so there is little room for manoeuvre,&#13;
About 4/5 days to get forms back.&#13;
An address label (from computer) supplied on a continuous sheet has to stuck manually on Form A, and both forms inserted in a window envelope.&#13;
Over 4000 have to be done and by enlisting all staff we have managed to get the job done in 4/5 days in the past.&#13;
Last year the Unattached representatives included a Newsletter in the circulation which is an added factor in the operation.&#13;
A special Post Office collection has to be arranged. Envelopes have to be tied up in bundles of 50 and put into sacks which have to be labelled. A day needs to be allowed for this since if the number of envelopes&#13;
for posting does not agree with the total number of Unattached they have&#13;
to be rechecked.&#13;
e&amp; November30 ThisisthelastdayforpostingaccordingtotheRegulations. Inthe past we have managed to get the forms out about 4 days earlier but this&#13;
depends on how the weekends fall.&#13;
The consignment to the 400 Unattached architects has always been sent 2nd class post until now&#13;
When the Nominations (Form B) come in they have to be checked against tke printout, the number of nominations recorded against each name and a record kept of the number of nominations received by each candidate.&#13;
Notifications from architects who have joined one of the constituent bodies are received. These have to be crossed off the list, their numbered envelopes taken opt and kept in a separate pile, and the&#13;
label removed if the stage of sticking on the large envelopes has not been reached. If it has take out large envelope and extract voting envélope and keep.&#13;
Unattached who have not received papers, because they have just dropped out of the RIBA or something, telephone or write and ask for papers because they have heard they are going around. The above procedure has to be reversed&#13;
in these cases,&#13;
Acareful check has to be kept on insertions and deletions so that the final number is accurate.&#13;
&#13;
 January 2&#13;
Before the middle of January the following processing must be completed&#13;
1. each name on the nominal roll printout has to be given a serial voter's number;&#13;
Ze each voter's envelope has to be stamped with the individual voter's number;&#13;
of address labels removed from adhesive sheet and stuck on large envelope;&#13;
4. insert in large envelope, voter's envelope,&#13;
and scrutineers' envelope but the worst job&#13;
of all is checking each name and voter's envelope number against the list to see that the correctly numbered envelope for each name is put in the right envelope.&#13;
1-4 is done in advance of the Voting Papers and Particulars of Candidates being received because to insert 2 (or 3) forms in the large envelopes takes as much time as we&#13;
can afford at the end of the month.&#13;
Last date for receiving nomination forms —&#13;
Unattached candidates who have not previously been on the Council seem to have difficulty in getting six nominations and these have always come in at the last minute. By reducing the time from 4 weeks to 2 it could be that new candidates would have difficulty in getting the required number of nominations.&#13;
From our point of view making the last date for receiving nominations 15 December does not help much. No printing is done between 20 December and 2 January. Between 15 and&#13;
20 December the Christmas post rush is on so it it is unlikely that anything can be delivered any earlier anyway.&#13;
None of Form C and Particulars can be set in advance so nothing can be done to help here.&#13;
Collating, typing and checking the particulars to forward&#13;
for printing has to take priority over everything else. 200 words in 1980 adds to the task. It seems too with each year that the number of candidates increases. At best nothing could be posted before 16 December.&#13;
Forms C etc. back from printer.&#13;
Insert in large envelopes already processed as above. Arrange a Special collection again as outlined above.&#13;
Last day for posting in accordance with the Regulations. In the past we have always managed to post 3/4 days before this&#13;
date.&#13;
This consignment has always been sent by 2nd class post.&#13;
January 24&#13;
January 31&#13;
&#13;
 Count votes&#13;
February 7 Last date for votes to be received&#13;
As soon as the scrutineers' envelopes start coming in they have to be&#13;
Counted and the number recorded each day Voter's envelope taken out and slit Sorted in numerical order&#13;
Checked against voter's list to see that the signature agrees with the name against the number&#13;
&amp;&#13;
13 candidates for 9 places&#13;
February 13&#13;
Very last day for results of election to be sent to all candidates. This is to be in time to report to the F&amp;GPC meetin&#13;
March 1 March 7&#13;
Last date for receiving above for inclusion in Annual Meeting pa]&#13;
Now take voting paper from envelope&#13;
Last year 772 voting papers received 737 counted&#13;
5104 votes&#13;
cast&#13;
Successful candidates have to liaise with each other to decide on their nominations under the Gentlemen's Agreement for the Board and Committees, as well as any nominations they wish to put forward for free election. These nominations need&#13;
to be seconded and biograp ical details supplied.&#13;
Very last date for Ordinary March meeting and Annual Meeting papers to go out.&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1552">
                <text>ARCUK</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="1553">
                <text>John Murray</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1554">
                <text>1979</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2331">
                <text>Letter from ARCUK Registrar re Unattached Election timetable</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="278" public="1" featured="0">
    <fileContainer>
      <file fileId="288">
        <src>https://nam.maydayrooms.org/files/original/d6822909d5de523d9a8f0dd0a6b3857a.pdf</src>
        <authentication>e7011eb2caf48ce0b5f301d143fc2c48</authentication>
      </file>
    </fileContainer>
    <collection collectionId="4">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="7">
                  <text>Professional Issues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="8">
                  <text>A cohort of NAM members became engaged with the professional registration body, standing&#13;
as elected councillors on the Architects Registration Council and its various committees. Hitherto entirely dominated by&#13;
the RIBA bloc, the Council began to yield to a new dynamic through NAM's involvement, enabling fresh perspectives on&#13;
such issues as mandatory fee scales, greater lay representation on the body, ethically-based standards of professional&#13;
conduct, etc.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1545">
                <text>Report on Professional Issues Group, Annual Meeting, Feb 1981</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1546">
                <text> (i)&#13;
PIG ANNUAL MEETING&#13;
Feburary 14 1981, at Islington Bus Company, London N7.&#13;
PRESENT:&#13;
John Allan&#13;
Bob Maltz&#13;
Giles Pe body David Burney&#13;
Mick Broad&#13;
Ken Thorpe (part) Ian Cooper (part) David Roebuck&#13;
APOLOGIES:&#13;
Eddie Walker Norman Arnold&#13;
ANNUAL REVIEW: Generally and ''Code':&#13;
John Allan:-&#13;
(11) That the work on thecode put the u/a firmly in the No. 2 seat and by our "intimate" incorporation in its drafting recognisedtheu/aasanumerouseae ens&#13;
((sisiat))&#13;
oo&#13;
A need for our cooperation because we are/"unreliable" to&#13;
be left out (viz monopolies) and the need for the RIBA not to push something through on the strength of an RIBA vote.&#13;
(iv) The result was consensus policies and it was necessary to elucidate this and how it would shape further action.&#13;
Bob Maltz:-&#13;
(i) Too much time, resources and commitment was being devoted&#13;
to ARCUK at the expense of NAM. NAM was weak as a result and therefore there was a need to re-orientate and re-direct resources back to NAM.&#13;
Debate between mainly BM and JSA over whether the extensive commitment and detailed work within ARCUK was the most effective way to achieve NAM's aims, in summary these arguments were&#13;
The current work particularly on the code was probably the climax of all the previous work done by NAM on Code and Monopolies and that we had primarily achieved our objective of driving a wedge between RIBA and ARCUK.&#13;
&#13;
 (ii) The emphasis of working within ARCUK blinkered our overview. ((aislit))&#13;
(iv)&#13;
It was restated that our primary aim was that "ARCUK is&#13;
to be a public interest body and not a front for the RIBA".&#13;
Board of Architectural Education:&#13;
It was decided to direct more effort to the BAE this year. As the BAE had in theory a lay majority and that we should&#13;
be re-orientating the BAE by exploiting&#13;
and by suggesting possible well known lay contacts on to ARCUK visiting boards.&#13;
PRAP was preparing a report for Council on Continuing Education and that the u/a should nominate a councillor in order to prepare a minority report.&#13;
Further NAM nominees to be put up for visiting boards and criteria to be challenged.&#13;
"Clean Up" Campaign:&#13;
Finnieston Report :&#13;
Government had decided not to implement the report and&#13;
create a statutory registration&#13;
standards to be formed instead. No further action.&#13;
Changes in Building Regulations:&#13;
David Burney had written to Heseltine putting forward u/a's views. It appeared that Heseltine was now backtracking on self—certification.&#13;
lay representation&#13;
body. A bodyon educational&#13;
We should be pursuing our aims with respect to ARCUK outside, i.e. through press, Privy Council, Legal and by building alliances outside e.g. Unions, M.P.s.&#13;
We should be using our ARCUK status for pursuing other aims rather than solely pursuing our aims within ARCUK.&#13;
The debate was rather wide ranging and generally unresolved at present but as our work on the Code was shortly to end this would be an opportunity to change direction.&#13;
It was agreed that the letter prepared for all the nominating authorities should be re-drafted and used in the press&#13;
rather than risk upsetting those existing nominees who&#13;
were sympathetic to our aims.&#13;
No actions since solicitors letter. Work to be directed to considering proposals for re-scheduling schedule I of the Act rather than attempting some legal "nice ones".&#13;
&#13;
 Monopolies:&#13;
Keyte:&#13;
Committee Representation:&#13;
Bob Maltz as reserve. D.B. to contact B.A.&#13;
PPC —- Edward Walker Norman Arnold&#13;
GPC - Giles Peabody David Roebuck&#13;
Admissions - Mick Broad ANO&#13;
Free election&#13;
BAE —- Alan Lipman and ANO PPC —- David Roebuck&#13;
John Allan&#13;
to see if interested.&#13;
This work was now at an end in ARCUK's terms as all our criteria were being met by the proposed new code.&#13;
It was decided that if ARCUK voted not to remove him from the register that we should ensure that there is adequate press coverage. Press to be pre-briefed.&#13;
More importantly what is our general attitude to criminal convictions. After some debate it was agreed that there&#13;
were three class of convictions that we considered merited removal from the register and that these were:&#13;
(i) conviction of an offence in connection with the practice of architecture resulting in death - indefinite removal.&#13;
(ii) convictions of an offence in connection with the practice of architecture with no death involved, e.g. corruption or tax frauds.&#13;
(iii) Convictions of an offence not connected with the practice of architecture, removal from register for period of prison term. Where no prison term set, but fine instead, then no removal.&#13;
It was provisionally agreed as follows. Gentlemen's agreement.&#13;
BAE - David Burney, Brian Anson.&#13;
GPC - 6 others to be decided. Discipline - Mick Broad&#13;
Also D.R. to be nominated for Chairman of Council and J.S.A. as vice Chairman.&#13;
&#13;
 Future Strategy:&#13;
D.R. 20.2.80.&#13;
It was agreed that new initiatives would evolve during the year and must be more NAM based.&#13;
As 1981 was ARCUK's 50th anniversary a working group is&#13;
to be formed to prepare "our" version of ARCUK's history and purpose and which could be used to launch a programme for ARCUK's reform and re-constitution. The group will start meeting at the end of March when the Code work is mainly out of the way. J.S.A. to approach Malcolm McEwan and D.R. to prepare list draft agenda and to anchor.&#13;
J.S.A. christened group "Quinquagenary Quango" or QQQ for short.&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1547">
                <text>DR</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="1548">
                <text>John Murray</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1549">
                <text>1981</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2330">
                <text>Report on Professional Issues Group, Annual Meeting, Feb 1981</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="277" public="1" featured="0">
    <fileContainer>
      <file fileId="287">
        <src>https://nam.maydayrooms.org/files/original/d84c830d6cd0c0e3b6eaa8ccb0bfe4a7.pdf</src>
        <authentication>f476cb70d62f2c8a59d24fc14cab7039</authentication>
      </file>
    </fileContainer>
    <collection collectionId="4">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="7">
                  <text>Professional Issues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="8">
                  <text>A cohort of NAM members became engaged with the professional registration body, standing&#13;
as elected councillors on the Architects Registration Council and its various committees. Hitherto entirely dominated by&#13;
the RIBA bloc, the Council began to yield to a new dynamic through NAM's involvement, enabling fresh perspectives on&#13;
such issues as mandatory fee scales, greater lay representation on the body, ethically-based standards of professional&#13;
conduct, etc.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1540">
                <text>Report on Professional Issues Group Meeting, Feb 1980</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1541">
                <text> to *an Cooper.&#13;
The PIG group convened at an unusual and outst.naing londmork Aron Sebruary 22nd — 24th to discuss current and future issues concerning NAM, SLATE and ARCUK. The venue was the Tower Mill,&#13;
a disused windmill at Burham Overy Staithe on the Norfolk coast. ie were unfortunately not able to explore the be: utiful surrounding countryside as time was short and the issues were MANY e&#13;
It was pointed out during the weekend that many people do not understand the term "unattached", especially in relation to&#13;
ARCUK councillors. It was also noted that these"unatt«ched" councillors were the only elected ones on ARCUK. A decision was therefore taken to refer to them as "elected" councillors as opposed to RIBA or other constituent body "nominee" councillors. whether or not this title will stick remains to be seen, but they will be referred to as such for the purposes of this «rticle.&#13;
During the weekend we decided to carry out an initial&#13;
colletion exercise of replies received so far from the elected ARCUK councillors' questionnaire published recently in the AJ,&#13;
or which there were some 500-600. At the time of writing this article the full analysis is not available. However two points worthy of note were:&#13;
1) The vast majority of RIBA members who replied were in favour&#13;
of direct election of councillors to ARCUK;&#13;
2) A considerable number of unattached architects had not received nomination or election papers for the ARCUK elections this year.&#13;
This information led to a lengthy debate concerning the apportionment of seats on the Council together with general&#13;
conuuct and the obstruction of business within the council&#13;
chamber. These discussions finally manifested "The Burham Charter"&#13;
iteport_on Professional Issues Yroup (PIG) meeting 22nd—24th&#13;
Mebruary. 11580)&#13;
Nor forwarding to SLATH/NAM Lieison Group ifter omissions&#13;
end udditions by PIG members.&#13;
Vistribution to «11 PIG members, Please forward any amendments&#13;
&#13;
 ate&#13;
to head the "Clean up ARCUK" campaign, the draft of which is published here,&#13;
TO BH INSERTED&#13;
An upproach to the elected oounoillors ‘by, another non— architect ARCUK councillor, intending to mediate between our— selves and the RIVA, wis discussed. It was generally felt however that while not wishing to detract from Nr. Leggatt's worthy intentions, more positive action and democratic behaviour in&#13;
the Council chamber could be brought about by promotion and Giscussion of the Burham Cherter.&#13;
Initizl moves to establish communications with the Hlectoral ‘eform Society concerning ARCUK elections heve as yet not met with great enthusiasm, as they apparently consider their province covers the conduct of the election machinery as it exists and&#13;
mot constitutional arrangements, even if these were considered "faulty beyond tolerance".&#13;
Another major debate of the weekend revolved around amendments to the Code of Conduct, particularly in relation to directorships, advertising and limited liability. A strong argument was put in favour of allowing these on the grounds that in practice they&#13;
all but exist enywey, often to the disadventage of unettached architects. Amendments to the Code allowing them would help to destroy ahy misapprehensions the lay public may be under about&#13;
the professionwl integrity of many architects, and this action could thus be considered to be in the public interest. This strong and prepmatic argument for operating within the capitalist system was, however, not adhered to unanimously and uniortimetely the fain opponents to the idea on fundamental ideological and ethical grounds were not present to put forward their vicws.&#13;
A small amount of timejas apent discussing outside funding for PIG, such as chariteble trusts. These arguments were reminiscent of past NAM Liaison Group discussions and no real conclusion&#13;
was reached.&#13;
&#13;
 ate&#13;
Time was set aside for discussion on the future of NAM and SLATE, bearing in mind the decision of the last Congress to holda special conference this spring on the future strategies of NAM.&#13;
The concensus appeared to be that NAM was essential as a focal point in order to identify the issues for which it stood. iio discussion took place regardingthe future form of NAM except that the orginisation of an Annual Congress end AGM should definitely continue, providing an open forum for debate.&#13;
It appears that local groupe continue on their own momentum regardless of whether or not they come under the NAM umbrella.&#13;
In both Cardiff and Leeds regular local meetings and action continue although largely unreported nationally in SLATE.&#13;
It might help if the communication network could be strengthened.&#13;
The London group is upparently about tovbe resurrected from the grave due to the efforts of Ken Pierce among others. It is understood that they intend to organise a series of discussions&#13;
on current issues during the comingyear, and it was suggested at the Burham PIG gatheriny that these could be focussed on subject-orientated forums discussing the effects of the cuts&#13;
and how to conbat them.&#13;
The key to all these suggestions appears to revolve eround&#13;
SLATE, which it is understood is in desperate need of both sHilled labour and material on NAN groups! activities, interests and opinions. While nothing particularly constructive was forth— coming on how to solve ‘the labour problem, it wes suggested that SLATE should at least ( or most) reduce its publications to 4 per annum (assuming finance and lahour are forthcoming).&#13;
“evarding material, PIG resolved to make u more concerted effort to keep NAN and particularly SLATE regularly informed of ell its activities, provisionally using Ian Cooper as 4 collecting point for forwarding information.&#13;
Enclosed are ehected councillor nominations for committee representation on ARCUK for 1980-81. The "Gentleman's Agreement" guarantees these nominations being accepted,&#13;
&#13;
 to: ARCUK Registrar&#13;
From; ‘'Unattached' Councillors&#13;
Representation on the poard and Committees of the Council: Gentlemen's Agreement&#13;
Board of Architectural&#13;
Education ; David John surney&#13;
Robert Maltz&#13;
Admission Committee $ Peter John Cutmore Peter William Howe&#13;
Finance &amp; General&#13;
Purposes Committee : Norman Frknk Arnold a ee&#13;
Edward walker&#13;
Professional Purposes&#13;
Committee John Stewart Allan&#13;
vavid Roebuck&#13;
20 February 1980&#13;
The following are the ‘Unattached’ Councillors! nominations under the Gentlemen's Agreement for the year 1980/81:-&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1542">
                <text>Unknown</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="1543">
                <text>John Murray</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1544">
                <text>Feb 1980</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2329">
                <text>Report on Professional Issues Group Meeting, Feb 1980</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="276" public="1" featured="0">
    <fileContainer>
      <file fileId="286">
        <src>https://nam.maydayrooms.org/files/original/8a4bdf73a4f4fc8aa8a65cc1aa6bc3ea.pdf</src>
        <authentication>78c37d8392db6790d890f5a2c23eb975</authentication>
      </file>
    </fileContainer>
    <collection collectionId="4">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="7">
                  <text>Professional Issues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="8">
                  <text>A cohort of NAM members became engaged with the professional registration body, standing&#13;
as elected councillors on the Architects Registration Council and its various committees. Hitherto entirely dominated by&#13;
the RIBA bloc, the Council began to yield to a new dynamic through NAM's involvement, enabling fresh perspectives on&#13;
such issues as mandatory fee scales, greater lay representation on the body, ethically-based standards of professional&#13;
conduct, etc.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1535">
                <text>Notes on Technical Competence</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1536">
                <text> ACTION&#13;
Lee Ne eoaeArcsinARSCON Ca ee&#13;
Er&#13;
aa 2“ A We q7rG oh UWA DAG AD AK PED&#13;
jKd,&#13;
DANafnG9.T8 @VaR.&#13;
Dey Aide G asw oy P.f,C. Gructa,&#13;
¢&#13;
K INGOT UENO | /1-O0An(a) F,WGN I&gt;&#13;
Meelys _ AicDd, OCM7O0KER //7H&#13;
©. a&#13;
Nk, a. ~ortiu AGCunrA&#13;
(a ave lng . (7-94-78)&#13;
EeRR hrRAR KALK REGhte,&#13;
i Sf on Yes U.K.&#13;
EOr-28 CoG, 2) Hy ARCLK ¢ Or&#13;
Rey oto — i Gf (CGronw, COGnn a) 3) BA Ainncber&#13;
:; NZ AM. Gpash fo MOLE Gte Go Vascina, fo Pr2rsek Sar&#13;
cs ereeat’ &amp; Kscof Tm,|aOtte,AkAneBuGA 7b.allCuteQu&#13;
Avthonta, . \ZM, Afro @ 7x ergQannodesCOfeACGOUNOENDjmWreralCAQLgoZ&#13;
[oa ae ne&#13;
sz i&#13;
oz&#13;
AY Aterd. .A- AxperCaahHoax NAM Boke GS45 GS mam 9 R@SsI Se) CZSs) OR KAX&#13;
Carte (Qs Gumanrctset) WO, jews Wh Arcot&#13;
\o pix a a*&amp;&#13;
ComdevQouce eee VL Gprea ‘ Q04q&#13;
GaawOnVobLReee&#13;
to rial 24&#13;
Qn RA wRADE ADVERIN NO,&#13;
A.b, Q npdevt Q@ aceabeSEES:&#13;
of Copa Qwe c&amp; ALCOL oN Avo&#13;
ae s .&#13;
Yes, 4 &amp; @ Arete fm Prapaauns O.Arwtm ou&#13;
—~&#13;
BPE&#13;
&#13;
(ey)&#13;
 Aut —&#13;
BM&#13;
please 72&#13;
oO&#13;
ss. Horta xkecAw a tl BES CONE PripOsohd oO Plewas&amp; SCiuekGACo jSf~HLCervoProms yd&#13;
NQunrckKaeMure who)on AA.,oee(Ochs Grediver. yPervibl,wicholeCOANg KARE&#13;
os oper. ux£ Ans. Jt) (Griloce&#13;
he Arcdstectvee ol 4Q, te Ru IGA GARG) eas&#13;
tomers LQ&#13;
RA, or QAlRrQhin&#13;
wCrrns OL sr.&#13;
ot OF eee Onc&#13;
Certy 7 af ARUK&#13;
Ry.Tee &amp;ProuseG.CesUae&#13;
Se Arel2 Ge&#13;
TQ Quan Korvnolonn&#13;
g Ce AQm,&#13;
2 SAMaits AOC. Gn,&#13;
olsCut peeswsol VAgrn/l Olas €s inns&#13;
JforrrsOrektok &amp; Ort 8, fa tacks-&#13;
Le,(ee CO. AhsTARToene aeeaae&#13;
EeBR he “telrolaal&#13;
vOcdurt YF&#13;
:|Porton peansiess o alerr.Durch Prof. rani, TH,&#13;
fo One Aer KonR G Whiner&#13;
Quo&#13;
BRa2KUnkeSAYpiso€GockCoenon,UL4A7E&#13;
Tel W&amp;&amp; sast hy&#13;
16. Refeorng (Accent — “4- &amp; sok &amp; iu,&#13;
Q4wWe ; aay V4A7E Gnortr AR LK Corer! oe 7M. f NAIAK &amp; RARER obew Oskar AU Geir Pree An OFRusf Cowie A423.b:5&#13;
Qruk Alef. AR pose Padtn OA a&#13;
Bus 3toteat Coven Mbeya OCs tok re &gt; UAH&#13;
Q. AS CrwvGaork Geek. He Abe ASA ale Que eS P&amp;snsq wo AObkeh Vora ackass 2/64&#13;
: 6King AGlx &amp; Cri A&amp; Gre 2) Care,&#13;
Q LCom, 7) &amp; Ryne LO asw ALK OH&#13;
Hy GGA o~ : getNUnn Omer Wo 10]Pg Mrs Oy&amp;Gintoneohntefo,oyAPr bk&#13;
&#13;
 k&#13;
a7) ECA CASULA SD)&#13;
lo. Tai&#13;
oe Caw&#13;
Got thy Crrnte AtnolOnen ~&#13;
REET GOGCOS NEA Cepy AH Wrovenie PainGneie (AGS BapOrewkl&#13;
lO. \A&amp; ADVERIAS 30 |&#13;
4 M-'— br em PPC, er AGenwea Gola Cn Aeneas ONC ee Peleg&#13;
AwunYtaeSe rte.NOs.&#13;
Kae the Anoudtis. ? Lecel 4uAws, | LQu8 Occ”RatAS.proxiesla&amp;pee&#13;
boRiBAOrchKarbsae fo,Kotter COGS NU Grae raGtlee =BMD&#13;
Ue NOs Agar .&#13;
&gt;i&#13;
—IL LNYAINEAD!, FM. GGinro eters, Qee BxGf, horns, ooUbon&#13;
Ante Kure be (ChOntQu Pox CSA. )LQ oA&#13;
©&#13;
bits WEI hr SAE fe HsYok SSemOURS @ourm, Kasele byl Coct&lt;Qdc Ay&#13;
oH ARC umn dG Aust Lon clang Pegi 7s “Cha! ov Dow, dig POACIC. GusGs&#13;
ae CP. QAcG OQ yp han, Korshk LUorn, CAGsnLOWS Oca.” La SiG /6oxo an&#13;
Qoasvas Eo) CSFa OSOo CoC CREO Re AN SPamvele (Ake broke) Bea&#13;
Giro tpeol AL GP - Wr%2 OK. T Akar&#13;
Zoo ,Aowikinr Zyl, 4h,Vue&#13;
Jude &amp; ALEDR&#13;
20.4FAL.Achar, [Wxsalanhole|sBD&#13;
Ae Qemobs.Gu etohn. AbebriGh nbrolneher, ry ainlahive GA.&#13;
cepe&#13;
agen&#13;
cemane&#13;
Gone&#13;
G2 Also AQ A&#13;
Contry&#13;
&#13;
 A.M.&#13;
(3. Para &amp; Exe Anernee). J vet7e§ Senet.&#13;
Io Kodi&#13;
kon A On Ph.&#13;
7&#13;
/@ / a Fed. Vili FinsS RomARNE. J SA. Sy. |&#13;
z./n&#13;
‘Ab. Creweee&#13;
Ca ACs Enka&#13;
C.J/NEV USeeue econ O ses GAS So)&#13;
‘oce&amp;PQ ae ho-ceUntkaclsA&#13;
ey ANrepmtreutea ¢aAPate oy)—4urk&#13;
ne 5 b3IDAK slprtel GR 2olac, 2 en Gra : Gs 4o a&#13;
Caen [Ar por Jog PholrGsr. Kn &amp;, fe CLO Cundhi&#13;
cp 7© ex eee &amp;, Qr&amp; @ Axe 6A ;noe &amp;&#13;
J :AL} oa Le ae f~&#13;
Ki sao KyiA DOppO21 ZFe,+ Adz&#13;
PQ.AR aT 2&#13;
LQunn AGok 2tpuring pee Ki, |&#13;
tc/Au Amase&#13;
ie. NA. Aeesdlove|&#13;
tux fe .&#13;
TA. Csyfrrid Acgicbalck wmt Qu Phy am&#13;
OOnttactsdA Archtach fe Ay.A. MW, AQ Seok AL. |e dare tes Hib 10, Ayp0O0th wAQnl, redoly&#13;
s Z Ko Gsieae ibe ar&#13;
iS. Arkek Hoiol Geetk |&#13;
Reh See @ be Verde fr (&amp;&#13;
Ase&amp;Se CmGar2ckae foreworekosQ.banrGeesPCOS.ProofinoV0CatemQue&#13;
Adc &amp; ae&#13;
Mek ofc&#13;
a&#13;
fo. NoQwAar ARan OC), Cott&#13;
&#13;
 / (iAyD&#13;
S AD GenieSoe Cae Enka&#13;
/.oe USFinsO RnRBeAS ATaSe&#13;
(3. frea 3 ExAnme). yUMP7S Senet. a&#13;
3¢./ YrerturgBoOvelnsambSafernice64E~&#13;
Woe eee eS fevkr.Ad ‘ogo&amp; QSL Wwe 6A- Ova ey Untiaclsr&#13;
6 Mplatith a5 AEP ERY —hak ine|astaueshortedGeMleuoOnOntos“G4Lea&#13;
enta&#13;
Corl Arefar erg Pho(2bs. ku, fr Coane&#13;
1# AL enw&#13;
SeCe fe&#13;
Pasze Uf ?&#13;
Jew AC.&amp;,Are@AseeBAE wnhok=&gt;&#13;
Asac&amp;HEARS «&#13;
(o ~ AloQmArs Aarne gatoree&#13;
KyMae7intsces (KIA DLPO2A WAGEACG&#13;
LQunnAGolk20gusringOWPEs HG, refau Ama Hae fe .&#13;
,&#13;
[EES TING ATLNG Lhtesd lovk .&#13;
wae Os Ant AAU Ao‘al pmAbe Qu. ESS Qu&#13;
On. Ottachsd ArchiGch fr NAM. HAOncolSook 1 Kare ts HibK 10, Ay0rmth OOK r2Goly&#13;
[im wpetyel I&#13;
bee A Gstux Suk,&#13;
(IS. ARerK LOA Geok |&#13;
Ruisonac Seat oa&#13;
Ase &amp;pre Cu&#13;
loreck) Hand} Gook . eee&#13;
aM. fore work osQa&#13;
ban Gees PCOSG . Presprtve&#13;
VvFa femur&#13;
&#13;
(S&#13;
 (i NCAR CRON Ce&#13;
loz rate Pratt cle Aye bhn See {Sm. (RING EO ees &amp;S&#13;
bom ut) Dorcluclack Nbawtol 42 su freporas&#13;
p-RepsVolechimrt.2c.See&#13;
;&#13;
Detx. rae Ol, SaO)&#13;
fe Reps eae oe g yeas (e Rapwe ee ordJ)eg&#13;
asas&#13;
2.5 heCeol se ve Zre ith.&#13;
G@iGQuecunlascsPhar rouMestoeeratoALAN Groups — &amp; Weltrrelt, WO VE ,&#13;
Bp: wiere Clickee (olaesoeNOR&#13;
euAG oe Ae eoes&#13;
asw “2GA—E(StnOlu Oe Bae LH Ovo,&#13;
Gus Ser lQ ter&#13;
UP AR CLL AinQuer&#13;
7M, portal Paden, Qs (Pron |a .&#13;
) AypWawrcla As 9&#13;
Ober Rr bo. br. hog&#13;
Cus&#13;
i) Ae Or Pu GP (Shi Heese Peel&#13;
(yateary Ptopgerbak&#13;
bAESClon we wu Aa,&#13;
Ee&#13;
Oe aco&#13;
Qi bO&#13;
ju) Aneto. ple r at wx, Kat Re clef&#13;
98 hic ile&#13;
GG fe. &amp; Cbroppedk grow&#13;
&#13;
 AD. AL.&#13;
|&#13;
«&#13;
/CR bo QU&#13;
u) BAE&#13;
‘ (EB Napa Coe Urol Wl.&#13;
ole,ene strOnn&#13;
a aus (/ Or —fren (GER&#13;
.&#13;
heeee (fev&#13;
2&#13;
“LOQune Gioia&#13;
own Aw(00Ge Orla&#13;
an&#13;
paneQg ay l= ei ay ce&gt; Nahls wbFuck GB4&amp;sQreOpsCuK&#13;
e&#13;
Gon&#13;
Liv &amp; prin (!)&#13;
| &amp;(&#13;
my) Ad Susrgeutael e &lt; OnSOl:Eg CworOeCeOrgLrg&#13;
ee Wl pyasa&#13;
EWG),&#13;
OLE Un Ky, nee EyProclucg Regime A075.&#13;
Llpbn,POCA&#13;
vic) TM opined t&amp;QUe a Tee Gee&#13;
pees GPA&#13;
a a on : ; VPAxorJQAe+“4Ste&amp;Je hyLt—G&#13;
hp Ghre chal P N&#13;
ac RiAr PSHE LOunk,&#13;
WAGES yap vii Wea lodewOweGOK a ye Ryprs&#13;
pt Cambes Bolircokhsi&#13;
bX hee MO&#13;
Queca east 4 Russ Te bon ne&#13;
Lol, i505 06)ech Arpdr chotrerncnOt&#13;
a Ge, "l,&#13;
Cit) AL&#13;
IGO a&#13;
Rae&#13;
ks.[o,eo (hn Ft /1,Abas) —Asxolecl .&#13;
Botere Yor Cre.&#13;
fron M05—95 Pee1960 —&#13;
e&#13;
te, of[e6r&#13;
bs0, 7g&#13;
done Ocdsi (4x54)xamrfespt-b&#13;
CoriicGeeh tee tAEece&#13;
AL,FBpO-2ttyterrympforteCS,g AD, onl Pop site L4 oes \ZAY, co.&#13;
RemanBe —Sau&#13;
yoy trcfisus ofl&#13;
YA&#13;
Acker&#13;
JM.&#13;
otc. Aktu&lt; Bo 4 -/&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1537">
                <text>JM</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="1538">
                <text>John Murray</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1539">
                <text>October 1978</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="275" public="1" featured="0">
    <fileContainer>
      <file fileId="285">
        <src>https://nam.maydayrooms.org/files/original/d965edd3906af8484a1a682c53f3ca21.pdf</src>
        <authentication>7c6f03a6aadb133fe9abd755573eb5b4</authentication>
      </file>
    </fileContainer>
    <collection collectionId="4">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="7">
                  <text>Professional Issues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="8">
                  <text>A cohort of NAM members became engaged with the professional registration body, standing&#13;
as elected councillors on the Architects Registration Council and its various committees. Hitherto entirely dominated by&#13;
the RIBA bloc, the Council began to yield to a new dynamic through NAM's involvement, enabling fresh perspectives on&#13;
such issues as mandatory fee scales, greater lay representation on the body, ethically-based standards of professional&#13;
conduct, etc.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1530">
                <text>Notes of Unattached Representative meeting. July 1978</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1531">
                <text> ARCUK Unattached representatives meeting&#13;
Notes on meeting at Tom Woolley's house on 9th. July, 1978&#13;
Attended by : Tom W., John A., John M., Bob M. and David R.&#13;
N.B. Next meeting : 17th. September, at 67 Romilly Road, London N4, at 11 a.m.&#13;
Please let John Allan know if you cannot make it&#13;
Agreed to persuade local libraries to have copy of ARCUK Register. Discussion of Way Ahead. Slogans at end to be more positive.&#13;
Lengthy discussion on our position on Summerland.&#13;
Agreed to get ourselves briefed by looking at AJ reports on the Enquiry etc. John Murray to write paper on Discipline principles.&#13;
Bob Malz to contact Nick Wates for info on Summerland.&#13;
Corporate advertising.&#13;
We should force RIBA to stop until matter is settled - or unattached&#13;
shouldn't be discriminated against. Motion on this to be formulated.&#13;
Ledger of unattached motions should be kept, especially those we lose, and we should note who supports us.&#13;
.“&#13;
John Allan to come to meetings as an observer / reporter for SLATE.&#13;
Slate to write to Forder for credentials.&#13;
Are members of public allowed to attend meetings ?&#13;
John Murray to raise matter of whether RIBA facilities are paid for - possibility of alternative venue in the future.&#13;
Directorships — not discussed.&#13;
ICOM / TASS seminar important. (see enclosed Lathe from Mark Gimson)&#13;
Limited liability - we are in favour.&#13;
Ann is working on this.&#13;
Tom and Support to look into this and insurance.&#13;
Monopolies Commission&#13;
David R. had disappointing meeting with Green. DoE rep. on ARCUK.&#13;
Meeting to take place with Fraser.&#13;
MPs to be circulated. Hallam Street address to be used for reply.&#13;
Job Advertising. Bob Malz to redraft letter to Forder taking into account comments.&#13;
Investments&#13;
John Murray to ask for more details. Do they actually make money — Annual Report suggests Hill Samuels fees are higher than investment&#13;
income. Need to press ARCUK for policy.&#13;
12. Visiting Board / BAE&#13;
We should go and look at reports before next meeting.&#13;
13) Part 3 Examiners&#13;
Are these 'separate' exams or for the ones set by schools.&#13;
We need to find people to put forward . John Murray has been asked to by EE at Hull. Tom W. tofind out.&#13;
&#13;
 14. Visiting Boards&#13;
Who are the ARCUK reps on these — what are the ground rules ? Unattached should be on them.&#13;
15. Unattached meeting for November&#13;
We should ask people if they are interested in being on Visiting Boards or to be Part 3 examiners.&#13;
Everyone thought the BD article was good.&#13;
16. Circulation of information&#13;
We should send committee minutes to each other and reports to the liaison committee and Slate.&#13;
Las NAM Handbook&#13;
John Allan to write something.&#13;
18. ARCUK Handbook&#13;
We should attack it, especially Metcalfe's foreword.&#13;
19. Action on Norman Arnold's letter&#13;
Discussion of this. John Murray to send his reply.&#13;
20.NAMConferenceon10th.November._Pravwalthis we froawa&#13;
Who 1,Giaudlu.g&#13;
&#13;
 Sue Jackson,&#13;
Secretary, BDS/TASS London Branch, 4 Highshore Road,&#13;
London SE15 5AA&#13;
Dear Susan Jackson,&#13;
9th. August, 1978&#13;
I am writing to you about the joint ICOM/BDS conference on alternative&#13;
forms of architectural practice, which was planned for the autumn. We&#13;
had started to compile a short list of people we thought should be invited : e.g. someone we know from a law centre who knows a lot about co-operative structures, people from other professional co-operatives etc.&#13;
But when we phoned David Marshall of ICOM about this, he told us that it was going to be a meeting of about half a dozen people, and he grudgingly agreed that maybe someone fram Support could attend. Although we agree with keeping the numbers to, say, two dozen-or&#13;
so, his proposal sounds totally useless. If it goes ahead we at Support would probably have to&#13;
set up our own session on alternative forms of practice. This would te a regrettable duplication of energies, but unavoidable from our point of view if we are really to get clear in detail what the available alter- natives are.&#13;
When we contacted Bob Malz about this, he said that he had been too busy to take- it all on, and suggested that we could take over the organising with ICOM and Ian Tod.&#13;
Apart from what we at Support think about it, as a member of BDS/TASS I am concerned that it seems to be turning into something quite different&#13;
In any case, there is some urgency about their plans.&#13;
If you agree that the situation needs some sorting out, could you write&#13;
to David Marshall at ICOM, 31 Hare Street, London SE18 (Tel. 01.855.4099). Perhaps the best way to resolve things would be to set up a meeting with you or someone else from the branch committee and ICOM, at which we could be represented.&#13;
Yours,&#13;
WeeksGe oe&#13;
Mark Gimson&#13;
from what was discussed at branch meetings.&#13;
up at the next branch meeting, but I am going to be away in September.&#13;
Support&#13;
27 Clerkenwell Close&#13;
London EC1R OAT 01 251 0274&#13;
Normally I would bring this this before ICOM go ahead with&#13;
&#13;
 RECEIVED: 9aug:1978;&#13;
- 125Po. te,We Lottoot.louxkusole(Gsee):&#13;
| |&#13;
Leeds, G&#13;
Weer YoxReslure.&#13;
— Tow, |&#13;
ro;ee ni yonreAIM,4eneeeeereiser&#13;
ee Caoneby oeioeaceLoa ‘ravlsroeh ak Hs, mast. cee Adersseann urty wade,&#13;
oe 4h.s. rmeaderte Avcei ais wej that oe lhe&#13;
Seeatase laud&#13;
reCo&#13;
{ Midlowd Roark&#13;
Fun hugud I44s&#13;
Ss precta KS hak U — are welrewalk au,&#13;
ra uk i) underdunatt. tak Oe wl&#13;
jeable. te ott.N Wo Bertin jrewerte mawa ot |hshore.Lawn,TOROIENES&lt;ysro.alga, ACC OLGENSvery unClic trebeuse row&#13;
Cape WieaneesCEL oaene LHotha&#13;
Aa&#13;
i aaaalhkthhin2Gveldbeimmluble&#13;
Ey i 65 EG eek&#13;
Rove.ae oleboBprecetao&#13;
oT ZN se howeto&#13;
Cx eof&#13;
1s&#13;
nukAVE ae Z7S aaiabnctie&#13;
cee Ue_de 4 te, eer&#13;
ae us&#13;
B8BW9.San feae&#13;
1&#13;
en&#13;
amo Oy- ewe&#13;
Cansrks TN Wg rays7vOnin te av S&#13;
shonbh, pee ee Ward&#13;
oe.=&#13;
we v=&#13;
&#13;
 ees Sree&#13;
| cee hems deeut ope ues too&#13;
Vio. jerghona, Leode Airothon on the&#13;
Groprcws. Preggetian sir, Cteiiwia&#13;
.WE are epewdsres Qos CEE mA Or Ort BE fas ew&#13;
ta, t 2) actetiesTM cdLeods i, Fao th&#13;
leak Corp |Z. ma cals Wee Kargre, SOL hy mo&#13;
cowriwilyayeenerwoSleeoupla,&#13;
oe arg&#13;
opehieohaus eo Orch&#13;
AanneCUWE oeyMoreecee North—&#13;
heitdor en Zeb Crees aun On Yel Ace 2A Qrid4 Moaxo¢ wi, han bos wriooclsrtaho&#13;
wee=ts narCRE&#13;
cotta Po-tinmsaat eit A uN apare TR aa&#13;
SN eas. ot bw WrAemrplrnnge Clk wok bmckircsertcd)&#13;
onl (ray clwuinorkerk is on reek {eartac. jerSwww-+CueAAto aetheySia&#13;
C astauw (seakla, oy RRCAID),&#13;
&#13;
 BUILDING DESIGN JULY 28th. 1978&#13;
FOLLOWING a committee&#13;
meeting at RIBA headquarters&#13;
last week, the RIBA’s Community Architecture&#13;
Working Group iscompiling a&#13;
list of community architecture&#13;
case studies, which it will £0.75m.&#13;
Community architecture architecture, including could become as established as architects on the dole, local&#13;
present through RIBA&#13;
CAWG has already drawn up President Gordon Graham, to a national list of all architects Housing Minister, Reg Freeson. with experience of community&#13;
the National Health Service if authority architects working in the group’s plans are put into their spare time, and students.&#13;
practice.&#13;
CAWG’s idea is that&#13;
community architecture groups&#13;
would be set up in urban centres&#13;
It would like this list to be operated through the RIBA Clients Advisory Service.&#13;
““We would manage areas of&#13;
in the same way as doctors’ blight. The demand for this&#13;
Surgeries and legal aid centres. kind of work is so great that&#13;
They would be financed by&#13;
community aid funds which&#13;
would bridge the gap between&#13;
local authorities and private&#13;
money and would enable them be financed by Government to carry out remedial work on&#13;
money rather than private run-down properties for people because we need full&#13;
who could not afford private architects.&#13;
Freeson is thought to be&#13;
sympathetic to the idea and the&#13;
commitment”’, said Hackney. He added that CAWG would be pleased to hear from anyone&#13;
who could quote examples of&#13;
list of case studies is a good community architecture&#13;
preliminary to seeking financial and these should be sent to&#13;
support from the DoE. Two&#13;
DoE representatives sit on the Portland Place, W1.&#13;
CAWG committee. Commu- |&#13;
amount of money — about&#13;
individual people working in community architecture can only start on the pinnacle of the iceberg. Architectural aid must&#13;
Charles McKean, RIBA, 66&#13;
Architecture for needy communities&#13;
nity architect, Rod Hackney said: “Initially we are not setting our sights too high, we are seeking a reasonable&#13;
&#13;
 Mr. K. Forder Registrar&#13;
ARCUK&#13;
73 Hallam Street London WIN 6EE&#13;
Dear Mr. Forder ,&#13;
I enclose a copy of my Practice Information sheet for you to hold .&#13;
I was concerned to read in this week's Building design’ a claim that the RIBA Community Architecture Working Group has drawn up a "National last of all architects with experience of community architecture including ......." It wants this list to be operated through the RIBA @lients advisory service .&#13;
I wonder af you could write to the RIBA pointing out that any such statements made by them should make it clear that their " national list" is of RIBA members and not of " all architects " .&#13;
There are a substaftial number of architects with the kidd of experience described by the RIBA CAWG as TM community architecture " who age not members of the RIBA and to the best of my knowledge&#13;
have not beeh approached to be on this list . This list cannot, therefore be one of all architectswith this experience .&#13;
J would think that you should also be concerned at the way the RIBA CAWG is publicising experience of'community architecture’&#13;
as though it were a qualification . Having been a leader in this field for many years I have always tried to handle the concept carefully and refer to it in inverted commas . However the public might easizy be misled into thinking that this term is a recognised specialisation of qualification .&#13;
Please get in touch if you would like to discuss these points with me but I would expect meanwhile that you ensure the RIBA puts out factually correct statements .&#13;
yours sincerely&#13;
Tom Woolley&#13;
July 28 1978&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1532">
                <text>TW</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="1533">
                <text>John Murray</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1534">
                <text>July 1978</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2328">
                <text>Notes of Unattached Representative meeting. July 1978</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="274" public="1" featured="0">
    <fileContainer>
      <file fileId="284">
        <src>https://nam.maydayrooms.org/files/original/ed495ad5a222f3a88ea7bf3c82884925.pdf</src>
        <authentication>a63c92479bf0de2ec2b7f8689a13dac5</authentication>
      </file>
    </fileContainer>
    <collection collectionId="4">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="7">
                  <text>Professional Issues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="8">
                  <text>A cohort of NAM members became engaged with the professional registration body, standing&#13;
as elected councillors on the Architects Registration Council and its various committees. Hitherto entirely dominated by&#13;
the RIBA bloc, the Council began to yield to a new dynamic through NAM's involvement, enabling fresh perspectives on&#13;
such issues as mandatory fee scales, greater lay representation on the body, ethically-based standards of professional&#13;
conduct, etc.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1525">
                <text>Notes of Unattached Representative meeting. May 1978</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1526">
                <text> UNATTACHED REPRESENTATIVES ON ARCUK&#13;
Minutes of a meeting held at Dave Roebuck's home on Sunday May 21 1978&#13;
Those present: Bob, Anne, Dave, Alan, John Murray and John Allen&#13;
ds Items arising from the Minutes of the last meeting (i.e., April 28):&#13;
c) It was agreed that 'Way Ahead' is to be published by NAM. 2. ARCUK Committees:&#13;
a) BAE — a report had been presented at the previous meeting by Ian and Alan.&#13;
a) The arrangements for the coming meeting of the NAM Education Group in Cardiff, in the first week of July, were explained.&#13;
b) Monopolies Commission Group —- the letter to Peter Shore MP was read and discussed; the letter to Denys Hinton and his reply was read by Anne and discussed - it was agreed that no reply is required.&#13;
b) F&amp;GP — a verbal report was presented by John Murray: it was agreed that John and Alan were to raise the matter of first class travel&#13;
at the next Council meeting and that John (Murray) is to prepare a proposal re 'Statements by Unattached Candidates for ARCUK Elections’.&#13;
c) PPC — Dave presented a verbal report; it was agreed that he is to contact the Registrar re ARCUK/OFT discussions re Trade Descriptions Act issue.&#13;
d) Admissions Committee - no meeting has taken place since the last Unattached meeting.&#13;
3. Anne reported that she was still awaiting recognition of her Code of Conduct proposals.&#13;
4. Tt was agreed that Anne and Alan were to put a motion re ARCUK investments in South African firms to the next Council meeting..&#13;
5. It was agreed that Alan was to try to clarify the position of the York Centre and the recent report by that Centre to ARCUK (about Continuing Education).&#13;
6. John Allen gave a rapid 'run through! report of Monopolies Commission/OFT affairs; plans for the publicity campaign which he had described previously are in hand.&#13;
7. Unattached/NAM relations - it was agreed that John Murray is to reply to Norman Arnold's letter: Unattached Councillors are to offer reports of ARCUK affairs for each issue of Slate - Dave to prepare a report for the June 9 issue.&#13;
&#13;
 Jf ; Page: 2&#13;
8. Tt was agreed that Bob is to write a submission to the Finiston commission re registration of engineers.&#13;
_ 10.&#13;
It was agreed that Ian Cooper and Alan are to raise the question of recognition of South African Schools of Architecture (Natal, Cape Town and Vitz) at the next BAE meeting). =&#13;
o&#13;
The Registrar's letter re 'Limited Liability’ —- Anne reported on behalf of Ian Cooper and herself on her correspondence with Forder: it was agreed that Anne is now to reply on our behalf to Forder's letter and that this matter be discussed at our next meeting.&#13;
rls) Bob discussed the matter of our co-operation with the Institute of Worker Control vis-a-vis the Architects‘ Registration Acts; it was agreed that,&#13;
as well as continuing to consider for whom registration might be beneficial or advantageous, we should pursue attempts to reform the present Acts;&#13;
Bob to circulate his rough notes for comment. ;&#13;
(At this point I (Alan) left the meeting and Dave continued making notes)&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1527">
                <text>DR</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="1528">
                <text>John Murray</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1529">
                <text>May 1978</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2327">
                <text>Notes of Unattached Representative meeting. May 1978</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
