Custom Discovery Queue Screen Guide

This guide explains the main parts of the Custom Discovery Queue and how to use the page to manage custom application discovery work.

**Suggested screenshot title:** Custom Discovery Queue Overview

Screen sections

1. Page header

The header identifies the queue and provides context that this page is used for custom application intake and discovery progression.

2. Summary cards

Summary cards may show:

• total requests
• pending
• in progress
• needs info
• completed

These make it easy to understand current backlog and workflow state.

3. Search

Search allows users to quickly find requests by title, notes, status, or other text-based information.

4. Discovery request cards or rows

Each request entry may show:

• title
• notes
• status
• priority
• assignment
• activity
• linked application if conversion already happened

5. Status actions

Depending on role, users may be able to move a request through statuses such as pending, in progress, needs info, completed, or rejected.

6. Assignment controls

Assignment controls help users route the request to the correct owner.

7. Activity and attachments

Where shown, activity and attachment sections allow collaboration and evidence capture directly on the request.

8. Conversion action

If the request is ready, users may be able to convert it into a real application.

How to use this screen

A common workflow is:

1. review summary counts 2. search or filter to the needed request 3. review notes and activity 4. assign or update status 5. convert to application when ready

Best practice

Use this page to manage uncertainty and discovery, not to rush directly into application creation without context.