# Starting a run

> Every field on the Start a run panel, what it does, and what happens the moment you click Start sourcing.

A run is one ask sourced on every channel at once. Start one from the **AI sourcing** page; the panel there has three parts, and **Runs** beside it lists every run on the account.

## The role

A run is for one of your [roles](/documentation/search/roles): what you are hiring for, and where.

- **Role** (required). Choose one from the list. If it is not there yet, **Add a role** writes one without leaving the run. Tenure's database reaches only people whose profession and specialty on record are the role's. The role's profession also decides how the message greets people: physicians are addressed as "Dr. {LASTNAME}", everyone else by first name.
- **Location**. Starts as the role's own location. Change it for this run if you like: start typing a city or a ZIP code and pick it from the list, as in **Near** on the Sourcing page. Leave it empty for anywhere. If Tenure cannot find a location you typed without picking, it says so and nothing starts.
- **Distance**. Within 5, 10, 25, 50 or 100 miles, 50 to begin with. The run reaches people who live within that distance of the location, even across a state line, and those nearer rank higher. The run page shows it, as in "Within 50 miles of Abilene, TX".
- **Details about the ideal candidate** (optional). Anything for this run alone, such as a credential or experience to look for. The role's pay, schedule and description go with the run on their own.

## Remote and hybrid roles

A remote role has no location or distance. Its run looks for clinicians by the states they are licensed in, wherever they live: a physician in Ohio with a Florida licence is found by a remote run for Florida, and would not be by an on-site run in Tampa.

The licences a run matches on are the ones a clinician's CV lists. Tenure has not checked them with a state board, so confirm a licence when someone replies.

For a hybrid role, the location is the site they come in to.

## Where

Tenure's database is always on. Each connected job board is on by default, with a field for the most people to contact on that board this run. See [Channels and limits](/documentation/sourcing/channels-and-limits).

## The message

The subject line and message each person receives. Both start filled in from the role ("Hiring Urgent Care Physician - Abilene, TX"), and you can edit them, ask Tenure for a draft, and preview them per channel. See [Writing the message](/documentation/sourcing/messages).

## What happens when you start

1. Tenure's database is searched for people who fit: the role's profession and specialty, within the distance of the location. It leaves out anyone on your do-not-contact list, anyone already in your contact pool, and anyone messaged in the last 7 days.
2. Messages begin going out from the database at Tenure's daily pace.
3. Each job board pass is queued. Tenure's AI-powered sourcing technology starts it and works it at the pace that board allows.
4. The run page opens, with a card per channel. Every reply lands there and in your contacts.

If something is missing when you click Start, a message tells you what and moves you to that field.