MWS Technology Ltd

Aptem for welfare to work

Aptem is a welfare to work SaaS platform providing case management and jobseeker portals. Aptem has proved it can transform employment outcomes. In a recent study of 70,170 jobseekers, Aptem users were 78% more likely to get a job and 43% more likely to stay in employment after 26 weeks.


  • Programme onboarding
  • Programme eligibility
  • Case management
  • Vacancy aggregation and jobseeker matching
  • Outcome and funding reports
  • eLearning


  • Efficient employability programme delivery
  • Real time reporting
  • Efficient resource utilisation through activity tracking and reporting
  • Single system end-to-end efficiency
  • Easier and demonstrable GDPR compliance
  • Highly configurable for different delivery models
  • Encourages jobseeker personal responsibility


£1000.00 per user per year

Service documents


G-Cloud 11

Service ID

6 2 1 1 5 4 5 3 3 6 6 1 4 7 2


MWS Technology Ltd

Richard Alberg

020 7870 1000

Service scope

Software add-on or extension
Cloud deployment model
Public cloud
Service constraints
System requirements

User support

Email or online ticketing support
Email or online ticketing
Support response times
Two business hours on weekdays. No support over weekends.
User can manage status and priority of support tickets
Phone support
Phone support availability
9 to 5 (UK time), Monday to Friday
Web chat support
Onsite support
Yes, at extra cost
Support levels
Ongoing support (how-to / answers to problems, etc.) is included in our pricing.

Training and implementation support is provided by implementation consultants and priced at £325 plus VAT per day.
Support available to third parties

Onboarding and offboarding

Getting started
We provide onsite training, online training and extensive user documentation (written and video).

We have an implementation methodology that is followed by our Implementation Consultants and we use project management software to track and report on each customer's implementation process.
Service documentation
Documentation formats
End-of-contract data extraction
Aptem has comprehensive export capability and MWS can additionally create export data sets for customers.
End-of-contract process
If wanted by the customer, MWS can generate a Microsoft format export database of all the information within the customer's database.

For additional cost we can customise this data export process according to the customer's specific requirements. Given how variable this requirement can be we would need to quote according to the customer's indicated requirement.

Using the service

Web browser interface
Supported browsers
  • Internet Explorer 10
  • Internet Explorer 11
  • Microsoft Edge
  • Firefox
  • Chrome
  • Safari 9+
  • Opera
Application to install
Designed for use on mobile devices
Differences between the mobile and desktop service
The same functionality. There is also a free iOS and Android app that provides push communications.
Service interface
What users can and can't do using the API
There are several APIs for different areas of Aptem functionality. We request all users to discuss with us how they wish to use the Aptem APIs and we will provide implementation assistance.
API documentation
API documentation formats
  • Open API (also known as Swagger)
  • HTML
API sandbox or test environment
Customisation available
Description of customisation
Aptem workflows and functionality are controlled from 'Programme Manager'. This is an area of Aptem that facilitates extensive customisation and configuration.


Independence of resources
Azure hosting with each customer having its own separate database


Service usage metrics
Metrics types
All activity is recorded and can be reported on
Reporting types
  • API access
  • Real-time dashboards
  • Regular reports
  • Reports on request


Supplier type
Not a reseller

Staff security

Staff security clearance
Conforms to BS7858:2012
Government security clearance
Up to Security Clearance (SC)

Asset protection

Knowledge of data storage and processing locations
Data storage and processing locations
United Kingdom
User control over data storage and processing locations
Datacentre security standards
Complies with a recognised standard (for example CSA CCM version 3.0)
Penetration testing frequency
At least once a year
Penetration testing approach
‘IT Health Check’ performed by a Tigerscheme qualified provider or a CREST-approved service provider
Protecting data at rest
Physical access control, complying with CSA CCM v3.0
Data sanitisation process
Data sanitisation type
Deleted data can’t be directly accessed
Equipment disposal approach
Complying with a recognised standard, for example CSA CCM v.30, CAS (Sanitisation) or ISO/IEC 27001

Data importing and exporting

Data export approach
Typically this is an Excel format file of the customer's selected fields. Files uploaded to Aptem can be downloaded in the original format.
Data export formats
  • CSV
  • Other
Other data export formats
  • XLSX
  • PDF
Data import formats
  • CSV
  • ODF

Data-in-transit protection

Data protection between buyer and supplier networks
TLS (version 1.2 or above)
Data protection within supplier network
TLS (version 1.2 or above)

Availability and resilience

Guaranteed availability
Aptem will be available to Users a minimum of 99.8% of the time during a calendar quarter. There will be no period of interruption in accessibility to Aptem that exceeds 4 continuous hours from problem notification.

For any failure to meet our availability guarantee customers are entitled to a refund of 10% of the amount paid in the previous month.
Approach to resilience
We host at Microsoft Azure and have a second UK Azure facility for failover. Information on Azure resiliency at:
Outage reporting
Email alerts

Identity and authentication

User authentication needed
User authentication
  • 2-factor authentication
  • Identity federation with existing provider (for example Google Apps)
  • Username or password
Access restrictions in management interfaces and support channels
Access restrictions are broadly configurable and can be set according to the customer's requirements (e.g. 2-factor or simply username / password)
Access restriction testing frequency
At least every 6 months
Management access authentication
  • 2-factor authentication
  • Identity federation with existing provider (for example Google Apps)
  • Username or password

Audit information for users

Access to user activity audit information
Users have access to real-time audit information
How long user audit data is stored for
At least 12 months
Access to supplier activity audit information
Users have access to real-time audit information
How long supplier audit data is stored for
At least 12 months
How long system logs are stored for
At least 12 months

Standards and certifications

ISO/IEC 27001 certification
Who accredited the ISO/IEC 27001
SOCOTEC Certification International
ISO/IEC 27001 accreditation date
What the ISO/IEC 27001 doesn’t cover
ISO 28000:2007 certification
CSA STAR certification
PCI certification
Other security certifications
Any other security certifications
  • ISO 9001
  • Cyber Essentials

Security governance

Named board-level person responsible for service security
Security governance certified
Security governance standards
ISO/IEC 27001
Information security policies and processes
We have ISO 27001. Our CTO attends board and has responsibility for ensuring that our policies and processes are followed.

Operational security

Configuration and change management standard
Supplier-defined controls
Configuration and change management approach
We use Redmine to record change control approval procedures and prioritisation. This follows the request through to either rejection or implementation. All requests are assessed from a desirability and risk standpoint and prioritised or rejected accordingly. The process involves technical staff and at least two company directors.

Changes to the physical environment are made through the TPM who can authorise routine access or minor required network settings changes. For security or contractual changes, the TPM consults with the CTO who may also contact the CEO. All changes are detailed in the production environment log, audited monthly by the CTO.
Vulnerability management type
Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
Vulnerability management approach
Threat assessment and vulnerability management are inherent in the Microsoft Azure environment. This conforms to CSA CCM v3.0. As we are exclusively a Microsoft environment we accept all Microsoft patch recommendations.

We subscribe to third party threat notification services.
Protective monitoring type
Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
Protective monitoring approach
Log, threat and vulnerability management are all provided by Microsoft Azure and this is maintained to CSA CCM v3.0.
Incident management type
Supplier-defined controls
Incident management approach
Incidents are managed in accordance with our ISMS. Reported incidents are assessed by the CTO and TPM and the major or minor incident process is invoked as required. Incident status (major or minor) can be reviewed iteratively and the classification and process adjusted accordingly.

Staff are required to report incidents to our Information Security Manager who logs incidents and in turns reports to the CTO.

Incident reports are in our central Information Security Action Log and are reviewed incident logs and are reviewed and managed as part of our ISMS Continuous Improvement Action Log.

Secure development

Approach to secure software development best practice
Conforms to a recognised standard, but self-assessed

Public sector networks

Connection to public sector networks


£1000.00 per user per year
Discount for educational organisations
Free trial available

Service documents

Return to top ↑