A reviewable Verse of the Day workflow: select, swap, schedule, pause

An empty date is not the main risk in a Verse of the Day series. The larger risk is a polished graphic built on an unknown translation, approved too quickly, or marked complete before anyone checks the destination.

A reviewable workflow has eight steps:

1. Verify the passage, edition, authorized source, permission, attribution, date, time zone, and context.
2. Select a candidate design or replace it with another suitable design.
3. Review the exact words, caption, alternative text, crops, contrast, and required notice.
4. Save a version that a named person has approved.
5. Choose a future local schedule only after that review.
6. Pause, skip, or reschedule local intent when the situation changes.
7. Retry a known failure, but reconcile an uncertain result before sending again.
8. Inspect the live destination and record what actually appeared.

This sequence separates repeatable setup from the decisions that still need named owners: source, approval, accessibility, and delivery.

One limit matters before we go further. The active Church Media Kit schedule reviewed for this guide does not record the Bible translation behind its verse text. Its source history identifies an imported schedule. That history does not establish the edition or permission to redistribute its words.

Until a person resolves the translation, source, licence, and attribution, treat those dated entries as material to inspect, not material ready to publish.

Put the source gate before design

A design can look finished while its source record is incomplete. Do not let visual polish move an entry past questions that have not been answered.

Use one record for each dated entry:

Stop when any field is unknown. Do not identify a translation by familiar wording. Do not copy a passage from a website and assume that the site's display agreement covers redistribution through another product.

Publisher rules differ. The World English Bible copyright page says its text is in the public domain while treating its name as a trademark. Crossway publishes separate ESV permissions for quotation, notices, digital use, and uses that require further permission. Biblica publishes its own permissions for its texts and distribution methods.

Those differences are why the exact edition and intended use must be written down.

Source review also includes context. Read the surrounding passage. A graphic can quote a verse exactly and still mislead when its caption turns a general statement into a personal guarantee or assigns special meaning to the scheduled date.

Select and swap without changing the source

Once the source gate passes, select a design that can carry the approved words at the size people will receive.

In the Church Media Kit build reviewed for this guide, a dated entry opens a review dialog with its reference, current design, caption, alternative text, and a Choose another design action. That action replaces the design with another certified option. It does not correct the passage, reference, date, translation, licence, attribution, or context.

That boundary separates two kinds of work. A design problem may need a different layout. A source problem needs a corrected source record. Cycling through artwork cannot solve both.

Review the replacement at every planned crop. Check that:

• the full passage and reference remain legible at phone size;
• required attribution remains present and readable;
• decoration does not obscure a line or imply emphasis the passage does not contain;
• the graphic does not trivialize grief, violence, judgment, disability, poverty, or another serious subject;
• color is not the only cue carrying meaning;
• the caption still describes the approved passage and not an earlier draft.

If the words do not fit, shorten the verse range only through a new source review. Do not silently shrink the type or trim the passage inside the artwork.

Review the final pixels and the accompanying words

The review is not complete at the template preview. Review the actual exported pixels, each crop, the caption, and the alternative text together.

The W3C images tutorial explains that an informative image needs a text alternative that conveys its essential information. When an image contains readable text, the alternative should carry the same words.

For a scripture graphic, that usually means the verse words, reference, and translation identity, plus visual information that affects meaning.

Do not use a vague phrase such as "inspirational quote" in place of the scripture. Do not fill the alternative text with colors and decoration while omitting the words a sighted reader receives. The caption and alternative text have different jobs: the caption is church speech for the audience, while the alternative text gives access to the image's information.

Check contrast against WCAG 2.2's contrast criteria: 4.5:1 for ordinary text and 3:1 for large text, subject to the criterion's stated exceptions. A ratio does not settle the whole design. Line length, type size, background interference, and the final crop still need human review.

Saving a caption and alternative text in a product is not proof that a destination receives them. Verify the live result through the destination's accessibility view or a screen reader. When a publishing path cannot preserve alternative text, keep the essential scripture information in accessible visible text and repair the process before relying on that path.

Give Ready a narrow meaning

In the reviewed build, a Verse entry can become Ready when its design record passes the product's structural checks and it has a nonblank caption and nonblank alternative text.

That is a useful completeness check. It is not approval of the translation, rights, attribution, doctrine, context, design quality, accessibility, timing, or destination. A church should record the person who approved each of those decisions instead of asking one badge to stand for all of them.

A compact review record can include:

• exact passage, edition, authorized source, permission, and attribution;
• caption and alternative text as approved;
• final image files and every planned crop;
• contrast and phone-size readability result;
• destination, account, local date, time, and time zone;
• approver and approval time;
• hold, skip, correction, and uncertain-delivery rules;
• final destination link or provider identifier after handoff.

This record makes a later correction possible. It also helps a volunteer see what is settled and what still needs a decision.

Schedule only after the gate passes

The Verse entry flow reviewed for this guide accepts a future church-local time and an eligible destination selection. Scheduling creates local publishing intent. It does not prove that a provider has accepted the post or will display it at that time.

Keep the local date and time zone visible through approval. A post scheduled near midnight can cross a date boundary for part of the congregation or for a reviewer in another zone. The date on the graphic, the local schedule, and the destination timestamp should tell the same story.

Post now needs a separate explanation. That action exists in a separate Church Media Kit posting composer, where it creates a near-term local handoff record. No Post now control was found in the reviewed Verse entry flow. Do not describe it as a Verse shortcut unless the release being used shows that exact control.

In either flow, a local action is intent, not provider proof. The handoff is complete only after someone inspects the destination.

Read each state as a limited fact

Status labels help a team find the next action when everyone reads them narrowly.

The reviewed state model also has a destination-level reconciliation condition. That means the result is uncertain. An aggregate can present that condition with failed work, so open the destination-level record before choosing the next action.

Pause and skip are editorial controls, not remote deletion

Pause when the entry may still be appropriate later but should not leave on the current plan. Skip when the church intentionally omits the local entry.

Reasons to pause or skip include:

• the translation or permission is still unverified;
• the passage no longer fits the day's pastoral context;
• a local crisis makes the scheduled caption insensitive;
• no authorized reviewer is available;
• the attribution does not fit the final design accessibly;
• the destination connection needs attention;
• the date or time zone is wrong;
• the moment has passed and a late post would confuse readers.

The reviewed build blocks some changes while handoff is active, while a result is uncertain, after it records a provider result, and near the scheduled handoff time. A local pause or skip should never be described as deleting a post that already reached a provider.

Series pause and resume also need a careful rule. The reviewed local model holds eligible future items. When the series resumes, elapsed items remain paused and require an explicit reschedule. It does not release a missed backlog at once. That preserves the dated editorial record: yesterday's dated verse should not appear today because a queue woke up.

Retry a known failure; reconcile uncertainty first

A known failure and an uncertain result require different actions.

Retry is appropriate when delivery records show that one or more providers did not publish and the product offers the action for those failed destinations. Retries failed deliveries while preserving destinations already recorded as posted.

Reconciliation is for ambiguity. The provider may have received the request even though the local system did not obtain a final answer. Check the native account, recent posts, provider identifier, timestamp, media, and caption before sending again. A blind retry can create a duplicate.

Do not promise a fixed number of attempts, a retry cadence, or recovery without intervention. Those details are not a stable public contract in the reviewed build. The useful promise is smaller: known failure and uncertain outcome are not the same state, and a person should verify uncertainty before another send.

Close the loop at the destination

The local workflow ends with inspection, not with a green badge.

For each destination, check:

1. the authorized account and audience;
2. the live date and timestamp in the destination's zone;
3. the exact verse words, reference, translation mark, and required notice;
4. the intended image and crop;
5. the caption and any visible link;
6. the alternative text through the destination's own accessibility path;
7. whether the post remains visible after the initial handoff;
8. the final link or provider identifier in the review record.

If the destination and local record disagree, record the discrepancy and hold the next entry until the team understands it. A calendar full of local Posted labels is not a substitute for the posts people can actually receive.

When this workflow is not a fit

Do not use this workflow when the church cannot identify the translation or obtain permission for the intended use. It is also a poor fit when the church needs an editable lectionary, sermon-series source, devotional authoring, arbitrary passage correction inside the review dialog, guaranteed destination delivery, remote deletion, or proof of ministry results.

A ready-made dated resource with clear provenance and reuse terms may be the simpler choice. YouVersion Open Network's Verse of the Day collection, for example, provides dated artwork under its own resource terms. Compare the source, permission, formats, accessibility work, approval needs, and publishing effort. Ask which decision each control records and who remains responsible for it.

FAQ

Does choosing another design change the verse?

No. In the reviewed workflow, it changes the design option. It does not correct the passage, reference, date, translation, permission, or context.

Does Ready mean a pastor approved the post?

No. It means the required local design record is complete. Record human approval separately.

Can a Verse entry be published immediately?

The reviewed Verse entry flow shows future scheduling. A separate posting composer has Post now, but that is not evidence of a Verse shortcut. Check the release you use and verify the destination result.

Does Scheduled mean the destination accepted the post?

No. It records local future intent. Provider truth begins with destination-level delivery evidence and ends with native inspection.

Does pausing remove a live post?

No such remote effect is established. Treat pause as a hold on eligible future local action. Inspect and manage any live provider post separately.

Should the team retry every failed-looking item?

No. Retry a known failure when the action is available. When the result is uncertain, inspect the provider first so another send does not create a duplicate.

What should stop an entry?

Missing source or translation, unclear permission, absent attribution, disputed context, unreadable artwork, incomplete alternative text, no approver, wrong date or time zone, a sensitive event, a broken connection, or an uncertain provider result should all stop the entry until a person resolves the issue.

The working rule

Select and replace designs freely only after the source is settled. Schedule locally only after a named person approves the exact final post. Pause or skip when circumstances change. Retry known failures, reconcile uncertainty, and inspect the destination before calling the work complete.

That process may leave a date empty. Leaving the date empty preserves a clear record; publishing an unattributed, inaccessible, mistimed, or duplicated scripture post creates a different public record.