That's just returning to the topic of drafting agreements))) What question is this answer))) The questions in the assignment must be posed concrete, without vague wording (this will then avoid rumors). And the collection of some information (not even determined which one specifically) - assumes virtually the same answer: lol: So you should probably think about how to formulate the tasks in the contract correctly, and then make any claims to the contractor ... This topic has already been discussed -Area of cooperation ... Very it is difficult (in the absence of a specific task) to determine whether it has been completed or not ... When answering the question about the possible identification of a possibly unscrupulous partner during the task, we again rest on the specifics - put (in writing) before the contractor not a vague, but a specific task (in including indicate that it is necessary to establish complete installation data (for example, full name, date of birth, place of birth, registration address, address of the actual residence, etc. (what you need), be sure to indicate in the assignment that you need photos, videos, audio materials confirming the established facts, etc.) If the assignment of these circumstances does not indicate, hence the misunderstanding ... In terms of setting specific tasks, I personally like the approach to this issue from the project "Mystery shopper" ... (akin to our activity, also collecting information, only of a certain nature). Who has the desire, look ... Many people work in this project , with which written agreements are not concluded, but there is a logo when receiving a TA for a specific task, in which everything is written down to the smallest detail (up to the behavior in the test object) ... The absence of misunderstandings in this matter allows not only to qualitatively complete the task, but also then check the quality of its implementation and, of course, to resolve the issue (in the case of the qualitative fulfillment of a specific task) about the payment for the services of a "data collector" ...