SYSTEMS DESIGN November 2002 Fordham School of Law Scanlon.

16
SYSTEMS DESIGN • November 2002 • Fordham School of Law • Scanlon

Transcript of SYSTEMS DESIGN November 2002 Fordham School of Law Scanlon.

Page 1: SYSTEMS DESIGN November 2002 Fordham School of Law Scanlon.

SYSTEMS DESIGN

• November 2002

• Fordham School of Law

• Scanlon

Page 2: SYSTEMS DESIGN November 2002 Fordham School of Law Scanlon.

VENUES

• PRIVATE CONTEXT– B2B

• Multi-Tiered or Multi-Step Dispute Resolution Clauses

– Employers/Employees Systems

– Business-Consumer Systems

• PUBLIC CONTEXT– Court-annexed Systems

– Implementation of Mass Claims Settlements

– Federal or State Employers/Employees

Page 3: SYSTEMS DESIGN November 2002 Fordham School of Law Scanlon.

CHALLENGE

• “The task for parties who can reasonably anticipate a stream of disputes between them is to go beyond settling those disputes one at a time and to go beyond selecting one procedure to resolve all disputes. Their goal should be to design at comprehensive and effective dispute resolution system.” (Goldberg, Brett, and Ury)

Page 4: SYSTEMS DESIGN November 2002 Fordham School of Law Scanlon.

PRIVATE CONTEXT

• Pre-dispute– Dispute Resolution Clauses: Multi-tiered or

Multi-Step

• Post-dispute– Toro example

Page 5: SYSTEMS DESIGN November 2002 Fordham School of Law Scanlon.

MULTI-TIERED or MULTI-STEP CLAUSE

• Pre-dispute

• Features

• Usage

Page 6: SYSTEMS DESIGN November 2002 Fordham School of Law Scanlon.

EXAMPLE OF DESIGN PRINCIPLES

• Prevention checks

• Interests-based focus - not rights-based

• “Loop-backs” to negotiation

• Low-cost adjudication backups

• Low-to-high cost sequence

• Provide necessary motivation, skills, resources and environment

Page 7: SYSTEMS DESIGN November 2002 Fordham School of Law Scanlon.

BASIC BUILDING BLOCKS

• Step One: Negotiation

• Step Two A: Mediation

• Step Two B: “Loop-backs” - evaluative mediation, advisory opinions, ENE

• Step Three: Arbitration or Litigation

Page 8: SYSTEMS DESIGN November 2002 Fordham School of Law Scanlon.

DESIGN SEQUENCE: ONE ROADMAP

• Identification of Objectives and Goals

• Identification of Participants – Design Committee? – Importance of involving “stakeholders” in

system

• Prevention Procedures– Notification and Consultation– Post-Dispute Analysis and Feedback

Page 9: SYSTEMS DESIGN November 2002 Fordham School of Law Scanlon.

• Interest-Based Procedures– Negotiation– Mediation

• (valuable means to ensure that interests are thoroughly considered before a dispute turns into a lawsuit)

DESIGN SEQUENCE

Page 10: SYSTEMS DESIGN November 2002 Fordham School of Law Scanlon.

• Loop-Back Procedures– Advisory Arbitration– Dispute Review Board

• construction - nonbinding, yet typically admissible in any subsequent dispute resolution proceeding

– Minitrial (for more significant disputes)– Summary Jury Trial (for more significant

disputes)– Cooling-Off Period

DESIGN SEQUENCE

Page 11: SYSTEMS DESIGN November 2002 Fordham School of Law Scanlon.

• Low-Cost Back-Up Procedures– Arbitration (conventional, expedited, final

offer)

• “Marketing” of Design System– motivation, skills, resources

DESIGN SEQUENCE

Page 12: SYSTEMS DESIGN November 2002 Fordham School of Law Scanlon.

• Increase in claims if system is designed?

• Sequence of Procedures (e.g., negotiation, mediation, arbitration) may undermine negotiation stage

• Buy-In

HIDDEN PITFALLS

Page 13: SYSTEMS DESIGN November 2002 Fordham School of Law Scanlon.

DUE PROCESS CONSIDERATIONS

– Neutrals– Payment– Pre-dispute vs. post-dispute– Remedies– Notice– Others

Page 14: SYSTEMS DESIGN November 2002 Fordham School of Law Scanlon.

• How to evaluate systems?

• Criteria

MONITORING

Page 15: SYSTEMS DESIGN November 2002 Fordham School of Law Scanlon.

EMPLOYMENT PROGRAMS

• Private

• Case law

• Recent statutory developments

Page 16: SYSTEMS DESIGN November 2002 Fordham School of Law Scanlon.

PUBLIC CONTEXT

• Court Programs (e.g., Mandatory Mediation Programs)

• Mass Claims Settlements