Working as a freelancer, I often see strange requests from my customers, some of which can negatively affect my daily work¹, and others trying to set some sort of control. I usually encounter those things during preliminary negotiations, so it's easy enough at this statestage to explain to the customer that I do care about my work and productivity and expect my customers to trust my work.
Things were much harder² on a project I just accepted, since it's only after the end of the negotiations (the contract beinghas already been signed and did not mentioningmention anything about video tracking) and after I started to work on the project that my customer requested that I record a video of all I do on my machine when working on his project, that is, a video which will show that I move the cursor, type a character, open a file, move a window, etc.
How to explain to him that it is not an usual practice for the freelancers to record the videos of their daily work, and that such extravagant requests must be reserved tofor exceptional circumstances⁴?
¹ The most frequent example is to be requested to work through Remote Desktop on a more-than-slow server which uses a more-than-slow Internet connection, or to be forced to use an outdated software such as Windows Me without serious reasonsjustification such as legacy support.
² In fact, I already did a lot of management and system design related work, which is essential, but usually misunderstood by customers and perceived as a waste of time and money. Observing the concerned customer, I'm pretty sure that he will refuse to pay a large amount of money for what was already done, since there is actually zero lines of code. Even if legally I can easily prove that there was a lot of work undertaken on the design level, I don't want to end my relation with this customer in a court.
³ Which is not as risky as it could be, since I gave to this customer the expected and the maximum cost of the project, so the customer is sure to never be asked to pay more than the maximum amount, specified in the contract, even if the real work costs more.
⁴ One case when I effectively record on my own initiative the video of actions is when I have to do some manipulations directly on a production server of a customer, especially when it comes to security issues. Recording those steps may be a good idea to know precisely what was done, and also ensure that there were no errors in my work, or see what were those errors were.
Update:
First of all, thank you for all your answers and comments.
First update
Since the question attracted much more attention and had muchmany more answers than I expected, I imagine that it can be relevant to other people, so I addhere is an update. First, to summarize the answers and the comments, it was suggested to (ordered randomly):
- Suggest other ways of tracking, as shown in Twitter Code Swarm video, or deliver a "short milestone with a simple, clear deliverable, followed by more complex milestones", etc.
- Explain that the video is not a reliable source and can be faked, and that it would be difficult to implement, especially for support.
- Explain that the video is not a reliable source since it shows only a small part of the work: a large amount of work is done without using a computer, not counting the extra hours spent thinking about a solution to a problem.
- Stick with the contract; if the customer wants to change it, he must expect new negotiations and a higher price.
- Do the video, "but require that the customer put [the] entire fee into an escrow account", require a lawyer to video tape all billable time, etc., in other words, "operate in an environment void of trust", requiring the customer to support the additional cost.
- Search for the laws which forbid this. Several people asked in what country I live. I'm in France. Such laws exist to protect the employees of a company (there is a strict regulation about security cameras etc., but I'm pretty sure nothing forbids a freelancer to sign consciously a contract which forces him to record the screen while he works on a project.
- Just do it and send the videos: the customer will "watch a few ten second snippets of activity he won't understand", then throw those videos away.
- Say no. After all, it's my business, and I'm the only one to decide how to conduct it. Also, the contract is already signed, and has nothing about video tracking.
- Say no. The processes and practices I employ in my company can be considered as trade secrets and are or can be classified.
- Quit. If the relation starts like this, chances are it will end badly soonsooner or later. Also, "if he's treating you like a thief - and that is what he's suggesting - then it's just going to get worse later when XYZ feature doesn't work exactly the way he envisioned".
While all those suggestions are equally valuable, I've personally chosen to say to my customer that I accept to do the videos, but in this case, we must renegotiate the contract, keeping in mind that there will be a considerable cost, including the additional fee for copyright release. The new overall cost would be inon average three times the actual cost of the project. Knowing this customer, I'm completely sure that he would never accept to pay so much, so the problem is solved.
Second update:
Second update
The customer effectively declined the proposal to renegotiate the original contract, taking ininto account the considerable additional cost. He agreed to continue the project without video recording.
The project continued without video recording. Eventually, the customer seemed satisfied by the final result and cost, so the video recording was not mentioned again.