Definition

Formal communication processes are structured, documented methods for exchanging information within and between organisations, as distinct from informal or ad hoc communication. They include written procedures, standardised document formats, defined distribution lists and agreed escalation routes. In an APC context, formal processes underpin the RICS Rules of Conduct (2022) by providing the evidence trail that demonstrates professional conduct and competent service.

Why this matters for Diversity, Inclusion and Teamworking

  • Level 1 knowledge: you must describe at least three formal communication methods and explain their purpose.
  • Formal processes create an equitable information environment where all team members receive the same communications at the same time, reducing the advantage of informal networks that can perpetuate exclusion.
  • Documented communication reduces dispute by providing an objective record of what was agreed and by whom.
  • Client service obligations under Rule 2 require surveyors to keep clients informed using clear, timely and accurate communication.
  • In contract administration, formal processes such as instructions and payment notices are legally required under standard contract forms.

Key principles

Written project communications

Formal written communications in a surveying project include: client instruction letters; site instructions; architect's or engineer's instructions (AIs/EIs); payment notices; interim and final certificates; early warning notices (under NEC contracts); and formal meeting minutes. Each has a specific format, timing and legal consequence. The Construction Act 1996 (as amended) prescribes payment notice timescales; missing these can expose the client to liability for disputed sums.

Meeting structures and minutes

Formal meetings should have a structured agenda circulated in advance, a chaired discussion and minutes issued within an agreed timescale (typically five working days). Minutes should record: attendees; decisions made; actions with named owners and deadlines; and deferred matters. Clear, attributable minutes reduce the risk of disputed decisions and create an audit trail for professional indemnity purposes.

Project management platforms and escalation routes

Most surveying firms use digital project management platforms, such as Aconex or SharePoint-based systems, providing a single source of truth for document version control, approval workflows and distribution records. A common data environment (CDE) is increasingly mandated on publicly procured projects under BIM requirements. Formal communication processes also include defined escalation routes: knowing when to escalate a cost overrun, programme delay or quality concern to the project board, and documenting that escalation, protects both the candidate and the organisation.

Relevant RICS guidance and legislation

  • RICS Rules of Conduct (effective 2 February 2022) — Rule 2 (competence) and Rule 5 (professional service) require clear and timely communication with clients.
  • Housing Grants, Construction and Regeneration Act 1996 (as amended) — prescribes formal notice requirements for payment and adjudication in construction contracts.
  • NEC4 contract — the early warning notice and compensation event notification processes are formal communications with contractual consequences.
  • UK GDPR and Data Protection Act 2018 — formal communications containing personal data must comply with data protection law.

Ethics and Rules of Conduct angle

Rule 2 requires members to deliver competent service; formal communication is central to this. Poorly managed communications resulting in missed deadlines, undocumented instructions or disputed decisions expose clients to financial and legal risk. Rule 1 (honesty and integrity) also engages: formal communications must be accurate and not misleading. A surveyor who omits relevant information from a meeting minute, or who delays issuing a notice for tactical advantage, is in breach of their ethical obligations.

APC-style Q&As

Q (Level 1)Name three formal communication methods used in a construction project team and state the purpose of each.

Site instructions: formally direct the contractor to carry out specific work and create a contractual record. Meeting minutes: document decisions, action owners and deadlines. Payment notices: comply with the contractual and statutory payment process, notifying the amount due and the basis of calculation.

Q (Level 1)Why is it important to issue meeting minutes promptly after a project progress meeting?

Prompt minutes, typically within five working days, allow attendees to identify errors while the discussion is fresh, create an accurate audit trail of decisions, and ensure action owners are aware of their responsibilities without delay. Late minutes increase the risk of disputed records and missed actions.

Q (Level 2)How does a common data environment support formal communication on a project?

A common data environment (CDE) is a shared digital space where all project information is stored, version-controlled and distributed according to agreed protocols. It ensures all team members access the same current version of drawings and specifications, provides a time-stamped audit trail of document issue and approval, and is increasingly required on publicly procured projects under BIM Level 2 standards.

Q (Level 2)Describe a situation where a formal communication process prevented or resolved a project dispute.

(example) On a commercial fit-out the contractor claimed an oral instruction had been given to carry out additional partition works. Because all instructions were required to be in writing, and because I had issued no written instruction, I demonstrated from the document management system that no such instruction existed. The claim was not supported and the dispute was resolved without adjudication. The experience reinforced why formal communication processes are genuine protection for all parties.

Q (Level 3)A contractor submits a compensation event notification one week late under the NEC4 contract. The event is genuine. How do you handle it?

(example) Under NEC4 clause 61.3, late notification can bar entitlement. My first step would be to confirm the notification was indeed late, then take specialist NEC advice on whether any saving provisions apply, for example whether the project manager had been aware of the event through other formal communications. I would advise the client promptly in writing of the position. I would not make a unilateral decision to waive the time bar without authority. Throughout, I would act in line with Rule 2 (competence) and Rule 1 (honesty and integrity) of the RICS Rules of Conduct.