Account & delivery contacts
Name the commercial contact, operational delivery lead and client sponsor. Document their roles, reporting cadence and escalation routes in the engagement.
Understand the responsibilities, controls and evidence to agree when engaging Futurex for staffing, payroll, finance, technology or GCC services.
Agree the operating model before work or sensitive-data exchange begins.
Name the commercial contact, operational delivery lead and client sponsor. Document their roles, reporting cadence and escalation routes in the engagement.
Allocate sourcing, candidate selection, employment, payroll inputs, funding, payment authorisation, statutory tasks and system administration. Outsourcing a process does not automatically transfer approval authority.
Set definitions for quality, timeliness and exceptions. Agree issue severity, contact routes, review cadence and corrective-action ownership; response commitments belong in the service agreement.
Select controls that fit the role, employment model and client requirements.
Agree role-specific screening, assessor responsibilities and any authorised background checks. Assessments and verification depend on provider availability and agreed scope; hiring decisions remain with authorised reviewers.
Confirm required documentation, work-model acceptance and access approvals. Assign owners for attendance inputs, employee changes, exits, knowledge handover and access removal.
Define input cut-offs, maker-checker review, exception handling and approval evidence. Separate payroll calculation from funding and authority to release bank payments.
Specific controls and evidence should be confirmed during due diligence.
Define permitted users, least-privilege access, approved systems and confidentiality obligations. Agree how access is granted, reviewed and removed.
Choose approved channels for resumes, payroll files and documents. Set retention, deletion, permitted sharing and storage responsibilities; avoid sending sensitive documents through the public enquiry form.
Identify any assessment, verification, technology or form-processing providers involved. Confirm the contracting entity and the relevant data-handling responsibilities before providing live data.
Make continuity arrangements proportionate to the service being delivered.
Identify critical roles, systems, approvals and third-party dependencies. Agree backup coverage and the process for absences, access failures or missed inputs.
Agree who receives an incident, communicates with stakeholders, investigates and authorises recovery. Contractual reporting requirements and timeframes should be explicit.
Define the return or deletion of data, access removal, outstanding obligations and knowledge transfer. Confirm acceptance evidence and post-transition support in the agreement.
Certificates and audit claims should be verified against their entity, scope and validity.
Request the appropriate company and contracting details, insurance information where applicable, agreed terms and references that are authorised for sharing.
Request approved references, relevant sample reports, process documentation and service-specific control evidence. Illustrative templates are clearly distinguished from client results.
Technology capability may involve specialist partners, including Xelium Labs where agreed. Your proposal must identify who contracts, delivers, supports the work and handles data; a brand mention alone does not define these responsibilities.