ASA Policies & Procedures
Page 1 of 82
CODE OF ETHICS
Purpose
This Code of Ethics is designed to outline the standard of behaviour expected by employees of
Angel Solutions Australia (ASA).
Code
ASA staff are expected to adhere to the following values:
Be inclusive: ensure that all internal and external customers are treated the
same.
Be honest: ensure that you in business representations with internal and
external customers.
Be accountable: promise what you say you will deliver.
Be sustainable: ensure that sustainability plays an important part in any work
activities that you undertake.
Be professional: ensure that you act with integrity at all times.
Document Control
Document No. & Name: HR005 – Code of Ethics
Quality Area: Human Resources (HR)
Author: Angel Solutions Australia (ASA)
Status: Approved
Approved By: John Clarke
Approval Date: 26/10/2020
Review Date: 27/10/2021
ASA Policies & Procedures
Page 2 of 82
GOVERNANCE POLICY & PROCEDURES
Purpose
To ensure content of Angel Solutions Australia (ASA) constitution by making explicit the
underlying principles of governance approved by the organisation.
Policy
1. Board Members
The board is a made up of the following members:
Managing Director
Chief Financial Officer
Governance Manager
2. Board Objectives
The board objectives are to:
Set the strategic direction of the organisation
Uphold the organisations values
Ensure attainment of the organisations business objectives
Ensure the financial stability and viability of the organisation
Ensure compliance with legal and ethical obligations
3. Governance Framework
The following elements form the Governance Framework for ASA:
Organisational structure and governance
Strategic planning
Compliance and regulatory monitoring
Policies and procedures
Financial management
Leadership
Risk management
ASA Policies & Procedures
Page 3 of 82
Dispute management
Social responsibility
Accountability
4. Strategic Versus Operational
The Board’s objectives and responsibilities to manage the strategic direction and policies for
the organisation, rather than being involved in day-to-day operational issues which should be
the province of functional managers.
Procedure
1. Project Governance Management
1.1. When staff members are undertaking both functional operational duties and project-based
duties, a Project Governance Plan should be developed including:
An introduction should be provided about what the project and plan are
designed to achieve.
The scope for the plan should be specified.
The success criteria for measuring the plans success should be specified
Governance roles and responsibilities for the project should be specified to
ensure that the governance team for the project have a clear understanding of
their responsibilities
The levels of authority including those within the project team and functional
managers should be specified. This should detail who has authority and for what
to try and minimise conflict around project and operational tasks.
Specify how issues are escalated and resolved to ensure that a clear pathway of
issue resolution is mapped out.
1.2. Once the plan has been drafted, approval should be sought from the ASA board to ensure
the potential for later conflict is minimised.
1.3. Once approved, regular weekly reports by email should be to the ASA board on
performance and issues should be distributed by the project manager (or delegated team
member).
1.4. Once the project has been completed a review of the project governance impact on
achieving project objectives should be undertaken. The outcome of this review should be to
document any lessons learned using the Lessons Learned Form so that recommendations to
assist future projects can be identified for continuous improvements can be made.
ASA Policies & Procedures
Page 4 of 82
Related Documents
The following are related to this policy and procedures:
TM017 – Project Governance Plan
FM024 – Lessons Learned Form
Document Control
Document No. & Name: IM001 – Governance Policy
Quality Area: Internal Management (IM)
Author: Angel Solutions Australia (ASA)
Status: Approved
Approved By: John Clarke
Approval Date: 26/10/2020
Review Date: 27/10/2021
ASA Policies & Procedures
Page 5 of 82
DOCUMENT MANAGEMENT POLICY & PROCEDURES
Purpose
This policy defines Angel Solutions Australia’s (ASA) approach to the development, review,
naming and version control of all documents including tools, forms, resources, policies and
procedures.
Policy
1. Version Control
All internally produced documents used by the organisation are subject to version
control as set out in the procedures section of this document.
All staff must ensure that they use the cu
ent version of all documents.
2. Document Storage and Development
Electronic files will be saved centrally for access by staff in the organisations cloud-
ased storage system. Files are archived as they are superseded by a new version. Files
will not be deleted other than by an appointed person for maintenance purposes and
only where a backup of the data exists.
3. Document Development and Reviews
All document authors or reviewers must follow a consistent approach to the
development of documents, and follow all guidelines as set out in the procedures
section. Document authors or developers must also ensure that prior to the
development or revision of any document, approval to commence revision or
development is granted by their immediate manager, or by the Managing Director.
Policies and procedures will be reviewed at least annually to ensure they are up to date,
accurate and compliant. Other documents will be reviewed during continuous
improvement processes. The Governance Manager is responsible for ensuring that
policies and procedures are reviewed by their due date.
4. Document Approval
All documents are subject to approval prior to use by any staff member. Approval must
e given for every document by the authorised person specified within the procedure
section.
Approved documents will be saved for use in the organisations cloud-based storage
system.
ASA Policies & Procedures
Page 6 of 82
Procedures
1. Document Development
Format of documents
All documents must conform to the ASA Style Guide.
Document naming
All documents must be named clearly so that others can easily interpret what
the document is for. For example, “Sales Report December 2021”
Development of policies and procedures
Policies and procedures are to be written using the Policy and Procedures
template. The templates include the appropriate headings and format.
Include the ‘Document Control’ section at the end of the document showing the
details of the policy/ procedure and link it to standards where applicable.
Policies and procedures are coded according to the area of business they relate
to.
All policies and procedures are to be considered draft until approved by the
Governance team.
2. Version Control
Whenever an update is made to a file, a new version of the file with the same name is
created.
The cloud-based storage system implements an automatically version numbering
system when a new version is updated to the system. The system will increment the
cu
ent version by 1. For example, version 1 will become version 2 when the document
is updated.
Version control should be shown on in the footer of the first page of the document.
3. Document Approval
Approval responsibility
Forms, policies, and procedures need to be approved by the Governance
Manager.
Training and assessment documents and materials must be approved by the
Training Manager.
ASA Policies & Procedures
Page 7 of 82
All other documents must be approved by the Governance Manager or by the
Managing Director as appropriate.
4. Saving Approved Versions
When approving a document, save the approved version to the organisations cloud-
ased storage system.
Record approved documents
Once a document has been approved ensure the document details are provided to the
Governance Manager for recording in the document register.
5. Document Storage
Electronic File Storage
The cloud-based storage system has folders set up for each area of the business.
Files must be saved in the folder most appropriate to its area of business.
Documents from ‘Archived’ folders are not to be used. These are used for
archival purposes only.
If a required document cannot be found contact the Governance Manager.
No files are ever to be deleted from the file server by anyone other than a
designated person appointed to do so by the General Manager.
Archiving Documents
Upon the approval of a new version of a document, the cloud-based system will
move the superseded files into the ‘Archived’ folder automatically.
Related Documents
The following are related to this policy and procedures:
BD002 – ASA Style Guide
TM005 – Policy and Procedures Template
Document Control
Document No. & Name: IM002 – Document Management Policy & Procedures
Quality Area: Internal Management (IM)
Author: Angel Solutions Australia (ASA)
ASA Policies & Procedures
Page 8 of 82
Status: Approved
Approved By: John Clarke
Approval Date: 26/10/2018
Review Date: 27/10/2018
ASA Policies & Procedures
Page 9 of 82
COMMUNICATION POLICY & PROCEDURES
Purpose
The purpose of this policy is to specify the various channels of communication within Angel
Solutions Australia (ASA), determine their intended purpose, and the roles and responsibilities
of staff in accessing and using them.
Policy
1. Communication Objectives
Internal communication is used to reinforce the organisations business priorities and
objectives. This involves ensuring that information disseminated to staff is valid, reliable,
elevant, easy to access, and appropriate.
ASA aims to continue to develop and trial new communication ideas, channels, and
tools to improve information sharing and collaboration between staff members.
Staff are actively encouraged to share information within the workplace. ASA expects
that staff will use the communication channels and associated tools for business work
practices and in compliance with this and other relevant policies and procedures.
2. Communication Channels
ASA has a number of communication channels for intended purposes including:
Email: Used for messages to staff, clients, and other stakeholders.
Client surveys: Used to gather information and feedback from clients for a range
of purposes.
Presentation: Used to present information ve
ally for internal work groups such
as meetings, inductions, or to external clients and stakeholders.
Business documentation: Used to present information formally in written format
to staff members such as reports, policies and procedures, and other business-
elated documents. Also used to present information in written format to clients
and other stakeholders such as business co
espondence, invoices, and other
usiness-related matters.
Cloud-based collaborative tools: Used by work groups of staff to collaborate,
share, and communicate on projects online
Website and social media channels: Used to inform clients of services offered.
Used by staff to access policies and procedures.
ASA Policies & Procedures
Page 10 of 82
Instant messaging: Used to allow real-time communication between staff
members informally.
Video-conferencing: Used for video communication between staff, clients, and
other stakeholders where communication occurs remotely.
Phone: Used for real-time discussion between staff members and clients.
Procedures
1. Meeting Preparation
Prior to a meeting taking place the presenter of the meeting should:
Identify the objective(s) of the meeting
Identify the audience of the meeting
Schedule a time and location for the meeting location
Identify the items to be covered at the meeting to meet its objective(s)
Ensure that they have reserved
ooked out facilities required for the meeting.
Develop a Meeting Agenda and distribute this to the audience of the meeting
prior to the meeting occu
ing.
Prepare appropriate materials as required for the meeting such as handouts,
equipment such as projectors and computers, catering, or any other materials
equired for the meeting
2. Meeting Delivery
The presenter should conduct the meeting as per the Meeting Agenda by:
Providing an introduction to the purpose of the meeting
Taking attendance
Covering minutes from any previous meeting
Covering agenda items
Coming to agreement about planned outcomes.
Provide a closing to the meeting, thanking the attendees for their time.
The presenter should ensure that they and the attendees show respect to other
attendees by:
ASA Policies & Procedures
Page 11 of 82
Ensuring attendees don’t speak over other attendees
Ensuring that attendees act ethically as per the organisations Code of Ethics
during the meeting
Ensuring attendees answer questions posed to them openly and with honesty
Managing disagreements between attendees ensuring that differences of
opinions are acknowledged, and that rigorous examination of all options is
explored to reach a