PROJECT / EXTRAORDINARY BOOKS

Manuscript submission ecosystem for modern publishing house

Building a publishing workflow into a structured, multi-stage submission and review platform connecting publishers, authors, readers, and administrators.

Role
UX | UI | Product Designing
Timeline
July 2025 – Present
Scope
Multi Tenant Ecosystem
Extraordinary Books hero preview

The challenge

Traditional manuscript submission systems often rely on disconnected emails, spreadsheets, manual review coordination, and fragmented communication between publishers, readers, and authors. Managing submissions at scale introduces operational complexity across multiple stages — especially when submissions move through pitch approvals, manuscript collection, reader assignments, deadlines, and final editorial decisions.

Discovery

The real product wasn’t the submission form. It was the workflow around it.

As I mapped the experience, I found that the difficult part wasn’t allowing someone to submit a pitch. The difficult part was everything that happened after submission.

A single submission could carry

  1. 01Multiple readers
  2. 02Different review stages
  3. 03Reader invitations
  4. 04Voting
  5. 05Feedback
  6. 06Discussions
  7. 07Publisher decisions
  8. 08Notifications
  9. 09Deadlines
  10. 10Multiple outcomes

What it meant for design

Users could participate in multiple open calls at the same time. Every state above running in parallel, more than once, for the same person. The product needed to keep everyone oriented — without forcing them to understand the entire system.

The process

Instead of treating every state as another status, I separated the system into three things.

Discussion thread on a manuscript titled Plot Clarity and Story Flow, with reader comments and replies, a list of other topics, participating readers and a topic summary.

Future Scope

Search that reads the pitch, not the tags

A feature I thought worth adding, because nobody thinks in genre tags. They think something like the "last book I couldn't put down.".

The outcome

Project is in running phase, few of the features and design work including from very start had changed during my engagement, so the impact shown here reflects product and design outcomes rather than post-launch business metrics.

Admin dashboard showing a system overview: counts of active publishers, total authors and books published, a platform growth chart, reader and publisher-website status rings, and recent activity.
Book submissions table listing author, book, publisher, approval date and a review status for each submission, with search, status and date filters and pagination.
Reader availability settings: current status options such as active, at capacity or on leave, turnaround time, scheduled time off and a monthly reading capacity limit.
Reader preferences screen for choosing which publishers to review for, shown as cards with each publisher's address and counts of active readers and authors.