> ## Documentation Index > Fetch the complete documentation index at: https://docs.beatpass.ca/llms.txt > Use this file to discover all available pages before exploring further. # Beat Requests > Use Beat Requests to describe the sound you need, spend tokens on a 24, 48, or 72-hour request window, and receive matching beat submissions from BeatPass producers. Beat Requests let you post a brief for the sound you need and receive beat submissions from producers on BeatPass. You choose how long the request stays live, and BeatPass uses tokens to control how many requests you can create each month. Beat Requests let producers send tracks from their existing BeatPass catalog, or upload new beats and auto-submit them. They are useful for discovering strong matches quickly. For the legal summary covering request tokens, producer submissions, custom beat discussions, delivery scope, and disputes, see [Custom Beat and Beat Request Terms](/help/legal/custom-beat-request-terms). ## Reference tracks guide fit. They do not replace licensing. A reference track helps producers understand direction, mood, tempo, arrangement, and energy. It should not be used to copy another producer's beat, avoid licensing an available beat, or recreate protected elements from a song. If you already found the exact beat you want and it is available, license that beat from the original producer. Use Beat Requests when you need a similar direction, a custom fit, or a beat that matches your project without copying the original. *** ## How It Works Open **Beat Requests** and click **Submit Request**. Add a description, a required **Reference Track**, and any optional details that help producers understand your sound. Pick a request window of **24**, **48**, or **72 hours**. Those durations cost **1**, **2**, or **3** tokens. Verified producers are notified automatically when a new request is posted. Other eligible producers can still browse the public request feed and submit if they find a good match. Producers send BeatPass-hosted tracks from their catalog. Each submission increases the request's submission count and can trigger a notification based on your notification settings. You can track active and expired requests from **My Requests** on the **Beat Requests** page or from **Library** → **Beat requests** on the dedicated **My Beat Requests** page. *** ## Feature Overview Learn how to post a beat request and what information to include. How the token system works and how many requests you can make. Details on genre, BPM, key, mood, and reference tracks. How producers can browse and submit beats to requests. What happens when producers send you beats. View, track, and delete your requests. *** ## Quick Facts 24 / 48 / 72 hrs Longer windows cost more tokens but give producers more time to respond 1 / 2 / 3 tokens Matches the duration tier you select 1 token Eligible expired requests can be renewed within 30 days Up to 5 per producer A single producer can send up to five different tracks to one request Required Helps producers understand your vision 500 characters Be specific about what you need *** ## Who Can Use Beat Requests? ### Creating Requests Any signed-in BeatPass user can create requests as long as they still have tokens available for the month. ### Sending Beats as a Producer To submit beats to requests, you need: * A BeatPass **producer profile** * The ability to upload tracks to BeatPass * At least one BeatPass-hosted track that you own or collaborate on Verified producers are the ones BeatPass notifies automatically about new requests. Non-verified producers can still browse the public feed and submit when they have eligible tracks. *** ## What You Can Review Today BeatPass currently gives you three main ways to track responses: * Submission notifications * Submission counts on each request card * Producer messages and submitted track pages BeatPass does not currently include a dedicated request-details submissions inbox. If you want the fastest path back to a submitted beat, open it from the notification when it arrives. *** ## Request Lifecycle 1. **Created** — Your request is posted and visible to producers. The token cost is consumed immediately. 2. **Active** — Producers can submit beats for the duration you selected (24, 48, or 72 hours). 3. **Expired** — The time window has closed and new submissions stop automatically. 4. **Renewed** — Eligible expired requests can be renewed for **1 token** within 30 days of expiring, which reactivates the request for another window matching the original duration. Requests stay open for the full time you selected. They do not close early just because you already received submissions. *** ## Best Practices ### For Requesters * **Be specific** — The more detail you provide, the better matches you'll receive * **Include a reference track** — This helps producers understand your vision * **Keep notifications on** — Notifications are currently the main entry point into submitted beats * **Avoid deleting too early** — Deleting removes the request from the public feed and from the current request-management flow ### For Producers * **Read carefully** — Make sure your beat actually matches what's requested * **Submit your best work** — Quality submissions lead to connections * **Be timely** — Requests expire after 24, 48, or 72 hours depending on the tier selected *** ## Related Topics See how many tokens are included with each plan. Connect with producers who submit to your requests. Legal summary for tokens, submissions, and custom beat discussions. Review the standard license terms before you release a finished song. Understand the human-made catalog standard for submitted beats. See how reference-guided discovery fits into BeatPass's proof system. ## Need Help? If you have questions or need assistance, contact the support team at [**contact@beatpass.ca**](mailto:contact@beatpass.ca) or visit the [Contact Support](/help/contact-support) page.