01
Write the assignment before listing the accounts
Describe the specific pages or content the supplier is expected to update and identify who will accept the work. Then list the systems that the assignment actually involves. In the example, editing website copy may require a publishing workspace, but the team should consider separately whether other accounts are needed. Give each requested access a stated purpose. Keeping the task and the request together makes it easier for the person approving access to understand what they are enabling and to ask about unexplained items.
02
Record the owner and the agreed review point
For each system, name the internal person responsible for checking the access decision and record the intended end date or project milestone. Include a way to identify the supplier account without placing passwords in the handover document. The example might use completion of the agreed content update as a review point. Record any extension as a new decision with its reason. This gives the team a concrete event to revisit rather than relying on someone to remember an open-ended arrangement.
03
Close the handover with a checked outcome
When the assignment reaches its review point, confirm the work status and ask the responsible owner to check the access in the actual system. Record what was checked, when and whether anything remains open. If another piece of work is planned, describe its access needs separately rather than assuming the earlier arrangement covers it. The resulting record connects purpose, responsibility and closure. It helps a future colleague understand the decision while leaving technical enforcement and any unresolved configuration issues with the appropriate system owner.