Slashdot Mirror


Proposed Federal Rules On E-Document Destruction

runner345 writes "The Federal Advisory Committee on Civil Procedure is evaluating a series of 'e-discovery' rules that will change the way litigation handles electronically stored information for the federal courts. Included in this is proposed Fed. R. Civ. P. 37 which would exempt parties from sanctions for electronic evidence destroyed in a 'routine operation of the party's electronic information system.' Microsoft and other technology heavy-hitters have strongly backed this safe harbor because it judicially validates electronic document retention policies (perhaps the most effective Orwellian misnomer for outright document destruction). If you thought it was hard to get incriminating documents from the tech industry now, think about what this rule will do to a plaintiff's chances. You can get the proposed rule here (when their site works) and read what Microsoft and Intel have to say about it here. You can also read my law school thesis on the topic (still only in draft)."

13 of 147 comments (clear)

  1. Simple! by sandstorming · · Score: 4, Funny

    Destroying E Documents for dummies... Place on Hard Drive Give Hard Drive to 3 year olds with knives Tell then there is candy inside.

    1. Re:Simple! by deutschemonte · · Score: 5, Funny

      Or...
      Install Windows, place on hard drive, give an open internet connection three days to install candy inside.

      --
      The preceding message was based on actual events. Only the names, locations and events have been changed.
  2. document rentention policies by alatesystems · · Score: 4, Insightful

    We already have electronic document retention policies, and we do get rid of things on a regular basis. I don't really understand what this rule would be for, except to validate practices already in place at almost every major company.

    The submitter makes it sound like it's horrible for the plaintiff, but would we really want to live in a world where we have to keep every single file forever? I think not.

    1. Re:document rentention policies by natrius · · Score: 5, Interesting

      The submitter makes it sound like it's horrible for the plaintiff, but would we really want to live in a world where we have to keep every single file forever? I think not.

      Do we really want to live in a world where there is no such thing as electronic evidence, since anyone can just say, "oops, it got deleted in the routine operations of my business... last night." I think not. See Burst v. Microsoft.

    2. Re:document rentention policies by corporatemutantninja · · Score: 4, Interesting
      Actually, I do see a change. And this applies to rules about paper, email, and now IM retention as well.

      All that currently happens is that companies avoid putting anything potentially incriminating in writing. "Call me about this," the email says. So companies spend huge amounts of money ensuring "compliance" with retention laws, plus they are unable to get all the efficiency out of communications technologies that are possible because they still end up having the important conversations in person, and we still can't prove anything in court. What's next? Require companies to record and save all phone calls? The ultimate step will be when we don't allow people to have off-record conversations:

      CEO: "What do you think, Phil?"
      CFO: "I don't think the [FLUUUUUUUSSSSSHHHHH] shareholders will suspect a [ZIIIIP!] thing."

      Retention requirements are a huge ball-and-chain for companies without fully addressing the problem they are intended to solve.

      --
      Actually, I was trying to be Insightful, not Funny.
  3. I agree with this legislation by Anonymous Coward · · Score: 5, Interesting

    Broadly, my company "EvilCorp" has a document retention policy, that simply states

    "Don't retain anything incriminating".

    I'm glad to see, government is catching up, with trends set by industry leaders like myself !!

    God Bless America.
    God Bless Corporate Malfesence.
    Death to document retaining, Commie Linux Users!

    Also, it's worth noting.

    We've always been at war, with East Asia !

    [Seriously folks]

    Am I the only one who thinks that government should be requiring companies to move the *other* way?

    Ie, retain, *everything*... absolutely *everything*, why should email/*doc* be an acceptable domain, where, one can simply erase data under dubious circumstances ?

    Because corporation (x) wants it that way ?

    [Aside]

    Corporations are too powerful now.
    Increasingly, law is coming to reflect the interests of Corporations, instead of the interests of countries citizens.

    It's not so absurd to suggest, that.. eventually, the little guy will revolt.

    Think the French revolution, think the American revolution...

    Eventually, when the little guy gets done taking enough crap from those on top... the little guy gives the other the boot.

    In this light, Bill Gates is the King of France.

    "Let them eat Patent-Cake".. etc.

  4. routine, huh? by sugapablo · · Score: 5, Funny

    "...which would exempt parties from sanctions for electronic evidence destroyed in a 'routine operation of the party's electronic information system.'"

    So I suppose the following is perfectly acceptable:

    30 0 * * * rm -rf /var/log/incriminating/*

  5. i see nothing wrong with this proposed rule by awb131 · · Score: 5, Insightful

    For instance, under HIPAA and other state insurance regulatory laws, my company is required to maintain all documentation related to a customer file for 7 years. Right now this constitutes about 2 million pieces of paper weighing approximately 14 tons and taking up about 1500 square feet of floor space in my office for filing cabinets. We go through things once a year and toss anything that's older than 7 years.

    When we move to an electronic imaging system, everything will probably fit on to a couple of high-capacity disks. In 7 years, the cost of that amount of storage is probably going to be negligible, so there's no technical reason we couldn't keep things forever. But I'm still going to configure the document management system to toss anything older than 7 years. Why? Because 7 year old information is not useful. The only reason it's there is because of state/federal rules of evidence that require me to keep it around. It's only useful to someone who's suing me, and when those 7 years are up I'm glad to get rid of it.

    One of the things that keeps people from modernizing their filing systems is the fear of losing this "protection," of being able to throw away old information. There's a fear that if you go electronic, it's always going to be "out there" somewhere and potentially a legal threat to you, even if you've done nothing (intentionally) wrong.

    I for one support this rule. And if it seems like a good idea for our small company, imagine how it would seem if you're, say, Citibank.

    This rule is obviously not designed to support policies of "oh, we're getting sued, so I'm going to throw out this particular subset of information related to the lawsuit and try to claim it's a standard practice," because any attorney worth the price of his suit would get me thrown in jail for destroying evidence.

    --
    "There is no night so forlorn, no mood so bleak, that it cannot be infused with pleasure by tender meat..." - R.W. Apple
  6. Too Much STUFF! by Hasai · · Score: 5, Insightful

    Y'know, judging from the submitter's slant on this, I would guess he's never had to maintain multi-gigabyte document repositories bursting at the seams with obsolete documents. Nor, I suspect, had to restore and rebuild five years worth of old email databases just to satisfy some little ambulance-chaser's fishing expedition.

    Bah.

    --

    Regards;

    Hasai

  7. Submitter has no idea what he's talking about by jizmonkey · · Score: 4, Insightful
    Clearly this "law student" has never worked at a firm involved in litigation. He's going to need a lot of luck getting that paper published.

    Abuse of American electronic discovery rules is getting worse every year. Defragment your disk? That's a sanction. Copy files from an old computer to a new one? That's a sanction.

    Seriously, the legal rules need to realize that asking for documents not normally accessible is extremely expensive and opens up possibilities for extortion. ("Looks like it will cost you three million dollars to restore and examine these tapes... Why don't we just settle the case for two?") Everything the Microsoft attorney said is true.

    The judges know this, the attorneys know this, the companies know this. The submitter needs to get out in the real world and get his head out of his ass. There's not even an ideological basis for thinking the way he does. It's not like poor people benefit from these rules (who Democrats like to protect) or self-made rich people (who Republicans like to protect).

    --
    With great power comes great fan noise.
  8. Notice from Legal by ajp · · Score: 4, Funny

    Please save every business-related e-mail you receive. And you shouldn't be using work e-mail for personal purposes so please save every e-mail you receive. Thank you.

    Inbox: 41559 messages (41551 read, 8 unread)
    Saved-messages: 4154854884569842455 messages
    You are usuing 12090% of storage capacity.

  9. some of us do, you insensitive clod! by RMH101 · · Score: 4, Informative

    i work in big pharma, and for a lot of our systems we *do* have to do this. legally, we've got to keep data for clinical trials for *twenty five years* after the patentable lifetime of a drug. not only that, but we've got to figure out a way of archiving complete systems for that long. suffice to say, it's really, *really* expensive...

  10. Context of the proposed rule: what's required now by Brian+See · · Score: 4, Informative

    I think some of this discussion is lacking in context.

    First, if you destroy evidence after the lawsuit gets filed (or when you enter the grey zone of when you "reasonably anticipate litigation"), you have just committed spoliation of evidence. While this makes intuitive sense - the rule prohibits a defendant from having a "shredding party" the day after a lawsuit gets filed - it becomes problematic as definitions of what constitutes "evidence" expand.

    Active emails? Check. Files on network servers? Check.

    Backup tapes from last night's cycle? OOPS. Yes, several court decisions /orders have taken parties to task for failing to suspend routine overwriting of backup tapes. Taken to the extreme, this means that once you get sued, you can't overwrite any of your backup tapes.

    Updating databases that might result in some data (i.e., last accessed, last modified) being modified? Uhoh, better take a snapshot of that database.

    Are your server logs at issue? Uhoh, better suspend rotation of your server logs.

    Hey, when you TURN ON your desktop, aren't you overwriting some cache space and slack space, that might make recovery of deleted files impossible? Guess what? If the other side wants to do a forensic examination of your machines, you can't even continue using them without taking a bit-by-bit image.

    And by the way -- if you miss any bit of this data, you get sanctioned. Monetary sanctions, or an adverse inference ("we don't know what was on that tape that was destroyed, but you can ASSUME it was bad!"), or even a default judgment. Yes, electronic discovery can turn into a game of "gotcha".

    Think how expensive this is for a small shop with just a handful of machines. And then think what's involved for a nationwide company with, say, 80 far-flung locations and company databases.

    See the problem?

    The "safe harbor" to Rule 37 says that you don't sanctioned for failure to preserve information lost from ROUTINE operation of a system UNLESS THE LOSS WAS INTENTIONAL OR RECKLESS. The "reckless" hole is very large, admittedly. But the rule attempts to bring some sanity to some of the broad-reaching data preservation games being played today.

    Also, note that a court can order a party to take steps above and beyond what the proposed Rule 37 requires.