1. Reading capacity
Available hours divided by average article time gives a practical weekly throughput.
READING BACKLOG CALCULATOR
Compare the articles you save with the time you really have. Get a weekly balance, a clear-date projection, and a realistic target without uploading your reading list.
SIMPLE MODEL, EXPLICIT ASSUMPTIONS
Available hours divided by average article time gives a practical weekly throughput.
New articles consume capacity before the old backlog can become smaller.
Items you knowingly archive after a quick review leave the active queue without pretending they were read.
HOW TO READ THE RESULT
The model is intentionally transparent. It does not fetch article lengths, inspect your history, or assume that every saved item deserves a full read.
New saves minus reading capacity. This is the most important number in the result.
The reading volume required to handle new saves and reduce the active backlog within your chosen window.
How many new articles your current reading time can absorb without making the queue larger.
It is a projection from the numbers you enter, not a behavioral forecast. Changes in article length, available time, new saves, or triage decisions will change the result.
No. Here it means removing an item from the active reading commitment. You can keep it as a searchable reference or archive it in your current system.
No. A reference library can stay large. The useful goal is to keep the active reading queue compatible with your available time.
Use a realistic mix. If you usually skim first, take notes, or verify claims, include that time. Recalculate with a range when your queue mixes short posts and dense papers.
No. The calculation happens in your browser. This tool does not upload the numbers or connect them to a Nodus Vault account.
FROM A NUMBER TO A FINITE QUEUE
The related guide shows how to separate an active reading queue from a reference library. Nodus Vault can then keep saved links searchable and bring a small set back for review.