A single recording can be connected to several dates, and those dates do not describe the same event.

A song may be written in one year, recorded in another, registered with a rights organisation later, mentioned publicly after that and leaked long before it receives an official release. In some cases, only one of those dates is known. In others, several can be documented.

Problems begin when one date is used as a substitute for another. A file that circulated in 2024 was not necessarily recorded in 2024. A publishing registration does not prove that vocals had already been recorded. An official release date does not tell us when an earlier demo was made.

EverySongBy keeps these events separate. Where reliable information exists, catalogue entries can show a recording date or period, a first public appearance, a reported circulation or leak date and a later official release date. When a date cannot be supported, the catalogue says so rather than guessing.

Why date labels matter

Dates shape the history attached to a recording. They can connect a song to an album era, a writing session, a collaborator, an abandoned project or a later revival.

An incorrect date can create a false story. It may suggest that:

Clear date labels make the catalogue more useful without pretending that every session can be reconstructed precisely.

The main dates used in a recording history

Several dates may be relevant to one song. Each answers a different question.

Writing date

The writing date describes when the composition was created or developed.

This may be supported by:

A writing date does not prove that a finished recording was made on the same day. A song can be written before vocals are recorded, rewritten across several sessions or registered before a final performance exists.

When only the writing period is known, the catalogue should describe it as writing or session context rather than presenting it as an exact recording date.

Recording date

The recording date describes when the relevant vocal or instrumental performance was captured.

This is often the most useful date for distinguishing demos, rerecordings and alternate versions. It can show whether two recordings came from the same session or whether an artist returned to the song years later.

Reliable evidence may include:

Exact recording dates are uncommon for many unreleased songs. A supported year, period or project era is often more honest than a precise day copied from an uncertain source.

Registration date

A registration date is the date a composition or recording was entered into a publishing, copyright or rights-management database.

Registrations can help establish that a title existed by a certain point. They may also identify writers, publishers, alternate titles or work numbers.

However, a registration date is not automatically:

Some works are registered long after they were written. Others are registered before recording begins. A composition can also be registered without the named artist ever recording it.

First public mention

The first public mention is the earliest supported occasion on which a title or recording was discussed openly.

This may come from:

A public mention can confirm that a title was known, but it may not confirm that a complete recording existed. The wording should reflect whether the source refers to a song, a session, a planned track or finished audio.

Snippet or preview date

A snippet date records when a short piece of audio became publicly available or was heard in a documented setting.

The source might be:

A snippet establishes that some audio was present at that time. It does not necessarily prove that a complete recording existed, and it should not be described as a full leak unless the complete track was also known to circulate.

Circulation or leak date

A circulation or leak date describes when unauthorised audio was first reported as moving beyond its private or intended audience.

The term leak date can sound more precise than the evidence allows. In practice, researchers may only know:

The earliest widely noticed date may not be the true first leak. Files can circulate privately for months or years before they become publicly documented.

For that reason, EverySongBy uses wording such as Reported leakReported in circulation or First publicly documented circulation when the exact origin cannot be proved.

Official release date

The official release date is when the recording received an authorised public release from the artist, label or rights holder.

This may be:

An official release can happen years after the recording was made or after unauthorised copies circulated. The earlier demo or leaked version may still deserve a separate entry when it contains a different performance, title, arrangement, lyric or vocal.

One recording can need several dates

A single catalogue entry may legitimately show more than one date.

For example:

Those dates describe four different stages in the recording’s history. Reducing the entry to 2024 would make the song look newly recorded at the time of the leak. Reducing it to 2026 would erase the earlier circulation history.

The About this recording text can explain how the dates relate to one another and whether the officially released version is the same master or a later version.

Why a leak date is not a recording date

This is one of the most common mistakes in unreleased-song lists.

A file appearing online tells us when that file became publicly known, not when the performance was recorded. The audio may come from:

Unless the session date is independently supported, the catalogue should not copy the leak year into the recording-year field.

Where no recording date is known, the entry can show the reported circulation date while stating that the recording period remains unconfirmed.

Why a release date is not a recording date

Official releases are frequently recorded well before the public receives them.

Delays may result from:

The release year is still important, but it should not be used to place the recording inside an artist’s creative timeline when stronger session information shows that it belongs to an earlier period.

Exact dates, years and recording periods

Dates should be displayed at the level of precision supported by the evidence.

Exact date

Use an exact day only when a reliable source supports it. This is most common for official releases and sometimes possible for documented sessions, broadcasts or public previews.

Year only

Use a year when the recording can be placed reliably within that calendar year but the exact day or month is not known.

Recording period

Use a period such as 2011–2012during the album sessions or early 2010s when the evidence supports a range rather than one precise year.

Approximate date

Use wording such as circa 2013 only when there is a reasonable basis for the estimate. Approximate language should not be added merely because a nearby project seems plausible.

Unknown date

Use Unknown date or Recording date not confirmed when no supported chronology is available.

An unknown date is more accurate than a guessed one.

How year ranges should be interpreted

A range does not mean the song was continuously recorded across every year shown. It means the available evidence places the session somewhere within that period.

Ranges can be useful when:

The accompanying background should explain what the range refers to whenever possible.

File dates are weak evidence

A date embedded in a circulating filename or file properties can be useful, but it is rarely conclusive.

File metadata can change when audio is:

A filename such as Song Title 2017 Final may reflect a genuine session label, a later guess or somebody’s attempt to organise files.

EverySongBy does not treat filenames or file timestamps as definitive without supporting context.

Community documentation and first-known dates

Fan-maintained databases and community archives can be valuable for identifying when a title, snippet or file first became widely discussed.

They are particularly useful for:

However, community dates should be labelled as community documentation and checked against earlier evidence where possible. A database’s added date may describe when its own page was created, not when the recording first circulated.

Regional release dates

A song can have more than one authorised release date.

For example, it may be:

The catalogue should use the earliest relevant authorised public release for the recording, while the background can mention important regional or format differences.

Popularity information should also specify the market being discussed. A UK chart date, a US chart entry and a worldwide streaming revival are different forms of context.

First release versus later rerelease

A rerelease does not reset the recording’s original release date.

The same master may later appear on:

These later appearances can be historically important, but they do not make the underlying recording new.

A newly performed rerecording, however, receives its own recording date and release history.

When an unreleased song becomes official

An unreleased recording may later receive an authorised release.

When that happens, the catalogue should determine whether the official release is:

The entry can move into the official section when appropriate, but its earlier history should not disappear.

A separate demo or circulating version can remain in the catalogue when it contains a meaningfully different performance.

Demos intended for other artists

Songwriter demos often involve several dates that are easy to confuse.

A demo can have:

The final performer’s release date does not date the songwriter’s demo. The two recordings should retain their own chronologies.

Where supported, the demo entry can show the intended performer and name the later released version inside About this recording.

Posthumous and archival releases

Posthumous releases may combine material from several periods.

A final release can include:

The release date describes when the finished product became public. It does not replace the date or period of the artist’s original vocal.

The catalogue should explain both stages when the information is available.

Manipulated and artificially generated audio

A claimed leak date means little if the recording itself is not authentic.

Audio can be:

A recent upload of manipulated audio should not become a new catalogue entry simply because it has a clear online date.

Authenticity must be considered before chronology.

How dates are shown in the catalogue

The date area is designed to show what each date represents rather than presenting one unexplained year.

Depending on the evidence, an entry may display:

Not every entry needs every field. The catalogue shows only the dates that add useful, supportable context.

How chronological sorting works

The catalogue opens with the newest known dates first so recent releases and newly documented material are easier to find.

Chronological sorting uses supported dates rather than alphabetical order or the date a page was edited. Exact dates, year-only dates and recording periods are handled consistently, while entries without a usable date appear after dated records.

Sorting does not change what a date means. A reported leak year remains a circulation date, not a recording year.

Sources used to establish dates

Useful date evidence may come from:

The strongest chronology usually comes from several sources that describe different stages of the song’s history.

What to do when sources disagree

Two sources may give different years because they are describing different events.

One may identify the writing session, another the vocal recording and another the first public appearance. Before treating them as contradictory, the catalogue should ask what each date actually refers to.

When sources genuinely conflict, the entry can use:

Uncertainty should remain visible rather than being silently converted into an exact year.

A practical date checklist

When assigning dates to a recording, ask:

Corrections and changing evidence

Recording histories can become clearer years later. An anniversary release may publish a session date, a producer may identify when a demo was made, or an official release may confirm that a circulating file came from an earlier project.

EverySongBy reviews dates when stronger evidence appears.

Corrections are most useful when they include an original credit, interview, archived page, registration record, catalogue number, scan, timestamp or enough context to distinguish the date being proposed.

The aim is an honest timeline

A useful catalogue does not force every recording into one unexplained year.

It distinguishes when a song was written, when a performance was recorded, when a title became public, when audio circulated and when an authorised release finally appeared.

Those events can be separated by months, years or even decades.

The goal is not to create false precision. It is to give each recording the clearest supported timeline available and to leave dates unknown when the evidence does not justify a stronger claim.

Leave a Reply

Your email address will not be published. Required fields are marked *