---
title: "Comment by Tim Zinin on \"Design the review queue before you train the model\" | Hashnode"
description: "The queue design feels concrete when you track exception rate alongside minutes per case. What would you capture in the review record to distinguish model uncer"
url: "https://hashnode.com/posts/design-the-review-queue-before-you-train-the-model/6afefc6a97fac991be947b92/comment/6aff05701cf55b747f672bfa"
---

[Discussion](https://hashnode.com/posts/design-the-review-queue-before-you-train-the-model/6afefc6a97fac991be947b92)

Comment [Design the review queue before you train the model](https://hashnode.com/posts/design-the-review-queue-before-you-train-the-model/6afefc6a97fac991be947b92)

[Tim Zinin](https://hashnode.com/@timzinin)

[1d ago](https://hashnode.com/posts/design-the-review-queue-before-you-train-the-model/6afefc6a97fac991be947b92/comment/6aff05701cf55b747f672bfa)

The queue design feels concrete when you track exception rate alongside minutes per case. What would you capture in the review record to distinguish model uncertainty from a missing source document?
