Skip to content
Chris Key of Rubber Duckers on a five-star testimonial card beside the agency logo, next to a care plan checklist with a scheduled form test highlighted

· Published October 6, 2026

What a WordPress Care Plan Misses Without Form Testing

A typical WordPress care plan covers core and plugin updates, backups, uptime monitoring and a security scan. Each of those answers a clear question: is the site up, is it patched, can we restore it? None of them answers the question a client cares about most. When someone fills in the contact form, does the enquiry actually arrive?

Rubber Duckers, a UK design and development agency, ran into exactly that gap as its care plan business grew. Here is why form testing tends to get left out of care plans, what it costs when it is, and how they added it without it turning into hours of manual work.

Why forms fall through the gap

Uptime monitoring checks that the page loads. A broken form still loads. The fields fill in, the submit button works, and often the thank-you message still appears. What fails is everything after that: the entry never saves, the notification email is never sent, or it is sent and never delivered.

The causes are the same things a care plan deals with every month. A plugin update changes how the form submits. A spam-protection or CAPTCHA setting starts rejecting real visitors. The SMTP connection or email provider changes. A hosting firewall rule starts blocking the submission. Some failures need no change on the site at all, like an email provider quietly filtering the notifications.

None of that shows up on an uptime check, an update log or a security scan.

Why it rarely makes it into the plan

The honest reason is time. Chris Key, Creative Director at Rubber Duckers, described how form testing worked for them before:

“Before CheckView, form testing was manual and ad hoc. We’d check forms when a site launched and occasionally after that, but it wasn’t a defined part of our care plans because of the hours involved.”

Submitting every form on every client site after every update takes hours. Even then, it only proves the form worked at the moment you checked. So form testing ends up happening at launch, and after that whenever someone remembers.

The real cost: not knowing how long it was down

The failure that stuck with Rubber Duckers wasn’t caught by the agency at all:

“The one that stuck with us was a client testing their own form and finding it wasn’t coming through. The submission history showed it had been working at some point, so we never knew how long it had been down or how many enquiries were missed.”

Fixing a broken form usually takes minutes. The damage is everything around it. The client found the problem before the agency that maintains the site did, and nobody can say whether the form was down for a day or a month.

What form testing looks like inside a care plan

Rubber Duckers now runs every form across its sites on automated CheckView tests. Whatever tool you use, this is what makes form testing work as part of a care plan:

  • A real submission on a schedule. Each test fills in and submits the form the way a visitor would. Rubber Duckers tests client sites every week and its own site every day. Set the schedule by how much a missed enquiry would cost.
  • Check the email, not just the thank-you message. A success message only proves the browser got a response. Rubber Duckers’ tests also confirm the notification email was sent and delivered, which is exactly the failure that used to go unnoticed.
  • Keep test emails away from the client. By default, CheckView redirects a test’s notification email to its own test inbox instead of the form’s usual recipient. A weekly test doesn’t land in the client’s inbox looking like a fake enquiry.
  • Alert the agency first. A failing test notifies the team by email, Slack or webhook, so the agency hears about it before the client does.
  • Keep the evidence. Every run keeps screenshots of each step, a video recording and the browser console log, so the team can see where it broke without reproducing it. The test history shows when it started failing.

As Chris put it:

“CheckView closed that gap. Every care plan client’s forms are now tested automatically, and we get told the moment something breaks rather than finding out from the client.”

One less thing to think about

For an agency, the change is less about the tool than about what the care plan can promise. Form testing stops being a launch-day task and becomes part of the plan, running every week without anyone setting time aside for it.

“Knowing our care plan clients’ forms are being tested automatically is one less thing to think about each week.”

Read the full story: Building Form Testing Into Every Care Plan.

If your care plans cover more forms than you can check by hand, you can see what a scheduled test catches on your own sites with a free trial. Happy Testing!

Stop Losing Revenue to Broken Websites

CheckView helps businesses and agencies catch website issues before they cost leads, sales, and client trust.

Get Started