WORDPRESS EDITING TRIAL WORKSHEET
WP Growth Labs | Version 1 | 18 October 2026
Companion guide: https://wpgrowthlabs.com/blog/elementor-vs-acf-wordpress/

Use this record to compare the editing workflow you are actually being offered.
It is an original planning template, not a completed test, speed benchmark or
claim that one editor is better. Start every task as NOT TESTED. Run the same
agreed tasks with representative content and the intended editor account.
Use a duplicate page or protected staging environment. Do not test recovery
by disrupting the live website. Never record passwords, keys or private data.

1. AGREE THE TRIAL
Project/site reference:
Reviewer and date:
Editor role (not an administrator unless that is the intended role):
Workflow under review (native blocks / Elementor / custom ACF / combined):
Relevant theme, plugin and integration versions:
Staging or duplicate-page reference:
Approved page/layout reference:
Desktop and phone viewport sizes to inspect:
Who may approve publication:
Who owns recovery if a test goes wrong:

2. DEFINE A RESULT FOR EACH TASK
Choose a result: NOT TESTED / PASS / NEEDS HELP / BLOCKED / NOT IN SCOPE.
PASS means the agreed saved result was observed, not that the plugin is
universally suitable. Record where help was needed and the remaining action.

TASK A: UPDATE COPY
Page, section and exact field/element:
Expected change and places that should remain unchanged:
Try a short value, realistic long value and optional empty value where safe.
Check the saved output at both agreed widths, including heading wrapping.
Result: NOT TESTED
Evidence reference and observed output:
Help needed / issue / owner / next action:

TASK B: REPLACE AN IMAGE
Page and image field/element:
Representative asset with confirmed usage rights:
Expected crop, aspect ratio and alternative-text decision:
Check the saved image and agreed optional empty state on both widths.
Result: NOT TESTED
Evidence reference and observed output:
Help needed / issue / owner / next action:

TASK C: ADD OR REORDER AN AVAILABLE SECTION
Section/block/layout already included in the proposed build:
Expected position and permitted changes:
Check heading order, spacing, navigation and the button destination.
If the requested composition is not supplied, record it as new scope.
Result: NOT TESTED
Evidence reference and observed output:
Help needed / issue / owner / next action:

TASK D: UPDATE SHARED CONTENT
Record type and content owner:
Locations expected to change:
Locations expected to remain unchanged:
Change one agreed value and inspect each location. Record actual behavior.
Result: NOT TESTED
Evidence reference and observed output:
Help needed / issue / owner / next action:

TASK E: RECOVER A MISTAKE
Approved safe test environment:
Recovery method and responsible person:
Does the method cover content, custom fields and layout settings separately?
Demonstrate only the agreed safe recovery process. Do not assume that one
revision or backup mechanism covers every plugin or integration.
Result: NOT TESTED
Evidence reference and observed output:
Help needed / issue / owner / next action:

3. RECORD DEPENDENCIES AND LIMITS
Features the editor can change independently:
Changes requiring review:
Changes requiring development or a separate estimate:
Extra add-ons, custom code or integrations required:
Licence account owner and renewal responsibility:
Maintenance, backup and compatibility-check owner:
Training or handover material still needed:

4. CLOSE THE REVIEW
Tasks passed:
Tasks needing help, blocked or not tested:
Agreed exclusions:
Issues to resolve before publication:
Person responsible and review date for each issue:
Decision (accept the scoped workflow / revise the scope / compare another):
Approval and date (leave blank until approved):

Keep this record with the project brief and handover checklist. Compare the
saved outcomes and responsibilities; do not turn a single trial into an
unsupported claim about rankings, conversion rates or universal performance.