Reader Bins (Legacy)


The procedures described in this article follow a legacy process. Refer to this article only for general concepts; follow the procedures described in the Workflows article when creating new bins within workflows. Workflows created using the legacy process cannot be managed using the Workflows tool and vice versa.

Reader Bins illustrate your reading workflow within Slate. Each Reader Bin will contain applications that are in a distinct stage of your reading process.

Take the extra time to ask and answer your reading process questions and settle on the desired behavior for each bin in your structure to streamline the bin configuration process.

  Custom Permissions?

Do not get distracted with creating bin permissions when building your Reader resources. Focus on developing a clear and meaningful bin structure and save the custom permission work for later.

Make a Plan

Use sticky notes to imagine and strategize your bin structure with your office. Design a bin structure that is simple and useful for your basic application reading process. Do not design a bin structure that reflects reading processes that only happen occasionally (e.g., a Dean Special Hold bin).

For example, a school that has a Slate-hosted application may develop a Bin structure like this:


  Best Practice

Develop a reader workflow that moves in the right direction. While applications might skip future bins (e.g., an application moves from the Read 1 bin directly to the Deny bin), your applications should never move backwards in your bin flow. For example, a sample application may take the following Reader bin path:


No Post-Decision Bins!

The Application Reader is for your reading process exclusively! Concluding your bin structure with clear and distinct decision bins will ensure a smooth decision release process.

Any post-decision activities are actions that happen after your reading process has ended and will employ resources within the student record view.

Process & Strategy

Once you have developed your bin structure on paper, move sequentially through your structure and determine the desired functionality for each specific bin. For example:


Common Questions Common Answers
1. When the review is complete, where should the application go next?  Admit or Deny or Waitlist 
2. Should there be a default next bin? No
3. Allow multiple readers to have the same application in their queues simultaneously? No, this bin should only allow an application to be in one reader’s queue at a time.
4. Warn readers if they have previously read an application? No Warning
5. Should the review be a blind read? No, the previous reviewers should be visible.
6. Should this bin be locked? No, readers should be allowed to manually add an application to their own queue.
7. Should this review be anonymous? No, readers should be allowed to see the applicant’s name.
8. Should queue notification reminders be emailed to readers when applications in this bin are in their queues? No

  How Should I Name and Order my Bins?

Use your sticky notes to make it easy to configure the name, column, and order number for a bin. Also, remember to leave gaps in your order to simplify reader bin creation in the future.


Make a Reader Bin

  1. Click Database in the top navigation bar and select Reader Bins.
  2. Click Insert.
  3. Enter the following User configurations in the popup window:
    • Base - Select Applications as your Base.
    • Active - Make your bin Active.
    • Order - Set a logical order number for your bin.
    • Column - Enter the column name. Remember: bins in the same column must share the same column name.
    • Name - Give your bin a name.

Reader Bin Settings

Bin Behavior Slate Default Settings Other Option
Next Bin All bins appear as possible destinations when a reader submits a reader review form in that bin Restrict the list of next available bins when a reader submits a reader review form in that bin
Default Bin The Next Bin drop down menu has nothing selected Pre-populate the Next Bin drop down menu
Checkout Mode An application may only be in one reader’s queue at a time Allow an application to be in multiple queues at the same time
Single Read Do not warn readers if they have already read an application Warn readers if they have already read an application
Blind Read Show readers who have reviewed an application Do not show previous readers
Anonymous Read Show the applicant's name Do not show the applicant's name
Locked Readers may manually add an application to their queues Readers may not manually add applications to their queues
Processing Readers may reassign materials when reading applications in that bin Readers may not reassign materials when reading applications in that bin
Annotations Privacy Readers may see all annotations Readers may see only their own annotations
Queue Notification See System Emails for more instructions 
Was this article helpful?
19 out of 27 found this helpful