Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /home2/redcavel/public_html/wp-content/plugins/revslider/includes/operations.class.php on line 2364

Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /home2/redcavel/public_html/wp-content/plugins/revslider/includes/operations.class.php on line 2368

Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /home2/redcavel/public_html/wp-content/plugins/revslider/includes/output.class.php on line 3169

Warning: Cannot modify header information - headers already sent by (output started at /home2/redcavel/public_html/wp-content/plugins/revslider/includes/operations.class.php:2364) in /home2/redcavel/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1648

Warning: Cannot modify header information - headers already sent by (output started at /home2/redcavel/public_html/wp-content/plugins/revslider/includes/operations.class.php:2364) in /home2/redcavel/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1648

Warning: Cannot modify header information - headers already sent by (output started at /home2/redcavel/public_html/wp-content/plugins/revslider/includes/operations.class.php:2364) in /home2/redcavel/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1648

Warning: Cannot modify header information - headers already sent by (output started at /home2/redcavel/public_html/wp-content/plugins/revslider/includes/operations.class.php:2364) in /home2/redcavel/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1648

Warning: Cannot modify header information - headers already sent by (output started at /home2/redcavel/public_html/wp-content/plugins/revslider/includes/operations.class.php:2364) in /home2/redcavel/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1648

Warning: Cannot modify header information - headers already sent by (output started at /home2/redcavel/public_html/wp-content/plugins/revslider/includes/operations.class.php:2364) in /home2/redcavel/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1648

Warning: Cannot modify header information - headers already sent by (output started at /home2/redcavel/public_html/wp-content/plugins/revslider/includes/operations.class.php:2364) in /home2/redcavel/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1648

Warning: Cannot modify header information - headers already sent by (output started at /home2/redcavel/public_html/wp-content/plugins/revslider/includes/operations.class.php:2364) in /home2/redcavel/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1648
{"id":1420,"date":"2017-01-03T02:44:21","date_gmt":"2017-01-03T02:44:21","guid":{"rendered":"\/\/redcavelegal.com\/?p=1420"},"modified":"2017-01-03T02:44:21","modified_gmt":"2017-01-03T02:44:21","slug":"dual-calendar-system-is-a-bad-idea","status":"publish","type":"post","link":"https:\/\/redcavelegal.com\/2017\/01\/03\/dual-calendar-system-is-a-bad-idea\/","title":{"rendered":"Dual Threat: Why Keeping Two Calendars is a Terrible Idea"},"content":{"rendered":"

I find it strange that many malpractice insurance applications continue to ask lawyers whether they maintain a \u2018dual calendar system\u2019 — because it is, and always has been, a terrible idea.<\/p>\n

Keeping more than one calendar invites transposition errors.\u00a0 Plus, it\u2019s more likely that any one person will fail to do two<\/em> things, than any one person will fail to do one<\/em> thing.\u00a0 (Enter a meeting twice?\u00a0 The chances of success go down from it happening once.)\u00a0 Then there\u2019s the whole \u2018too many chefs\u2019 thing<\/a>.\u00a0 And, though it won\u2019t matter for ethics purposes, under the dual calendar system, it\u2019s too easy for lawyers to pin scheduling mistakes on staff.<\/p>\n

The justification for a dual calendar system made some sense prior to the internet age.\u00a0 There wasn\u2019t really a better solution.\u00a0 (I imagine Bob Cratchit keeping two sets of books for Ebenezer Scrooge<\/a>.)\u00a0 Now, there is.<\/p>\n

In 2017 (wow – that was weird), the better strategy by far is to maintain one<\/em> calendar.\u00a0 Of course, that doesn\u2019t mean that you access<\/em> only one calendar.\u00a0 The rise of cloud computing<\/a>, including the modern facility of integrating between systems, makes it possible to link several calendars.\u00a0 Enter appointments and tasks into any of those calendars, and the events and responsibilities will populate to every other calendar you\u2019ve linked to it.\u00a0 In terms of streamlining that process, a preferred workflow would be to utilize your law practice management system<\/a> calendar as your primary entry point, and sync it to your email system,\u00a0 which method would also allow you access to each of those systems\u2019 mobile applications.<\/p>\n

Create once, and populate everywhere . . . Just don\u2019t get a God complex<\/a> about your newfound power.<\/p>\n

And, if you don\u2019t think calendar management is essential to law practice management, I can tell you that the number of ethics and malpractice claims that arise out of missed deadlines and appointments is staggering.<\/p>\n

. . .<\/p>\n

Liner Notes<\/em><\/p>\n

That\u2019s some ill communication<\/a> right there.<\/p>\n

\u2018Sabotage<\/a>\u2019 by Beastie Boys<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

I find it strange that many malpractice insurance applications continue to ask lawyers whether they maintain a \u2018dual calendar system\u2019 — because it is, and always has been, a terrible idea. Keeping more than one calendar invites transposition errors.\u00a0 Plus, it\u2019s more likely that any one person will fail to do two things, than any<\/p>\n","protected":false},"author":1,"featured_media":1421,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spay_email":""},"categories":[49,46],"tags":[124,119,116,121,117,120,123,68,122,75,101,125,118],"jetpack_featured_media_url":"https:\/\/redcavelegal.com\/wp-content\/uploads\/2017\/01\/Calendar.jpg","_links":{"self":[{"href":"https:\/\/redcavelegal.com\/wp-json\/wp\/v2\/posts\/1420"}],"collection":[{"href":"https:\/\/redcavelegal.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/redcavelegal.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/redcavelegal.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/redcavelegal.com\/wp-json\/wp\/v2\/comments?post=1420"}],"version-history":[{"count":1,"href":"https:\/\/redcavelegal.com\/wp-json\/wp\/v2\/posts\/1420\/revisions"}],"predecessor-version":[{"id":1422,"href":"https:\/\/redcavelegal.com\/wp-json\/wp\/v2\/posts\/1420\/revisions\/1422"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/redcavelegal.com\/wp-json\/wp\/v2\/media\/1421"}],"wp:attachment":[{"href":"https:\/\/redcavelegal.com\/wp-json\/wp\/v2\/media?parent=1420"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/redcavelegal.com\/wp-json\/wp\/v2\/categories?post=1420"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/redcavelegal.com\/wp-json\/wp\/v2\/tags?post=1420"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}