- Rejected Draft sketch names are the working labels attached to scrapped concept art and draft pages.
- Naming conventions usually combine a project code, a version number, and a short descriptor.
- Crossed-out names in sketch margins often reveal earlier identities before a design was renamed.
- Cataloging early prevents orphaned files and keeps archive research fast and consistent.
What Are Rejected Draft Sketch Names?
In the Rejected Draft archive community, a "sketch name" is the informal label an artist or writer gives a piece of work before it is officially accepted, titled, or discarded. When a draft is rejected, that sketch name often survives in filenames, margin notes, or crossed-out headers, becoming the only trace of an abandoned idea.
These names matter for three reasons:
- Provenance: They link a discarded sketch back to the working session that produced it.
- Version history: Early sketch names sometimes reveal what a character or scene was called before its final revision.
- Discovery: Researchers searching archives rely on consistent naming to surface related rejected material.
A struck-through sketch name on a draft page usually signals a rename, not a rejection of the artwork itself. Always check for a replacement name written nearby before assuming the piece was fully scrapped.
The table below summarizes the most common sketch name patterns found in Rejected Draft collections:
| Pattern | Example | Typical Use |
|---|---|---|
| Numbered code | RD-014_Sketch03 | Bulk archive files |
| Descriptive label | angry_face_v2 | Character concept iterations |
| Dated working title | 0312_idea_dump | Daily sketch sessions |
| Nickname | "Old Grumpy" | informal studio shorthand |
| Placeholder | untitled_final_FINAL | Unresolved drafts |
Naming Conventions Explained
Most Rejected Draft sketch names follow one of a few recognizable conventions. Understanding them helps you read an archive the way its creator intended.
Code-First Names
- Prefix like RD or a project tag
- Sequential numbering
- Easiest to sort and search
- Common in large collections
Descriptor Names
- Short visual description
- Version suffixes such as v2, v3
- Human-readable at a glance
- Risk of duplicates over time
Nickname Names
- Informal studio shorthand
- Highly memorable
- Rarely documented formally
- Often the hardest to trace
Never overwrite an original sketch name when archiving. Preserve the source label in a metadata field and record any new catalog name separately, so the provenance chain stays intact.
When two conventions collide in one collection, archivists typically keep both: the original sketch name as the primary identifier, and a normalized catalog name for indexing.
| Convention | Searchability | Provenance Value | Risk Level |
|---|---|---|---|
| Code-first | ★★★★★ | Medium | Low |
| Descriptor | ★★★ | Medium | Medium |
| Dated title | ★★★★ | High | Low |
| Nickname | ★★ | Very High | High |
| Placeholder | ★ | Low | Very High |
How to Catalog Sketch Names Step-by-Step
Building a clean index of Rejected Draft sketch names takes a little discipline, but the process is straightforward. Follow these five steps for any batch of scrapped material.
Inventory the Source
List every draft file or page, capturing the exact sketch name as written, including strikethroughs and version suffixes. Do not correct spelling at this stage.
Record Context
Note the date, project phase, and any adjacent notes for each sketch. Context is what separates a searchable archive from a pile of images.
Normalize a Catalog Name
Create a standardized duplicate name following one convention, such as RD-014_Sketch03, while preserving the original label in a metadata field.
Cross-Reference Renames
Link any crossed-out names to their replacements. This rename chain is often the most valuable data in a rejected draft collection.
Publish the Index
Export the catalog as a searchable table or wiki page so other researchers can trace sketch names back to source material.
A finished index should let anyone find a specific rejected sketch from its name alone, in under a minute, without opening unrelated files.
Common Problems and Fixes
Even careful archives run into naming issues. These are the problems editors encounter most often, along with practical fixes.
| Problem | Cause | Recommended Fix |
|---|---|---|
| Duplicate sketch names | Descriptor convention reused | Add sequential code suffix |
| Orphaned files | Name lost during transfer | Match by date and context notes |
| Ambiguous strikethroughs | Unclear rename vs rejection | Check nearby replacement text |
| Inconsistent casing | Mixed contributors | Normalize in catalog layer only |
| Placeholder overload | Untitled drafts piling up | Assign batch codes immediately |
When a sketch name carries multiple version suffixes such as v2_final_fix, treat the entire string as the historical name. Trimming suffixes destroys iteration history that cannot be recovered later.
Sketch Name Audit Checklist:
- Capture every original sketch name exactly as written
- Preserve strikethroughs and rename chains
- Assign a normalized catalog code to each draft
- Cross-reference duplicates and flag conflicts
- Export a searchable index for the wiki
FAQ
Q: What are Rejected Draft sketch names used for?
They serve as the primary identifiers for scrapped concept art and draft pages. Because rejected material rarely receives an official title, the informal sketch name becomes the main way to search, sort, and discuss the work.
Q: Why do some sketch names appear crossed out?
A crossed-out name usually indicates the piece was renamed during revision rather than fully discarded. Look for a replacement label nearby to trace the rename chain before treating the draft as rejected.
Q: Should I rename rejected sketch files when archiving them?
Keep the original sketch name intact and add a normalized catalog name in a separate metadata field. Renaming originals breaks the provenance chain and makes cross-referencing with other archives much harder.
Q: How do I deal with drafts that have no name at all?
Assign a batch code with a date, such as RD-0312_untitled_04, and record the context around the file. Consistent placeholder coding prevents orphaned files from accumulating.