When evaluating a rural operations team, start with the same question you would ask of any delivery partner: can this team run the agreed process reliably? Location is part of the operating context, but it should not replace evidence about capability, supervision or quality.
Avoid both extremes. Do not assume a team lacks ability because it works outside a major city. Do not assume a meaningful employment mission automatically makes it the right fit for your workflow. Respect the people and examine the process.
This guide sets out questions a buyer can use during an initial assessment. It is a due-diligence framework, not a claim that every rural team has the same advantages or that Dhiti already meets every requirement described below.
Begin with the actual work you want to move
Define the work in operational terms: input types, volume patterns, language requirements, systems, decision complexity and consequences of error. A partner cannot give a meaningful answer about readiness if the brief only says “back-office support.”
Share representative examples under an appropriate information-sharing arrangement. Include ordinary items and difficult cases. Ask the prospective team to explain how they would handle each one and where they would need your approval.
Listen for a clear boundary. A credible answer may include work the team is not ready to accept. Treat that as useful information rather than an automatic weakness. The aim is to establish fit, not to reward a presentation that promises to handle everything.
Examine the training path
Ask what a new team member learns before handling live work. Look for a sequence that connects basic tool skills, process understanding, supervised practice and a readiness decision. Request an anonymised example of the assessment, where appropriate.
Find out how training adapts to your specific process. A general computer course does not demonstrate that someone can apply your matching rules, recognise a high-risk exception or communicate an accurate customer update. Ask how these task-specific decisions are taught.
The ILO guide to quality apprenticeships discusses structured programmes, inclusion and protection of learners’ rights. If a provider uses the term apprenticeship, ask what arrangement actually applies; do not assume a general training programme carries a particular accreditation or legal status.
Ask who supervises an ordinary Tuesday
Presentations often feature senior leaders. Your process will depend on the people available during everyday work. Ask who assigns tasks, answers questions, reviews output and handles a problem when the account lead is unavailable.
Request a practical description of the supervision model. How does a new operator raise a question? How does a reviewer return an item? What happens when the reviewer and operator disagree? Who can change the rule?
Look for documented responsibilities rather than a promise that “management is always involved.” Continuous senior intervention may help a pilot succeed while hiding the absence of a repeatable operating model. You need to understand how delivery works when the process is no longer receiving launch-level attention.
Check infrastructure through scenarios
Ask the team to explain what happens during an internet interruption, device failure or unavailable application. The answer should cover the status of in-progress work, communication to the client and the conditions for restarting safely.
Do not ask only whether there is a backup connection. Ask how it is used, what work it can support and whether the team has tested the switch. A backup that nobody knows how to activate is not the same as a working recovery process.
Match requirements to the task. A workflow requiring continuous access to a client system has different needs from an approved offline preparation task. Do not let the conversation drift into impressive equipment lists that never connect to the actual work.
Make security and privacy explicit
Clarify where the work will be performed, which devices are approved, how accounts are assigned and what information can be downloaded or shared. Have your security and privacy owners review the proposed arrangement before providing live access.
Ask how access is removed when someone leaves the process and how incidents are reported. Verify any certifications or contractual commitments that matter to your business rather than accepting a general assurance that the team follows best practice.
NIST’s small-business cybersecurity resources provide a starting point for organisations developing a cybersecurity risk-management approach. They are background guidance, not a substitute for assessing the specific systems, data and obligations involved in your engagement.
Look at quality evidence, not just a headline score
Ask how quality is defined for the work under discussion. Does a score refer to every completed item or only a reviewed sample? Are critical errors counted separately? Does the measure include work returned by the client after internal review?
Request an anonymised review example that shows the original item, the reason for correction and the final accepted version. This can reveal more about the team’s quality discipline than an isolated percentage with no definition.
Discuss how the team responds to a repeated problem. A useful answer connects the issue to a change in input, instruction, training or review. Rechecking everything indefinitely may be necessary in some contexts, but it should not be the only improvement strategy the team can describe.
Understand the employment model without romanticising it
Ask about working arrangements, supervision, compensation clarity and routes for raising concerns. These are reasonable questions for any delivery model. Do not treat lower cost as a reason to accept ambiguity about the people doing the work.
If local employment impact is part of the proposed value, ask how it is defined and evidenced. Distinguish training participation from paid employment, and distinguish a current headcount from a cumulative total. These measures describe different things.
Avoid broad assumptions about loyalty, ambition or productivity based on where a person lives. Evaluate retention and performance using the provider’s actual evidence where available. People deserve to be assessed as professionals rather than as a convenient story about geography.
Use a pilot to connect the answers
A controlled pilot can test whether the described model works on your process. Agree scope, review criteria, access restrictions and a return path before starting. Keep the first stage small enough to inspect closely.
Use a simple assessment checklist:
- Process fit: Can the team explain the work and identify its boundaries?
- Training: Is readiness demonstrated through relevant practice?
- Supervision: Are ordinary decisions and escalations clearly owned?
- Infrastructure: Can the team explain and test a safe recovery route?
- Security: Have required controls and access been reviewed?
- Quality: Are measures defined and supported by traceable examples?
- Employment: Are the working arrangements transparent and appropriate?
- Commercial fit: Are scope changes, responsibilities and pricing assumptions clear?
Decide which gaps can be addressed during the pilot and which must be resolved first. A sensitive access requirement, for example, should not be deferred merely to keep the schedule moving.
The strongest evaluation is neither sentimental nor sceptical by default. It gives the team a fair opportunity to show its capability while keeping your standards clear.
Read the 30-day pilot guide to structure the next step. Use the handover checklist to make sure your own inputs and decision owners are ready too.
Examples and suggested targets are illustrative, not Dhiti client results or contractual commitments. Adapt the approach to your process, risk and team.
