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 £1, 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 (Technology and Construction Court) Decisions |
||
You are here: BAILII >> Databases >> England and Wales High Court (Technology and Construction Court) Decisions >> Atos Consulting Ltd v Avis Plc [2007] EWHC 323 (TCC) (14 February 2007) URL: http://www.bailii.org/ew/cases/EWHC/TCC/2007/323.html Cite as: [2007] EWHC 323 (TCC), [2008] Bus LR D20 |
[New search] [Printable RTF version] [Buy ICLR report: [2008] Bus LR D20] [Help]
QUEEN'S BENCH DIVISION
TECHNOLOGY AND CONSTRUCTION COURT
Strand, London, WC2A 2LL |
||
B e f o r e :
____________________
Atos Consulting Limited |
Claimant |
|
- and - |
||
Avis PLC |
Defendant |
|
JUDGMENT NUMBER 2 |
____________________
Duncan Mathews QC., Lawrence Akka, Henry Byham-Cooke and Colleen Hanley (instructed by Olswang) for the Defendant/Respondent
Hearing date: 9 February 2007
____________________
Crown Copyright ©
The Hon Mr Justice Ramsey :
Introduction
The Application by Atos
"In response to your paragraph 1.25, the sections of board minutes and papers which have been redacted on the grounds of irrelevance relate to Avis's activities other than in relation to the FSP Project and ITFS. For example, information and comment on Avis' turnover and profit margins. However, where paragraphs in these sections to relate to the FSP Project or ITFS they were not redacted."
"The minutes are of great intrinsic importance to a very important issue in this case. Beyond that however it will be noted that the redactions are made even in paragraphs of the minutes headed "Financial Systems & Processes Project" and in one case in the middle of that paragraph (see H18/35) at paragraph 7.3."
"The redactions of Avis' board documents were undertaken at my direction and all sections of the minutes and papers for Avis' board of directors' discussions which have been redacted are (1) confidential records of Avis' board of director's discussions in matters unrelated to this dispute which are by their very nature confidential and contain information which could be price sensitive, confidential as far as Avis employees (including potentially witnesses in this case) are concerned, of use to competitors or potentially damaging if revealed and (2) irrelevant to the issues in dispute. The redactions, and the basis for the redactions, was explained in Avis' List of Documents.
By way of example, the redacted sections of the 26 February 2003 board meeting to which Atos' application related are headed as follows and contain no reference to the FSP Project, ITFS or related matters:
2 2002 Financial Statements
3 Trading Results
4 Investor Relations Report
5 Treasury Report
6 Project Zodiac Update
8 Approvals Required
9 Approvals given
Page 10 of this minute contains a redaction in the "Overview" section regarding the FSP Project. The deleted sentence noted that there would be additional capital expenditure on unrelated confidential matters."
The Application by Avis
"The Court decide pursuant to CPR 31.19(5) whether some or all of the Claimant's claims of privilege in respect of the Challenged Documents (listed in the Schedule to the draft Order) should be upheld ."
"We have taken advice from counsel in respect of the documents in which Atos claimed common interest privilege. In order to save further correspondence, Atos has decided to waive privilege in these five documents….
Litigation privilege:
Litigation privilege is claimed in the remaining ten documents. The dominant purpose of the authors of these documents was to assist with the preparation of Atos' case (that is the subject of these proceedings)."
"I have reviewed these documents and I do not believe that there was any basis on which Atos could rightly claim any form of privilege in the documents. The fact that someone at Nabarros believed Atos was ever entitled to claim privilege in these documents suggests that their approach to questions of privilege is flawed".
"The Challenged Emails are dated between 18 and 25 November 2004 (after the FSP Project had ended but before proceedings were issued) and all are emails between PeopleSoft personnel only. None of the emails were sent by or to or copied to Atos personnel. Oracle/PeopleSoft is not a party to these proceedings. The authors of the Disputed Emails are Martyn Hardy, Ivo Lasan, Steve Gallagher, Anne van der Hagen and Gary Fitchett, none of whom is giving evidence in these proceedings.
Oracle itself has not claimed privilege in any of the Disputed Emails. It is of note that, whilst nine of the disputed emails mention "Avis", one is headed "How's India?" and even by its description would not appear to be privileged."
"The letter dated 26 January 2007 was simply in error in stating that privilege was being waived in the five documents. The documents had been identified as not privileged. I fail to understand Mr Baker's comment as to the title of one of the emails indicating the content of the document as not privileged. He does not suggest that the heading "How's India?" could possibly be relevant.
I have read and considered the content of every email in which privilege is claimed and have consulted Counsel on the matter (who have also read and considered the content). I am fully satisfied that the claim for privilege in these documents is correct."
"The Report was prepared towards the end of the FSP Project following Avis' request that Atos review the status of the FSP Project and report on this and what had caused the delays which had arisen. Atos did not disclose any drafts of the Report or any documents (such as emails) which relate to the drafting of the report in its standard disclosure despite their obvious relevance to the issues in dispute."
"In respect of the redacted versions of the "Report on the Progress of the FSP Programme" provided to you on 22 January 2007, Atos claims legal advice privilege in the redacted text. The redacted material was the subject of legal advice."
"The purpose of this document is to respond to concerns Avis have raised about the status of the FSP Programme and the quality of work delivered by [Atos] and PeopleSoft in the FSP Programme.
Based on the conclusions made in this document we will make Recommendations on what actions need to be taken by Avis, PeopleSoft and Atos to give a level of comfort and trust that both the Expenses and Revenue streams will be deployable.
It is the aim of this document to give Avis the information needed to confirm to their next Board meeting (October 19) that they will proceed with the Expenses go-live in Germany November 1, or otherwise."
"I do not believe that Atos' claims of privilege in respect of the drafts of the Report can be maintained because the Report was not drafted by or for lawyers, purports on its face to always have been intended for disclosure to Avis and because Atos has not identified any proper ground on which privilege is claimed."
"…the redacted passages of the Reports contain legal advice reviewed, amended, approved and given by James Loughrey (Atos' Head of their UK Legal Department) in his capacity as legal advisor to Atos"
The Law
"(3) A person who wishes to claim that he has a right or a duty to withhold inspection of a document, or part of a document, must state in writing –
(a) that he has such a right or duty; and
(b) the grounds on which he claims that right or duty.
(4) The statement referred to in paragraph (3) must be made –
(a) in the list in which the document is disclosed; or
(b) if there is no list, to the person wishing to inspect the document.
(5) A party may apply to the court to decide whether a claim made under paragraph (3) should be upheld.
(6) For the purpose of deciding an application under …paragraph (3) (claim to withhold inspection) the court may –
(a) require the person seeking to withhold disclosure or inspection of a document to produce that document to the court; and
(b) invite any person, whether or not a party, to make representations
(7) An application under paragraph …(5) must be supported by evidence."
"It has long been the practice that a party is entitled to seal up or cover parts of a document which he claims to be irrelevant.. Bray's Digest of the Law of Discovery, 2nd ed.(1910), pp. 55-56 puts the matter succinctly:
Generally speaking, any part of a document may be sealed up or otherwise concealed under the same conditions as a whole document may be withheld from production; the party's oath for this purpose is as vali in the one as in the other. The practice is either to schedule to the affidavit of documents those parts only which are relevant, or to schedule the whole document and to seal up those parts which are sworn to be irrelevant;…"
"The oath of the party giving discovery is conclusive, "unless the court can be satisfied-not on a conflict of affidavits, but either from the documents produced or from anything in the affidavit made by the defendant, or by any admission by him in the pleadings, or necessarily from the circumstances of the case-that the affidavit does not truly state that which it ought to state": per Cotton L.J. in Jones v Andrews (1888) 58 L.T. 601, 604"
"The inference I draw from this quotation is that the missing words deal with the shortcomings of the accountants in the other transaction. How can this, or the name of the party involved, be relevant to the issues in this case? Mr. Unwin says that other transactions may enable Arthur Anderson to assemble a general picture of G.E's investment strategy and invite an inference that G.E. was so anxious to become a big player on the London market that it was willing to lend money recklessly, paying little or no attention to accountants' reports and failing to make prudent inquiries."
"The fact that the blanked-out part deals with the same subject matter as the part admitted to be relevant may mean that the former is also likely to be relevant. On the other hand it may not. The link between the two pieces of information which makes it appropriate to say that the subject matter is the same may be irrelevant to any issue in the action. Thus the memorandum from which I have quoted deals in one sense with the same subject matter, viz., G.E. deals which have gone wrong. But given the restrictions on the use of similar fact evidence, this is not enough to entail the relevance of the other transaction."
(1) At para 5-21 and 9-22 in relation to blanking out, he states:
"It is apparent from r.31.19(3), which refers to a person who wishes to claim that he has a right or duty to withhold inspection of a document, or part of a document, that the right to blank out in appropriate cases is retained. The appropriate method is to make clear in the list that inspection is only being offered of part of certain documents because the party serving the list claims to be entitled to blank out parts."
and
"Where material in the document is simply irrelevant, it is unlikely that there will be any point in blanking it out unless it is confidential. Blanking out part of a document always seems to excite interest in the document and the hidden contents for the other side which would be unlikely otherwise to exist. If it is genuinely irrelevant and confidential it can be blanked out. If there is a dispute, the judge can always be asked to rule."
He adds as a footnote that: "In Paddick v Associated Newspapers [2003] EWHC 2991 Tugendhat J. accepted a submission by counsel that the statement of a party who has blanked out parts of a document that the blanked out parts are irrelevant is conclusive."
He comments: "This formulation goes too far. A better way of putting the point would be to say that unless there is evidence that the party has adopted a wrong test or otherwise erred in the decision to blank out the court is unlikely to go behind that decision."
(2) At para 12-33 in relation to the claim for privilege he states:
"It was often said under the RSC that a claim for privilege in the list which was formally correct may not normally be challenged. In fact, the position was less clear. The traditional view was that a claim for privilege, if formally correct might only be challenged if it could be seen from the whole affidavit, or from the nature of the case or the documents themselves, that the party making discovery had erroneously represented or misconceived their nature or effect, but the court would not speculate upon such misconception and would accept the list verified by affidavit as conclusive, unless it could see distinctly that the oath of the party could not be relied upon. There was plenty of old authority to support this statement of principle. The position in practice under the RSC was rather less dogmatic than the theory. The reality was that in many cases the courts did challenge the claim for privilege."
Under the CPR the indications are that if a party can provide an evidential basis for challenging the claim to privilege, the court will investigate the issue in full. First, there is now an express power to apply to the court, which can be invoked by either party, to determine the validity of a claim to privilege. Secondly, there is an increased emphasis on the power to ask the court to inspect to determine a claim. Under the traditional view, if the claim to privilege was in general conclusive, there was little room for inspection by the court. It would be fair to say that a properly drafted claim for privilege in the list imposes an evidential burden on the other party under the CPR. It will be necessary to put forward some sensible evidential basis for the challenge. But once that evidential burden had been satisfied the burden is likely to be on the party claiming privilege to make good the claim."
In this context, I was also referred to paragraph 5-37 of Matthews & Malek (2nd Edition) but I consider that the position under the former RSC now has to take account of the provisions of CPR rule 31.19 which is not dealt with expressly in that paragraph.
(3) At paras 8-40 to 8-42 in relation to CPR rule 31.19(6) he states:
"There is now express provision under the CPR for the court to require production to itself in order to determine whether to order disclosure or inspection, which suggests the procedure will be used more readily. Practically where the matter arises at trial, inspection by the court dispels any suggestion that there are sinister undisclosed documents lurking under some dubious claim for privilege or irrelevance. Skilful advocacy can sometimes give rise to a suspicion that there is more beneath the surface than is actually the case. So there are times when inspection by the court resolves all difficulties.
However, there are inherent difficulties in inspection by the court which the cases do not in general grapple with. First, the disclosure exercise is always carried out under the supervision of the lawyers, and relies upon the lawyers fulfilling their duties to the court. Day-to-day decisions as to whether to disclose specific documents are taken by the lawyers. No one else is in a position to make those decisions, and there is in practice no supervision by the court as to whether, for example, the lawyers have taken a wrong view of privilege or relevance. Applications for specific disclosure only provide the most limited supervision because the other party simply will not be aware in most cases of the facts relied upon to justify a particular claim for privilege or irrelevance, and the basis for such decisions will not usually be transparent. Given that basic premise, it is illogical for the court to be asked to intervene other than in a case where there is reason to believe on evidence that the lawyers have either misunderstood their duty or are not to be trusted with the decision-making. These will be exceptional cases.
In Paddick v Associated Newspapers [2003] EWHC 2991 Tugendhat J refused to go behind the statement of a party that redacted parts of a document were irrelevant. In Nucleus Information Systems v Palmer [2003] EWHC 2013 (CH) Lewison J. was told that the applicant did not accept that the other party had given proper disclosure of the relevant contents of his home computer, and sought an order that he should have access to the computer in order to search through his lawyers. The court refused to permit the applicant direct access to the computer. In either case the court plainly has jurisdiction to make the order sought. In neither case was the application for inspection by the court. But the issue is analogous. These are welcome examples of the Court recognising that it is for the party giving disclosure through his lawyer to make judgments as to what is to be disclosed, and not for the court to second-guess those judgments without good reason.
Secondly, and more importantly, inspection by the court is usually effected in circumstances in which only one party has seen the documents in question. It would be possible for the documents to be disclosed to the other side for the purpose of facilitating inspection by the court, and disclosed to the lawyers only, but this is rarely done for this purpose and will sometimes be impractical, such as where a claim for privilege is under consideration. It is extremely unsatisfactory that the court should be asked to make a decision where the information available to the parties is different. There is very little consideration of this point in the authorities. In a confidential case, KPMG v White & Case (unreported November 18, 1996) Harman J. observed, in refusing to look at the documents in issue:
"Matters before a judge must either be in evidence in the normal way or, in a confidential information case, it may be that part of the proceedings when the confidential information is disclosed should be heard in camera, but the evidence must be open to the judge and available to both sides. A judge cannot take into account secret information made available to him only by one side. Judicial Decisions must be made on material common to both sides."
Unless both parties consent to inspection by the court, problems may therefore arise in the parties not having equal access to the court, which gives rise to Art. 6 problems as well as under r.1.1(2)(a) of the CPR and thus makes the exercise less attractive to the court."
(1) The Court has to consider the evidence produced on the application.
(2) If the Court is satisfied that the right to withhold inspection of a document is established by the evidence and there are no sufficient grounds for challenging the correctness of that asserted right, the Court will uphold the right.
(3) If the Court is not satisfied that the right to withhold inspection is established because, for instance, the evidence does not establish a legal right to withhold inspection then the Court will order inspection of the documents.
(4) If sufficient grounds are shown for challenging the correctness of the asserted right then the Court may order further evidence to be produced on oath or, if there is no other appropriate method of properly deciding whether the right to withhold inspection should be upheld, it may decide to inspect the documents.
(5) If it decides to inspect then having inspected the documents it may invite representations.
The Application by Atos: Board Meeting Minutes
"MS confirmed that the Group's total capital expenditure commitments for 2003-2005 represents a cash investment of €100 million, comprising approximately €16 million approved for Project Pearl, €63 million for the Financial Systems & Processes Project, the €10.6 million requested expenditure for IT FutureShape and a remaining €10 million for Avis Futures which is scheduled to complete in mid -2004.
REDACTED-IRRELEVANT
The rate of spend will build up in 2003 and 2004, with savings generated from 2005 onwards."
The Application by Avis: The FSP Report
"To respond to concerns that Avis have raised about the status of the FSP programme and the quality of Atos Origin's and PeopleSoft's work on the FSP
To determine what actions need to be taken by AC, PeopleSoft and Avis to give the required level of comfort that:
The expenses system is ready to go live on the 1st November 2004 as planned
The revenue system will be deployable in an acceptable timeframe.
To review the commercial position relating to the assignment. It is recognised that this element will contain recommendations confidential to Atos Origin, and which will not be released to Avis."
The Application by Avis: The 10 emails
The Avis Application: Other matters
The Atos Application: Other matters
(1) Documents referred to in Requests 3 to 7 of 11 December 2006;
(2) All versions of "Scenario 1.xls";
(3) A copy of an email response from Jaspal Kalsi (8:36 on 7 April 2004);
(4) Copies of all existing K:Drive back up tapes and a full copy of the K:Drive as it existed at the termination of the MSA.
Requests 3 to 7
Scenario 1.xls
Jaspal Kalsi email
K: Drive
1 Atos relies on legal advice privilege. In relation to these drafts of the report. These drafts were not written by Mr James Loughrey but were produced by authors identified in the report. (see SB5/15)
2 The communications sent to Mr Loughrey or received from Mr Loughrey in the context of receiving legal advice would be privileged.
3 If the authors themselves set out their views in a draft which was circulated for comment generally including being sent to an in-house lawyer or if the authors altered the draft as a result of obtaining legal advice neither the original draft circulated by them generally nor the altered text taking account of legal advice would be privileged unless it set out the contents or gist of that legal advice obtained, in this case, from Mr Loughrey. I accept that the advice might include "presentational advice": see Three Rivers DC v. Bank of England (No 6) [2005] 1 AC 610 at 652H, 658D and 681D. Thus, such advice would be covered but not, in my judgment, the presentation which was made taking into account that advice.
4 In a note dated 12 February 2007 providing the Court with copies of further authorities, counsel for Atos also stated that:-
"Atos does not intend to tender further evidence on the points before the Court. However in light of the way in which the parties' arguments were developed on Friday, Atos thought it proper to record that the contemporaneous emails (in which privilege is not hereby waived): (1) do not disclose that version 0.2 of the Draft Review report (referred to at paragraph 9(b) of the fifth witness statement of Rosemary Mulley) and version 0.3 (paragraph 9(d) ibid) were sent to James Loughrey;(2) disclose that version 0.2 dated 6 October 2004 (paragraph 9(c) ibid) and version 0.5 (paragraph 9(e) ibid) were sent to James Loughrey, and (3) disclose that an earlier version 0.2 dated 4 October 2004 was sent to James Loughrey."
5 I bear that in mind when I consider the documents. My conclusions on the review of the five drafts is as follows, referring to pages in SB5:
A Version 0.1 dated 27/9/04 (SB5 1 to 11)
There are no redactions apparent in this version.
B Version 0.2 dated 4/10/04 (SB5 12 to 31)
(1) Redaction in para 4.6.1 on SB5/21
This does not contain legal advice and is not privileged.
(2) Redaction in para 4.6.2 on SB5/22
This does not contain legal advice and is not privileged.
(3) First redaction in para 4.6.2 on SB5/23
This does not contain legal advice and is not privileged.
(4) Second Redaction in para 4.6.2 on SB5/23
This does not contain legal advice and is not privileged.
(5) Third redaction in para 4.6.3 on SB5/23
This sets out the financial position and does not contain legal advice. It is not privileged.
(6) Redaction of para 4.6.3 and 4.6.4 on SB5/24
This sets out the financial position and deals with matters of corporate and commercial management. It does not contain legal advice and is not privileged
(7) Redaction of para 4.6.4 and 4.6.5 on SB5/25
This deals with matters of corporate and commercial management and supplier management. In the first bullet paragraph under para 4.6.5 the wording after "has not been reviewed" may properly be redacted as it is likely to contain legal advice. Otherwise the text does not contain legal advice and is not privileged.
(8) Redaction of para 5.6.1 on SB5/27
This deals with contractual issues and sets out views or arguments on legal matters. On balance it is likely that this paragraph contains legal advice and therefore may be properly redacted.
(9) Redaction of para 5.6.1, 5.6.2, 5.6.3, and 5.6.4 on SB5/28
The content of para 5.6.1 again deals with contractual issues which may properly be redacted.
The remainder of the paragraphs (para 5.6.2, 5.6.3 and 5.6.4) deal with financial and management matters and do not contain legal advice. They are not privileged.
(10) Redaction of para 6.6 on SB5/29
There is no text and the heading alone is redacted. It is not privileged.
C Version 0.2 dated 4/10/04 (SB5 32 to 56)
(1) Redaction of headings on contents page (SB5/33)
These headings relate to matters similar to those dealt with in B(5), B(6), B(7) and B(9) above which are not privileged.
(2) Redaction of heading on contents page (SB5/34).
The relevant heading relates to the matters similar to those dealt with in B(10) above and is not privileged.
(3) Redaction of text on SB5/36
This text is likely to be a request for legal advice and is privileged.
(4) Redaction of para 4.6.1 on SB5/44
As B(1) above.
(5) First redaction in para 4.6.2 on SB5/46
The words "This would appear to be inconsistent" should not be redacted but the remainder of this bullet paragraph is properly redacted on the basis that it contains legal advice.
(6) Second Redaction in para 4.6.2 on SB5/46
As B(2) above.
(7) Third redaction in para 4.6.2 on SB5/46
As B(3) above
(8) Fourth Redaction in para 4.6.2 on SB5/46
As B(4) above.
(9) Fifth redaction - para 4.6.3 on SB5/46
As B(5) above.
(10) Redaction in para 4.6.3 on SB5/47
As B(5) above.
(11) Redaction of para 4.6.3, 4.6.4 and 4.6.5 on SB5/48
In the first bullet paragraph under para 4.6.5 the wording after "has not been reviewed" may properly be redacted as it is likely to contain legal advice. Otherwise these sections deal with financial and management issues and do not contain legal advice and are not privileged.
(12) Redaction of para 5.6.1 on SB5/52
As B(8) above. I consider that this may properly be redacted.
(13) Redaction of para 5.6.1, 5.6.2, 5.6.3 on SB5/53
The contents of para 5.6.1 again may be properly be redacted. The remainder of the paragraphs (paras 5.6.2.ad 5.6.3) deal with financial and management matters and do not contain legal advice. They are not privileged.
(14) Redaction of paras 5.6.3 and 5.6.4 on SB5/54
These deal with financial and management matters and do not contain legal advice. They are not privileged.
(15) Redaction of para 6.6 on SB 5/55
As B(10) above.
D Version 0.3 7 October 2004 (SB5/57-82)
(1) Redaction of contents (SB5/58 and 59)
As C(1) and (2) above.
(2) Redaction of para 4.6.1 on SB5/69
As B(1) above.
(3) First Redaction of para 4.6.2 on SBS/71
As C(5) above.
(4) Second, third and fourth Redaction of para 4.6.2 on SB5/71
As B(2), B(3) and B(4) above.
(5) Fifth redaction - para 4.6.3 on SB5/71
As B(5) above.
(6) Redaction of para 4.6.3 on SB5/72
As B(5) above.
(7) Redaction of para 4.6.3 and 4.6.4 on SB5/73
As B(6) above.
(8) Redaction of para 4.6.4 and 4.6.5 on SB5/74
As B(7) above.
(9) Redaction of para 5.6.1 on SB5/77
As B(8) above.
(10) Redaction of paras 5.6.1, 5.6.2 and 5.6.3 on SB5/78
As C (13) above.
(11) Redaction of para 5.6.4 on SB5/79
This deals with management matters and does not contain legal advice. It is not privileged.
(12) Redaction of para 6.6 on SB5/81
This section contains commercial recommendations. The opening section of each draft report (except version 0.1), including the final report (SB5/171) served by Atos, it is stated that the objective of the Report was:
"To review the commercial position relating to the assignment. It is recognised that this element will contain recommendation confidential to AC, and which will not be released to Avis."
These commercial recommendations are said to the confidential to AC. They are commercial recommendations and do not on their face contain legal advice. Whilst they may have been "reviewed, amended or approved" by Mr Loughrey that does not make them privileged and I do not consider that paragraph 6.6 can properly be redacted on the basis of legal advice privilege.
E Version 0.5 8 October 2004 (BS/83 to 125)
(1) Redaction of contents pages (SB5/84 and 85)
As C(1) and C(2) above.
(2) Redaction of para 4.6.1 on SB5/104
As B(1) above
(3) First redaction of para 4.6.2 on SB5/105
As C(5) above
(4) Second and third Redaction of para 4.6.2 on SB5/105
As B(2) and B(3) above
(5) Redaction of para 4.6.2 on SB5/106
As B(4) above.
(6) Redaction of para 4.6.3 on SB5/106
As B(5) above
(7) Redaction of paras 4.6.3 and 4.6.4 on SB5/107
As B(6) above.
(8) Redaction of para 4.6.4 and 4.6.5 on SB5/108
As B(7) above.
(9) Redaction of 5.6.1 on SB5/120
As B(8) above
(10) Redaction of 5.6.1, 5.6.2, 5.6.3 and 5.6.4 on SB5/121
As B(9) above
(11) Redaction of 6.6 on SB5/123 to 124
As D(12) above
1 Atos relies on litigation privilege in relation to the emails. It does not rely on the emails being irrelevant or on there being any common interest privilege.
2 Litigation privilege applies to documents embodying communications with (including reports to or from) a non-professional servant agent or third party if they came into existence for the purpose of obtaining advice in anticipated proceedings.
3 That litigation privilege applies to a document which is produced or brought into existence where the demonstrated purpose of its author, or of the person or authority under whose direction it is produced or brought into existence is the use of the document or its contents in order to obtain legal advice or to conduct or aid in the conduct of litigation in reasonable prospect at the time of its production.
4 As Taylor LJ said Balabel v. Air India [1988] 1Ch 317 at 330 when speaking of legal advice privilege but which I consider is also relevant to litigation privilege:
"Usually a letter which does no more than acknowledge receipt of a document or suggest a date for a meeting will be irrelevant and so non-disclosable."
5 In the context of litigation privilege I consider that such privilege only applies to documents produced when the dominant purpose is the use of the documents or its contents in order to obtain advice or conduct the litigation. Thus questions asked or answers given or reports produced for that purpose will be covered by the privilege. The preliminary actions such as arranging a meeting or any documents produced which relate to the fact that information might be given or documents might be produced which then will be covered by litigation privilege are not, in my judgment, covered by such litigation privilege. They are generally likely to be irrelevant.
6 In the present case in relation to the particular documents:
(1) OR 004347: Email 18/11/04 Hardy to Gallagher, Fitchett, Lasan
This is an email concerning preliminary actions. It is not covered by litigation privilege.
(2) OR004348: Email 18/11/04 Gallagher to Hardy, Van der Hagen (copied to Fitchett, Lasan)
This is an email responding to and incorporating the email at 004347 concerning preliminary actions. It is not covered by litigation privilege.
(3) OR004349: Email 18/11/04 Van der Hagen to Gallagher (copied to Fitchett, Lasan, Hardy)
This is an email responding to 004348 (incorporating 004347 and 004348) and concerns preliminary actions. It is not covered by litigation privilege.
(4) OR004350: email 18/11/04 Hardy to Van der Hagan (copied to Fitchett, Lasan, Gallagher).
This is an email responding to 004349 (incorporating 004347, 004348 and 004349) and concerns preliminary actions. It is not covered by litigation privilege
(5) OR 004351: Email 18/11/04 Van der Hagen to Hardy (copied to Fitchett, Lasan, Gallagher).
This is an email responding to 004350 (incorporating 004347 to 004350) and covers preliminary matters. It is not covered by litigation privilege.
(6) OR 004358: Email 19/11/04 Fitchett to Hardy
This is an email which concerns preliminary matters. It is not covered by litigation privilege.
(7) OR 004360: Email 19/11/04 Hardy to Lobo
This is an email which, in the first paragraph, contains reference to irrelevant personal matters. The remainder concerns preliminary matters. It is not covered by litigation privilege.
(8) OR 004378: Email 23/11/04 Gallagher to Hardy.
This email incorporates three other emails:
(a) An email of 17/11/04 from Mark Tapp of Atos to Stephen Blundell and Richard Shakespeare at PeopleSoft concerning payment for work carried out by PeopleSoft on the Avis project. That is not covered by litigation privilege.
(b) An email of 18/11/04 from Mark Tapp to Serge Minne forwarding the email of 17/11/04 to him. That is not covered by litigation privilege.
(c) An email of 23 /11/04 from Serge Minne (copied to James Loughrey of Atos and Steve Gallagher) concerning the account between Atos and PeopleSoft, and responding to previous emails. That is not covered by litigation privilege.
The email itself concerns preliminary matters. It is not covered by litigation privilege.
(9) OR 004385: Email 25/11/04 Hardy to Gallagher.
This is a reply to 004378 (incorporating the same emails as 004378). It concerns preliminary matters. It is not covered by litigation privilege.
(10) OR 004379:Email 24/11/04 Lasan to Lasan
This email forwards an email of 23/11/04 from Gallagher to Hardy (copied to Van der Hagan, Fitchett, Lasan). That email of 23/11/04 concerns preliminary matters. It is not covered by litigation privilege.