Launching

Launching is completely controlled by you. You are able to choose when and how you launch your platform, the only thing you need to do is keep accessplanit updated with your approach and your date/time so that we can ensure everything is in place and your emails are enabled.

There are three main approaches to launching the platform:

• Basic launch: Ensures basic functions are all available and launch without website integration or customer communications.
• Soft launch: Begin to run new platform for internal Users on planned launch date, run existing platform parallel for external Users.
• Trial launch: Begin to use the new platform for a specific group of Users, or one customer, or department.
• Hard launch: Do not launh until all items are complete.

You also need to consider how you will provide access to any existing Users in the platform, while new registrants will define their own log in details. The existing Users in your platform will not know how to log in and what details to use when they first access your new platform.

Basic Launch

This requires you to identify what the ‘bare minimum’ for launching on the target date would be. This could include ability to book courses and manage Delegates, but not send any automated Communications or allow access to the platform. Everything else is still progressed/trained but resources are more focused on ensuring the bare minimum is covered. Everything which is complete by the launch date is launched, and the rest is added to when ready. The benefit of this approach is that the launch date is met.

Soft Launch

The platform is launched as an internal admin tool only. All bookings processed by Administrators are processed through the platform whilst bookings made by external Users continue through their existing route but are also added into the new platform by Administrators. This ensures that the new platform is kept up to date during this time period. Customers do not need to know that there is a new platform in place, even if they are receiving automated Communications from it. The benefit of this approach is that Administrators can become fully fluent in the platform before customers begin to make their own bookings. This also means that only Delegate Communications need to be confirmed as fully tested as everything else can be improved through experience before the customers begin to log in.

Trial Launch

The platform is launched to a specific group of Users. This could be one customer, one department, selected key contacts, or managers only. This allows you to gain their feedback on the platform and provides you with opportunity to make changes before a full launch to your entire customer base. The length of the trial is up to yourselves, but it is important that you have everything completed beforehand as if you were running the hard launch approach, to test this accurately. 

Hard Launch

The launch of the platform is not completed until the entire platform is signed off. This is the most challenging approach and includes fully tested payment gateway, website integration, customer communications and extensive process testing. The benefit of this approach is that there is a clear implementation end date and customers can begin to make their own bookings and log into the Learner Portal as soon as everything is ready.

This approach is ideal for those who do have a required launch date, and will be marketing the launch well ahead of time.

Providing Access to Users

1. You can send users their log in details via the Users DataGrid
   To do this, access the DataGrid and select each user that you would like to send their credentials to, then select the Send Reset Password Link option from the top of the page
   
   
   This will issue the user with a platform standard email containing their log in details, you are able to customise this email.