Submitting a track is a small moment; the days after are where anxiety lives. This article walks the full lifecycle of a paid track submission on TrackGiant so you know what to expect, what you control, and what triggers a refund.
1. Checkout and order creation
When you pay, the platform creates a submission tied to:
- Your track (title, audio link, optional context you provided).
- The curator you selected.
- The price and turnaround band shown on their profile.
If you used batch submissions, one checkout creates parallel submissions — each curator has their own clock and status.
2. Pending: waiting for acceptance
After payment, the submission is usually pending until the curator accepts it into their working queue. Curators can decline paths that are a bad fit; if that happens, the product flow handles refund or credit according to the rules in place at checkout time.
What you should do: nothing spammy. The curator sees your order in their inbox. Use the message field at submission time to front-load context — not to bump the thread hourly.
3. Accepted: the 7-day review window starts
Once accepted, the curator has seven days to complete the review. That window exists so artists are not left in limbo indefinitely.
- If they deliver in time → you get feedback and the submission moves to completed.
- If time expires → the submission is treated as expired and the artist is refunded automatically for that path.
Curators: operational detail in manage your inbox.
4. In progress: what “in progress” means for you
While the curator is listening, you might see an in-progress state in your dashboard. You do not need to message unless they ask a clarifying question through the product.
Duplicate guard: you cannot submit the same track to the same curator again within 24 hours — the platform blocks duplicate spam.
5. Completed: reading the feedback
When the review is done, read it twice:
- First pass — absorb the overall judgment without defending your mix.
- Second pass — extract action items (arrangement, vocal comp, low-end, intro length, etc.).
If the curator offers services that extend the conversation (consultation, deeper notes), you can order those separately — that is often cheaper than guessing from one review.
6. Expired: refunds and resubmission limits
If your submission expires because the curator did not finish in the window:
- You receive a refund for that submission.
- You may resubmit the same track to that curator again, but the platform limits how many times you can retry the same curator + track after failures (up to three attempts total for that combination).
After you hit the limit, stop brute-forcing the same path. Either pick a different curator, change the master, or use a service order if the curator offers a better format for your problem.
7. Promo codes and pricing quirks
At checkout, promo codes may apply to single or batch flows when the product exposes a field. Codes are percentage discounts on the subtotal; stackability and eligibility follow whatever the checkout UI allows at the time.
8. Parallel paths: batches and parties
- Batch: each curator’s submission still follows the same accept → window → complete/expire logic independently.
- Listening parties / Live Sessions: different product surface — see how listening parties work. Do not confuse party queue refunds with track submission refunds.
Mental model
You paid for time and taste inside a bounded SLA. The platform enforces the SLA with the 7-day window and automatic refunds on failure. Your job is to choose curators well and write submissions that make the first listen efficient — see write a submission that gets reviewed.
Once you internalize the timeline, the emotional part gets easier: either you get notes, or you get money back and a lesson about capacity. Both outcomes are legible.