> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/interview-studies/what-are-interview-studies-in-dscout/how-much-should-an-interview-study-pay.md).
# How much should an interview study pay?
{% hint style="info" %}
**A note on niche recruits:** The following guidance does not apply when recruiting from our Partner Panels. Partner Panels offer access to niche, B2B recruits whose expertise is hard to source. Their schedules are tight, and the compensation you offer should reflect that. Expect to pay somewhere between $150 and $600 for just 15 to 30 minutes with a C-suite exec, clinician, etc.
{% endhint %}
Participating in interview studies involves the extra effort required to schedule a session and sit down for a one-on-one conversation. So, it’s a good idea to offer a slightly higher incentive for these missions. Consider the intended length of your sessions and go from there:
| Session length | Baseline incentive |
| -------------- | ------------------ |
| 30 minutes | $50 |
| 60 minutes | $75-100 |
{% hint style="success" %}
**Tip:** Recruiting participants with very specific experience or within a tight turnaround period is typically easier with a higher incentive.
{% endhint %}
We typically kick off payments once all sessions in an interview mission are complete. (No action in the platform automatically triggers payments, so don’t forget to close out your mission under the **Setup** tab, and ping your dedicated research advisor with a list of participants who are ready to be paid out).
Will I have to pay out participants I over-recruited for my interview study?
No. However, we do expect you to provide enough time slots for all invited participants. You can read about this in our [Scout Experience Standards](https://dscout.com/legal/scout-experience-standards). It’s good to note as well that over-recruiting from the start isn’t always necessary. If you have one or a few unresponsive participants, you can always [close them out](/interview-studies/manage-an-interview-study/close-a-participant-in-an-interview-study.md) of the mission and invite new participants in their place—even after you’ve launched your mission.
If you anticipate needing to over-recruit participants due to timing constraints, we’d recommend only starting with a few extra participants and including copy such as this in your mission instructions to help ensure a smooth participant experience: **"We have a limited number of session slots in this mission, so not everyone invited will be able to participate. Accept your session as soon as you can to save your seat!"**
Once your mission wraps up, consider sending a message to any unscheduled participants thanking them for their interest before closing it out.
## No-shows and cancellations
If a moderator is a no-show, or is at least 10 minutes late to a session and a participant is no longer able to complete the interview, we’d recommend offering your participant partial compensation for their time.
Need to make some last-minute changes and cancel an upcoming session? Be sure to send a message to your participant letting them know in advance. You can cancel their session under the **Manage** or **Schedule** tabs. *If you have to change plans within 24 hours of a scheduled session, we’d recommend paying them partial compensation for their time.*
If a participant is a no-show, or is at least 10 minutes late to a session and a moderator is no longer able to participate, you will not be responsible for compensating the participant.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.dscout.com/interview-studies/what-are-interview-studies-in-dscout/how-much-should-an-interview-study-pay.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.