Manuscript workflow

Prepare, route, and track every manuscript.

Scribo helps authors build a clean submission package, send it to publishers or independent reviewers, and follow every response from one record. When reassurance matters, the uploaded file can also carry a recorded hash and downloadable certificate.

Submission-ready packageDeliberate routingTracked responses

The trust layer stays quiet in the background: keep the file private until you route it, then keep the evidence attached to the same manuscript record.

Prepare

One package

Bring the active file, synopsis, audience, and editorial framing together before you send it.

Route

Two lanes

Send the manuscript to publishers, independent reviewers, or both without splitting the record.

Track

One record

Follow statuses, notes, and decisions without rebuilding the story from inbox threads.

Live Workflow Snapshot

One manuscript, multiple outcomes, no ambiguity.

The system should feel like a manuscript pipeline. Submissions, reviews, and decisions stay visible as a single operating surface.

River of Ash

Historical fiction · Version 2 · 98,000 words

Under Review

Northbridge Press

Acquisitions review in progress

Under Review

Ledger House

Declined after editorial screen

Rejected

Morning Table

Queued for first pass

Pending

Reviewer Lane

Independent feedback

Compare fit, turnaround, and pricing before sending a review request.

Publisher Lane

Publisher workspace

Publisher teams capture intake, assign new submissions, work assigned reads, and land decisions from one connected surface.

Three-step operating model

Upload once, route clearly, track everything.

The product is not a document editor. It is a pipeline system built around manuscripts, submissions, and reviews.

01

Package the manuscript

Upload the latest file, attach market and rights metadata, and prepare a submission-ready package.

02

Route it deliberately

Send the manuscript to publishers, request independent feedback, or do both in a controlled sequence.

03

Manage the responses

Watch status changes, review notes, and decisions without leaving the object page.

Role-based shells

Each role sees a different center of gravity.

Authors manage manuscripts, publishers manage incoming work, and reviewers manage assigned feedback. The UI should respect those mindsets instead of forcing one navigation model onto everyone.

Authors

Manage projects, package submissions, and keep an eye on momentum across publishers and reviewers.

Primary focus

Recent manuscripts with visible stage and next action.

Submission watchlists that surface who has the manuscript now.

Independent review planning before the next submission round.

Publishers

Treat the platform as an operating workspace for new work rather than a passive archive.

Primary focus

Filterable submission workspace with clear status and assignment.

Author signals and editorial notes close to the manuscript.

Fast routing of new submissions into reviewer ownership before review begins.

Reviewers

Work the inbox, accept the right projects, and move active reviews toward a finished letter.

Primary focus

Request inbox organized by due date and fit.

Active review list with current progress and deadlines.

Completed work that demonstrates pace and quality.

Built-in trust layer

The certificate is there when you need it.

Scribo keeps the uploaded file connected to the same manuscript record, so hash evidence, private storage, and certificate download stay available as supporting proof rather than becoming the whole workflow.

When reassurance matters

Manuscript certificate

Scribo can generate a certificate that references the recorded upload date and cryptographic file fingerprint for the uploaded manuscript.

Recorded file fingerprint: each uploaded version can carry a SHA-256 hash and registration date.

Downloadable certificate: export a certificate tied to the exact file version stored in Scribo.

Private until routed: keep the manuscript in your workspace until you decide where it should go next.