A devotional is the hardest structural task in religious publishing, because it must work twice: each entry has to stand entirely alone for the reader who opens it on a Tuesday, and the whole must add up to something for the reader who finishes it. Most fail the second test, which is why so many are abandoned in February.
How to write a devotional book
Which form, and what it demands
Start at the bottom of this table, not the top. A 40-day devotional that works is worth more than a 365 that runs dry in March.
| Form | Entries | Words each | Total | Difficulty |
|---|---|---|---|---|
| Daily, full year | 365 | 250–400 | ~110,000 | Very high. Most first attempts fail here. |
| Daily, seasonal (Advent, Lent) | 24–47 | 300–500 | ~15,000 | Manageable, and the best entry point |
| Weekly | 52 | 500–800 | ~35,000 | Moderate, and often the most useful to readers |
| Themed series | 30–40 | 400–600 | ~20,000 | Moderate. Strongest arc of any form. |
| Small group | 6–12 sessions | 1,500–2,500 | ~20,000 | Different craft — needs questions and structure for a group |
A structural read of your devotional
Send five entries and your plan for the sections, and we'll email back whether the arc holds, whether the pattern is consistent, and where it will run dry. Free.
The double structure
Every entry must be complete in itself, because your reader has not read yesterday's — they missed four days, opened the book on a Tuesday, and need this page to work alone.
And the whole must be more than 365 unrelated pieces, or there is no reason for it to be a book rather than an app.
The resolution is thematic arcs: sections of seven, thirty or ninety entries that build, inside a book whose entries each stand alone. The reader who dips gets a complete page; the reader who follows gets the argument.
A consistent pattern, and why it matters
Devotional readers want the same shape every day. It is a form with genuine conventions, and departing from them is felt as friction rather than variety.
The common pattern: a scripture, a reflection, an application, and often a short prayer. Some add a question or a single line to carry through the day.
Whatever pattern you choose, keep it. And keep the length consistent — a devotional where entries swing between 200 and 900 words reads as unfinished, because the reader's daily habit has a shape too.
How not to run dry
This is the practical problem, and it defeats most first attempts.
Write in themed batches, not in date order. Twenty entries on one theme in a week is far easier than twenty consecutive days, and the material is better because you are not starting cold each time.
Keep a running list of seeds — a verse, an image, a question, an overheard line. Never sit down to a blank page and a date.
Use what you already have. Sermons, talks, small group notes, a blog. Rewritten to the pattern, they are your fastest entries.
Start with 40, not 365. A completed Lent devotional is a real book. An abandoned year is not, and the year is much easier to attempt once you have done a season.
Consistency across 365 entries
The mechanical problem nobody warns you about.
Across a year of entries you will drift: the pattern loosens, the translation changes because you were quoting from memory, an illustration gets used twice, a phrase becomes a tic, and the entries written in month nine are noticeably different from month two.
The defences are a style sheet — pattern, length, translation, formatting, conventions — and a mechanical consistency pass at the end that searches rather than reads. Also keep an index of your illustrations, because repeating one in April and October is the error readers notice most.
What Your Book Pro does here
Your Book Pro is a British book-writing platform. You bring a book — an idea, a folder of notes, half a draft, or a finished manuscript written somewhere else — and it gives you the editorial process a publisher would run: a plan, structured feedback, a simulated beta read, a line edit, a proofread, a cover, a blurb and a print-ready file. You can type it, upload it or speak it. The tools sit in one place and work on the same manuscript, so the feedback compounds instead of arriving as twelve disconnected opinions.
For a devotional the two hard problems are the arc and the consistency, and both have tools.
Plan Feedback tests the structure before you write 365 entries into it — whether the sections build, whether the arc is real, and whether each block has a job. That is the check that prevents a year's work becoming a list.
The Book Dictionary is the style sheet across all 365: your pattern, your translation, your formatting conventions, your recurring terms — applied consistently rather than remembered. Proofread then checks against your own conventions rather than a generic standard.
Fact Check & Citations extracts every scripture reference for checking, which at 365 entries is a real job. Light Edit brings entries written months apart to a consistent register without rewriting your wording.
Plus lets you upload material you made anywhere, run whichever tool you actually need, and export it again. No subscription to start, 1,000 welcome credits that never expire, and a plain export of your own words is free forever.
Test your structure
Upload entries written anywhere
Email me the readQuestions people ask
- How long should a devotional entry be?
- 250–400 words for daily, 500–800 for weekly. Consistency of length matters as much as the number, because the reader's habit has a shape.
- Do I need 365 entries?
- No, and you probably should not start there. A 40-day themed devotional or an Advent or Lent series is a real book and far more likely to be finished.
- Should each entry include a prayer?
- Common and expected in most traditions. Whatever pattern you choose, keep it consistent — readers notice when it changes.
- Can I use my sermons?
- Yes, rewritten to the pattern and cut to length. It is the fastest route to your first fifty entries.
- How do I avoid repeating myself?
- Keep an index of illustrations and themes as you write. Repeating an illustration in April and October is the error readers notice and mention.