Make a responsibility map
- Domain: the business owns the registrar account; record the renewal date and the person monitoring it.
- Hosting and CMS: list the environment, version, modules and owners of payments, updates and support.
- Forms, email, CRM and payments: give each channel an owner and a separate verification method.
- Access: grant the required permissions for an agreed period; document revocation and handover without putting passwords in an ordinary document.
Test restoration, not the presence of a file
Agree what the backup contains: files, a database where applicable and necessary settings. Record its location, retention period and owner. Match the CMS procedure to the installed version and documentation; another system’s instructions do not prove compatibility.
Restore into an agreed separate environment. Check pages, images, sign-in, forms and data relationships. Restrict test notifications and payment actions beforehand so the copy cannot contact real customers. Record the result and test time.
Official source: 1C-Bitrix: environment, updates and migration
Use the same scenario before and after a change
Before an update, preserve the original version and a reproducible symptom. Assess the change in a copy, then agree a production window and rollback. After installation, test the same scenario that passed beforehand.
For a service website this means a mobile page and an inquiry; for a store, the catalogue, cart and an agreed test order. Checking only the home page does not prove forms, email or payment work. A problem in one layer does not justify clearing every cache immediately.
Send an incident record, not “everything is broken”
Hypothetical example: “The contact page displays an error after Send; 13 October, 10:20, mobile browser; no inquiry reached the test channel.” This helps reproduce the issue without exposing customer data.
Include the URL, steps, expected and actual outcome, last successful test and recent changes. Remove personal information from screenshots. Share passwords or access keys through an agreed protected method, separately from the incident record.
Agree what completed work means
Separate regular checks, fixing an agreed issue, website development and external service costs. Agree hours, working periods and response times; “support” does not automatically mean 24/7 or a fixed SLA.
A report should name the change, tested scenario, result and next owner. BSMGROUP’s Bitrix/ASPRO support is a separate service; this general checklist does not promise support for every CMS. After handover, the business owner should know where access is managed and how to verify the result.
Discuss your project
Tell us your goal, languages and required functions. We will agree on the scope and next steps.