# Tradie IT handover checklist [Read the public page](https://www.adarkcloud.com.au/guides/tradie-it-handover-checklist) Record the accounts, job files and devices your trades business needs to keep working when a person, phone or supplier changes. By Josh C, A Dark Cloud Creative Published 2026-10-08 A useful trades IT handover records who owns each service, which job records matter, how a replacement device gets access and who handles a failure. Confirm each entry with a task or record. Keep passwords and customer documents out of the worksheet. ## Your printable worksheet Record business account ownership, job file access and device handover, then agree who will follow up the gaps. - [Download the printable PDF](https://www.adarkcloud.com.au/downloads/tradie-it-handover-checklist.pdf) You can read the guide and download the worksheet without an email sign up. Keep passwords, recovery codes and private customer records out of it. ### Email, domain and quoting Confirm business ownership and approved access. Use a harmless sample to check the quote and invoice handover. ### Current job files Check the shared location and who can update it. Use an empty test file and record the result without job or customer details. ### Phone and laptop handover Confirm the device owner, approved access and recovery contact. Agree which access should stay or be removed before changes. Mark what you can verify and give each gap an owner. If you want help with an item, describe the task and how it affects your work. ## Set the handover and its owner Write down what is changing, the date and the person who approves the handover. That might be a replacement phone, a departing crew member or a new website supplier. List the work that must still happen afterwards, such as opening the current drawing, receiving a customer enquiry or issuing a quote. Record the person who will check each task and a date for that check. A verbal assurance that everything is sorted is difficult to use when a problem appears later. This worksheet records ownership and follow up work; it is not a security assessment. ## Identify business owned accounts List the domain registrar, email platform, website host and job applications by name. Record the business owner, billing contact and who currently administers each service. Note whether a supplier is involved and which business controlled recovery method exists. Do not put the password or recovery code in the list. Confirm the entry against the actual account or an agreed supplier handover. If you cannot identify the owner, leave that as an open task. An invoice describes a purchase, but it may not identify the account that controls the service. ## Locate the current job records Choose a representative job and record where its current drawing, photos and supporting documents belong. Identify who approves a revised document and how the crew knows which version to use. Note any work held in personal storage or messages that has not reached the agreed business location. Ask the office and a site user to find the same approved test file on their normal devices. Record the result and any access gap. Use a safe example where possible and avoid distributing customer documents simply to demonstrate a problem. ## Test the device where it will be used Record the phone, tablet or laptop assigned to the person, the supported work apps and the accounts needed to sign in. Check the ordinary task using the connection available in the intended location. An office WiFi test may not represent a job with limited mobile coverage. If the work requires offline access, agree what can be used without a connection and how changes return to the shared record. Confirm that behaviour in the actual application before relying on it. Record who handles device updates, a loss or a replacement. ## Follow one quote or enquiry through Use a labelled test to confirm that the website enquiry reaches an inbox somebody checks. Where the job application sends quotes or invoices, agree a safe test and confirm its sender and recipient. Keep the result with the handover rather than assuming that successful sign in proves delivery. Record the shared address, who monitors it and who takes over an outstanding request. A product sending the message may need its own vendor to investigate. Do not change mail routing or application settings until the affected senders and access have been identified. ## Record recovery you can verify Identify which important job records need a recoverable copy, who maintains it and the evidence of a suitable restore test. Record the date and outcome, without copying the recovered customer information into the worksheet. A sync indicator or an account that opens does not confirm that a deleted file can be restored. If recovery is unverified, give the task an owner and agree what can safely be tested. The person who handles the test needs the appropriate access and a scope that avoids overwriting current work. Keep the resulting recovery instructions in a protected business location. ## Approve what happens to old access For a departure or supplier change, list the services the person could reach and the business records that need to remain. Agree who receives those records and when access ends. Check the job application, website and local devices as well as the main email subscription. Record the change and its verification. Do not delete an account or wipe a phone simply to finish the checklist. Subscription removal, personal device handling and record retention need an approved decision and the appropriate platform instructions. ## Leave a usable supplier handover List the IT contact, application vendor, carrier and hardware supplier relevant to the job. Record the product or service they support and the route for reporting a fault. Keep agreed hours and response commitments with the actual arrangement rather than assuming every provider offers urgent help. For each open task, record the affected service, owner, evidence needed and next review date. A Dark Cloud Creative can discuss the IT investigation from Perth, with remote support across Australia where it suits the work. Send the gap and its effect on the job, without credentials or customer records. ## Should I include passwords in the handover worksheet? No. Record the service owner, recovery arrangement and protected location of access instructions. Share any credentials through an appropriate method agreed with the person doing the work. ## Can I use this when changing a website or IT supplier? Yes. Confirm the domain, hosting, email and application owners, the required records and the access that changes. A supplier exit may need additional contractual or technical work, so use the worksheet to identify the tasks rather than assuming it completes the transfer. ## What if the crew cannot open a file on site? Record the device, application, file location and available connection. Check whether the issue is access, the app or connectivity before changing the shared setup. Offline behaviour needs confirmation for the actual product. ## Further reading - [ASD small business cyber security resources](https://www.cyber.gov.au/small-business-hub) - [Microsoft shared file permissions](https://learn.microsoft.com/en-us/sharepoint/modern-experience-sharing-permissions) ## Useful next steps - [IT support for tradies](https://www.adarkcloud.com.au/industries/tradies) - [Business email support](https://www.adarkcloud.com.au/services/business-email-support) - [OneDrive support](https://www.adarkcloud.com.au/services/onedrive-support) - [Backup and recovery support](https://www.adarkcloud.com.au/services/backups-and-security) - [Prepare a support request](https://www.adarkcloud.com.au/guides/before-you-ask-for-it-help) Reviewed 2026-10-08 - [Ask for IT help](https://www.adarkcloud.com.au/contact) - [Check your IT basics](https://www.adarkcloud.com.au/tools/it-health-check)