Editing Records management (section)

=== Defensible solutions ===
A ''defensible solution'' is one that can be supported with clearly documented policies, processes and procedures that drive how and why work is performed, as well as one that has clearly documented proof of behavior patterns, proving that an organization follows such documented constraints to the best of their ability.<ref name="Defensible_Solutions">{{cite book|url=http://www.wiley.com/WileyCDA/WileyTitle/productCd-1118027248.html|title=Performance-Based Certification: How to Design a Valid, Defensible, Cost-Effective Program|author=Hale, Judith|date=December 2011|publisher=John Wiley & Sons, Inc.|isbn=978-1-118-02724-0|archive-url=https://web.archive.org/web/20130927151031/http://www.wiley.com/WileyCDA/WileyTitle/productCd-1118027248.html|archive-date=2013-09-27|url-status=live}}</ref>

While ''defensibility'' applies to all aspects of records life cycle, it is considered most important in the context of records destruction, where it is known as "''defensible disposition''" or "''defensible destruction''", and helps an organization explicitly justify and prove things like who destroys records, why they destroy them, how they destroy them, when they destroy them, and where they destroy them.<ref name="Defensible_Disposition">{{cite journal|author=Hulme, Tony|date=June 2012|title=Information Governance: Sharing the IBM approach|journal=Business Information Review|volume=29|issue=2|pages=99–104|doi=10.1177/0266382112449221|s2cid=154276859}}</ref>