Preparing Your QQI Blended Learning Application: A Practical Approach

Once a training provider has decided to seek Quality and Qualifications Ireland (QQI) approval for blended or fully online provision, the next question is often a very practical one: how do we actually prepare the application?

The application can initially appear daunting. There are requirements to work through, existing Quality Assurance (QA) documentation to review, gaps to address and evidence to identify. Different documents also need to provide a consistent picture of how blended learning operates within the organisation.

A useful starting point is not to treat the application simply as a form that needs to be completed. It is better approached as a structured review of your provision, your QA arrangements and the evidence that demonstrates how these work in practice.

Having supported training providers through this process, there are a number of practical steps that can make preparing the application considerably more manageable.

Start with the application and gap analysis

Before writing new policies or creating additional documentation, become familiar with the QQI application and associated gap analysis.

The gap analysis is particularly useful because it provides a structured way of working through the requirements and identifying where your existing arrangements are satisfactory and where further work is required.

For each relevant requirement, establish:

- What do we currently do? - Is it formally documented? - Where is it documented? - What evidence shows that it happens? - Is there a gap? - If there is a gap, what action is required, who is responsible and when will it be completed?

The QQI application structure itself reinforces this approach by asking providers to identify whether requirements are relevant to their intended scope, whether the gap analysis is satisfactory, actions and dates where it is not, a description of the evidence or process, and exactly where that evidence is documented.

The objective at this stage is not to make every requirement appear complete. It is to establish an accurate picture of where you are and what still needs to be done.

Be clear about the scope of the application

Before getting too far into individual responses, establish exactly what the application covers.

Which programmes are involved? What is the proposed delivery model? Which elements take place online and which remain face-to-face? What technology supports delivery? Are you introducing a new model of provision or formalising and developing practices that already exist?

These decisions provide the context for the rest of the application.

Your responses, policies, procedures and supporting evidence should describe the provision you actually intend to deliver rather than a generic version of blended learning.

Work systematically rather than document by document

One of the risks when preparing an application is concentrating on individual documents rather than the requirements they are intended to address.

A provider may update the QA Manual, then the Learner Handbook, then a strategic document, without having a clear overview of how everything fits together.

I find it more useful to work from the requirements outwards.

Take each requirement and establish what the organisation does, how the process operates, where it is documented and what evidence supports it.

The documentation can then be updated as gaps become apparent.

This approach also helps prevent the creation of unnecessary policies or procedures simply because it feels as though another document is needed.

Don't just name a policy — explain what happens

This is one of the most important parts of preparing the application.

A reference to a policy or procedure does not necessarily explain how something works in practice.

If the requirement relates to learner engagement, for example, explain how engagement is monitored, who is responsible, what information is considered and what happens when a learner begins to disengage.

If staff development is referenced, explain how development needs are identified, what Continuing Professional Development (CPD) takes place and how this is recorded.

If programme monitoring is referenced, explain who carries it out, what information is reviewed and what happens as a result.

The application therefore needs to do more than point towards documentation. It needs to help the evaluator understand how the process actually operates.

Build an evidence map

As the application develops, create an evidence map.

This is one of the most useful ways of keeping a large application under control.

For each relevant requirement, create a clear connection:

QQI requirement → what we do → where it is documented → evidence that it happens → outstanding action, if any.

Your evidence may sit across several documents, including the QA Manual, strategic plan, learner and trainer handbooks, risk register, programme documentation, policies, procedures and operational records.

Cross-reference the application against these documents to check alignment and coverage.

An evidence map also makes gaps easier to identify. If you can describe a process but cannot identify where it is documented or provide evidence that it happens, that deserves further investigation.

Be precise about evidence references

Once you have identified the evidence, make it easy to find.

Avoid broad references such as:

“See QA Manual.”

Instead, identify the relevant policy, procedure, section, page or reference as precisely as possible.

The QQI application documentation provides space for the summary of the evidence or process, the document in which it is evidenced and the relevant page number or reference.

Use this structure to your advantage.

Precise referencing makes the application easier to review and also provides a useful test of your own documentation. If you cannot readily locate the process or evidence yourself, an evaluator may have the same difficulty.

Check for consistency across documents

An application should not be reviewed in isolation.

As documentation develops, inconsistencies can easily appear.

The application may describe a responsibility differently from the QA Manual. A Learner Handbook may contain an older process. The Strategic Plan may identify something as an outstanding action while another document presents it as already implemented.

Carry out a cross-document consistency check.

Pay particular attention to:

- roles and responsibilities - terminology - the proposed delivery model - governance arrangements - learner support - staff responsibilities - technology - assessment - monitoring and review - actions and timescales

The objective is not to repeat identical wording throughout every document. It is to make sure that the documents agree with one another.

Manage gaps rather than hiding them

It is quite normal to identify gaps while preparing an application.

In fact, identifying them is one of the purposes of carrying out the gap analysis.

The important issue is what happens next.

Where further development is required, create a defined action. Record what needs to change, who is responsible, the timeframe for completion and what will demonstrate that the action has been completed.

This could involve updating a procedure, formalising something that currently happens informally, developing staff capability, improving learner guidance or strengthening monitoring arrangements.

This turns the gap analysis into an active management tool rather than a checklist completed for the application.

Check that what is written reflects what happens

As the documentation develops, there can be a temptation to concentrate on whether the wording satisfies the requirement.

A more useful question is:

Does this describe what actually happens?

If the application says learner engagement is monitored, could you demonstrate the monitoring?

If it says staff receive appropriate development, are there CPD records?

If learner feedback informs programme improvement, can you show how feedback has resulted in review or action?

If governance oversees blended learning, are decisions, responsibilities and actions visible?

Your application, documentation and operational practice should align.

Where a process has only recently been introduced, it is better to describe it accurately than to create the impression that it has been operating for much longer.

Keep control of actions as the application develops

An application of this type can generate a significant number of small and large actions.

Without a central action log, these can become difficult to manage.

Maintain one working list showing the action, responsible person, target date, current status and evidence of completion.

Some actions will be straightforward document updates. Others may involve governance approval, staff development, technology changes or the introduction of a new operational process.

The action log also provides a useful link between the gap analysis, the application and the wider strategic development of blended learning.

As actions are completed, update the relevant application response and evidence reference rather than leaving this until the end.

Carry out a final application QA review

Once the individual sections appear complete, review the entire application as one package.

This is different from proofreading.

Ask:

Does every response answer the requirement?

Can every important statement be supported?

Are document and page references accurate?

Do the application and supporting documents agree?

Are responsibilities clear?

Have outstanding actions been addressed?

Does the documentation describe the provision we actually intend to operate?

Could someone unfamiliar with the organisation follow the application and understand how the system works?

This final review is important because issues that are difficult to see while working on individual sections often become much more obvious when the application is read from beginning to end.

Think ahead to the evaluation

There is another useful test before considering the application finished.

Could the people responsible for the provision explain what has been written?

The application should not contain processes that only the person who drafted the documentation understands.

Those responsible for governance, programme delivery, learner support, technology and QA should understand their roles and be able to explain how the relevant processes operate.

That does not mean preparing for the evaluation panel while you are still writing the application. It simply means making sure the application represents the organisation's actual practice.

It also provides a natural next stage once the application has been submitted: preparing the relevant people to explain and demonstrate the provision during the evaluation process.

Bringing the application together

A strong application is not necessarily the one with the greatest volume of documentation.

What matters is whether the application, QA arrangements, supporting documentation and evidence provide a coherent account of the proposed provision.

A useful final test is:

Does the application clearly explain what we do, how we do it, who is responsible, where it is documented and what evidence demonstrates that it happens?

If a provider can answer those questions consistently across the application, it is much easier to identify what is ready, what still requires attention and what needs to happen before submission.

About this article

This article draws on practical experience supporting training providers with QQI Quality Assurance and blended learning applications, alongside current QQI guidance.

QQI requirements and processes can change, so providers should always consult the current QQI guidance and application documentation relevant to their circumstances.