Developer Checklist

This field is for validation purposes and should be left unchanged.

Internal developer checklist. Complete this form for every Staging-to-Production push. Tick each item only after it has been verified. A second engineer must independently sign off in section 7.

1. Push Details

Linked Change Request ID(Required)

Site / Domain(Required)

Push Date(Required)

Push Time(Required)

Push Engineer Name(Required)

Push Engineer Email(Required)

Push Method Used(Required)

2. Pre-Push Checklist

Tick each item only after it has been verified.

Pre-Push Items

Approved Change Request received from client (signed).

Push date and time confirmed with client (outside business hours preferred).

Full backup of PRODUCTION taken via Cloudways (On-Demand). Backup ID recorded below.

Full backup of STAGING taken via Cloudways.

Plugin versions on Staging match Production (no version mismatch).

Staging is still noindex: robots.txt, Discourage setting, HTTP Basic Auth all active.

Final client review of Staging completed and signed off.

3. Backups Captured (Required Evidence)

Cloudways Backup ID / Reference(Required)

4. Push Process Checklist

Tick each step actually performed during the push.

Push Process Items

Logged into Cloudways (or chosen push tool) for the application.

Selected Push Web Application and Database Changes.

[CRITICAL] On the Database Tables screen, UNTICKED: wp_users, wp_usermeta , wp_gf all options(to preserve production-specific settings, users,metadata and gravity forms).

Reviewed the file-change preview against the Change Request scope.

Clicked Proceed and waited for push completion.

Screenshot of push success confirmation captured.

5. Post-Push Verification

Critical gate - any unchecked item blocks the push from being signed off.

Post-Push Items

6. Issues and Notes

Issues Encountered During Push

Rollback Performed?(Required)

Yes - rollback performed (explain in notes below)

Additional Notes

7. Independent Reviewer Sign-Off

A second ITSOFT engineer must independently verify the post-push state of production.

Reviewer Name(Required)

Reviewer Email(Required)

Reviewer Confirmation

I confirm I have independently verified all post-push items above and Production is operating correctly.

8. Attachments

Attach push screenshots (Cloudways success screen, robots.txt, smoke test, etc.)

Screenshots / Evidence

Drop files here or

Accepted file types: jpg, jpeg, png, gif, webp, pdf, doc, docx, xlsx, xls, csv, txt, Max. file size: 100 MB, Max. files: 10.

Allowed: images (jpg, png, gif, webp), PDFs, docs (doc, docx, xlsx, csv, txt). Up to 10 files.