PlainPerks
Back to lessons

Write, review and schedule an Advice article

Lesson 22 of 24

Move a real Contributor draft through Pending Review, correct it as Editor, schedule a future release and verify the actual visitor result.

Before you start

Use the disposable Cedar Lane Garden Care practice site. The accounts and records in this chapter are fictional. Keep real users, passwords, customer details and live services out of the exercise.

1. Agree the article brief and reviewer

Open the editable editorial card. The fictional title is Three things to check before seasonal garden work. Write a short introduction and three sections: Describe the work, Plan ahead and Prepare questions. Use safe original wording and a Services link; make no price, availability, customer or hazardous-work claims. Choose the existing Getting ready category. Record Cedar Contributor as writer and Cedar Editor as reviewer. This example is intentionally text-only. The review card records the vague heading that the Editor will improve; keep private feedback out of the public article.

The editorial card separates the article brief and private review decisions from public content.
Full editable editorial brief and review record for the seasonal garden article.

2. Create a Contributor draft and check its privacy

Sign in as Cedar Contributor in a separate browser window. Open Posts → Add Post, enter the title and full article, choose Getting ready, then Save draft. Reopen the saved draft and read it back. The full editor below shows the article and Submit for Review control. Copy its visitor address from the editor into a separate signed-out window. A draft is unavailable there. Search the public site for the unique title as a second check. The screenshots show the actual missing-page result and search exclusion. Never treat an authenticated preview as proof that a draft is public.

Cedar Contributor saves the complete fictional article as Draft, with Submit for Review available and no Publish permission.
Cedar Contributor saves the complete fictional article as Draft, with Submit for Review available and no Publish permission.

3. Submit the saved article for review

As Contributor, click Submit for Review. WordPress 7.1 opens a confirmation panel. Read the article identity and click the second Submit for Review button. Return to Posts and confirm Pending Review. The writer has requested editorial work; the article has not been published. Keep the brief, reviewer and intended timing in the private editorial record.

The Contributor Posts list now labels the article Pending Review rather than Published.
The Contributor Posts list now labels the article Pending Review rather than Published.

4. Preview the pending article as Editor

Save and exit the writer’s editor. Sign in as Cedar Editor and open the pending item in Posts. If WordPress shows an edit-lock notice, arrange the saved handover before using Take over. Click View and then Preview in new tab. Wait for the actual article to load; Generating preview is a temporary screen. Read the complete preview, test the Services link, and inspect it at a phone width. These full-page screenshots show the real menu and resulting desktop and phone previews. The preview remains authenticated and does not change publication status.

The actual authenticated preview shows the article the Editor is reviewing, including the vague Plan ahead heading.
The actual authenticated preview shows the article the Editor is reviewing, including the vague Plan ahead heading.

5. Make one explicit correction and read it back

Return to the Editor window. Replace the vague Plan ahead heading with Check access before the visit. Keep the nearby sentence about avoiding private codes and addresses. Click Save, leave the editor, then reopen the pending article. Check the full article, category and link—not only the changed heading. The screenshot below was captured after Save and reload, and the saved content still had Pending Review status. Record this as the accepted fictional wording for the exercise.

After Save and reload, the Editor sees the corrected Check access before the visit heading in the complete pending article.
After Save and reload, the Editor sees the corrected Check access before the visit heading in the complete pending article.

6. Choose and confirm a future release

As the course Administrator, open Settings → General and confirm the site timezone. This fixture uses Australia/Melbourne. Save any intentional change, then use the Editor account for the article again. In the Post sidebar, click Immediately beside Publish. Use the calendar’s Year, Month, Day, Hours, Minutes and AM/PM controls to choose a time several minutes in your future. Check the displayed timezone. Do not copy the historical date from these screenshots. Close the calendar, click Schedule, inspect the confirmation, and click Schedule again. The result panel and Posts list must show Scheduled and the intended local release time. Before that time, open the visitor address in a fresh signed-out window: it must still be unavailable.

The Editor selects a real future date and time. The publishing calendar shows the site timezone; use your own future time when practising.
The Editor selects a real future date and time. The publishing calendar shows the site timezone; use your own future time when practising.
A separate signed-out visitor cannot open the future article before its release time.
A separate signed-out visitor cannot open the future article before its release time.

7. Verify the scheduled result and final article

After the chosen time, open the visitor site and refresh the article. The scheduled WordPress event published this article after its due time. The verification did not use a manual Publish action. Confirm the reviewed heading, all surrounding paragraphs, Services link and publication date. Check the full article at desktop and phone widths, then open Advice and find the new title in its listing. Return to Posts and confirm Published. Record the local time, UTC equivalent and observed result in the editorial card. Keep this accepted article for the revisions lesson. Remove any temporary review notes from public content; the separate training drafts remain private.

After the scheduled time, a signed-out visitor sees the reviewed article with its corrected heading and Services link.
After the scheduled time, a signed-out visitor sees the reviewed article with its corrected heading and Services link.

Practise

Prepare the fictional article as Contributor, submit both review confirmations, preview and correct it as Editor, then schedule it for your own future time. Capture the real signed-out state before and after its release.

Check your result

The Contributor cannot publish; the Editor reviewed the full desktop and phone previews. The saved correction is present, the future article was private, and the scheduled event released the accepted content without a manual Publish shortcut.

If something goes wrong

The preview only says Generating preview? Wait for the article itself before checking or capturing it. The article is still private after its due time? Verify the site timezone and exact scheduled date, then visit a normal page to trigger WordPress scheduled work. A quiet local site may not have traffic, and a blocked loopback or cron runner can leave Missed schedule. Inspect the local environment and Site Health; keep scheduling marked unverified until the actual event runs. Do not silently click Publish and claim scheduling worked. An unexpected edit-lock appears? Ask the writer to save and exit before taking over.

Optional notes

Words used in this lesson
Pending Review
A saved post waiting for a person with publishing permission.
Preview
An authenticated view of content before public release.
Scheduled
A future release waiting for the WordPress scheduled event.
Site timezone
The timezone WordPress uses to show and interpret publication dates.
Choose another lesson