From 94dcc33787a173917a0af7ae022fced8d0306a0e Mon Sep 17 00:00:00 2001 From: glipstein Date: Wed, 24 Apr 2024 16:44:11 -0600 Subject: [PATCH] Update checklist.yml --- deon/assets/checklist.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/deon/assets/checklist.yml b/deon/assets/checklist.yml index a1aff3c..f21abe8 100644 --- a/deon/assets/checklist.yml +++ b/deon/assets/checklist.yml @@ -61,14 +61,14 @@ sections: line_summary: Explainability line: Can we explain in understandable terms a decision the model made in cases where a justification is needed? - line_id: D.5 - line_summary: Communicate bias + line_summary: Communicate limitations line: Have we communicated the shortcomings, limitations, and biases of the model to relevant stakeholders in ways that can be generally understood? - title: Deployment section_id: E lines: - line_id: E.1 line_summary: Monitoring and evaluation - line: How are we planning to monitor the model and its impacts after it is deployed (e.g., performance monitoring, regular audit of sample predictions, human review of high-stakes decisions, reviewing downstream impacts of errors or low-confidence decisions, testing for concept drift)? + line: Do we have a clear plan to monitor the model and its impacts after it is deployed (e.g., performance monitoring, regular audit of sample predictions, human review of high-stakes decisions, reviewing downstream impacts of errors or low-confidence decisions, testing for concept drift)? - line_id: E.2 line_summary: Redress line: Have we discussed with our organization a plan for response if users are harmed by the results (e.g., how does the data science team evaluate these cases and update analysis and models to prevent future harm)?