We assemble a complete handover bundle for an incoming developer — technical architecture, code documentation, credentials, and access — bringing together what would otherwise be several separate documents into one coordinated package for a genuine transition.
Onboarding pack for incoming developer
A coordinated handover bundle for an incoming developer — architecture, code docs, and access, together.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Comprehensive access to the site, code, hosting, and related accounts
- Confirmation of the incoming developer’s actual technical background, so detail is pitched appropriately
- Your timeline for the handover
This or something else?
| You’re handing the site off to a new developer and want a complete, coordinated package | This fix covers it |
| You only need one specific document, not the full bundle | The relevant individual document instead — likely more cost-effective if that’s genuinely all you need |
| You want this for your own team’s reference, not an actual external handover | Site documentation pack, the more general version |
| The incoming developer needs training, not just documentation | Worth discussing directly — documentation supports a handover, but genuine hands-on training is different work |
What we do
- Confirm which documents genuinely need to be part of this bundle for your situation
- Produce or compile technical architecture, code documentation, and credentials access as needed
- Coordinate these into one clear, organised package
- Review the complete bundle for consistency and completeness
- Deliver in a format suited to an actual handover
What is included
- A coordinated bundle of the documents relevant to your handover
- Consistency and completeness review across the bundle
- Delivery suited to an actual transition
Not included
- Hands-on training or a live walkthrough with the incoming developer, beyond the documentation itself
- Ongoing support during the transition period, unless separately arranged
- Documents beyond what’s confirmed as relevant to your specific handover
- Updates to the bundle after the handover is complete
Questions about this fix
What documents actually make up this bundle?
It depends on your specific situation — commonly a technical architecture overview, code-level documentation, and a credentials and access document, though we'd confirm exactly what's relevant for your handover.
Is this cheaper than ordering the individual documents separately?
Often more efficient when bundled together, since reviewing the site comprehensively once serves multiple documents rather than repeating that review for each — worth discussing your specific needs to confirm.
Will you also train the incoming developer directly?
Not as part of this fix — this produces the documentation itself; direct training or a live walkthrough would be separate, additional work.
How current is this by the time the developer actually starts?
It reflects the site as of when it's compiled — if there's a significant gap before the handover actually happens, worth flagging so we can confirm nothing material has changed.
What if the incoming developer is very experienced and needs less hand-holding?
We'd pitch the detail level accordingly — confirming their background upfront helps us avoid over-explaining basics they already know.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.