BAILII is celebrating 24 years of free online access to the law! Would you consider making a contribution?
No donation is too small. If every visitor before 31 December gives just £5, it will have a significant impact on BAILII's ability to continue providing free access to the law.
Thank you very much for your support!
[Home] [Databases] [World Law] [Multidatabase Search] [Help] [Feedback] | ||
England and Wales High Court (Chancery Division) Decisions |
||
You are here: BAILII >> Databases >> England and Wales High Court (Chancery Division) Decisions >> Shanley v Lloyds TSB Insurance Services Ltd & Anor [2013] EWHC 411 (Ch) (25 February 2013) URL: http://www.bailii.org/ew/cases/EWHC/Ch/2013/411.html Cite as: [2013] EWHC 411 (Ch) |
[New search] [Printable RTF version] [Help]
CHANCERY DIVISION
INTELLECTUAL PROPERTY
The Rolls Building 7 Rolls Building Fetter Lane, London EC4A 1NL |
||
B e f o r e :
(Sitting as a Judge of the High Court)
BETWEEN:
____________________
JAMES MICHAEL SHANLEY |
Claimant |
|
- and – |
||
(1) LLOYDS TSB INSURANCE SERVICES LIMITED (2) HALIFAX GENERAL INSURANCE SERVICES LIMITED |
Defendants |
____________________
MR R ONSLOW (instructed by Bevan Brittan LLP) appeared on behalf of the Defendants.
____________________
Crown Copyright ©
"This trial shall henceforth be for the purposes of resolving all issues, save whether there has been ongoing infringing use of the pilot scoping tool, as that term is defined in the amended particulars of claim herein, provided that the issues of whether pure archive use as asserted in paragraph 34A of the amended particulars of claim, and the use by Mr Ian Sutherland set out in his witness statement of 20th February 2013, are infringing shall also be resolved at this trial ..."
Background
"... a turning point in the level of service management in controlling and increasing profits of jobs. It was tied to the database of rates and service levels for each aspect of the work, which was set by each of our customers so that as soon as a job was set up, it used the correct rates, and the admin staff could see that a contract had to be made with the insured within the right number of days, the surveyor's appointment within the next number of days, and so on. The system displayed critical jobs which had not yet been done in red, so it acted as a time-management function as well. After logging on, the admin staff could already see which were the most urgent things for them to tackle that day.
"As a result of everyone using the same basic information about a job, such as dimensions of the room being repaired, there was much greater accountability. The scope for accidental or deliberate exaggeration for the amount of work needed for plastering or flooring, for instance, was gone, so cost leakage was tightly controlled. This meant the estimate tool could also be used in an auditing function to check what had actually been done against what had been identified as needing to be done. Also it speeded up the progressing of the job compared with the previous way of doing things, where surveyors or foremen used to take notes by hand on site, typing them up when they got back to the office, transferring that information across to any of the tradesmen who needed them to work on the job and so on. It removed the risk of errors creeping in when communicating about the job between the various people working on it, and it allowed reporting to the client and to the insured about what was happening. We made so it you could print a report of the schedule of works without the pricing for that purpose. It saved time, labour, mistakes and miscommunication. Overall it was very, very cost effective."
"Halifax provided no IT support for suppliers under any of these systems. The suppliers just used spreadsheets with no consistency. There was no end-to-end managing of the process once it had been given to a supplier. The process simply involved instructing the supplier by fax and awaiting an invoice. It was often commented on at the highest level that the most sophisticated piece of supplier management kit was a fax machine, and our supplier management process was referred to as 'fax and forget'. The supplier was given the job and eventually an invoice came back. It was all fragmented and unsatisfactory, with little or no cost or service level control of the supply chain."
Mr Poulsen accepted in cross-examination that the claim management system operated by Halifax was deficient because:
"Once we instructed a supplier ... we could not see what was happening to the claim until we received an invoice."
This was to be contrasted with the position at CSL, which was described by Mr McKeown at paragraph 9 of his statement in these terms:
"Completecare Scotland were a supplier on the Halifax network going back to 2006. CCS were one of several HBoS suppliers who had developed their own claims management system. CCS's system was one of the most sophisticated."
"I did not discuss or know anything about the contractual arrangements between Jim Shanley and the Halifax for this work, since I did not expect or need to, nor did I discuss the contractual or financial arrangements for the work to be done with Jim Monteith at any time. Jim Shanley asked me to do the work and paid me for doing it. It must have been quite obvious to Jim Monteith that I was doing the work for Jim or else for CCS, since I would not have been doing the work at all unless someone was paying me for it. I did not just walk in and sit at CCS's premises doing coding for anyone who happened to pass by, and needed something done. I have never given the Halifax a licence to use the spreadsheet. I could not have done since, as far as I was concerned, the software belonged to Jim Shanley."
Save that it was suggested to Mr Muirhead in cross-examination, and accepted by him, that it was CSL rather than the claimant that paid him for the work, this part of his evidence was unchallenged.
"It is admitted that until 9th September 2011, the defendants had continued to use the spreadsheets as amended by Mr Muirhead, and further admitted that such use was at all times commercial use. As of 12th December 2011, the defendants have started to use new spreadsheets which were created independently of the earlier spreadsheets."
"HRS: Jim has worked hard and well to ensure the successful launch of HRS with his 13 suppliers. All of Jim's suppliers (13) who were offered contracts accepted the terms offered and signed their contracts. Jim completed training on the new scope tool with all of his suppliers prior to the launch of HRS. To date, Jim reports that all of his suppliers are finding the new scope tool to be more user-friendly than the previous versions. Only minor issues/queries have been raised by the suppliers to Jim, and Jim has easily been able to address these. Indeed, as the building services 'scope tool champion', Jim has successfully supported his colleagues in the wider HRS network in the addressing of any issues with the new scope tool since network launch."
An internal appraisal dated 21st May 2007, also for Mr Monteith, records:
"Jim has shown initiative in leading the development/improvement of the scope tool. We agreed that this was a critical area, as it would help drive down CPS estimating cost and thus overall claims costs to HBoS. Jim will complete improvement work in line with the overall rates review forum work by the end of June 2007."
"Dear contractor/partner,
Subject to a successful IT upgrade over the weekend of 24th/25th May, Monday 26th May will see the launch of our new HBoS GI buildings scope tool and updated schedule of rates.
The ability to produce an accurate, detailed and fairly priced scope of work on each and every HBoS GI job is, it goes without saying, a prerequisite to the service offering of each contracted partner on the HRS network. The new HBoS GI scope tool and updated schedule of rates will undoubtedly enhance your ability in this regard.
From launch on 26th May, all HBoS GI contracted partners must use the new scope tool and updated schedule of rates for the pricing of all HBoS GI building repair works.
An electronic copy of the new scope tool and updated schedule of rates are now combined in one easier to use document and, together with an instruction guide, are attached for your attention.
Your Partner Manager is of course available at any time to answer your queries and to help with any ongoing training requirements you may have in the use of the new scope tool. Please feel free to give him a call at any time.
For HBoS GI, the launch of the improved building's scope tool and updated schedule of rates represents an undoubted improvement to our contracted partners over our existing arrangements in respect of the processing of building claims. ..."
"JS: The reality is, Jim, my software is getting Lloyds, getting used at Lloyds Banking Group and the reality is, Jim, if I don't get this sorted out then people are ... court order and I'll ask you to stop using my software and I mean that …
But I need a list of who is currently using this ...
But see, all the times and creating all the scoping tools, printing buttons and all that, that's all mine. That's my software and that gets used at Lloyds Banking Group up and down the country and that must save a contractor and your suppliers at least an hour every day in work, and I've checked out the software, Jim ...
And I told him exactly where the software sat. That is my software. And at the moment I'm saying you've not got permission to use that any longer.
"JM: Well, as I say, I'll give notice and obviously I'll speak to Reuben later on regarding that ...
Okay, he knows that the scoping tool is being used. Sorry, I think he is still aware of that ...
"JS: So the reality is that for Lloyds Banking Group that you read about intellectual property rights within your contract and it tells you that you have got to protect mine. Now I need to know how many claims it's been used on because there will be a charge per claim, so I will need to know how many claims throughout Britain have used that.
"JM: Well, as I say, I'm going to raise that just now, you know, whenever Reuben feels he needs to go with it then you'll ...
"JS: No, wherever Reuben wants to go with it, tell him where it's going with me. If he doesn't stop using the contract, I'm going to the High Court to seek an injunction, but this is separate for the WIP, but I will need a list, whether you supply it or the court will ask for it. They need a list of who's used it, how many claims it's been used on, and ultimately the reality is is it's not right that a company like Lloyds can come, in, take over and just say, 'You know what, see all that brilliant work that Jim Shanley created and did? We're just going to take that and roll it right through my business and give him no recompense for it.' At no point did I agree to give that to Lloyds Banking Group."
"Supply to the Halifax.
"Through its use of the scoping tool and other associated processes, CSL became known for its efficient and economical way of running insurance claims and was asked to join the insurance repair network of the Halifax division of Bank of Scotland Plc ('Halifax'). In 2004 Halifax began to show interest in adopting the scoping tool internally, as it was felt that companies in the supply chain would be able to work on claims together more productively if they both used the scoping tool. Our client was approached by Karl Poulsen of Halifax and entered into an oral agreement through which Halifax was licensed to use the scoping tool on a temporary trial basis. Mr Muirhead and our client subsequently worked together with Jim Monteith, the network manager for Halifax, to modify the scoping tool to meet the particular specifications required. A modified version of the product was sent to Halifax on 19th May 2004. This was further adapted over the period 2004-2007, although our client understood that as a result of ongoing work to merge the networks of Halifax and Bank of Scotland following the mergers of legal entities in 2001, no decision could yet be taken as to Halifax formal procurement of the package. At this stage, our client believed that the package had been trialled by approximately 60 personnel within Halifax's claims handling department.
"In or about November 2006 Jim Monteith informed our client that Halifax was not known to take a product on a permanent basis. Our client was given the impression that HBoS would instead create its own bespoke system to include parts of the company outside the insurance market. At this point Mr Shanley believed the matter to be closed and all use within Halifax to have ceased."
The letter went on to allege copyright infringement in these terms:
"It has recently come to our client's attention that Halifax continues to use a scoping tool through its business in substantially the same form, subject to minor changes, to reflect, for example, the VAT increase at the beginning of 2011. We have advised our clients that the use of the scoping tool is an infringement of his intellectual property rights.
Furthermore our client has discovered that the scoping tool is being used by other companies within, and connected to, Lloyds Banking Group, of which HBoS has since January 2009 formed part, including Lloyds TSB Bank Plc, insurance networks, suppliers and contractors. Our client has never provided or licensed the scoping tool to any of these parties, which must have received copies derived from Halifax. Halifax was licensed to use the scoping tool only internally, and only on a temporary trial basis. There was never any licence to distribute it to connecting companies, let alone third parties. Consequently this unlicensed distribution and use of the scoping tool is a further infringement of our client's intellectual property rights."
(a) it was being alleged that an oral licensing agreement had been made between Mr Poulsen and the claimant in 2004,(b) the temporary arrangement allegedly so licensed came to an end in November 2006 as a result of a conversation between the claimant and Mr Monteith,
(c) two distinct allegations of infringement of copyright were being made, being
(i) continued use by Halifax; and
(ii) unauthorised distribution to Lloyds by Halifax and use by Lloyds and its various connections.
"As a preliminary point, we note that your reference to the 'scoping tool' appears to be a reference to a software package used for the planning and management of construction projects arising from buildings insurance claims, whereas your client's complaint appears to relate to use by our client of a spreadsheet in respect of which our client asserts it is the copyright owner. Having sought clarification from our client, it would appear that the software package you refer to is an end-to-end claims management system demonstrated to our clients, Jim Monteith and Karl Poulsen, in or around 2007, but not adopted in any way by our client. Whilst your client may be the owner of the copyright that subsists in the wider elements of the software package, it is not the owner of the copyright that subsists in the spreadsheet which our client is using. We are instructed that our client has not at any time used any software provided to it by your client, his associates, or business concerns."
This is now accepted to be untrue. What is described as the "spreadsheet" was the scoping tool that utilised the software written by Mr Muirhead and owned by the claimant following the assignment to which I have referred. The issue is whether the claimant licensed its use for commercial purposes by Halifax, and whether to license its distribution to or use by Lloyds. The letter continued:
"We note that your letter makes reference to 'source code'. We are instructed that Mr Hanson did not write any source code for the work, the only source code being the code in the Excel software develop by Microsoft, but created specifically formulae within Excel which allowed the work to perform calculations using the data that was inputted by the case handlers on the screen. Furthermore, at no time during the creation of the work or during its ongoing development by either HGISL or any external contractors used by it ... was any new source code written for the work. For the avoidance of doubt, our client wishes to confirm that at no time has any stand-alone software been used in conjunction with or developed for use with the work, and it has been in the form of a spreadsheet developed within Microsoft Excel."
This too is now accepted to be untrue. Mr Muirhead's evidence as to what he did is set out in paragraphs 13-14 of his witness statement and was in these terms:
"I could not just copy the Estimate Builder code into the Halifax spreadsheet. Instead I broke the Estimate Builder down into component functions and wrote new Visual Basics deliver the same functions in the new Halifax version as a stand-alone. It was an iterative process. I would add some functionality, and, with Jim Shanley's approval, e-mail the amended spreadsheet to Jim Monteith, who would come back with comments and further requirements. I also wrote user instructions on to the spreadsheet. Between September 2006 and March 2007, my timesheet shows that I spent at least 50 hours on this project. The modified spreadsheet was used as the basis for all the Halifax claims CCS worked on while I was there. From March 2007, I continued to receive requests for modifications, tweaks and corrections from Jim Monteith, and I continued to make the changes. I did not discuss this with Jim Shanley, since it was just a continuation of the work I'd already been doing. Halifax also issued updates to ourselves from time to time, which seemed to be simply amendments to rates and other minor tweaks. On some occasions I had to correct changes which had been made by someone at the Halifax.
Nonetheless, the Halifax scoping spreadsheet was never as sophisticated as the CCS Estimate Builder since this was part of a much more sophisticated system. The functionality that I put into the Halifax tool is more basic, allowing the user to move around the spreadsheet, and more open to amendments, since it is less easy to control the functions of the user in respect of a portable stand-alone Excel aisle."
None of this was challenged, other than in relation to the knowledge of the claimant concerning activity after the date when he alleges he was told that the trial pilot, which he claimed to have licensed, had come to an end.
"Halifax agreed with the claimant's proposal and on 8th September 2006 Halifax entered into a written agreement with the claimant ('the scoping tool agreement') in the following terms:
"i. The claimant is the owner of CSL and all the claims control software is currently owned by him independently and used in his business.
"ii This will remain on the same basis on which the claimant will create the same or similar scoping estimating tool for the Halifax.
"iii It has therefore been agreed that the claimant will provide and develop a similar estimating scoping tool to that which he has already created with the CSL business.
"iv The claimant and Halifax have agreed to enter into the first stage of this agreement being about a development pilot ...
"v In order that the claimant creates the desired product for Halifax, they may wish to have some historical elements of their previous tool incorporated in the future development of the Halifax scoping tool to be developed by the claimants similar to the scoping tool mentioned above.
"vi Therefore it has been agreed, as Halifax is in the process of terminating their historic and current scoping tool, that they therefore agree to assign complete historic and current ownership and any rights to the claimant. In return, he has agreed to use/adapt any elements requested from previous Halifax scoping tools and the claimant agrees to use and implement them if required.
"vii The claimant agrees to allow direct communication between Jim Muirhead of Ultra-Soft, his developer, and his current employees to Jim Monteith and his pilot team, in order to provide direct feedback et cetera during the creation of the scoping tool pilot, but on the strict basis that Jim Muirhead cannot be asked to create any work whatsoever for the Halifax, including current, past, future employees and linked associates, without the claimant's written consent.
"viii Once the pilot work and testing has been completed, the claimant agrees to licence this to the Halifax on the basis that he will invoice and prorate per licence for each charged licence which is restricted to 1 PC and 1 PC user.
"ix Further costs will be agreed based on the additional savings that have been created through the introduction of the scoping tool throughout Halifax insurance and future licence fees et cetera will be charged/invoiced on current market rates at the time, which will be reviewed annually.
"x The claimant agrees to provide a fair and average market discount.
"xi The claimant and the Halifax agree to respect each other's confidential works and not provide them to any other parties unless either party has provided and obtained the written consent, and the same will apply to the copying of any works, et cetera.
"xii It has been agreed that, during the pilot and roll-out, the master copy would remain in the claimant's office at 134 Comiston Road, Edinburgh, given that complete ownership rests with the claimant, as set out and agreed above. All parties agree and consent to ensure that written approval is received that they require to alter this agreement.
"17. The pilot agreement had the following effects:
i. the claimant was to be the owner of and all rights in the estimating scoping tool that was to be developed under the pilot agreement ('the pilot scoping tool');
ii. Halifax assigned to the claimant any and all rights in the Halifax tool;
iii. Halifax enjoyed a licence to use the pilot scoping tool for the exclusive purposes of developing and evaluating the same during the period of the pilot scheme;
iv. Halifax was obliged to keep the pilot scoping tool confidential and not disclose the same beyond the Halifax pilot team."
"Halifax agreed with the claimant's proposal, and on 8th September 2006 Halifax entered into an oral agreement with the claimant ('the pilot agreement') in the following terms:
"i Halifax accepted that the claimant was the owner of the copyright in Estimate Builder in the claims control system.
"ii The claimant was to develop a scoping tool for Halifax similar to and based upon Estimate Builder ('the pilot scoping tool').
"iii The pilot scoping tool was to be developed for the purpose of testing and evaluation by Halifax, and Halifax was permitted to use it for these purposes.
"iv At Halifax's demand, the claimant would seek to incorporate some elements of the previous Halifax scoping tool and the pilot scoping tool.
"v Halifax agreed that the claimant would be the owner of the copyright in the pilot scoping tool.
"vi Halifax was permitted to liaise directly with the claimant's programmer, Mr Muirhead, during the development of the pilot scoping tool.
"xii Upon completion of testing and evaluation of the pilot scoping tool by Halifax, if Halifax wished to use the same, the parties would negotiate terms for such use in good faith to reflect existing market practice and Halifax's expected volume of use."
An amended defence was filed in which, in relation to the new paragraph 16 of the amended particulars of claim, it was pleaded that:
"Paragraph 16 of the amended particulars of claim is denied: (a) Mr Monteith did not say or hear any words to the effect of subparagraphs i to vii; (b) Mr Monteith had no actual or ostensible authority to contract on behalf of the second defendant in the terms set out in subparagraphs i to vii."
The issues
"48. Clearly, if C was unaware of the use by Lloyds of the scoping tool, then C's failure to object would not be relevant to ascertaining the scope of the indefinite consent. Here there would be two possible arguments why Lloyds had a consent: firstly, that the consent was given to Monteith, allowing Monteith to sub-licence his employer, provided always that the employer continued to use C's companies as contractors.
"49. Secondly, that the consent extended to any company in common corporate governance with Halifax, provided again that C's companies continued to be used as contractors. However, if C knows that Lloyds is using the tool, as D submits was the case in fact, then the acquiescence of C is the best evidence of the true scope of the licence as originally granted in indefinite terms.
50. D's doubt that an analysis based on the equitable principles of acquiescence are quite right in this case, because acquiescence is all about the case where no words are spoken. Here words were spoken, and the resulting licence was indefinite and needs to be defined by reference to, amongst other things, subsequent conduct. In ascertaining that scope, the court takes note of the fact that C did not complain of a particular circumstance of which he knew. Whether this is classified as licence or acquiescence probably doesn't matter. The latter requires detriment and unconscionability, but both are present in this case in any event."
The factual issue that arises is whether the claimant was aware of the use by Lloyds of the scoping tool prior to June 2011. The claimant denies that he had the alleged knowledge, but in any event it is asserted by him that whether he did or not is immaterial in law.
The Halifax licence issue.
(a) Mr Monteith was cross-examined about his ability to alter macros, and specifically about the removal of the claimant's name from a piece of code. The substance of his response was that the exercise was beyond his technical expertise (see transcript Day 3, page 1, line 20 to page 2, line 8). He was then cross-examined by reference to a section of code that on the face of it recorded that it had been carried out by Mr Monteith (see transcript Day 3, page 4, lines 9-15).He was then driven to accept that he could carry out coding but when coached by Mr Muirhead (see transcript Day 3, page 5, lines 19-21) before the following exchange took place:
Q: "In 2007, if I gave you a scoping tool, you could have brought it up to your laptop and you could have accessed the virtual basic code, couldn't you?"
A: "I have to say, at this moment in time, I don't know whether or not I could do that back then."
Q: "I put to you that you could and that yesterday you lied about your ability in relation to virtual basic code."
A: "I don't necessarily agree with that. I think the question yesterday was whether I removed anything from the document that was through the macro."
These answers I am afraid do not persuade me that Mr Monteith was being frank in the evidence he gave.
(b) Mr Monteith was cross-examined by reference to the transcript of the meeting on 24th October 2011, which led to the following exchanges:
"All he is asking you, this man who did you this terrific favour, is to tell the truth, and you indicate there that you will, yes?"
A: Yes."
Q: Why didn't you?"
A: "I don't think I've ever been on record as saying Mr Muirhead and Mr Shanley were not heavily involved."
Q: We discussed yesterday, instead of telling about the heavy involvement, you said that the contribution of Mr Muirhead and Mr Shanley amounted to minor technical changes and, on the basis of that assertion, Bevan Brittan on behalf of Lloyds and Halifax said there was no copyright in them. Why?"
A: "The choice of words may well be sort of detracted away from the input that Mr Shanley had, but as I say there, and I will stick by that, you know, Mr Shanley and Mr Muirhead did a lot of development on that tool."
Q: I'm sorry, I couldn't hear what you said at the end there. Could you just repeat that?"
A: Yes. I said that Mr Shanley and Mr Muirhead did have heavy involvement in the development of that tool."
Q: Can't you see the difference between heavy involvement in the development and minor technical changes? What I don't understand is on your case this man did you a big favour. Why are you deriding his contribution to your employers?"
A: Mr Shanley did not do me a big favour. Mr Shanley did work on behalf of Halifax, not on behalf of me."
Q: On your case, on your evidence, Mr Shanley did Halifax and Lloyds a very big favour. Why did you deride his contribution to them?"
A: If that's the way it's come across, I'm sorry about that."
Question: "No, no. That's how it did come across. We've established that. I'm asking you why."
A: As I say, it may be a poor choice of words at that particular time."
Q: No, that's not an explanation though, is it?"
A: I'm sorry, you're asking me a question, I can only give you the answer I'm giving you."
Q: You could give me a truthful answer." A: I think that is a truthful answer."
Q: A poor choice of words?" A: Yes."
Q: There is a motivation underlying this. Do you not see that?"
A: No."
Judge Pelling: Can I just ask you this. I don't want you to tell me anything about what Bevan Brittan said to you, but I do understand you to accept that you told representatives of Bevan Brittan that the involvement of the claimant was minor as described by counsel?"
A: My Lord, yes, if it is down there, I did say that to Bevan Brittan."
Judge Pelling: So was that in circumstances where you knew that the information you were providing to Bevan Brittan would be used for the conduct of this litigation?"
A: I assumed it would be used for this."
Thus Mr Monteith was driven to accept that he had misled the lawyers acting for the defendants on a critical issue at the time, in circumstances where he knew that the answers he gave would be used in a formal litigation setting. It is not necessary that I decide why he did what he did; it is sufficient for present purposes to note what he did. I do not accept the explanation that it was a poor choice of words. It was an active attempt to mislead, in my judgment.
Q: "Towards the bottom you say that 'with that in mind, the defendants stated that they had not at any time used any software provided to it by Mr Shanley'."
A: Yes.
Q: In fact it says 'or his associates', right? You said, 'I believed that position to be true at the time and indeed I believe that position to be true today', and you told my Lord that this statement is accurate?
A: That bit is not accurate.
Q: How much of this is not accurate? I gave you the opportunity to avoid all of this.
A: Yes, that is accurate at the time we had.
Q: You thought it was accurate at the time, it was inaccurate always. It was just that you had a reason to believe it because Mr Monteith told you lies.
A: Well, he told me what he said had happened, yes.
Q: We now know it wasn't quite like that, was it? A: Right.
Ultimately, Mr Williams was driven to accept that the letter he had come to court to defend was in fact indefensible, and that was so in substantial parts at least because he had been provided with false information by Mr Monteith.
"We are hoping this is of interest and would welcome a chance to demonstrate our service."
Two points emerge from this. First, it is consistent with the notion that the claimant was keen for CSL to win business from Halifax. Secondly, it contains no mention of the oral agreement which it is now alleged was made on the previous Friday.
"Hi Jim. I confirm on behalf of Completecare Scotland Limited that I have reviewed U schedule of rates and fully accept them and confirm we will work strictly to your SLA. My team are currently learning and adapting our reports to ensure we deliver you format and system requirements. We hope you have us up and running on this coming Monday, as we have now implemented your template into our management tracking system, et cetera. Kind regards, Jim Shanley for Completecare."
This email is significant because it too contains no mention of the oral agreement alleged to have been made on 8th May 2006. That point is all the more significant, in my judgment, because of the final sentence, which refers in terms to "implementing your template into our tracking system". This is a clear reference to the IT relevant to the conduct of the business emanating from the Halifax, and would have been the obvious and natural point to record the existence of the agreement, if only to demonstrate what steps were being taken by the claimant or CSL to implement it. Although the claimant tried to distance himself from this e-mail (see transcript Day 1, pages 113-116) he conceded, at transcript Day 1, page 117, line 1, that it: " … is more than likely that ..." he typed it.
"In or about the first half of February 2007, after my return from Australia, Jim Monteith and I had a meeting. In this meeting I asked about the scoping tool and he said that they do not wish to use the scoping tool, as the insurance company are going with a bidder product that incorporate all areas of their entire company. I also attended the Halifax suppliers' forum that month and saw the presentation where Karl Poulsen said that they were moving to a new claims-management system designed by someone else, and they were going down the route with them it seemed. This confirmed my understanding of their decision that it was part of their overall process/re-organisation which was discussed at the suppliers' forum. After that I thought no more about it. It seemed to me that I had made a proposal, but, as had happened with the Churchill discussions, it had not worked out and someone else's scoping tool would be used."
"Following a review of disclosure in this action, the claimant has become aware that Mr Muirhead continued providing further updated versions of the pilot scoping tool to Halifax pursuant to the pilot agreement until around February 2009."
The implication of this is that at the post February 2007 work, it came as a surprise, at any rate, to the claimant. This cannot be right for the following reasons: first, as Mr Muirhead made clear in the part of his witness statement quoted in the background section of this judgment, he expected to get paid for his work. Secondly, he was paid by CSL acting by the claimant - see transcript, Day 1, page 57, lines 17-21). Thirdly, Mr Muirhead's evidence at transcript Day 1, page 58, on this issue was as follows:
"Q: As I understand it, Mr Muirhead, you did a large amount of work on the spreadsheets after February 2007 and continued after that date; do you recall that?"
A: I recall doing some work after that, the amount of it I'm not sure about."
Q: Mr Shanley, Jim Shanley, says he didn't know you were working on that spreadsheet after February 2007; is that something that surprises you, to hear him say that?"
A: There were times when I was asked by Mr Monteith to do work and I did it without referring to Mr Shanley."
Q: But there were occasions when you let Mr Shanley know what you were up to?"
A: I suspect there would have been, yes. I expect there would have been."
This is evidence that I accept because Mr Muirhead could have no reason to mislead me in relation to this point. There can be no possible basis on which the claimant could have been paying or sanctioning payment to Mr Muirhead for work being done on the scoping tool for Halifax after February 2007 if the position was that there was an agreement to the effect now asserted by the claimant, made in September 2006, and Halifax had informed him that it had decided not to proceed further with the development of the pilot scoping tool in February 2007. It might have been suggested that in some way the work was of benefit to CSL. The claimant's case is however that this work would have been of no direct benefit to CSL in the sense of improving its systems. Indeed, the claimant's case is to the contrary, that the CSL and Halifax scoping tools were utilised different operating software.
"Judge Pelling: The question was, your recollection/understanding in evidence is it, is that the pilot in relation to your software, which you say was the subject of the oral agreement with Mr Monteith, came to an end in February 2007, yes or no?"
A: Around that time I agreed that there was no contract, they were not taking up my licence. I can't specifically say the pilot was at an end. I can remember them saying that they were not going to be taking it on, going forward. I just thought nothing of it ..."
Mr Onslow...
Q: You would agree with me that it would be most surprising to see you discuss improvements for your scoping tool with Halifax after the pilot came to an end; would you go that far?"
A: Repeat the question, please."
Q: Would you agree with me that it would be surprising to find you discussing improvements for the scoping tool with Halifax after the pilot came to an end?"
A: Yes."
Q: So that if the pilot came to an end in February 2007, when Mr Monteith had said that Halifax weren't interested in the tool, it would be surprising to see you discussing improvements for the scoping tool after February 2007; you'd agree with that?"
A: I would agree with that, yes."
Q: Now we know, at paragraph 50 of your statement, if you just turn on to that, that you do faintly remember discussing improvement for the scoping tool around May and June 2007?"
A: Yes."
Q: Yes?"
A: Yes."
Q: You do faintly remember discussing those improvements, do you?"
A: I will be honest, you know. I, at that time -- at that period I can't -- I can vaguely remember the timing of what happened because it is difficult for me today. It is really not having the real, you know, the actual -- my old e-mail account. It has been very difficult, the evidence, and I have tried to get these dates as close to what happened at that time
..."
In my judgment, this was a clear example of an attempt to avoid what was perceived by the claimant -- correctly -- to be a damaging point, but at a time when he had perceived the potential damage that would be done only relatively late in the exchange. He was asked specifically about the e-mail exchange that I had been considering. He said first it related to another pilot (see transcript Day 1, page 155, lines 24-25), then that he was busy and not on the ball (see transcript page 156, line 20), then that he could not recall it, (see transcript Day 1, page 157, lines 17-21). I reject all this as an attempt to avoid the effect of these e-mails on the basis that it is mutually inconsistent, and is an attempt to avoid what is obvious: that there were e-mails, one of which was written by him, concerning the development of the scoping tool after the date when he maintains the alleged agreement with Halifax had come to an end following a conversation that had taken place between him and Mr Monteith in February 2007.
(a) "... as per my discussion with you on Friday ..." in the first paragraph on page 1;
(b) "... I detail below some of the reasons why your financial plan ... simply cannot work for us ...", fourth paragraph on page 1; and
(c) "... I am sure you will appreciate I didn't have the time to do this last week ..."
This satisfies me that the response was written by the claimant. I accept he did not type it, and that if he had typed it himself, the grammar and layout may not have been the same but that is not the point. It was, on any view, a document that he had had significant input to, or had dictated, and the content of which pre-supposed sight of an understanding of the spreadsheets attached to the original Bellamy e-mail.
All this material leads me to reject the claimant's case concerning the oral agreement he alleges. It also leads me to accept the defendants' case that a voluntary bare licence was the result which was the outcome of the discussions which took place in 2006 concerning the scoping tool. This material shows ongoing development work well beyond February 2007, and shows, by reference to at least the exchange of e-mail on 23rd May 2007, that to the knowledge of the claimant the scoping tool was being exploited commercially by Halifax in the management of its contractors' network, of which CSL was a member.
"Jim Monteith 1:1
21/05/07
"1 HRS: Jim reports that PCC usage of HRS is 'low'. Cashing out prefers to be the preferred PCC settlement route. However, large loss PCC Tony Bowie (?) has been instructing his HRS network on larger claims. Jim further reports that Completecare are the PCC-preferred supplier of choice, and as such are picking up the most PCC constructions. Other CPs have commented on this, but the rebuttal from Jim is that Completecare are providing the benchmark service level that all suppliers in his region need to aspire to."
The Lloyds Position
(a) there was an implied licence granted to Lloyds because either
(1) Mr Monteith was entitled to grant sub-licences or
(2) the voluntary licence granted to Halifax was one that extended to any company in common corporate governance with Halifax; but
(b) irrespective of whether Lloyds' use had been licensed, the claimant was precluded from denying that such was the case by acquiescence and/or estoppel founded on alleged knowledge of use by Lloyds and the absence of any objection after that knowledge was acquired.
A: And then, near the end, by father brought up the situation about the software, from what I can recall."
Q: Right."
A: And it was all -- well, myself and Tom, I know myself felt quite awkward."
Q: I'm sorry?"
A: It was quite an awkward situation." Q: Awkward?"
A: Yes."
Q: In what way?"
A: Well, it was quite intense. It was quite -- you know, we were talking about an audit and then the software was brought up at the end, and it's, you know, it's got nothing to do with me and Tom, so I was quite uncomfortable."
Q: It had nothing to do with you and Tom, this complaint of your father's?"
A: No."
Q: Is it a complaint of your father that you supported, or are you neutral about it?"
A: At the start I was neutral because, you know, I didn't know anything about it. I knew he owned the scoping tool but I didn't know he didn't have an agreement with them in regards to, as time has gone on, and obviously supportive of himself ..."
This evidence is supported by the transcript of the meeting that hints at real anger, which also records the claimant as very clearly making the point that the claimant had not granted a licence to Lloyds. The recording does not suggest that this was challenged by Mr Monteith, who accepts that the record is accurate.
"Again, you know, through conversations with myself and Jim, Jim has started to intimate, you know, his input into the scoping tool. At this stage of our relationship, you know, we'd been working, you know, both at Completecare and Arngove, not necessarily at Arngove, because it's more Jamie working at Arngove. All of a sudden, the scope tool to be mentioned, the fact that all the development work that went in from, as Jim put it himself ..."
"Effect of Estoppel and Acquiescence
"Where a copyright owner stands back and allows another to assume that no objection will be taken to the exploitation of his work, the effect may be that the copyright owner will become estopped from asserting that there was no consent or that any consent has been revoked. The ordinary principles of estoppel or acquiescence would operate. In Fisher v Brooker, the claimant had contributed to a composition but left the band soon afterwards, making no claims to the copyright. His co-writer, the defendant, and his publishing company, continued to exploit the composition for almost 40 years. The claimant claimed that such exploitation was pursuant to an implied licence, which he purported to revoke. At first instance it was held that the claimant's contribution entitled him to a 40 per cent share and declarations as to joint authorship and joint ownership were granted, together with a declaration that the implied licence had been revoked and an order for an inquiry as to damages in respect of infringement during the period after revocation. The claim for restitution of past licence fees was dismissed on the grounds that there was an implied licence. Defences of a laches acquiescence and estoppel were rejected. The judgment was for the most part upheld in the House of Lords since the mere passage of time could not itself undermine a claim, and for it to do so, laches would need to be established. However, laches can only bar equitable relief and the declaration as to the existence of a long-term property right recognised as such by statute is not equitable relief. The defendants had not demonstrated any acts during the course of the delay which resulted in the balance of justice justifying the refusal of the relief to which the claimant would otherwise be entitled. They could not show any prejudice resulting from the delay, and even if they could, the benefit they had obtained from the delay would outweigh any prejudice."
The Archive Use Issue
"In a case where the licence is gratuitous and informal, the position is different, thus, where the work is supplied, knowing that it will be used for a particular purpose, the licence may be limited to that purpose, but where the purpose is less vague, the extent of the licence is unlikely to be confined to the immediate purposes which the parties had in mind. No doubt the test is objective. For what purposes would a reasonable person in the shoes of the licensee consider that he could use the work?"
In my judgment, on the findings I have made, the outcome is, or ought to be, obvious. Having been granted an gratuitous licence to use the scoping tool software for its commercial activities with its contractor network, a reasonable person in the position of Halifax would be bound to have concluded that the licence extended to archiving the material generated during the currency of the licence and to entitle Halifax thereafter to view the archived material for business and regulatory purposes, even after the licence had been terminated for all other purposes.
Conclusions
(1) There was no oral or any other agreement to the effect alleged by the claimant;
(2) There was a gratuitous and informal licence granted to Halifax by which it was entitled to use the software generated by Mr Muirhead on the instructions of the claimant for the purpose of conducting its business with its network of contractors. The licence was personal to Halifax and arose out of the commercial relationship between it and CSL. It did not entitle Halifax either to grant sub licences or to assign; in consequence
(3) The claim in infringement, breach of confidence and for unjust enrichment in relation to user by Halifax must necessarily fail other in relation to infringement by permitting Lloyds to use the software. The unjust enrichment claim must fail because the existence of the licence precludes it from being asserted that there was a mutual understanding that CSL expected payment for use of the software. In any event, I do not see how the claimant could make a monetary claim for any period prior to the date of the assignment to him of the software;
(4) Halifax was not able to sub-licence use of the software by other insurers, nor was its licence capable of assignment. In consequence, Lloyds is not, and never has been, licensed to use the software;
(5) Lloyds are not entitled to assert that the claimant is precluded by estoppel or acquiescence for denying the existence of a licence in its favour;
(6) Halifax's gratuitous licence extends to the storage and viewing of records prepared by it using the software during the currency of its licence, either by implication or because the claimant is estopped from revoking the voluntary licence to that limited extent;
(7) Had I concluded that Halifax was entitled to and had sub-licensed Lloyds to use the software, I would have concluded that Lloyds would have been entitled to the same outcome in relation to the storage and viewing of records prepared by it using the software during the currency of any sub-licence or licence assigned to it;
(8) In consequence, the claim against Halifax must fail and be dismissed in relation to any usage prior to 9th December 2011 or thereafter in relation to storage and view only of records created prior to that date using the software but otherwise succeeds; but
(9) The infringement claim against Lloyds succeeds.
I will hear counsel as to the appropriate directions necessary to carry into effect the findings I have made.
Postscript
(a) I record that the very serious allegations of conspiracy made by the defendants against JTS in opening this case were unequivocally withdrawn by the time they came to close their case.
(b) I conclude that Mr Williams was not personally responsible for the untruths that appeared in Bevan Brittan's letter in response to the letter before action, because the information was supplied to Mr Williams by others, and in particular by Mr Monteith, and was accepted by him in good faith.
(c) I acquit Bevan Brittan of culpability for the contents of the letter, which I am entirely satisfied was written by them on instructions.