15.08.2013 Views

Aggravated, Exemplary and Restitutionary ... - Law Commission

Aggravated, Exemplary and Restitutionary ... - Law Commission

Aggravated, Exemplary and Restitutionary ... - Law Commission

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

(31) once punitive damages have been awarded to one or more ‘multiple<br />

plaintiffs’ in respect of the defendant’s conduct, no later claim to<br />

punitive damages shall be permitted for that conduct by any<br />

‘multiple plaintiff’. (Draft Bill, clause 7(4))<br />

1.167 This provision means that a ‘multiple plaintiff’ will need to satisfy one additional<br />

condition if his or her claim is to succeed: there must have been no previous action<br />

brought by one or more other ‘multiple plaintiffs’ in which punitive damages have<br />

been awarded in respect of the defendant’s conduct.<br />

(iii) The assessment of punitive damages<br />

1.168 We consider that a court should make a separate assessment of punitive damages<br />

for each multiple claimant. That is, the court should decide upon an appropriate<br />

sum by reference to the circumstances of the particular plaintiff before it. One<br />

plaintiff may have provoked the defendant to act in such a way that he or she<br />

committed a wrong against the provoking plaintiff <strong>and</strong> several others. If so, it is<br />

likely that the award (if any) which is made to the provoking plaintiff will be<br />

significantly less, in the light of his or her responsibility for the wrongful conduct,<br />

than any which is made to the other, non-provoking plaintiffs. Where the<br />

defendant’s conduct vis-à-vis the plaintiffs is essentially the same, it would<br />

obviously be open to a court to make identical ‘individually-assessed’ awards to<br />

each of the plaintiffs.<br />

1.169 Nevertheless, we do consider that a ‘special’ approach must be taken to<br />

assessments of punitive damages in ‘multiple plaintiff’ cases. It should be laid<br />

down in statute that the aggregate award of punitive damages to two or more<br />

multiple plaintiffs should conform to what we call the principles of ‘moderation’<br />

<strong>and</strong> ‘proportionality’, which apply to limit the assessment of individual punitive<br />

damages awards. In other words, the aggregate award should not punish the<br />

defendant ‘excessively’ for his conduct. We therefore recommend that:<br />

(32) if the court intends to award punitive damages to two or more<br />

multiple plaintiffs in the same proceedings, the aggregate amount<br />

awarded must be such that, while it may properly take account of<br />

the fact that the defendant has deliberately <strong>and</strong> outrageously<br />

disregarded the rights of more than one person, it does not punish<br />

the defendant excessively for his conduct. (Draft Bill, clause 7(3))<br />

1.170 This express limitation on the total level of punitive damages awards in multiple<br />

plaintiff cases is, in effect, an application of the principles of moderation or<br />

proportionality (which are expressed in clause 5(2) of the draft Bill). 726<br />

But for<br />

two reasons, we think that such a special statutory limitation is still required. The<br />

first is that our assessment provisions (in particular, clause 5 of the draft Bill) are<br />

otherwise directed only at individual assessments. As a result, the principles of<br />

proportionality <strong>and</strong> moderation (in clause 5(1)) prima facie only apply to require<br />

that the award which the court is making for the defendant’s conduct vis-à-vis a<br />

particular individual be proportionate <strong>and</strong> moderate. Without further provision<br />

they do not furnish a separate limitation - the requirement that the aggregate of a<br />

726 See paras 5.120-5.122 above.<br />

147

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!