Changing the maintainer of the site requires organizing access, documentation and open cases. The new team should know the status of the service before it starts to make bigger improvements.
Prepare the transfer range
Collect information about the system, hosting, domain, post office and services connected to the site. Save which accounts belong to the company and who can give access. Do not upload the entire set of passwords in a regular message; specify the appropriate way to transfer permissions.
Also include source materials, project files and licensing rules in the documentation. Without one supplement or forgotten renewal may affect the possibility of further work.
Describe the status, not just the wish list
Report known errors, planned changes and previous findings. Separate the problem already occurring from the new idea. The new maintainer needs a reference point to assess the effects of later actions.
For example, occasional lack of delivery of the form is worth describing with date and scope of observation. The order itself “to improve contact” does not explain whether it is about appearance, dispatch or organization of service of the message.
Check basic functions on acquisition
Agree a short check:
- the public and the panel;
- the most important forms;
- search and files;
- availability of copies;
- connections to external services;
- lists of persons with rights.
Save the result before major changes. If there is a test environment, confirm its role and separate from the public version. If it is not there, set a way to prepare a safe space for work.
Close change of responsibility
Specify the date of the acquisition, the notification channel and decision-makers. Access the previous contractors according to the end of their tasks. The new care agreement should clearly explain the scope and method of ordering additional work. Useful materials concern Scope of care i hosting and contingency plan.
