ERP Software Management (Ltd) Pty treats all cases of suspected malpractice* very seriously and will
investigate all suspected and reported incidents of possible malpractice. The purpose of this Policy is

to set out how allegations of malpractice in relation to all our qualifications are dealt with. The scope
of the policy is to provide:

• A definition of malpractice
• examples of student and centre malpractice and maladministration.
• possible sanctions that may be imposed in cases of malpractice.

– The term CIPS is used to indicate any International Certification Organization represented by
ERP Software Management.

– *The term ‘malpractice’ in this policy is used for both malpractice and maladministration.

1 Introduction

1.1 For this document ‘malpractice’ is defined as:

Any act, or failure to act, that threatens or compromises the integrity of the assessment process or the
validity of our qualifications and their certification. This includes maladministration and the failure to maintain appropriate records or systems; the deliberate falsification of records or documents for any reason connected to the award of our qualifications; acts of plagiarism or other academic misconduct; and/or actions that compromise the reputation or authority of ERP Software Management (Pty), or of our Chartered Institute Of Procurement and Supply Chain (CIPS), its centres and employees.

ERP Software Management (Pty) Ltd will report all relevant cases of suspected malpractice to CIPS, accepting that in certain circumstances the CIPS may take necessary action of its own, including imposing sanctions.

Malpractice Policy — For Students

2 Malpractice by students

2.1 Some examples of student malpractice are described below. These examples are not exhaustive and all incidents of suspected malpractice,
whether described below, will be fully investigated, where there are sufficient grounds to do so.

2.1.1 Obtaining examination or assessment material without authorisation.
2.1.2 Arranging for an individual other than the student to sit an assessment or to submit an assignment not undertaken by the student.

2.1.3. Impersonating another student to sit an assessment or to submit an assignment on their behalf.

2.1.4 Collaborating with another student or individual, by any means, to complete a coursework assignment or assessment, unless it has
been clearly stated that such collaboration is permitted.

2.1.5 Damaging another student’s work.
2.1.6 — Inclusion of inappropriate or offensive material in coursework assignments or assessment scripts.

2.1./_ Failure to comply with published CIPS’s examination regulations.

2.1.8 Disruptive behaviour or unacceptable conduct, including the use of offensive language, at centre or assessment venue (including
aggressive or offensive language or behaviour).

2.1.9 Producing, using, or allowing the use of forged or falsified documentation, including but not limited to:

personal identification
supporting evidence provided for reasonable adjustment or special consideration applications and

the CIPS’s results documentation, including certificates

2.1.10 Falsely obtaining, by any means, an CIPS’s certificate.

2.1.11 Misrepresentation or plagiarism or fraudulent claims for special consideration while studying.

                Malpractice Policy and Procedure – Employees

3 Malpractice by center employees and stakeholders

3.1 Examples of malpractice by, teachers, tutors and other officers are listed below. These examples are not exhaustive and all incidents of suspected
malpractice, whether described below, will be fully investigated, where there are sufficient grounds to do so.

3.1.1 Failure to adhere to the relevant CIPS’s regulations and procedures, including those relating to centre approval, security undertaking and monitoring
requirements as set out by the CIPS.

3.1.2 Knowingly allowing an individual to impersonate a student.
3.1.3. Allowing a student to copy another student’s assignment work or allowing a student to let their own work be copied.
3.1.4 Allowing students to work collaboratively during an assignment assessment, unless specified in the assignment brief.

3.1.5 Completing an assessed assignment for a student or providing them with assistance beyond that ‘normally’ expected.

3.1.6 Damaging a student’s work.

3.1.7 Disruptive behaviour or unacceptable conduct, including the use of offensive language (including aggressive or offensive language or behaviour).

3.1.8 Allowing disruptive behaviour or unacceptable conduct at the centre to go unchallenged, for example, aggressive or offensive language or
behaviour.

3.1.9. Divulging any information relating to student performance and / or results to anyone other than the student.

3.1.10 Producing, using, or allowing the use of forged or falsified documentation, including but not limited to:

• personal identification
• supporting evidence provided for reasonable adjustment or special consideration applications and

« The CIPS’s results documentation, including certificates

3.1.11 Falsely obtaining by any means an CIPS certificate.

3.1.12 Failing to report a suspected case of student malpractice, including plagiarism, to the CIPS.

Malpractice Policy – Sanctions

3 Possible malpractice sanctions

3.1 Following an investigation, if a case of malpractice is upheld, ERP Software Management (Pty) Ltd may impose sanctions or other penalties on the
individual(s) concerned. Where relevant we will report the matter to the CIPS, and the CIPS may impose one or more sanctions upon the

individual(s) concerned. Any sanctions imposed will reflect the seriousness of the malpractice that has occurred.

3.2 Listed below are examples of sanctions that may be applied to a student, or to a teacher, tutor, invigilator, or other officer who has had a
case of malpractice upheld against them. Please note that
i) this list is not exhaustive and other sanctions may be applied on a case-by-case basis

1. ii) where the malpractice affects examination performance, the CIPS may impose sanctions of its own

Possible study centre sanctions that may be applied to students
A written warning about future conduct.
« Notification to an employer, regulator, or the police.

Removal from the course.

Possible sanctions that may be applied to teachers, tutors’ invigilators, and other officers

A written warning about future conduct.

Imposition of special conditions for the future involvement of the individual(s) in the conduct, teaching, supervision, or administration of
students and/or examinations.

Informing any other organisation known to employ the individual in relation to CIPS courses or examinations of the outcome of the case.

¢ ERP Software Management (Pty) Ltd may carry out Unannounced monitoring of the working practices of the individual(s) concerned.

Dismissal.

Malpractice Policy – Procedure

Procedure

4 Reporting a suspected case of malpractice

4.1 This process applies to, teachers, tutors, invigilators students and other centre staff, and to any reporting of malpractice by a third
party or individual who wishes to remain anonymous.

4.2. Any case of suspected malpractice should be reported in the first instance to Abiola Oliyide(Co-founder & Managing Partner)

4.3. A written report should then be sent to the person identified in 5.2, clearly identifying the factual information, including statements
from other individuals involved and / or affected, any evidence obtained, and the actions that have been taken in relation to the
incident.

4.4 Suspected malpractice must be reported as soon as possible to the person identified in 5.2, and at the latest within two working
days from its discovery. Where the suspected malpractice has taken place in an examination, the incident be reported urgently, and
the appropriate steps taken as specified by the CIPS.

4.5 Wherever possible, and provided other students are not disrupted by doing so, a student suspected of malpractice should be
warned immediately that their actions may constitute malpractice, and that a report will be made to the centre.

4.6 In cases of suspected malpractice by centre teachers, tutors ’invigilators and other officers, and any reporting of malpractice by a
third party or individual who wishes to remain anonymous, the report made to the person in 5.2 should include as much information
as possible, including the following:

the date time and place the alleged malpractice took place, if known
the name of the centre teacher/tutor, invigilator or other person(s) involved
a description of the suspected malpractice and
any available supporting evidence
4.7 In cases of suspected malpractice reported by a third party, or an individual who wishes to remain anonymous, ERP Software Management (Pty) Ltd  Institute will take all reasonable steps to authenticate the reported information and to investigate the alleged malpractice.

Malpractice Policy – Procedure

5 Administering suspected cases of malpractice

5.1 ERP Software Management (Pty) Ltd will investigate each case of suspected or reported malpractice relating to the CIPS’s qualifications, to ascertain whether
malpractice has occurred. The investigation will aim to establish the full facts and circumstances. We will promptly take all reasonable steps to prevent any
adverse effect that may arise as a result of the malpractice, or to mitigate any adverse effect, as far as possible, and to correct it to make sure that any
action necessary to maintain the integrity of the CIPS’s qualifications and reputation is taken.

5.2. ERP Software Management (Pty) Ltd will acknowledge all reports of suspected malpractice within five working days. All of the parties involved in the case will then

be contacted within 10 working days of receipt of the report detailing the suspected malpractice. We may also contact other individuals who may be able
to provide evidence relevant to the case.

5.3. The individual(s) concerned will be informed of the following:

that an investigation is going to take place, and the grounds for that investigation.

details of all the relevant timescales, and dates, where known.

that they have a right to respond by providing a personal written response relating to the suspected malpractice (within 15 working days of the date
of that letter).

that, if malpractice is considered proven, sanctions may be imposed either by ERP Software Management (Pty) Ltd or by any CIPS, reflecting the seriousness of
the case.

« That, if they are found guilty, they have the right to appeal.

That ERP Software Management (Pty) Ltd has a duty to inform the relevant CIPS and other relevant authorities / regulators, but only after time for the appeal
has passed or the appeal process has been completed. This may also include informing the police if the law has been broken and to comply with any
other appropriate legislation.

5.4 Where more than one individual is contacted regarding a case of suspected malpractice, for example in a case involving suspected collusion, we will contact
everyone separately, and will not reveal personal data to any third party unless necessary for the purpose of the investigation.

5.5 The individual has a right to appeal against a malpractice outcome if they believe that the policy or procedure has not been followed properly or has been
implemented to their detriment.

5.6 Records of all malpractice cases and their outcomes are maintained by ERP Software Management (Pty) Ltd for a period of at least five years and are subject to
regular monitoring and review.