This not the latest approved version of this apprenticeship. View the latest version
This apprenticeship is in revision and yet to be approved
This apprenticeship has options. This document is currently showing the following option:
This occupation is found in organisations, large and small, in all sectors, and within public, private and voluntary organisations. Organisations of all types are increasing applying digital technologies across all their business functions to maximise productivity. The demand for people who can support and implement these digital operations and digital change projects is increasing. Organisations of all types are increasingly supporting their service users though online and digital channels. Organisations are developing omni-channel approaches to meeting customer needs to deflect telephone and face-to-face contacts and so reduce costs.
The broad purpose of a Digital Support Technician is to maximise the effective use of digital office technologies, productivity software and digital communications. These will include collaborative technologies, and digital information systems.
A Digital Support Technician will select one of the following two options.
A Digital Applications Technician (DAT) helps their organisation and its internal users to maximise the use of digital technologies. They help organisations adapt to and exploit changes in technology to meet objectives and maximise efficiency. They ensure effective use of digital office technologies, productivity software, digital communications, including collaborative technologies, and digital information systems.
A Digital Service Technician (DST) supports external customers and clients through a wide variety of digital channels. A DST helps them access and receive services and provides coaching and support to them in their use of the digital systems. A DST will support external customers and clients to complete and submit data remotely. They will help them to diagnose and resolve problems with their access to and use of digital tools.
In their daily work, Digital Support Technicians interact with a wide variety of internal or external users of digital systems. They will communicate through digital channels, by phone and/or face to face. Digital Support Technicians work under general direction, using discretion in identifying and dealing with complex issues. They receive clear instructions and have their work reviewed at frequent milestones and determine when issues should be escalated to a higher level. Digital Support Technicians interact with and influence others, having working level contact with colleagues or customers. They may supervise others or make decisions which impact the work assigned to others or to other phases of projects. A Digital Support Technician plans, schedules and monitors their own work within limited deadlines and according to relevant law, standards and procedures.
Digital Applications Technicians (DAT) devise digital productivity solutions and roll them out in the organisation. They work as digital champions, training and supporting colleagues to make the best use of digital tools and diagnose problems. They provide internal end-user application support. The DAT may also assist with digital operations and digital change projects.
Digital Service Technicians (DST) help customers and clients register for and access data, products and services through online and digital channels. This can be as part of a sales or customer service process. They support and coach external users in their use of these digital systems. They diagnose and resolve external users’ digital problems with accessing and using digital tools. A DST also advises on related hardware and software problems. They use software packages and tools such as collaborative technologies, to interface effectively with external end-users. They will use a variety of digital channels to maximise effective external user support and to resolve external end-user problems. A DST will use and maintain information systems such as Customer Relationship Management tools to manage service delivery, improve user experience and increase efficiency.
Duty |
KSBs |
---|---|
Duty 1 Provide technical support to customers through a range of communication channels |
|
Duty 2 Manage their time, prioritising their digital support workflow to meet critical milestones |
|
Duty 3 Apply relevant policies and legislation appropriate to their role, and follow appropriate escalation procedures |
|
Duty 4 Undertake basic data analysis utilising appropriate digital technologies |
|
Duty 5 Maintain security of data by applying the appropriate policies and complying with legislation |
|
Duty 6 Support continuous improvement activity within the organisation |
|
Duty 7 Resolve digital issues using the appropriate tools and technologies |
|
Duty 8 Collaborate with stakeholders to manage expectations, escalating as appropriate |
|
Duty 9 Take responsibility for own continuous professional development (CPD) by keeping up to date with technological developments |
|
Duty 10 Document actions to ensure a clear audit trail and progression of issues |
Duty |
KSBs |
---|---|
Duty 11 Take appropriate action when application problems are identified |
|
Duty 12 Support application users, advising on how to optimise productivity |
|
Duty 13 Provide application training to users as required |
|
Duty 14 Source information to support, advise or guide as appropriate to the audience |
Duty |
KSBs |
---|---|
Duty 15 Determine the root cause of technical issues to identify the potential solutions |
|
Duty 16 Take appropriate action when technical problems are identified |
|
Duty 17 Configure a range of digital devices or systems to meet user needs |
|
Duty 18 Communicate technical concepts or solutions using appropriate language for the audience |
K1: digital office automation technologies; • how to use them to create, update, edit, manage, and present data• the organisation’s use of templates and their best working practice• how these tools can be used to collaborate with others
Back to Duty
K2: types of digital architecture and how it relates to their organisation;• physical storage versus cloud• role of operating systems and servers
Back to Duty
K3: the importance of backing up data securely and the technologies that support it.
Back to Duty
K4: the principles, processes and procedures for the secure handling of data in compliance with legislation.
Back to Duty
K5: the concepts and fundamentals of data;· searching, storing, integrating, and organising data· how organisations use various types of data· the key features and functions of information systems· data formats and their importance for analysis· data entry and maintenance
Back to Duty
K6: the key principles and processes for diagnosing stakeholder’s digital problems.
Back to Duty
K7: principles of a helpdesk system, including accessing and maintaining stakeholder information and the contribution of helpdesk system to the organisations performance and customer service.
Back to Duty
K8: approaches to risk mitigation for data loss including confidentiality, integrity and availability
Back to Duty
K9: significance of an organisation’s digital presence;· how this is maintained and what products are used· how the brand is represented and safeguarded
Back to Duty
K10: approaches to a range of communication channels and how to adapt to different audiences and situations.
Back to Duty
K11: the principles and constraints of searching the internet and accessing information securely • Currency- Relevance- Authority- Accuracy- Purpose
Back to Duty
K12: approaches to planning and organising own learning activities to maintain and develop digital skills (CPD).
Back to Duty
K13: approaches to effective time management and prioritisation
Back to Duty
K14: principles of continuous improvement within the context of the application and use of digital technologies and the benefits
Back to Duty
K15: current and emerging digital technologies and the possible implications for work on a support desk including the impacts of digital technologies for climate change, sustainability and moving to net carbon zero
Back to Duty
K16: approaches to assessing the impact of their actions on other stakeholders within a support desk environment
Back to Duty
K17: principles of productivity software applications used to create, update, edit, manage, and present data and information including how to support stakeholders in their use.
Back to Duty
K18: the features and benefits of digital information systems and how these are used to maintain application support.
Back to Duty
K19: working practices for the productive use and administration of stakeholder’s applications.
Back to Duty
K20: organisational approaches to incorporating different digital applications across business functions and the implications for their stakeholders.
Back to Duty
K21: approaches to the training and support of stakeholders to make the best use of the organisation’s applications.
Back to Duty
K22: the components of databases and their use
Back to Duty
K23: approaches to stakeholder system configurations and how this impacts on providing technical support
Back to Duty
K24: the importance and security implications of updating and maintaining stakeholders systems.
Back to Duty
K25: approaches to minimising and communicating the impact of required technical procedures.
Back to Duty
K26: approaches to the training and support of stakeholders to make the best use of the organisation’s digital systems.
Back to Duty
S1: use digital technologies, including collaborative tools, to operate effectively as part of a team, and with other stakeholders, enabling sharing of information and best practice.
Back to Duty
S2: use data accurately and securely to meet business requirements and in line with organisational procedures and legislation.
Back to Duty
S3: apply information security principles, for example: information transfer, deletion, storage, usage and communications that may include using mobile devices.
Back to Duty
S4: provide an appropriate and effective response to enquiries, providing support and information utilising digital channels and in line with organisation protocols
Back to Duty
S5: operate digital information systems, for example• Management- Finance Human Resources• Bespoke departmental or organisational systems or databases
Back to Duty
S6: communicate effectively through a variety of different channels using terminology appropriate to the audience
Back to Duty
S7: use digital resources to extend own knowledge and skills relevant to their role
Back to Duty
S8: risk assess the organisational impact of decisions that they take
Back to Duty
S9: use digital systems to identify productivity and performance improvements
Back to Duty
S10: use digital technologies to operate effectively as part of a team, and with other stakeholders, enabling sharing of information and best practice
Back to Duty
S11: maintain system security in line with organisational policies.
Back to Duty
S12: support digital operations or digital change and transformation activities.
Back to Duty
S13: investigate application problems and enable resolution to maintain productivity and improve quality of service.
Back to Duty
S14: coach and guide stakeholders to develop their applications skills to use digital systems effectively.
Back to Duty
S15: monitor data to analyse systems use and provide insights to recommend use or applications developments.
Back to Duty
S16: support customers in the use of information, products and services through digital channels.
Back to Duty
S17: diagnoses technical problems by identifying and applying tools and techniques to undertake fault finding, recording and rectification.
Back to Duty
S18: maintain end-user systems physically or remotely. For example: software, hardware or operating systems
Back to Duty
S19: provide and direct end-users to tools and resources to help them to resolve their digital problems.
Back to Duty
B1: work independently and take responsibility to maintain productive and professional working environment with secure working practices.
Back to Duty
B2: use own initiative when implementing digital technologies and finding solutions to stakeholder’s problems.
Back to Duty
B3: professional approach to dealing with stakeholder’s problems.
Back to Duty
B4: self-motivated for example: takes responsibility to complete the job.
Back to Duty
B5: takes a sustainable mindset towards digital support activities ensuring climate change and the move to net carbon zero by 2050 is a consideration
Back to Duty
Apprentices without level 2 English and maths will need to achieve this level prior to taking the End-Point Assessment. For those with an education, health and care plan or a legacy statement, the apprenticeship’s English and maths minimum requirement is Entry Level 3. A British Sign Language (BSL) qualification is an alternative to the English qualification for those whose primary language is BSL.
This standard aligns with the following professional recognition:
AP02
This document explains the requirements for end-point assessment (EPA) for the digital support technician apprentices. End-point assessment organisations (EPAOs) must follow this when designing and delivering their EPA.
Digital support technician apprentices, their employers and training providers should read this document.
An approved EPAO must conduct the EPA for this apprenticeship. Employers must select an approved EPAO from the Education and Skills Funding Agency’s Register of end-point assessment organisations (RoEPAO).
Digital support technician is a core and options apprenticeship standard. Apprentices must be trained and assessed against the core and one option. There are two options:
• Option 1: Applications support
• Option 2: Technical support
A full-time apprentice typically spends 15 months on-programme (this means in training before the gateway) working towards competence as a digital support technician. All apprentices must spend at least 12 months on-programme. All apprentices must spend at least 20% of their on-programme time completing off-the-job training.
This EPA has 2 EPA methods.
The grades available for each EPA method are:
EPA method 1 - project report with presentation, questions and answers:
EPA method 2 - professional discussion underpinned by a portfolio:
The result from each EPA method is combined to decide the overall apprenticeship grade. The following grades are available for the apprenticeship:
On-programme (typically 15 months) |
Training to develop the knowledge, skills and behaviours (KSBs) of the occupational standard. Training towards English and mathematics qualifications at Level 21, if required. Compiling a portfolio of evidence. |
---|---|
End-point assessment gateway |
The employer must be content that the apprentice is working at or above the level of the occupational standard. The apprentice’s employer must confirm that they think the apprentice:
Apprentices must achieve all of the qualifications listed in the Digital support technician occupational standard ST0120 relevant to their chosen option. Apprentices must have achieved English and mathematics at Level 21. An apprentice must submit all gateway evidence to the EPAO. The EPAO must review the evidence. When the EPAO confirms the gateway requirements have been met, the EPA period starts and typically takes 3 months to complete. The expectation is that the EPAO will confirm the gateway requirements have been met as quickly as possible. For the professional discussion underpinned by a portfolio, the apprentice will be required to submit a portfolio of evidence. Apprentices must submit any policies and procedures as requested by the EPAO. |
End-point assessment (typically 3 months) |
Grades available for each method: Project Report with presentation, questions and answers Professional Discussion underpinned by a portfolio Overall EPA and apprenticeship can be graded: |
Professional recognition |
This apprenticeship standard aligns with Register of IT Technicians for Level 3. The experience gained and responsibility held by the apprentice on completion of the apprenticeship will either wholly or partially satisfy the requirements for registration at this level. |
Re-sits and re-takes |
|
1For those with an education, health and care plan or a legacy statement, the apprenticeship’s English and mathematics minimum requirement is Entry Level 3. British Sign Language (BSL) qualifications are an alternative to English qualifications for those who have BSL as their primary language.
The EPA will be taken within the EPA period. The EPA period begins when the EPAO confirms the gateway requirements are met and is typically 3 months.
The expectation is that the EPAO will confirm the gateway requirements are met and the EPA begins as quickly as possible.
The apprentice’s employer must confirm that they think the apprentice is working at or above the occupational standard as a digital support technician. They will then enter the gateway. The employer may take advice from the apprentice's training provider(s), but the employer must make the decision.
Apprentices must meet the following gateway requirements before starting their EPA.
These are:
Apprentices must submit any policies and procedures as requested by the EPAO.
The EPA period starts when the EPAO confirms all gateway requirements have been met. The expectation is they will do this as quickly as possible.
The assessment methods can be delivered in any order.
The result of one assessment method does not need to be known before starting the next.
A project involves the apprentice completing a significant and defined piece of work that has a real business application and benefit. The project must start after the apprentice has gone through the gateway.
The project report with presentation, questions and answers must be structured to give the apprentice the opportunity to demonstrate the KSBs mapped to this EPA method to the highest available grade.
The project must meet the needs of the employer’s business and be relevant to the apprentice’s occupation and apprenticeship. The EPAO must confirm that it provides the apprentice with the opportunity to demonstrate the KSBs mapped to this EPA method to the highest available grade. The EPAO must refer to the grading descriptors to ensure that projects are pitched appropriately.
This EPA method includes 2 component(s):
The project and any components must be assessed holistically by the independent assessor when they are deciding the grade for this EPA method.
• it allows for a range of digital support activities to be demonstrated
• it provides a cost-effective assessment, as it makes use of the apprentice’s employer’s workplace, equipment and resources, and should contribute to workplace productivity.
Apprentices must complete a project which may be based on any of the following:
The project may also be based on:
Given the number of apprentices, EPAOs do not need to sign-off each project title before the project starts. The EPAO must instead provide detailed specifications. The specifications must detail what must be included in the project to allow an apprentice to evidence the KSBs mapped to the EPA method to the highest available grade. The EPAO must include suggested project titles to enable the employer to select a project that will meet the EPA’s requirements for their apprentice.
The project output must be in the form of a report.
The apprentice must start the project after the gateway. They must complete and submit the report to the EPAO after a maximum of 4 weeks. The employer should ensure the apprentice has the time and resources within this period, to plan and complete their project. The apprentice must complete their project and the production of all its components unaided.
The apprentice may work as part of a team which could include technical internal or external support. However, the project output must be the apprentice’s own work and will be reflective of their own role and contribution. The apprentice and their employer must confirm that the project output(s) is the apprentice’s own work when it is submitted.
The report must include at least:
The project report has a maximum word count of 1500 words. A tolerance of 10% above or below the word count is allowed at the apprentice’s discretion. Appendices, references and diagrams are not included in this total. The project report must map, in an appendix, how it evidences the relevant KSBs mapped to this EPA method.
In the professional discussion, an independent assessor and apprentice have a formal two-way conversation. It gives the apprentice the opportunity to demonstrate their competency across the KSBs as shown in the mapping.
• it is cost effective, as it can be conducted remotely to reduce travelling time
• it enables assessment of an in-depth understanding of the KSBs
• it can draw upon the portfolio of evidence and can effectively determine the authenticity of that supporting evidence
• it can effectively assess those skills and behaviours that require probing questions to explore the reasons for the apprentice’s ideas or actions
• it can be recorded to aid moderation and internal/external quality assurance.
The professional discussion must be structured to give the apprentice the opportunity to demonstrate the KSBs mapped to this EPA method to the highest available grade.
The EPAO must give an apprentice 14 days notice of the professional discussion.
The independent assessor must have at least 2 week(s) to review the supporting documentation.
Apprentices must have access to their portfolio of evidence during the professional discussion.
Apprentices can refer to and illustrate their answers with evidence from their portfolio of evidence, however the portfolio of evidence is not directly assessed.
The professional discussion must last for 60 minutes. The independent assessor can increase the time of the professional discussion by up to 10%. This time is to allow the apprentice to respond to a question if necessary.
For the professional discussion, the independent assessor must ask at least 12 questions. Follow-up questions are allowed. The independent assessor must use the questions from the EPAO’s question bank or create their own questions in-line with the EPAO’s training. The professional discussion must allow the apprentice the opportunity to demonstrate the KSBs mapped to this EPA method at the highest possible grade.
The independent assessor conducts and assesses the professional discussion.
The independent assessor must keep accurate records of the assessment. The records must include the KSBs met, the grade achieved and answers to questions.
The independent assessor will make all grading decisions.
The professional discussion must take place in a suitable venue selected by the EPAO (for example the EPAO’s or employer’s premises).