Release and Update Policy

Version: 1.0 Prepared By – Presales Review By – Tech

Scope

This document outlines the policies and procedures followed by Recruitment Smart Technologies(“RST”), for releasing updates and maintaining the SniperAI platform. The policy ensures thatproduct updates are delivered in a secure, consistent, and transparent manner, minimisingdisruptions to clients while maximising operational and business value.
‍
This policy applies to:

  • All SniperAI (JeevesAI+VScreen) application modules, including AI engines, parsingcomponents, recruiter dashboards, integration connectors, and analytics modules.
  • Integrations with external systems, including SAP SuccessFactors, Oracle, third-partyjob boards, and ATS platforms.
  • Deployment environments, including production, staging (UAT), and sandboxenvironments.

What Does This Policy Cover?

All new SniperAI provisioning and existing customer upgrades, where this policy applies, areperformed only on the current GA release version. RST team will provide the technical upgradeas part of base SniperAI subscription. To ensure customers obtain the maximum value of theoffering, customers or their representatives should ensure they review any of the client developedconfigurations they have implemented for usability and effectiveness when Major Releases occur,as outlined below.

In short the policy covers all types of software changes, including:

  • Major product releases
  • Minor feature enhancements
  • Security patches
  • Bug fixes and hotfixes
  • Integration updates

What Is the Purpose of This Policy?

The purpose of this policy is to describe SniperAI release and upgrade cycles by the RST team,customer notices, timing, as well as other pertinent information, such as version requirements forall the SniperAI offerings that have published release cycles, so customers understand andappreciate the nature and pace of these efforts

About SniperAI Release

This section applies to SniperAI as a Software-as-a-Service (SaaS) offering, which is deliveredvia a secure, cloud-native architecture with automated deployment capabilities. SniperAIfollows a hybrid model that supports both scheduled release cycles (for major and minor featureupdates) and continuous delivery (for security patches and non-disruptive enhancements).

For customers operating in integrated enterprise environments such as SAP SuccessFactors, allupdates are conducted in accordance with predefined SLAs and customer communicationprotocols, ensuring transparency, data integrity, and service continuity.

Release Cadence

Recruitment Smart’s approach to SniperAI’s release cycle is designed to balance platform stabilityand predictability with the flexibility to resolve critical issues quickly and deploy featureenhancements efficiently.

Release Type Cycle Upgrade Type Customer Notification
Major Release Annual Scheduled, coordinated 5–10 business days advance notice with full release notes
Minor Feature Updates Semi-Annual (2x/year) Auto-deployed or on-demand 3–5 business days advance notice
Security Patches Quarterly Continuous Delivery Notification only if the impact is material
Hotfixes / Emergency Fixes Monthly or Ad hoc Continuous Delivery Immediate notification upon deployment
UI/UX Enhancements Rolling (as part of minor releases) Seamless Bundled in minor release notification

Continuous Delivery and Improvement Procedures

Recruitment Smart SniperAI uses a CI/CD pipeline for continuous improvement, enablingnon-intrusive updates to backend services, parsing logic, and AI model performance.These updates are designed to be transparent to end users and require no action onthe customer side, unless specifically configured otherwise.

Updates delivered via the continuous delivery model are governed by the following principles:

  • No impact on service availability or existing configurations
  • Logged and traceable through internal release tracking systems
  • Subject to automated and manual QA in staging environments
  • Aligned with security and compliance protocols (e.g., ISO 27001, GDPR, CCPA)

Pre-Deployment Procedures:

  • Code is tested in staging/UAT environments.
  • SAP SF integrations are validated against the latest API specs and configurations.
  • Rollback plans are prepared for high-risk updates.

Deployment Windows:

  • Default deployment windows occur during non-peak hours or as agreed withenterprise clients.
  • For SAP-integrated environments, updates are coordinated to ensure zero downtime or scheduled maintenance with prior approval.

Customer Notification Policies

Scheduled Releases:

  • Advance Notification: Customers receive notification at least 5 business days in advance of a planned update via an email.
  • Release Notes: All major and minor updates are accompanied by acomprehensive documented release notes made available to customers via emailor the customer portal.
  • Admin Briefings (Optional): For major releases, clients may request a walkthrough session with a product manager or solutions engineer.

Emergency Patches / Hotfixes:

  • Clients are notified immediately via email or ticketing portal in case of anemergency patch or critical issue resolution
  • A post-patch report is shared within 24–48 hours detailing the issue, fix applied,and systems affected.

Maintenance/ Downtime Windows:

  • Notifications for scheduled maintenance or platform downtime are sent 48–72 hours in advance.
  • For changes impacting data integrations (e.g., SAP field mappings, APIversioning), a co-review process may be offered

Post-Deployment Support

  • Monitoring: Real-time API health checks, sync logs, and system usage aremonitored post-deployment.
  • Feedback Window: Clients are encouraged to report any issues within 72 hours for prioritised investigation.
  • Version Control: Recruitment Smart supports N–1 versions at minimum; clientsare expected to upgrade at least once per year unless otherwise agreed.

Software Version Information

SniperAI uses a structured semantic versioning scheme to track all releases acrossmajor, minor, service pack, and hotfix updates. This versioning approach ensures clarityand traceability for clients, system integrators, and support teams.

Version Format Example:

For Current Version: 3.5.1+hf1

  • 3 – Major Version
  • 5 – Minor Version
  • 1 – Service Pack/Security Patches
  • hf1 – Hotfix Number

Each component of the version number provides information about the scope and intentof the release:
Each release is assigned a unique version code.Recruitment Smart supports N-1 versions at a minimum (i.e., current and previous major release).
Clients can choose to defer non-critical updates up to 1 cycle with prior notice, thoughsecurity patches are mandatory.

Release Content

Major Versions
Major versions introduce significant changes to the platform, such as:

  • Architectural overhauls (e.g., model engine upgrades, new parser frameworks)
  • New core modules (e.g., bias explainability, auto-forwarding logic)
  • Changes that may require schema adjustments, re-mapping, or client-side migration
  • May involve user training or admin reconfiguration

Example: Upgrading from v2.x to v3.0 might require integration revalidation for SAPSuccessFactors.

Minor Versions
Minor versions include feature enhancements that are fully backward-compatible

  • Addition of new UI components or recruiter dashboards
  • Improvements to parsing logic or AI scoring algorithms
  • Expanded configuration settings or admin capabilities
  • No migration or system downtime is typically required

Example: Moving from 3.4 to 3.5 adds new job tagging features without disruptingexisting SAP SF integrations.

Service Packs
Service packs are maintenance-focused and contain:

  • Bug fixes for previously reported issues
  • Performance enhancements in processing, parsing, or matching
  • Compatibility updates for partner platforms (e.g., SAP OData API versionchanges)
  • Security patches based on known CVEs or compliance risks

Note: No new features are introduced in a service pack.

Hotfixes
Hotfixes are emergency patches released outside of the standard cycle to address:

  • Critical defects or malfunctions
  • API failures or parsing issues affecting production workflows
  • Integration failures with SAP SF or job board connectors

Hotfixes are deployed rapidly (within 24–48 hours), often with minimal or no impact onsystem availability.

Summary

This policy ensures:

  • Predictable, high-quality releases with minimal operational risk.
  • Transparent communication throughout the software lifecycle.
  • Reliable support and rollback strategies in case of unexpected issues.

Recruitment Smart remains committed to delivering continuous innovation and platformstability while respecting the operational constraints and compliance requirements of ourenterprise customers. The dual model of structured releases and agile deployment supports both enterprise-grade reliability and modern software velocity.