Manchester, United Kingdom Last checked

The University of Manchester

Independent · Open access · Not an official university page

What would you like to check?

Search universities

Explore the current record by topic

Coursework & Assessment Categories

Senate 4-Category Framework

Under Senate Policy DocID 79331 §2.1.1, assessments are categorized into four levels (Category A: AI Prohibited, Category B: AI Minimal, Category C: AI Permitted, Category D: AI-Integrated) by Course Unit Directors and clearly stated in unit specifications and Canvas briefs (§2.1.3). Students may choose not to use AI for Categories A, B, and C without disadvantage, but this choice does not apply to Category D assessments which assess AI learning outcomes (§2.1.2). In Category A, all AI use including proofreading and text editing is prohibited; in Category B, AI is restricted to presentation only (fluency, grammar, spelling, formatting) without altering student ideas, arguments, or conclusions.

Official source ↗

Examinations & Timed Assessments

Assessment Categorization & Exam Rules

Examinations and timed assessments are categorized individually under the four-category framework (DocID 79331 §2.1.1). Under Academic Malpractice Procedure DocID 639 §3.1.2.5 and §4.3.1, students must adhere strictly to examination conditions communicated before the exam, and possessing or using unauthorized AI tools or online materials in examination sittings constitutes academic malpractice.

Official source ↗

Acknowledgment & Citation

Cite them Right Standards

Under University Library referencing guidance, students must cite generative AI tools when using text or images directly in their work following 'Cite them Right' conventions. Where asked or deemed appropriate, students should include an overview acknowledgement at the start of work or in a footnote. An appendix detailing relevant prompts, outputs, generation dates, and modification statements is required when referencing AI as personal communication or when instructed by School guidance. Using tools for basic grammar and spell checking does not require acknowledgement unless School guidance requires it.

Official source ↗

Data Protection & Copyright Restrictions

Upload Restrictions & Recording Safe Harbor

Under Senate Policy DocID 79331 §2.2.1(c), students must not upload University-owned copyright materials (such as lecture recordings, slides, handouts, or examination questions) to external commercial AI tools. Under §2.2.2, students are explicitly permitted to upload session recordings into University-provided Microsoft 365 Copilot for study support. Under §2.3.1, staff members who use AI in Teaching and Learning activities must adhere to the University's AI Guidelines, and only the University-provided Microsoft 365 Copilot service may be used for student-identifiable or confidential data.

Official source ↗

Approved AI Tools

Copilot Chat (All) & M365 Copilot (Phased)

The University provides Microsoft Copilot Chat with Commercial Data Protection to all active students and staff using University credentials. Microsoft 365 Copilot suite is deploying in phased license cohorts across 65,000 colleagues and students. NebulaONE is provided as an enterprise cloud AI development sandbox. Under DocID 79331 §2.1.1 and §2.2.1, having access to institutional AI tools does not confer permission to use them in Category A assessments.

Official source ↗

Research, Data Synthesis & Publication

Author Responsibility & Peer Review Confidentiality

Under StaffNet Research Guidelines, any use of AI to synthesise research data must be completely transparent, and fabricating or falsifying data with AI constitutes research misconduct. Corresponding authors carry ultimate responsibility for publication credibility and must declare significant AI assistance. Researchers reviewing papers or grants must preserve peer review confidentiality and never upload unpublished manuscripts into external AI services.

Official source ↗
More reviewed record topics

Malpractice Detection, Viva Voce & Case Handling

DocID 639 §4.2, §4.4 Viva Voce & §5 Case Routing

The University does not currently use software claiming to detect generative AI; Turnitin alone does not confirm malpractice and academic judgment is required. Under Academic Malpractice Procedure DocID 639 §4.4.2, where indicators raise concerns of commissioned work without direct evidence, or available information does not satisfy the balance of probabilities, a viva voce can be arranged in agreement with the School Officer to demonstrate authorship; it does not contribute to the mark. If held, it should not normally take place more than 30 working days after the assessment feedback deadline (§4.4.3.1); the student should receive at least five working days notice explaining its nature, purpose and potential outcomes (§4.4.3.2). Accompaniment by a person of the student’s choice is for support only without participation (§4.4.3.4), and reasonable adjustments must be made (§4.4.3.5). The viva itself cannot impose a penalty (§4.4.4.2); case handling follows the applicable AUO/SDP/UDP procedures (§5.1–5.5).

Official source ↗

Teaching Practice & Assessment Governance

Assessment Briefs, Group Work & Staff M365 Rule

Senate Policy DocID 79331 and Faculty guidance mandate that Course Unit Directors specify AI categories in unit specifications and Canvas briefs (§2.1.3), establish group work logging rules and require prior peer consent before recording group discussions (§2.1.4–2.1.5), and require teaching staff handling student-identifiable data to use M365 Copilot (§2.3.1). Faculty guidance (FSE, BMH) supplements central policy.

Official source ↗

Cloud Sandbox Governance & Data Security

Commercial Data Protection & NebulaONE Gateway

IT Services and Information Governance establish clear tenant boundaries for Copilot Chat, Microsoft 365 Copilot, and NebulaONE cloud sandbox, ensuring user authentication, commercial data encryption, and exclusion of university data from public LLM training.

Official source ↗

Before you submit

Do

  • Always verify the designated AI assessment category (A, B, C, or D) in the course unit handbook and Canvas assessment brief before starting coursework (DocID 79331 §2.1.1, §2.1.3).
    Source guidance
  • Acknowledge AI use following University Library guidance: cite direct text/image use formally, provide an overview acknowledgement when asked or appropriate, and include prompts/outputs in an appendix when referencing AI as personal communication or required by School instructions.
    Source guidance
  • Use your University IT account to access Microsoft Copilot Chat for commercial data protection; if uploading taught session recordings for study assistance, use University-provided Microsoft 365 Copilot (DocID 79331 §2.2.2).
    Source guidance

Don’t

  • Never upload University copyright materials—including lecture recordings, slides, handouts, and exam questions—to external AI tools (DocID 79331 §2.2.1(c)); teaching staff handling student-identifiable data must exclusively use M365 Copilot (§2.3.1).
    Source guidance
  • Do not use generative AI in Category A (Prohibited) assessments (even for proofreading or spelling/grammar correction), or beyond surface presentation in Category B (Minimal); note that student choice not to use AI does not apply to Category D (Integrated).
    Source guidance
  • Do not present unacknowledged AI-generated content as your own (an indicator of academic malpractice under DocID 639 §3.1.3.6); markers rely on academic judgement and Turnitin similarity as the University does not use software claiming to detect GenAI (§4.2.2).
    Source guidance

AI use questioned?

The University of Manchester

Audience and activity scope varies strictly by source: Senate Policy DocID 79331 governs taught assessment categorization (Categories A–D) and copyright upload restrictions; Library referencing guidance governs citation and acknowledgement in coursework; Academic Malpractice Procedure DocID 639 governs malpractice investigations, detector prohibition, and authorship vivas; IT Services policies govern Copilot and NebulaONE tenant access.

Investigation & response

Under Academic Malpractice Procedure DocID 639 §4.4.2, where indicators raise concerns of commissioned work without direct evidence, or available information does not satisfy the balance of probabilities, a viva voce can be arranged in agreement with the School Officer to demonstrate authorship; it does not contribute to the mark. If held, it should not normally take place more than 30 working days after the assessment feedback deadline (§4.4.3.1); the student should receive at least five working days notice explaining its nature, purpose and potential outcomes (§4.4.3.2). Accompaniment by a person of the student’s choice is for support only without participation (§4.4.3.4), and reasonable adjustments must be made (§4.4.3.5). The viva itself cannot impose a penalty (§4.4.4.2); case handling follows the applicable AUO/SDP/UDP procedures (§5.1–5.5).

Original evidence and scope

Under Academic Malpractice Procedure DocID 639 §4.4.2, where indicators raise concerns of commissioned work without direct evidence, or available information does not satisfy the balance of probabilities, a viva voce can be arranged in agreement with the School Officer to demonstrate authorship; it does not contribute to the mark. If held, it should not normally take place more than 30 working days after the assessment feedback deadline (§4.4.3.1); the student should receive at least five working days notice explaining its nature, purpose and potential outcomes (§4.4.3.2). Accompaniment by a person of the student’s choice is for support only without participation (§4.4.3.4), and reasonable adjustments must be made (§4.4.3.5). The viva itself cannot impose a penalty (§4.4.4.2); case handling follows the applicable AUO/SDP/UDP procedures (§5.1–5.5).

clm-man-authorship-viva-voce

Optional authorship viva voce trigger, 30-working-day post-feedback-deadline timing, 5-working-day notice, support-only accompaniment, reasonable adjustments, non-punitive viva outcome, and AUO case handling

4.4.2. If there is a concern, based on indicators of malpractice, that a student may have commissioned a piece of work from a third party, but there is no direct evidence of this, or the information available does not satisfy the balance of probabilities, then in agreement with the School Officer a viva voce can be arranged to give the student the opportunity to demonstrate that they: 4.4.2.1. Produced the work; 4.4.2.2. Undertook the reading and research themselves; 4.4.2.3. Undertook the preparatory work themselves; 4.4.2.4. Understand what they have written. 4.4.3. If a viva voce is held, the following principles

Section 4.4 Contract cheating, Paragraphs 4.4.2–4.4.3.4, Page 9; Extracted text SHA256 db1ed4db97896ef1f771a937943e2402de1a954b0b0a56c53a781efa68c9af77; original binding lines 484–518; characters 31340–33372; excerpt offset 0–700

Official university source ↗
shall be met: 4.4.3.1. If a viva voce is to be conducted it should not normally take place more than 30 working days after the assessment feedback deadline. 4.4.3.2. The student should be given at least five working days’ notice of the requirement to attend the viva voce. An explanation of what a viva voce is, the purpose of it and the potential outcomes should be outlined in the invitation. It should be made clear that the viva voce is arranged due to the detection of potential academic malpractice and it is to allow the student an opportunity to demonstrate that the work is their own; i

Section 4.4 Contract cheating, Paragraphs 4.4.2–4.4.3.4, Page 9; Extracted text SHA256 db1ed4db97896ef1f771a937943e2402de1a954b0b0a56c53a781efa68c9af77; original binding lines 484–518; characters 31340–33372; excerpt offset 700–1400

Official university source ↗
t will not contribute to any mark obtained for the piece of work. 4.4.3.3. Two members of academic staff (at least one of whom must be a subject specialist) must conduct the viva voce; this will normally be the School Officer and the examiner of the assessment. 4.4.3.4. The student may be accompanied by a person of their choice for support only (normally a fellow student, member of staff or Students’ Union representative). Any individual accompanying the student should under no circumstances participate in the viva voce.

Section 4.4 Contract cheating, Paragraphs 4.4.2–4.4.3.4, Page 9; Extracted text SHA256 db1ed4db97896ef1f771a937943e2402de1a954b0b0a56c53a781efa68c9af77; original binding lines 484–518; characters 31340–33372; excerpt offset 1400–2032

Official university source ↗
4.4.3.5. Reasonable adjustments must be made to ensure that candidates with additional support needs are not disadvantaged for reasons relating to a long-term medical condition, sensory impairment, specific learning difficulty and /or disability. 4.4.3.6. The viva voce will not normally exceed 45 minutes. 4.4.3.7. Depending on situational circumstances, the viva voce can be conducted via video link. 4.4.3.8. Intensive questions are expected. The questions asked should provide the student with the opportunity to demonstrate that the work is their own. 4.4.3.9. An accurate record

Section 4.4 Contract cheating, Paragraphs 4.4.3.5–4.4.4.2, Page 10; Extracted text SHA256 db1ed4db97896ef1f771a937943e2402de1a954b0b0a56c53a781efa68c9af77; original binding lines 523–549; characters 33484–35257; excerpt offset 0–700

Official university source ↗
of the viva voce should be taken; this record may be used to form the evidence base for any future disciplinary hearing. It may be necessary for an administrative member of staff to be present at the viva voce to make the record. The student is entitled to have a copy of the record. 4.4.4. The viva voce can have one of two outcomes: 4.4.4.1. The staff conducting the viva voce will confirm that they accept that the student wrote the work in question; no further action will be taken. The work should then be marked on its own merit, if it has not already been marked. 4.4.4.2. If the st

Section 4.4 Contract cheating, Paragraphs 4.4.3.5–4.4.4.2, Page 10; Extracted text SHA256 db1ed4db97896ef1f771a937943e2402de1a954b0b0a56c53a781efa68c9af77; original binding lines 523–549; characters 33484–35257; excerpt offset 700–1400

Official university source ↗
aff conducting the viva voce still remain doubtful of the authorship of the work in question, or the student admits that it is not their work, then the case should be referred for disciplinary action. The viva voce, in itself, will not result in a penalty being applied; a penalty can only be applied by a disciplinary panel.

Section 4.4 Contract cheating, Paragraphs 4.4.3.5–4.4.4.2, Page 10; Extracted text SHA256 db1ed4db97896ef1f771a937943e2402de1a954b0b0a56c53a781efa68c9af77; original binding lines 523–549; characters 33484–35257; excerpt offset 1400–1773

Official university source ↗
5.1. When academic malpractice has been identified following section 4 above, the AUO responsible for assessing the allegation should gather any supplementary information that may be relevant for a disciplinary hearing. In particular, they should enquire as to whether a student has any previous offences for academic malpractice as this will indicate the appropriate panel to refer a case to. This information is usually retained in the student’s School record. This will assist the AUO in determining whether a case can be heard by a Summary Disciplinary Panel (“SDP”) or if the case should be referred to the University Disciplinary Panel (“UDP”).

Section 5 Case handling, Paragraph 5.1, Page 10; Extracted text SHA256 db1ed4db97896ef1f771a937943e2402de1a954b0b0a56c53a781efa68c9af77; original binding lines 553–560; characters 35279–35978; excerpt offset 0–699

Official university source ↗
5.4. The original person who reported the alleged malpractice should not be a member of the disciplinary panel. Additionally, where a student has already been interviewed or attended a viva as part of the information gathering exercise, any future disciplinary panel should not include, as a member of the panel, the same examiner or School Officer.

Section 5 Case handling, Paragraph 5.4, Page 11; Extracted text SHA256 db1ed4db97896ef1f771a937943e2402de1a954b0b0a56c53a781efa68c9af77; original binding lines 617–620; characters 40035–40411; excerpt offset 0–376

Official university source ↗

Possible outcomes

Under Academic Malpractice Procedure DocID 639 §4.4.2, where indicators raise concerns of commissioned work without direct evidence, or available information does not satisfy the balance of probabilities, a viva voce can be arranged in agreement with the School Officer to demonstrate authorship; it does not contribute to the mark. If held, it should not normally take place more than 30 working days after the assessment feedback deadline (§4.4.3.1); the student should receive at least five working days notice explaining its nature, purpose and potential outcomes (§4.4.3.2). Accompaniment by a person of the student’s choice is for support only without participation (§4.4.3.4), and reasonable adjustments must be made (§4.4.3.5). The viva itself cannot impose a penalty (§4.4.4.2); case handling follows the applicable AUO/SDP/UDP procedures (§5.1–5.5).

Original evidence and scope

Under Academic Malpractice Procedure DocID 639 §4.4.2, where indicators raise concerns of commissioned work without direct evidence, or available information does not satisfy the balance of probabilities, a viva voce can be arranged in agreement with the School Officer to demonstrate authorship; it does not contribute to the mark. If held, it should not normally take place more than 30 working days after the assessment feedback deadline (§4.4.3.1); the student should receive at least five working days notice explaining its nature, purpose and potential outcomes (§4.4.3.2). Accompaniment by a person of the student’s choice is for support only without participation (§4.4.3.4), and reasonable adjustments must be made (§4.4.3.5). The viva itself cannot impose a penalty (§4.4.4.2); case handling follows the applicable AUO/SDP/UDP procedures (§5.1–5.5).

clm-man-authorship-viva-voce

Optional authorship viva voce trigger, 30-working-day post-feedback-deadline timing, 5-working-day notice, support-only accompaniment, reasonable adjustments, non-punitive viva outcome, and AUO case handling

4.4.2. If there is a concern, based on indicators of malpractice, that a student may have commissioned a piece of work from a third party, but there is no direct evidence of this, or the information available does not satisfy the balance of probabilities, then in agreement with the School Officer a viva voce can be arranged to give the student the opportunity to demonstrate that they: 4.4.2.1. Produced the work; 4.4.2.2. Undertook the reading and research themselves; 4.4.2.3. Undertook the preparatory work themselves; 4.4.2.4. Understand what they have written. 4.4.3. If a viva voce is held, the following principles

Section 4.4 Contract cheating, Paragraphs 4.4.2–4.4.3.4, Page 9; Extracted text SHA256 db1ed4db97896ef1f771a937943e2402de1a954b0b0a56c53a781efa68c9af77; original binding lines 484–518; characters 31340–33372; excerpt offset 0–700

Official university source ↗
shall be met: 4.4.3.1. If a viva voce is to be conducted it should not normally take place more than 30 working days after the assessment feedback deadline. 4.4.3.2. The student should be given at least five working days’ notice of the requirement to attend the viva voce. An explanation of what a viva voce is, the purpose of it and the potential outcomes should be outlined in the invitation. It should be made clear that the viva voce is arranged due to the detection of potential academic malpractice and it is to allow the student an opportunity to demonstrate that the work is their own; i

Section 4.4 Contract cheating, Paragraphs 4.4.2–4.4.3.4, Page 9; Extracted text SHA256 db1ed4db97896ef1f771a937943e2402de1a954b0b0a56c53a781efa68c9af77; original binding lines 484–518; characters 31340–33372; excerpt offset 700–1400

Official university source ↗
t will not contribute to any mark obtained for the piece of work. 4.4.3.3. Two members of academic staff (at least one of whom must be a subject specialist) must conduct the viva voce; this will normally be the School Officer and the examiner of the assessment. 4.4.3.4. The student may be accompanied by a person of their choice for support only (normally a fellow student, member of staff or Students’ Union representative). Any individual accompanying the student should under no circumstances participate in the viva voce.

Section 4.4 Contract cheating, Paragraphs 4.4.2–4.4.3.4, Page 9; Extracted text SHA256 db1ed4db97896ef1f771a937943e2402de1a954b0b0a56c53a781efa68c9af77; original binding lines 484–518; characters 31340–33372; excerpt offset 1400–2032

Official university source ↗
4.4.3.5. Reasonable adjustments must be made to ensure that candidates with additional support needs are not disadvantaged for reasons relating to a long-term medical condition, sensory impairment, specific learning difficulty and /or disability. 4.4.3.6. The viva voce will not normally exceed 45 minutes. 4.4.3.7. Depending on situational circumstances, the viva voce can be conducted via video link. 4.4.3.8. Intensive questions are expected. The questions asked should provide the student with the opportunity to demonstrate that the work is their own. 4.4.3.9. An accurate record

Section 4.4 Contract cheating, Paragraphs 4.4.3.5–4.4.4.2, Page 10; Extracted text SHA256 db1ed4db97896ef1f771a937943e2402de1a954b0b0a56c53a781efa68c9af77; original binding lines 523–549; characters 33484–35257; excerpt offset 0–700

Official university source ↗
of the viva voce should be taken; this record may be used to form the evidence base for any future disciplinary hearing. It may be necessary for an administrative member of staff to be present at the viva voce to make the record. The student is entitled to have a copy of the record. 4.4.4. The viva voce can have one of two outcomes: 4.4.4.1. The staff conducting the viva voce will confirm that they accept that the student wrote the work in question; no further action will be taken. The work should then be marked on its own merit, if it has not already been marked. 4.4.4.2. If the st

Section 4.4 Contract cheating, Paragraphs 4.4.3.5–4.4.4.2, Page 10; Extracted text SHA256 db1ed4db97896ef1f771a937943e2402de1a954b0b0a56c53a781efa68c9af77; original binding lines 523–549; characters 33484–35257; excerpt offset 700–1400

Official university source ↗
aff conducting the viva voce still remain doubtful of the authorship of the work in question, or the student admits that it is not their work, then the case should be referred for disciplinary action. The viva voce, in itself, will not result in a penalty being applied; a penalty can only be applied by a disciplinary panel.

Section 4.4 Contract cheating, Paragraphs 4.4.3.5–4.4.4.2, Page 10; Extracted text SHA256 db1ed4db97896ef1f771a937943e2402de1a954b0b0a56c53a781efa68c9af77; original binding lines 523–549; characters 33484–35257; excerpt offset 1400–1773

Official university source ↗
5.1. When academic malpractice has been identified following section 4 above, the AUO responsible for assessing the allegation should gather any supplementary information that may be relevant for a disciplinary hearing. In particular, they should enquire as to whether a student has any previous offences for academic malpractice as this will indicate the appropriate panel to refer a case to. This information is usually retained in the student’s School record. This will assist the AUO in determining whether a case can be heard by a Summary Disciplinary Panel (“SDP”) or if the case should be referred to the University Disciplinary Panel (“UDP”).

Section 5 Case handling, Paragraph 5.1, Page 10; Extracted text SHA256 db1ed4db97896ef1f771a937943e2402de1a954b0b0a56c53a781efa68c9af77; original binding lines 553–560; characters 35279–35978; excerpt offset 0–699

Official university source ↗
5.4. The original person who reported the alleged malpractice should not be a member of the disciplinary panel. Additionally, where a student has already been interviewed or attended a viva as part of the information gathering exercise, any future disciplinary panel should not include, as a member of the panel, the same examiner or School Officer.

Section 5 Case handling, Paragraph 5.4, Page 11; Extracted text SHA256 db1ed4db97896ef1f771a937943e2402de1a954b0b0a56c53a781efa68c9af77; original binding lines 617–620; characters 40035–40411; excerpt offset 0–376

Official university source ↗

Review & appeal

The current evidence does not include a verified specific procedure or deadline. Check the applicable university rules.

AI tools & access

  • Microsoft CopilotInstitutional access / licenceRecorded as allowed in the source scope

    Log in to copilot.microsoft.com or Microsoft Teams using University credentials.

  • Microsoft 365 CopilotInstitutional access / licenceConditions apply

    Licenses assigned in phased cohorts; check the Microsoft 365 Copilot SharePoint space.

  • NebulaONEUniversity-hosted serviceConditions apply

    Submit early access request via the Nebula One Request Form.

Record updatesLast 90 days · Recorded updates: 3

Updates to this site's reviewed record, not confirmation that the university changed its policy.

  1. Page update

    Other records · Page update

    View revision

    Loading revision…

  2. Record maintenance

    Other records · Record maintenance

    View revision

    Loading revision…

  3. Record addition · Site correction

    Academic integrity · Teaching · 3 more topics · Records involved: 31 (15 corrected / adjusted · 16 added)

    View revision

    Loading revision…

Reviewed claims

31

Official sources

8 official URLs; 8 source attributions and their captured versions retained.

AI in Teaching and Learning Policy

documents.manchester.ac.uk

University official source

Senate, The University of Manchester

Hash and captured version

AI in Teaching and Learning Policy · 2026-10-21T15:06:00Z

SHA-256 of the retained capture file bytes.

dcff27c5977597bc51e7617581945974a44729b229de2e9efe42e230d00ccaeb

Hashes identify a captured version; they do not establish current policy or review approval.

Official source ↗

Academic Malpractice Procedure

documents.manchester.ac.uk

University official source

Student and Academic Services, The University of Manchester

Hash and captured version

Academic Malpractice Procedure · 2026-10-21T15:06:00Z

SHA-256 of the retained capture file bytes.

23a15e2b813deead551a3e3151c3b3f01a17d7c204723f94abd4c76494b31e49

Hashes identify a captured version; they do not establish current policy or review approval.

Official source ↗

University AI Guidelines | AI Hub | StaffNet | The University of Manchester

www.staffnet.manchester.ac.uk

University official source

StaffNet, The University of Manchester

Hash and captured version

University AI Guidelines | AI Hub | StaffNet | The University of Manchester · 2026-10-21T15:06:00Z

SHA-256 of the retained capture file bytes.

becd22deed500c75cb396085f5e2023181214ce41ca020584032407b014db270

Hashes identify a captured version; they do not establish current policy or review approval.

Official source ↗

Approved Tools | AI Hub | StaffNet | The University of Manchester

www.staffnet.manchester.ac.uk

University official source

StaffNet, The University of Manchester

Hash and captured version

Approved Tools | AI Hub | StaffNet | The University of Manchester · 2026-10-21T15:06:00Z

SHA-256 of the retained capture file bytes.

308d1a6ab33417437cf2580a3f79c6e6b0c1c1687d1531dd6de9a86970b8b398

Hashes identify a captured version; they do not establish current policy or review approval.

Official source ↗

AI and referencing - Referencing guide at the University of Manchester

subjects.library.manchester.ac.uk

University official source

University of Manchester Library

Hash and captured version

AI and referencing - Referencing guide at the University of Manchester · 2026-10-21T15:06:00Z

SHA-256 of the retained capture file bytes.

7a92ceddd3973ac5742b594cd7454424eac321a4469555ae8c15f89b86505d65

Hashes identify a captured version; they do not establish current policy or review approval.

Official source ↗

Copilot (The University of Manchester)

www.itservices.manchester.ac.uk

University official source

IT Services, The University of Manchester

Hash and captured version

Copilot (The University of Manchester) · 2026-10-21T15:06:00Z

SHA-256 of the retained capture file bytes.

f4482920cb6906f1bc0db2421c6c757cd3618c63cadcd40b7087bd7454913881

Hashes identify a captured version; they do not establish current policy or review approval.

Official source ↗

Artificial Intelligence and Teaching and Learning - Teaching College

www.teachingcollege.fse.manchester.ac.uk

University official source

Faculty of Science and Engineering Teaching College, The University of Manchester

Hash and captured version

Artificial Intelligence and Teaching and Learning - Teaching College · 2026-10-21T15:06:00Z

SHA-256 of the retained capture file bytes.

fce26e2c6bb6df07090689b87c4222118190a262f5d5dbaf73d1c98e0d785b7f

Hashes identify a captured version; they do not establish current policy or review approval.

Official source ↗

AI Guidance for Learners - Technology Enhanced Learning and Design

elearning.bmh.manchester.ac.uk

University official source

Faculty of Biology, Medicine and Health, The University of Manchester

Hash and captured version

AI Guidance for Learners - Technology Enhanced Learning and Design · 2026-10-21T15:06:00Z

SHA-256 of the retained capture file bytes.

ee497397a173ad2529eb76ec25b69eb24ba2f9e90c85dcce2aafbcf83b949e00

Hashes identify a captured version; they do not establish current policy or review approval.

Official source ↗
Record information, JSON & citation

Review layers: claim review applies to the claims only. Analysis is a separate machine-generated summary awaiting review. Coverage scores do not establish complete policy knowledge.

Claim review state
agent_reviewed
Analysis review state
machine_candidate
Record revision
qs35-40-v6-r4-meta-20261022
Dataset release
public-release-20260924-002
Correction published
Student snapshot
Not published
Current reviewed JSON · Historical baseline

Published V6 presentation; JSON and MCP retain the existing public record. Supplementary quotations and scope notes remain pending review. Local candidate corrections, tools and student summaries are not approved for publication. Institution-wide audit remains PARTIAL.

  • No separate centralized AI examination policy document exists; exams are categorized individually under the Senate 4-category framework (DocID 79331 §2.1.1).
  • Public REST API tools.json exposes 8 standalone records for universitySlug=='manchester' without explicit id fields; reconciled by naturalKey into 3 canonical tool proposals. MCP get_student_policy returns an empty tool array.
  • DocID 639 references separate University instruments—Regulation XVII (Conduct and Discipline of Students), Guidance to students on Penalties for Academic Malpractice, and SDP/UDP procedures—which are not captured in the current source bundle; specific appeal deadlines, start events, and penalty tariffs are held.
  • Complete private historical held decisions have not been independently reconciled; original captured history is preserved.
  • The historical student snapshot is preserved and does not grant approval to this local corrected view.
        Current reviewed JSON
        Questions students ask

        Questions students ask

        Can I use AI for my coursework?

        Under Senate Policy DocID 79331 §2.1.1, assessments are categorized into four levels (Category A: AI Prohibited, Category B: AI Minimal, Category C: AI Permitted, Category D: AI-Integrated) by Course Unit Directors and clearly stated in unit specifications and Canvas briefs (§2.1.3). Students may choose not to use AI for Categories A, B, and C without disadvantage, but this choice does not apply to Category D assessments which assess AI learning outcomes (§2.1.2). In Category A, all AI use including proofreading and text editing is prohibited; in Category B, AI is restricted to presentation only (fluency, grammar, spelling, formatting) without altering student ideas, arguments, or conclusions.

        View evidence →
        Do I need to disclose AI use?

        Under University Library referencing guidance, students must cite generative AI tools when using text or images directly in their work following 'Cite them Right' conventions. Where asked or deemed appropriate, students should include an overview acknowledgement at the start of work or in a footnote. An appendix detailing relevant prompts, outputs, generation dates, and modification statements is required when referencing AI as personal communication or when instructed by School guidance. Using tools for basic grammar and spell checking does not require acknowledgement unless School guidance requires it.

        View evidence →
        Can I upload sensitive data?

        Under Senate Policy DocID 79331 §2.2.1(c), students must not upload University-owned copyright materials (such as lecture recordings, slides, handouts, or examination questions) to external commercial AI tools. Under §2.2.2, students are explicitly permitted to upload session recordings into University-provided Microsoft 365 Copilot for study support. Under §2.3.1, staff members who use AI in Teaching and Learning activities must adhere to the University's AI Guidelines, and only the University-provided Microsoft 365 Copilot service may be used for student-identifiable or confidential data.

        View evidence →
        Which tools can I access?

        The University provides Microsoft Copilot Chat with Commercial Data Protection to all active students and staff using University credentials. Microsoft 365 Copilot suite is deploying in phased license cohorts across 65,000 colleagues and students. NebulaONE is provided as an enterprise cloud AI development sandbox. Under DocID 79331 §2.1.1 and §2.2.1, having access to institutional AI tools does not confer permission to use them in Category A assessments.

        View evidence →
        What are the examination rules?

        Examinations and timed assessments are categorized individually under the four-category framework (DocID 79331 §2.1.1). Under Academic Malpractice Procedure DocID 639 §3.1.2.5 and §4.3.1, students must adhere strictly to examination conditions communicated before the exam, and possessing or using unauthorized AI tools or online materials in examination sittings constitutes academic malpractice.

        View evidence →
        What rules apply to research and publication?

        Under StaffNet Research Guidelines, any use of AI to synthesise research data must be completely transparent, and fabricating or falsifying data with AI constitutes research misconduct. Corresponding authors carry ultimate responsibility for publication credibility and must declare significant AI assistance. Researchers reviewing papers or grants must preserve peer review confidentiality and never upload unpublished manuscripts into external AI services.

        View evidence →
        What counts as academic misconduct?

        The University does not currently use software claiming to detect generative AI; Turnitin alone does not confirm malpractice and academic judgment is required. Under Academic Malpractice Procedure DocID 639 §4.4.2, where indicators raise concerns of commissioned work without direct evidence, or available information does not satisfy the balance of probabilities, a viva voce can be arranged in agreement with the School Officer to demonstrate authorship; it does not contribute to the mark. If held, it should not normally take place more than 30 working days after the assessment feedback deadline (§4.4.3.1); the student should receive at least five working days notice explaining its nature, purpose and potential outcomes (§4.4.3.2). Accompaniment by a person of the student’s choice is for support only without participation (§4.4.3.4), and reasonable adjustments must be made (§4.4.3.5). The viva itself cannot impose a penalty (§4.4.4.2); case handling follows the applicable AUO/SDP/UDP procedures (§5.1–5.5).

        View evidence →
        What guidance applies to teaching?

        Senate Policy DocID 79331 and Faculty guidance mandate that Course Unit Directors specify AI categories in unit specifications and Canvas briefs (§2.1.3), establish group work logging rules and require prior peer consent before recording group discussions (§2.1.4–2.1.5), and require teaching staff handling student-identifiable data to use M365 Copilot (§2.3.1). Faculty guidance (FSE, BMH) supplements central policy.

        View evidence →
        What security and procurement requirements apply?

        IT Services and Information Governance establish clear tenant boundaries for Copilot Chat, Microsoft 365 Copilot, and NebulaONE cloud sandbox, ensuring user authentication, commercial data encryption, and exclusion of university data from public LLM training.

        View evidence →
        When was this record checked?

        Record checked:

        Record version →
        Which official sources support these rules?Official source →
        Where can I read the full evidence?

        31 · Full policy evidence

        Full policy evidence →
        The University of Manchester AI Policy