Free planning tool
Content review workload planner
Estimate how many whole pages fit into a review session, the time your review list needs, and whether it fits your target number of weeks. Start with your page count and a realistic review estimate. The calculation runs in your browser; it does not scan your website or schedule reminders.
Updated · All Staleaway features are free.
Plan a manageable review batch
Prefilled numbers are an illustrative example, not a recommendation. No inputs are sent, saved or added to the URL. A local text file is created only if you choose Download.
Interactive calculation is unavailable until JavaScript loads. No estimate has been calculated. You can use the manual formula below.
Your workload estimate
Assumes distinct pages, equal review time and every session used. Spare minutes do not carry between sessions. Reserved time includes the full final session; page slots may exceed your review list. Fixes, research and interruptions may need additional time.
This is not an audit score, a deadline or a forecast of Staleaway coverage. It does not change your reminder settings.
What your review plan means
A content review planner estimates how many sessions and working weeks one manual pass through your website pages will take. It answers a practical question: can the review work fit into the time you have set aside? It does not decide which pages are accurate, which deserve attention first, or when a particular fact will expire.
Pages per session counts only complete reviews that fit your time estimate. If a review takes eight minutes, a thirty-minute session holds three pages, not four. The spare six minutes cannot become part of another session in this model. That makes the estimate different from simply dividing total review time by your weekly availability.
Weeks needed means weeks of work at your chosen number of sessions, rounded up. It is not a calendar finish date. Missed sessions, holidays, research, approval waits and fixes can extend the work. The target comparison shows how many pages would remain after the entered number of weeks, assuming you complete every planned session and choose different pages each time.
How the workload calculation works
The inputs are your assumptions, not industry benchmarks. Count the pages you intend to review, estimate minutes per page, and choose a session length you can protect. Use whole numbers. This version accepts one to seven sessions per week; it does not assign them to particular days. The target is a number of working weeks, not a promise about page freshness.
- Divide minutes per session by minutes per page. Round down to find the whole-page batch, capped at your page count.
- Divide the page count by that batch. Round up to find sessions needed.
- Divide sessions needed by sessions per week. Round up to find weeks needed.
- Multiply batch size by sessions per week and target weeks. Subtract this capacity from your page count; a negative shortfall becomes zero.
- For minimum weekly sessions to meet the target, divide sessions needed by target weeks and round up. A result above seven is outside this planner's input range.
Estimated review time is pages multiplied by minutes per page. Reserved calendar time is sessions needed multiplied by session length, including unused time in the final session. If even one page cannot fit into a session, there is no whole-page plan to calculate. Increase the session length or divide the work into a different, manually planned process.
A 60-page review, worked through
This is a fictional planning example, not customer data or a recommended review speed. With 60 pages, eight minutes per page and thirty-minute sessions, each session holds three pages. You need twenty sessions. At two sessions per week, that is ten working weeks, with 480 minutes of estimated review work inside 600 reserved minutes.
An eight-week target has room for sixteen sessions, or 48 pages. Twelve pages remain. Three sessions each week would provide enough whole sessions within the target; the last week would need fewer. Alternatively, keep two weekly sessions and extend the target to ten weeks. Do not reduce the review-time estimate just to make the result look better.
Set priorities before filling the sessions
Group pages with similar review effort rather than treating a short contact page and a long tutorial as identical. Run the planner separately for each group, then check that the groups are not using the same calendar time. Time a few actual reviews and replace the example estimate with what you learn. Set aside additional time for fixes and follow-up.
A page's next review date is a separate decision. Cornell's content-review guidance varies the cycle by how often information changes. FIU's scheduling guide connects reviews to known updates and expiring information. These are institution-specific practices, not universal deadlines or Staleaway features.
If a service changes today, check the affected page today. A workload estimate cannot make an incorrect statement safe until next month's slot. Use the website content review checklist to record evidence, unresolved questions and who owns the next action.
Choose what should prompt the review
The estimate answers “How much time does this review list need?” Next, decide when each page needs attention. A routine nudge, a deadline for one page and an alert about a page changing are different jobs.
- Build a regular review habit. Set aside a manageable session and use the content review checklist to check facts and record unfinished work. Staleaway's email reminders can provide the nudge; they do not verify the review.
- Check a particular page by a fixed date. Record its owner, due date and any earlier change trigger in your calendar or task system. For example, check event details before registration opens. This calculator does not schedule those dates, and Staleaway's random page selection cannot guarantee that a particular page appears before its deadline.
- Notice a page changing. Consider change monitoring when you need an alert about an edit or a configured condition. Staleaway sends review reminders; it does not detect page changes. Compare content review reminders and change monitoring to decide whether you need one workflow or both.
If reminder emails fit your workflow
The calculator works locally in your browser. It does not read your site, save your plan to an account, send reminders or schedule calendar events. Copy or download the result if you want to keep your assumptions. The calculation uses no changing external rates; its method was checked on 15 October 2026.
Staleaway's separate email reminder workflow can help you begin regular reviews. Find your website's sitemap, then choose a daily, weekly or monthly reminder and pages per email. Staleaway selects from eligible unreviewed pages at random. This estimate instead assumes you choose different pages for each completed review. Reminder frequency does not guarantee complete or repeated site coverage.
Opening a review link marks that page reviewed and redirects to it; it does not prove the content was checked or a fix finished. Keep your own record for deadlines and unresolved work. If reminders suit the habit you want, create a free Staleaway account. The planner neither changes those settings nor predicts delivery.
Cite this tool: Staleaway, Content review planner, methodology checked 15 October 2026.