release triage lanes

Triage a Release Package Before It Gets Rejected — Free

Paste the release assets you hold, and read which are missing, which are wrong and which are fine, before the distributor does.

The proof surface

Distributors reject deliveries on the same handful of items every time, and the rejection arrives late. Sorting the reader's own assets into lanes moves the same information ahead of the deadline.

Inputyour own asset list with the state of each item

Rare devicesorts the reader's own asset list into lanes by what blocks distribution now versus what blocks it later

Output artifactthree lanes with each asset filed and the reason it sits there

Cost$0 · local-first · one free run · samples labelled

Sample, not your facts: Sample: master delivered, artwork not started at 3000x3000, three of five ISRCs assigned, three of four writers signed, metadata unproofed, 14 days to the distributor deadline — four concrete points across four types.

Why the flat version breaks

Uploading and hoping

A rejection restarts the review queue, and the days lost are usually the ones the release window needed.

Unsigned splits

A missing signature from one writer is the most common reason a delivery stalls, and it is also the slowest to fix at short notice.

Artwork at the wrong size

Artwork that is not square or below the minimum resolution is rejected automatically, and re-exporting takes minutes once it is spotted.

How to work the release triage lanes

List the assets

One per line with what you actually hold and what is still outstanding.

Set the deadline

Days until the distributor needs the files, so the lanes carry a clock.

Read the lanes

Assets land in blocked, fixable or ready, with the reason printed on each card.

Work the blocked lane

Fix the items nobody else can fix for you, then re-run before uploading.

What the lanes replace

Question	Before	On the triage board
What will be rejected	find out after uploading	blocked lane named before delivery
What can be fixed today	no idea where to start	fixable lane sorted by what you can do in an hour
What is already done	recheck everything	ready lane cleared and left alone

The lanes sort the assets you describe; the distributor's own requirements list is the authority and may differ.

Run it on the samples, right here

FIRST-LOAD

Data note: Everything runs in this browser tab on the release triage lanes: your asset list and delivery dates stays on this device, nothing is uploaded, and the reading is rebuilt only when you press run.

Go deeper: the companion app files the same reading as a triage clipboard with three lanes

The article demo above runs without limits. The companion app keeps a local history, exports the rows as CSV, prints the ready-to-mail packet, and holds your drafts on this device — one free run, then $ 7 one-time for the layer that keeps filing.

The three lanes and the blocked list are free. The paid layer keeps the asset register and prints the delivery checklist for the session.

Open the release asset triage lanes companion

Boundary

This release triage lanes works only on the asset list and delivery dates you paste you paste. It does not guarantee acceptance by a distributor, does not upload or deliver your files, and does not advise on rights or contracts. The figures describe what you supplied, not what is true in the world. Confirm anything you plan to act on with your distributor's delivery team, and a music lawyer for anything touching splits or rights before you rely on it.

What this is built on

Every figure comes from the asset list and delivery dates you paste you paste; nothing is looked up, scraped or asserted as verified.
Method: each asset line is matched against the required delivery items you supplied; unmatched items are filed as blocked
Sample values are labelled samples — illustrative by design, not your data and not a quotation of any organisation's policy.

Before: the reader uploaded what they had. After: they can see three assets blocking distribution and one that can be fixed in an hour.