Bring the requirement.
Build the right delivery model.

For a direct appointment or executive search, describe the position outcome, reporting line, essential technical and behavioural competence, compensation parameters, notice flexibility, work location and target start. Identify the interview decision maker and any confidentiality or regulated-role requirement. State whether the mandate is contingency, exclusive or retained if already determined.

The team uses this information to calibrate the scorecard, choose channels and agree shortlist and feedback checkpoints. Avoid uploading sensitive candidate files or a named employee’s personal records at this stage. A job description and an anonymised role context are generally more useful than an unfiltered personnel file.

For temporary staffing, outsourcing or EOR, include headcount by role, duration, shift pattern, location, joining cohorts, existing worker status and whether recruitment is required. Describe the intended supervision, attendance approval, overtime, safety exposure, site access and any accommodation, transport or PPE. For transfers, state the expected transition date without sharing passport, bank or medical records through the public form.

The response can then distinguish source availability, selection, legal authorisation, insurance, onboarding and client access. Identify the desired commercial model, funding expectations and who can approve changes. A forecast headcount is not treated as a confirmed mobilisation until scope and dependencies are agreed.

For business setup or corporate administration, describe the planned activity, current entity status, ownership and proposed mainland or free-zone route if known. List the FTA, product, food, health, conformity or certification tasks separately, with the intended launch date and any existing authority correspondence.

Company formation, tax registration, product approval and management-system certification involve different authorities and evidence. The consultation identifies the workstreams, authorised representation needs and decision dependencies before a submission schedule or fee is proposed. Do not send owner identity documents or account credentials in the initial brief.

For HR consultation or HRMS/ERP work, explain the operating problem, employee population, locations, current software, intended platform if selected, modules, interfaces and affected user groups. Identify policy or payroll-rule changes, migration history, data quality concerns, desired go-live and the client decision owners.

A techno-functional discovery converts the requirement into process maps, functional rules, integration boundaries, data reconciliation, access design, testing and adoption outputs. Do not upload production employee datasets, credentials or system backups. A controlled sample or anonymised specification can be agreed later through the project’s secure process.