The Unofficial Handbook for New Academic Staff

Welcome

Congratulations on your appointment.

You have joined a dynamic, innovative, student-centred institution committed to excellence, impact, inclusion, transformation, strategic alignment, and other nouns.

This handbook explains how things actually work.

Please destroy it after reading, or leave it prominently displayed on your desk, where no one will ever notice it.

---

Section 1: Understanding Priorities

You may initially believe that priorities are established through strategic plans.

This is incorrect.

Priorities emerge through a sophisticated institutional process involving:

• recent emails,

• approaching deadlines,

• senior management anxiety,

• and whatever was discussed most recently in a meeting.

Consequently, priorities operate according to a principle known as:

Simultaneous Hierarchical Fluidity

This means that everything is important, but some things are more important than other things until tomorrow.

---

Section 2: Meetings

Meetings exist to answer three fundamental questions:

1. Has everyone been informed?

2. Has everyone been consulted?

3. Can responsibility now be distributed sufficiently widely?

New staff sometimes make the mistake of attending meetings in order to make decisions.

Please avoid this.

The primary function of meetings is to establish that a decision pathway exists.

Actual decisions generally emerge later through email.

---

Section 3: Email

Email is the circulatory system of the modern university.

Messages fall into four categories:

Category A: Immediate Action Required

No action required.

Category B: Important Reminder

No action required.

Category C: Final Reminder

Possibly action required.

Category D: URGENT – RESPONSE REQUIRED TODAY

The sender has just discovered the problem.

---

Section 4: Strategic Plans

Every strategic plan contains five key commitments:

• Innovation

• Excellence

• Sustainability

• Collaboration

• Transformation

These commitments appear because no one has yet discovered a strategic plan that opposes them.

Should you encounter two strategic plans that contradict one another, remember:

Both remain strategically valid until replaced by a third strategic plan.

---

Section 5: Student Feedback

Student feedback is essential.

Student feedback is invaluable.

Student feedback must be carefully considered.

Student feedback indicating opposite things simultaneously must also be carefully considered.

Examples:

"The lectures moved too quickly."

"The lectures moved too slowly."

"Assessment requirements were unclear."

"Assessment requirements were obvious."

The correct institutional response is:

"We appreciate this valuable feedback and will reflect upon it."

This phrase has successfully resolved feedback since approximately 1994.

---

Section 6: Performance Reviews

Performance reviews are opportunities for professional growth.

You will be asked to demonstrate:

• teaching excellence,

• research excellence,

• service excellence,

• community engagement,

• innovation,

• leadership,

• strategic contribution,

• wellbeing.

Please note that excellence in one category does not compensate for shortcomings in another category.

Excellence is assessed holistically.

No further clarification is available.

---

Section 7: The Most Important Rule

Eventually you will discover a secret.

The University does not actually function because of policies.

It functions because thousands of intelligent people quietly help one another navigate the gap between policy and reality.

This knowledge should not be shared with auditors.

---

Final Advice

When confused, locate the longest-serving administrator in your area.

Ask:

"How does this actually work?"

They will look around carefully.

Then they will explain everything.

Welcome to the University.

Most Pageviews by Country Since Blog Relocation

Informal Guide to Navigating the Formal System

Internal Communication (Uncirculated Version)

Staff Survival Practices Unit (Unofficial)

Subject: Informal Guide to Navigating the Formal System

---

Colleagues,

This document is not formally issued. It exists in the same way most work gets done here: acknowledged implicitly, denied explicitly, and referenced retrospectively when something goes wrong.

It is a guide to surviving within the institutional architecture described in policies such as MAOCP, PMUEUP, ARR, PPRP, SFCDDM, and others that are currently being reviewed for coherence with themselves.

---

1. The First Principle: Assume You Are Already Non-Compliant

You will save time by accepting that:

• You are always slightly out of alignment
• Any action can be reclassified after the fact
• Any silence can be interpreted as consent or negligence, depending on context

Therefore:

Do not aim for compliance. Aim for plausible defensibility under retrospective review.

---

2. The Art of Strategic Acknowledgement

Survival depends on knowing when to:

• Reply “noted, thank you” (no action taken)
• Reply “we will take this forward” (no ownership taken)
• Reply “we are currently aligning this with institutional priorities” (no timeline exists)

These phrases do not communicate meaning.

They communicate administrative survival status.

---

3. Meetings: A Parallel Reality System

Meetings serve three functions:

1. Recording attendance of ideas
2. Preventing unrecorded decisions
3. Converting uncertainty into action items that will never act

Survival protocol:

• Speak once, early, vaguely
• Nod at key moments to establish epistemic presence
• Volunteer for tasks that will be reassigned before completion becomes possible

If a decision is made, assume it will be:

• revised
• reinterpreted
• or placed into a pilot programme designed to investigate whether it was actually a decision

---

4. Email Strategy (Critical Skill)

Inbox survival requires mastery of:

• The “looping reply-all closure”
• The “gentle deferral with implied urgency reversal”
• The “attachment that resolves nothing but looks complete”

Recommended phrases:

• “Just circling back on this” (translation: I am still alive in this thread)
• “Happy to discuss further offline” (translation: please do not)
• “Let’s park this for now” (translation: it is already buried but we need ceremony)

---

5. The Policy Stack Survival Method

You will encounter conflicting policies. This is normal.

Do not attempt resolution.

Instead:

• Identify which policy is most recently updated
• Pretend it supersedes all others
• If questioned, refer to “local interpretive discretion frameworks”
• If further questioned, escalate to a committee that does not yet exist

Remember:

The goal is not consistency. The goal is traceable intent alignment under shifting policy terrain.

---

6. Work Output Optimisation (Informal Reality)

Officially:

• Quality matters
• Innovation is valued
• Reflection is essential

Practically:

• Deliver what can be easily described in a report
• Avoid outputs that require explanation in meetings
• Ensure all work can be summarised in three bullet points or fewer

If it cannot be bullet-pointed:

It will be considered “emergent complexity” and deferred indefinitely.

---

7. Emotional Survival Layer

Key truth:

Most institutional stress comes not from workload, but from trying to interpret whether the workload is real, symbolic, or aspirational.

Therefore:

• Treat urgency as performative unless accompanied by a deadline reminder email
• Treat deadlines as suggestions unless accompanied by escalation language
• Treat escalation language as atmospheric rather than literal

---

8. The Golden Rule

When in doubt, ask yourself:

“Can this be retrospectively justified in a way that sounds like I understood the system all along?”

If yes:

• Proceed

If no:

• Create a working group

If uncertain:

• You are already correct

---

9. Closing Note

No one fully understands the system.

Those who appear to understand it are either:

• new
• leaving soon
• or actively being scheduled for a review of their understanding of understanding

The system continues to function because everyone agrees, tacitly, not to test it too closely at the same time.

---

Kind regards,

Staff Survival Practices Unit (Unofficial)

---

P.S. If you are reading this during work hours, you are probably already in compliance with something, somewhere.

Policy for Managing Unavoidable Exceptions to Universal Policy (PMUEUP)

Internal Communication

Office of Universal Standards and Exception Governance

Subject: Policy for Managing Unavoidable Exceptions to Universal Policy (PMUEUP)

---

Colleagues,

In order to uphold the integrity, consistency, and universal applicability of institutional policy, the University is pleased to introduce the Policy for Managing Unavoidable Exceptions to Universal Policy (PMUEUP).

This policy ensures that while all policies are universally applicable, there exists a clear, standardised mechanism for handling the circumstances in which universality cannot, under any reasonable interpretation, be applied universally.

---

1. Purpose

The PMUEUP provides a structured framework for:

• Identifying exceptions to universal policy
• Determining whether such exceptions are unavoidable
• Ensuring that unavoidable exceptions are managed in accordance with universal principles
• Maintaining the universality of policy even when universality is not possible

In essence, this policy ensures that no deviation from policy occurs outside a formally recognised policy-compliant deviation structure.

---

2. Definition of “Unavoidable Exception”

An Unavoidable Exception (UE) is defined as:

A situation in which adherence to universal policy would result in outcomes that cannot be reconciled with the intent of universal policy.

Examples may include (but are not limited to):

• Cases where policy contradicts itself in practice
• Situations where policy implementation would prevent policy implementation
• Scenarios where all available options are non-compliant under at least one interpretive framework
• Events that were not anticipated by the policy designed to anticipate all events

---

3. Exception Identification Process

Staff identifying a potential UE must:

Step 1: Confirm Policy Applicability

Review all relevant universal policies to ensure the situation is fully encompassed by at least one policy.

Step 2: Confirm Exception Status

Determine whether the situation is:

• Fully compliant
• Non-compliant
• Compliantly non-compliant
• Exceptionally compliant with exception conditions

Step 3: Submit an Unavoidable Exception Notification (UEN)

This must include:

• Description of the situation
• Relevant policies in conflict
• Evidence that no non-conflicting interpretation exists
• A preliminary statement confirming that this is indeed an unavoidable exception, unless it is not

---

4. Governance and Approval

All UENs will be reviewed by the:

Committee for the Validation of Exceptionality within Universality (CVEU)

The CVEU may determine that:

• The exception is valid and must be managed as an exception
• The situation is not an exception and must be treated as a policy violation
• The situation is both an exception and not an exception, requiring dual classification
• The policy already accounts for this exception implicitly and therefore it is not an exception

In cases of unresolved ambiguity, the matter will be escalated to the:

Supreme Panel for Exception Governance Consistency (SPEG-C)

whose decision will be final, except where subsequent exceptions arise.

---

5. Management of Approved Exceptions

Where an Unavoidable Exception is approved, it must be managed according to the following principles:

• The exception must be documented as an exception to a universal policy
• The management of the exception must itself be universally applied to similar exceptions
• Any deviation in handling must be recorded as a secondary exception
• All exceptions must remain compatible with the principle of universality at a meta-policy level

---

6. Reporting Requirements

All exceptions must be recorded in the:

Universal Exception Register (UER)

Each entry must include:

• Nature of the exception
• Policies affected
• Reason for exception status
• Confirmation that exception handling followed universal exception protocol
• Retrospective assurance that no policy breach occurred, including breaches arising from exception management itself

---

7. Staff Guidance

Staff are reminded that:

• Universal policy remains universally applicable, including in cases where it is not
• Exceptions are not deviations from policy, but regulated expressions of policy flexibility
• Failure to identify an unavoidable exception in a timely manner may itself constitute an avoidable exception misclassification event
• When in doubt, assume universality, unless universality appears not to apply

---

8. Closing Statement

The University remains committed to the principle that universal policy must remain universal in all circumstances, including those in which universality requires structured suspension.

The PMUEUP ensures that exceptions do not undermine universality, but instead reinforce it through formal recognition, controlled classification, and retrospective coherence.

---

Kind regards,

Office of Universal Standards and Exception Governance

---

Attachment: Exception Decision Flowchart (Version 1.0 — universally applicable except where not)

Mandatory Adoption of Optional Compliance Procedures (MAOCP)

Internal Communication

Office of Procedural Coherence and Adaptive Standards

Subject: Mandatory Adoption of Optional Compliance Procedures (MAOCP)

---

Colleagues,

In order to enhance institutional flexibility while maintaining consistent oversight, the University is pleased to introduce the Mandatory Adoption of Optional Compliance Procedures (MAOCP).

This initiative ensures that optionality itself is standardised, and that all staff have equal access to the freedom to comply in a structured and auditable manner.

---

1. Purpose

The MAOCP framework is designed to:

• Preserve optionality as a core institutional value
• Ensure that optional procedures are applied consistently
• Provide mandatory pathways for the exercise of discretion
• Harmonise divergent approaches to compliance flexibility

In short: to ensure that everyone is free to choose from the same set of approved choices, in the same approved way.

---

2. Scope of Optional Compliance

The following areas are now designated as Optionally Mandatory Domains (OMDs):

• Administrative reporting practices
• Meeting attendance modalities
• Teaching delivery adjustments
• Research output classification
• Emotional tone calibration in formal correspondence

Within these domains, compliance is optional—except where it is mandatory.

---

3. Implementation Framework

All staff are required to adopt the MAOCP through the following steps:

Step 1: Declaration of Optionality Awareness

Staff must acknowledge that optional procedures exist.

Step 2: Selection of Approved Optional Pathways

Staff may choose from the following options:

• Full compliance (mandatory optional route)
• Partial compliance (conditionally mandatory optional route)
• Deferred compliance (temporarily mandatory optional route)
• Non-compliance (requires mandatory justification)

Step 3: Submission of Optional Compliance Intent Form (OCIF)

This form confirms that the staff member understands that optional compliance is now mandatory.

---

4. Governance Structure

Oversight will be provided by:

The Central Authority for Optional Mandatory Alignment (CAOMA)

Supported by:

• The Optionality Assurance Working Group (OAWG)
• The Mandatory Discretion Advisory Panel (MDAP)
• The Committee for the Standardisation of Non-Standard Practices (CSNSP)

All groups will operate with full procedural autonomy under centrally defined constraints.

---

5. Reporting Requirements

All optional compliance activity must now be recorded in the:

Register of Mandatory Optional Actions (RMOA)

Entries must include:

• Which optional pathway was selected
• Whether the choice felt genuinely optional
• Any perceived deviation from mandatory expectations
• Retrospective confirmation of compliance status

Failure to submit reports on optional compliance will be treated as a mandatory compliance breach.

---

6. Staff Guidance

Staff are reminded that:

• Optionality is a structured institutional asset
• Freedom is best exercised within clearly defined boundaries
• Non-compliance with optional procedures may still be compliant, provided it is documented correctly
• Confusion is expected and therefore partially non-optional

Where uncertainty arises, staff should consult their local Optionality Liaison Officer (OLO), who will provide guidance on whether optional advice is mandatory.

---

7. Closing Statement

The University remains committed to fostering a culture of empowered discretion, supported by robust procedural scaffolding.

The MAOCP represents a significant advancement in ensuring that optionality is not left to chance, interpretation, or uncontrolled autonomy.

We look forward to your mandatory engagement with this optional framework.

---

Kind regards,

Office of Procedural Coherence and Adaptive Standards

---

Attachment: Optional Compliance Decision Tree (Version 1.0 – mandatory reading required)

Strategic Framework for the Centralisation of Decentralised Decision-Making

Internal Communication

Office of Distributed Governance Coordination

Subject: Strategic Framework for the Centralisation of Decentralised Decision-Making

---

Colleagues,

As part of the University’s ongoing commitment to agility, empowerment, and coordinated institutional responsiveness, the Executive is pleased to announce the implementation of the:

Strategic Framework for the Centralisation of Decentralised Decision-Making (SFCDDM)

This initiative reflects our shared recognition that decentralised decision-making functions most effectively when guided through a coherent centralised structure.

---

1. Background

Recent reviews have demonstrated that decentralised decision-making has produced:

• Increased local autonomy
• Greater contextual responsiveness
• Variable institutional alignment
• Multiple simultaneous interpretations of policy reality

While these outcomes have generated innovation, they have also led to inconsistencies in:

• decision visibility,
• approval pathways, and
• strategic synchronisation across decentralised units.

Several faculties were found to be making decisions independently without central awareness that decisions had occurred.

---

2. Purpose of the Framework

The SFCDDM aims to preserve the benefits of decentralised decision-making while ensuring that all decentralised decisions are:

• Centrally visible
• Strategically harmonised
• Operationally aligned
• Retrospectively confirmable

This will allow units to continue exercising local autonomy within an appropriately coordinated framework of central oversight.

---

3. New Decision-Making Structure

Effective immediately, all decentralised decisions will proceed through the following process:

Step 1: Local Decision Identification

Units identify a decision requiring local determination.

Step 2: Preliminary Autonomy Notification

A notification is submitted to the:

Central Office for Distributed Decision Awareness (CODDA)

This confirms the intention to undertake decentralised decision-making.

Step 3: Strategic Alignment Review

CODDA assesses:

• alignment with institutional priorities,
• compatibility with parallel decentralised decisions,
• and the degree of acceptable local variation.

Step 4: Conditional Decentralisation Approval

Upon approval, units may proceed with locally determined decision implementation, subject to:

• central visibility,
• ongoing reporting,
• and retrospective harmonisation if required.

---

4. Levels of Decentralised Autonomy

To ensure consistency, autonomy will now operate across four approved tiers:

Tier	Description
D1	Fully centralised decision presented locally
D2	Centrally guided local implementation
D3	Locally adapted decision within central parameters
D4	Experimental autonomy (pilot basis only)

Units seeking D4 autonomy must submit an:

Enhanced Decentralisation Justification Statement (EDJS)

---

5. Governance Arrangements

Oversight will be provided by the newly established:

Central Steering Committee for Distributed Governance Alignment (CSCDGA)

Supported by:

• The Decentralisation Coordination Working Group
• The Local Autonomy Harmonisation Taskforce
• The Advisory Panel on Strategic Distributed Consistency

To maintain distributed participation, all meetings will be centrally scheduled.

---

6. Reporting Requirements

All decentralised decisions must now be recorded in the:

Institutional Register of Distributed Decision Activity (IRDDA)

Entries must include:

• rationale for local variation,
• anticipated impact,
• degree of autonomy exercised,
• and whether the decision still feels decentralised following implementation.

Quarterly summaries will be prepared for Executive review.

---

7. Staff Guidance

Staff are reminded that decentralised decision-making does not imply unstructured independence. Rather, it reflects a collaborative institutional model in which local autonomy is exercised responsibly within centrally coordinated boundaries.

Where uncertainty exists regarding whether a decision is sufficiently decentralised, staff should consult CODDA before proceeding.

---

8. Closing Remarks

The University remains deeply committed to empowering local units while ensuring institution-wide coherence, visibility, and strategic alignment.

The SFCDDM represents an important milestone in achieving a more integrated approach to distributed autonomy and coordinated independence.

Further clarification sessions will be scheduled centrally across all decentralised units in coming weeks.

---

Kind regards,

Office of Distributed Governance Coordination

---

Attachment: Decentralised Decision Escalation Pathway (Central Version)

Launch of Pilot Programme to Reduce Pilots (PPRP)

Internal Communication

Office of Strategic Innovation and Experimental Initiatives

Subject: Launch of Pilot Programme to Reduce Pilots (PPRP)

---

Colleagues,

Following sector-wide concerns regarding pilot proliferation, pilot fatigue, and the long-term sustainability of perpetual trial implementation, the University is pleased to announce the launch of a new institutional initiative:

The Pilot Programme to Reduce Pilots (PPRP)

This 18-month pilot seeks to explore whether the number of pilot programmes currently operating across the University can be strategically reduced through targeted piloting interventions.

---

1. Background

A recent internal review identified that the University is currently running:

• 14 active pilot programmes
• 9 pilot evaluations
• 6 pilot extensions
• 3 pilot feasibility studies
• 1 pilot review of pilot feasibility methodologies

In several cases, pilot programmes had become operationally indistinguishable from permanent practice, despite remaining formally classified as “temporary exploratory initiatives.”

Staff expressed uncertainty regarding:

• Whether pilots were still pilots
• Whether completed pilots had officially concluded
• Whether some pilots were themselves piloting the concept of pilots

---

2. Purpose of the PPRP

The Pilot Programme to Reduce Pilots aims to:

• Assess institutional dependency on pilot structures
• Identify opportunities for pilot consolidation
• Develop a sustainable framework for future pilot restraint
• Pilot alternative approaches to pilot management

The programme is expected to generate actionable insights into the long-term viability of non-pilot operational models.

---

3. Pilot Methodology

The PPRP will proceed in three phases:

Phase 1: Pilot Mapping

Identification and categorisation of all existing pilots according to:

• Pilot duration
• Pilot clarity
• Pilot awareness among participants
• Degree of pilot self-reference

Phase 2: Pilot Rationalisation

Selected pilots will be:

• Merged
• Paused
• Reclassified as “emergent operational practices”
• Subjected to secondary pilot review

Phase 3: Pilot Reduction Pilot

A small-scale pilot will test whether pilot reduction itself can be sustainably piloted before broader institutional rollout.

---

4. Governance Structure

Oversight of the PPRP will be provided by the newly established:

Pilot Oversight Steering Committee (POSC)

Supported by:

• The Pilot Review Working Group (PRWG)
• The Interim Taskforce on Pilot Transition Pathways (ITPTP)
• The Advisory Panel on Sustainable Piloting Futures (APSPF)

To minimise administrative burden, all groups will meet separately.

---

5. Evaluation Metrics

Success of the PPRP will be measured using the following Pilot Reduction Indicators (PRIs):

• Reduction in total pilot visibility
• Increased clarity regarding pilot status
• Percentage of pilots acknowledged as pilots by participants
• Reduction in pilot-related uncertainty (subject to pilot verification)

A dashboard will be developed to monitor pilot optimisation in real time.

---

6. Risks and Mitigations

Potential risks include:

Risk	Mitigation
Excessive pilot reduction	Introduction of contingency pilots
Staff uncertainty regarding pilot status	Additional pilot communication strategy
Emergence of unapproved pilot-like behaviour	Pilot awareness training
Permanent dependence on pilot reduction pilots	Deferred review at later pilot stage

---

7. Staff Guidance

During the pilot period, staff are advised to:

• Continue participating in existing pilots unless informed otherwise
• Avoid initiating unauthorised pilots
• Clearly label any experimental activity as:
  • Pilot
  • Pre-pilot
  • Post-pilot transitional pilot
  • Pilot-adjacent exploratory initiative

---

8. Closing Remarks

The University recognises the important role pilots play in fostering innovation, experimentation, and strategic uncertainty management. At the same time, we acknowledge the need for a more intentional approach to pilot sustainability.

The Pilot Programme to Reduce Pilots represents an important first step in piloting a future in which pilots may eventually become less necessary, subject to pilot outcomes.

Further updates will be provided following completion of the preliminary pilot evaluation phase.

---

Kind regards,

Office of Strategic Innovation and Experimental Initiatives

---

Attachment: Pilot Reduction Pilot Timeline (Draft Version – Pilot Use Only)

Policy for Retiring Policies (Pending Replacement Policy)

Internal Communication

Policy Lifecycle Management Unit

Subject: Policy for Retiring Policies (Pending Replacement Policy)

---

Colleagues,

In recognition of the University’s commitment to agile governance, adaptive frameworks, and the sustainable management of legacy documentation, we are pleased to introduce the Policy for Retiring Policies (PRP).

This policy establishes a clear and consistent approach to the retirement of policies that are no longer fully aligned with current institutional priorities, while ensuring continuity through the anticipation of their eventual replacement.

---

1. Purpose

The PRP provides guidance on:

• Identifying policies suitable for retirement
• Managing the transition from active to retired policy status
• Maintaining operational continuity in the absence of a confirmed replacement policy

This ensures that all policies are either:

• Active,
• Retired, or
• Pending retirement pending replacement

No policy will be considered simply “no longer used,” as this category is not currently recognised.

---

2. Definitions

• Active Policy (AP): A policy currently in force
• Retired Policy (RP): A policy formally decommissioned following due process
• Pending Replacement Policy (PRP): A policy identified for retirement, contingent on the future development of a replacement policy
• Interim Interpretive Framework (IIF): A temporary set of guiding assumptions used in the absence of an active or replacement policy

---

3. Criteria for Policy Retirement

A policy may be considered for retirement if it is:

• No longer reflective of current practice
• Superseded in principle but not in documentation
• Operationally ambiguous
• Excessively clear in ways that limit interpretive flexibility

All retirement proposals must be supported by a Policy Retirement Justification Statement (PRJS).

---

4. Retirement Process

Step 1: Submission of PRJS to the Policy Lifecycle Review Panel (PLRP)

Step 2: Preliminary assessment of whether the policy can be retired without immediate disruption

Step 3: Determination of whether a replacement policy is:

• Required immediately
• Required eventually
• Conceptually desirable but operationally deferrable

Step 4: If a replacement policy is not yet available, the policy is designated as Pending Replacement (PRP)

---

5. Status: Pending Replacement

Policies in PRP status:

• Remain notionally in effect
• May be selectively applied, interpreted, or referenced
• Should not be relied upon as definitive guidance
• Must be acknowledged as transitional in all formal use

Staff are encouraged to exercise informed discretion, supported by local interpretive practices and retrospective alignment.

---

6. Replacement Policy Development

Replacement policies will be developed:

• When sufficient clarity emerges
• When operational need becomes unavoidable
• When prompted by audit, incident, or sustained confusion

Until such time, the existing policy remains in a state of provisional retirement readiness.

---

7. Communication and Documentation

All policies designated PRP will be:

• Clearly labelled as “Pending Replacement”
• Accompanied by a disclaimer noting their transitional status
• Included in the Register of Policies in Anticipated Transition (RPAT)

Staff accessing these policies will be prompted to confirm awareness of their provisional nature.

---

8. Monitoring and Review

The status of PRP-designated policies will be reviewed annually, or more frequently if:

• Circumstances change
• A replacement policy becomes available
• The absence of a replacement becomes unsustainable

---

9. Closing Remarks

The University recognises that policies, like the environments they govern, must evolve. The PRP ensures that this evolution occurs in a structured and transparent manner, even where the future state has not yet been fully defined.

Staff are reminded that the absence of a replacement policy should not be interpreted as an absence of guidance, but rather as an opportunity for context-sensitive decision-making within a formally recognised state of transition.

---

Kind regards,

Policy Lifecycle Management Unit

---

Attachment: Policy Retirement Flowchart (Version 0.9 – pending replacement)

Implementation of the Annual Review of Reviews (ARR)

Internal Communication

Office of Reflective Oversight and Iterative Assurance

Subject: Implementation of the Annual Review of Reviews (ARR)

---

Colleagues,

In alignment with the University’s commitment to continuous improvement, reflective practice, and the optimisation of evaluative ecosystems, we are pleased to announce the formal introduction of the Annual Review of Reviews (ARR).

This initiative ensures that all reviews conducted across the institution are themselves subject to systematic review.

---

1. Rationale

Recent audits have identified that while the University produces a high volume of reviews—including:

• Performance reviews
• Course reviews
• Programme reviews
• Policy reviews
• Review reviews (pilot phase)

—there has been limited oversight of the quality of the reviewing itself.

This has led to variability in:

• Depth of reflection
• Consistency of critique
• Appropriateness of recommendations
• Confidence in the tone of evaluative language

The ARR addresses this gap by introducing a review layer above all existing review layers.

---

2. Scope

The ARR applies to all formal reviews completed within the previous review cycle, including but not limited to:

• Annual staff performance reviews
• Student feedback summaries
• External examiner reports
• Internal audit findings
• Reviews that concluded no further review was necessary

Each review will now be assigned a Review Integrity Score (RIS).

---

3. The Review Integrity Score (RIS)

The RIS is calculated based on the following criteria:

• Clarity of evaluative intent
• Consistency between findings and recommendations
• Appropriate use of constructive ambiguity
• Alignment with institutional tone guidelines
• Evidence of reflexive awareness in the act of reviewing

Scores will be categorised as:

• Exemplary Review (ER)
• Satisfactory Review (SR)
• Review Requiring Review (RRR)
• Review Requiring Immediate Re-Review (RRIRR)

Reviews falling into the latter categories will be escalated.

---

4. ARR Process

Step 1: Identification of all reviews conducted in the previous cycle

Step 2: Allocation of each review to a Review Reviewer (RR)

Step 3: Completion of the Review Review Form (RRF)

Step 4: Submission to the Panel for the Evaluation of Reviews (PER)

Where discrepancies arise between reviewers of reviews, the matter will be referred to the Adjudication Committee for Divergent Review Interpretations (ACDRI).

---

5. Timeframes

We recognise the importance of timely review. The ARR will therefore operate within the following indicative timeframes:

• Review of reviews initiated: within 4 weeks of review completion
• Review of review of reviews (if required): within 6–8 weeks
• Final confirmation of review status: within 10–12 weeks

Please note that these timeframes are subject to review.

---

6. Training Requirements

All staff involved in reviewing activities must complete the new professional development module:

“Reviewing Reviews: Principles, Practices, and Reflexive Frameworks”

This module includes:

• Recognising effective reviewing behaviours
• Identifying under-reviewed reviews
• Maintaining neutrality while evaluating evaluation

Completion will be recorded and may be reviewed as part of future reviews.

---

7. Key Outcomes

The ARR is expected to deliver:

• Greater confidence in institutional review processes
• Improved alignment across review outputs
• Enhanced visibility of evaluative quality
• A sustainable culture of recursive reflection

---

8. Closing Statement

The University recognises that reviewing is a cornerstone of academic life. By reviewing our reviews, we ensure that our commitment to evaluation remains itself rigorously evaluated.

Staff are encouraged to engage proactively with the ARR and to view it not as an additional layer, but as a necessary extension of existing layers.

Further guidance will be provided following the first cycle of review reviews.

---

Kind regards,

Office of Reflective Oversight and Iterative Assurance

---

Attachment: ARR Workflow Diagram (Version 1.0 – under review)