You do not need to read the framework to run the next two weeks. You do need to know which missing facts turn a small request into an incident on a call you did not prepare for. The pack below is for taking over a product you did not build. It is not the creative brief for a new campaign.

The agency says the site runs on Laravel and the change is small, so the date stays where it is. You are on the receiving side of this: no technical director on your side, the previous developer stopped answering, and the person who opens the project for the first time is someone you hired last week. They open it the night before the date. There is no second environment. The production password sits in an old chat. The change touches payments, and nobody wrote that into the brief. The database holds records for more than one customer, and nobody has said whether that is expected. Then a normal question arrives on the call, and this time you answer it. If the work is a new page or a new flow, attach the brief a developer can start from. Use both when an existing application and a new request arrive together. Use this one whenever the code already runs somewhere your customers can reach.

1. Where the production surprise really starts

Usually you hold what the agency showed you: the copy, the layout, the page list. The risky part lives elsewhere, in the repository you were not given, on a server that someone else pays for, and in jobs that run later without anyone watching. The sentence that tells a developer the shape of the code tells them nothing about which branch is live, whether a copy exists, or which click takes money.

The date makes the other half of the problem. It came from the visible part of the work, from a promise the agency made while looking at a screen. The developer meets the hidden part the night before release, and the fastest way to keep the date is to try the change on the live site. That is the quiet patch. It looks like discipline, and it puts your real orders inside the test.

If there is nowhere to try the change except production, write that in the first message and move the date before anyone edits the live server. The owner-side version of that decision is covered in why a missing staging site is not a reason to edit live.

Write the gap before you repeat the date to anyone:

2. Ownership, without passwords in chat

Taking over someone else’s Laravel means the code, hosting, domain, payments and mail are not yours yet. Parts of them may not be yours even after you pay the agency, because a previous contractor still holds the accounts. A developer cannot work safely with access they do not have, and production secrets should not arrive in the same thread where people discuss a layout.

List the systems by name: repository, hosting, domain, payments, mail, queue, scheduled job. For each one, write down who can grant access and who can revoke it, and make sure that person answers to you rather than to someone who left. Give access through accounts that you can close later. Do not paste a production password, a payment secret or a copy of the customer database into chat, and do not put it in the brief either.

A second environment holding a full copy of real customer records on someone’s laptop is not a safer test setup. It is one more place where data can leak.

When you take the project over completely, put this list next to the handover checklist the developer you bring in will use. Your part is to arrive with the owners already named, so that checklist does not start from an empty inbox.

3. Say clearly whether a second environment exists

This is the fact that shows up too late most of the time. The developer asks where to test the change, the honest answer is the live site, and the date is tomorrow. Say that on day one, in writing, to the agency and to the developer. A missing environment is not a failure on your side. Pretending it exists until the evening before release is how your date becomes their incident.

If a second environment does exist, describe it plainly: the URL, whose account opens it, and whether its data comes from a restored backup or from a toy dataset. A toy dataset will not show the bug that depends on a real order. A restored backup only counts if someone has actually restored it at least once. If nobody has done that, write “not proved” instead of “we have backups”.

4. Name the flows that can hurt the business

You can describe these without opening the code. Which click takes money? Which form creates the lead or the record your team reports on? Which night job sends mail, rebuilds a file, or charges again? Which of those did the previous developer call fragile?

If you cannot answer, the change is not small yet. Small is something you earn after you name the neighbours of the edit.

If more than one of your customers shares the application, say that directly. A fix on an internal staff page can still show one customer another customer’s rows, or a job can send the wrong file. You do not need to decide how the data is separated, but you do need to tell the developer that the separation exists and must be checked again. Where that usually goes wrong is covered in where shared customer data usually mixes.

An inherited system that already has problems should be steadied before new features are added. If this Laravel arrived half-broken, do not put stabilization and a campaign launch onto one Friday. Tell the agency and the customers about the order. You will sound more reliable on the second call than on the first one that treated both tasks as one.

5. Review on the copy, then name the release

Your review means the checks from the pack were done on the second environment, and you watched at least one of them yourself. The developer shows the payment step or the lead step, or the closest safe substitute, and you compare it with the sentence in the pack.

Production is a separate, named release after that. It has a time and a person who checks it again once it is live, and it is not the place for the first attempt. It is not a surprise waiting for both of you on a call.

Keep passwords out of that note, and keep private customer records out of the screenshot you drop into the channel. A handover that protects the date but leaks the data did not avoid a production surprise. It only changed which surprise you got.

When to bring the developer in before the date

Bring the developer in before the date is fixed when the change touches payments, a database shared by customers, or a system you cannot describe. Do the same whenever a second environment is not confirmed. A developer who arrives after the agency has said “almost done” inherits the surprise with you, and that is a bad start that you can avoid.

I take on the technical side of that handover for owners: which systems you now control, where the change can be tested, which flows can hurt, and then the change itself. Services cover a defined project or ongoing collaboration on Laravel and backend systems that already have customers. Selected work shows the kind of inherited product these handovers usually land on. The Laravel handover service describes what the first week looks like. If you need a developer to take the project over, write to me: send the ownership list, whether a second environment exists, and the date you have or have not promised. The credentials can follow later, once the work has started.