A recognised client name can make a security provider appear reassuring. Yet the client's size does not establish that its service was delivered under conditions comparable to yours. For an Ankara business, a more useful question is what the reference actually knows about the assignment and working arrangements under consideration. A short, authorised conversation can help answer it.
Agree the boundaries first
A provider supplying someone's name does not mean their contact details can be used without limits or that they may discuss every aspect of their organisation. Clarify the purpose of the call, appropriate permission to make contact and the subjects that may be discussed. If those arrangements are absent, ask the provider to organise an appropriate introduction.
NPSA's security-minded communications approach addresses avoiding unnecessary disclosure of operational detail. [2] Applied here, the principle is to learn about the service relationship without exposing protective arrangements or personal information. Process experience may sometimes be discussed within agreed limits even where the client organisation cannot be named.
Examine three different aspects of trust
Mayer, Davis and Schoorman's organisational trust model distinguishes ability, benevolence and integrity when considering trustworthiness. [1] This conceptual study does not prove that the questions below improve sales or service outcomes. Its value here is showing why one broad satisfaction question may conceal different aspects of an assessment.
For ability, ask how duties were performed. For the relationship, explore communication. For consistency, ask how commitments compared with practice. A favourable observation in one area should not automatically become evidence for the other two.
Ask five neutral questions
- During which period and within what general service scope did you have direct working experience?
- Can you give an example of everyday coordination that does not identify individuals or reveal sensitive site details?
- When a change or problem arose, how was it handled, and which part did you personally observe?
- Was there a duty or responsibility that would have benefited from clearer agreement at the beginning?
- Is any part of the service we are considering outside your experience or something you cannot comment on?
Prefer open questions to leading prompts such as “they were highly professional, weren't they?” Do not pressure a respondent who cannot share a detail. An unanswered question, on its own, is not evidence of a negative service experience.
Keep a one-page conversation record
The record can contain the date, confirmation that the conversation was appropriately arranged, the respondent's connection to the service and the permitted discussion scope. For each question, distinguish direct observation, general opinion and information that could not be verified.
For example, “their communication was good” is a broad judgment. “They acknowledged our requests through the agreed communication channel” is a more specific process observation. Even the second answer does not guarantee that your project will work in the same way. It gives procurement a concrete point to discuss with the proposed provider.
Avoid turning notes into stronger claims than the respondent made. A comment about one coordinator should not silently become praise for every team, and a comment about a short assignment should not be presented as evidence about a long-term operation. Retain the period and scope alongside the observation.
Use references as one input
Provider-nominated references are not an independent sample of all client experiences. An older assignment may also say little about the current proposed team or scope. Place the conversation alongside checks of permissions, task definition, readiness and contractual arrangements.
Three conclusions are sufficient: observations that support the assessment, follow-up questions for the provider and matters still unknown. This turns a list of impressive names into a bounded piece of procurement evidence.
