My developer is no longer available: how can I take over my application?
Which access to recover, what to do without a handover and how to scope the first assessment of a business application.
Start with what makes action possible
Your application still accepts orders, but the person maintaining it no longer responds. The first step is to recover access that will let someone else intervene. With this inventory, the incoming developer can examine the project and propose a date to take responsibility.
In a fictional order-management scenario, the first question would be: who can view errors and restore the current version to service? The business owner describes essential uses. The account owner then confirms which permissions are actually available. An old password or a code archive does not prove this access.
An owner for each access
- Immediate priority, management: identify domain, hosting and billing account holders; check account recovery contacts.
- Immediate priority, technical owner: obtain named access to the repository, logs and deployment; record the running version.
- Before working on data, operator: locate backups, their storage location and the last verified restoration.
- To prepare the takeover, business owner: describe a critical flow with its expected result and appoint the person who will validate it.
- For the handover, outgoing provider if available: supply the build procedure, configuration without secret values, external services and decisions still implicit.
For each entry, record the account owner, tested access, missing information, person responsible for retrieving it and deadline. Send secrets through an appropriate channel, not in an issue or repository.
With a handover, have the incoming person repeat the steps
If the provider remains reachable, arrange a session where the incoming developer builds a version and runs the demonstration flow. The outgoing person fills in what is missing. For a GitHub repository, ownership transfer has its own documented conditions and effects; it does not automatically transfer external services.
Without a handover, keep an explicit list of unknowns. An unexplained configuration variable, a scheduled process or an unrestored backup becomes a point to verify. Avoid changing production to discover its role. First prepare an isolated environment and an authorised data copy.
Request an initial continuity scope
The assessment should state what could be started, which flows were examined, observed risks and access still missing. It supports proposing a first fix or restart procedure with validation criteria.
Then agree support hours, how to report an incident and cover during absences. A critical application outside those hours requires additional arrangements. To begin the discussion, share its primary use, known technology stack and access inventory, openly flagging entries still blank.