--- title: Website Launch Support date: 2025-07-20T12:26:00+08:00 author: Jessica Kaitse canonical_url: "https://remedystudio.com.au/services/website-launch-support" section: Site Pages --- TRUSTED BY [ ![Black Duck Seat Covers }}](https://remedystudio.com.au/assets/uploads/images/logos/black-duck.png) ![Black Duck Seat Covers](data:image/gif;base64,R0lGODlhwgEBAPAAAP///yZFySH5BAEAAAEALAAAAADCAQEAAAIThI+py+0Po5y02ouz3rz7D4ZTAQA7) Black Duck Seat Covers Specialist Industry ](https://remedystudio.com.au/our-work/black-duck-seat-covers-website-rebuild) [ ![Trillion Trees }}](https://remedystudio.com.au/assets/uploads/images/logos/TrillionTreesLogo.png) ![Trillion Trees](data:image/gif;base64,R0lGODlhwgEBAPAAAP///yZFySH5BAEAAAEALAAAAADCAQEAAAIThI+py+0Po5y02ouz3rz7D4ZTAQA7) Trillion Trees Not-For-Profit ](https://remedystudio.com.au/our-work/trillion-trees-website-redesign) [ ![Whiteman Park }}](https://remedystudio.com.au/assets/uploads/images/logos/whiteman-park.png) ![Whiteman Park](data:image/gif;base64,R0lGODlhwgEBAPAAAP///yZFySH5BAEAAAEALAAAAADCAQEAAAIThI+py+0Po5y02ouz3rz7D4ZTAQA7) Whiteman Park Tourism ](https://remedystudio.com.au/our-work/whiteman-park-website-redesign) ![Parcel Propery }}](https://remedystudio.com.au/assets/uploads/images/logos/parcel.png) ![Parcel Propery](data:image/gif;base64,R0lGODlhwgEBAPAAAP///yZFySH5BAEAAAEALAAAAADCAQEAAAIThI+py+0Po5y02ouz3rz7D4ZTAQA7) Parcel Propery Property & Construction [ ![Comet Bay College }}](https://remedystudio.com.au/assets/uploads/images/logos/CometBayCollege.png) ![Comet Bay College](data:image/gif;base64,R0lGODlhwgEBAPAAAP///yZFySH5BAEAAAEALAAAAADCAQEAAAIThI+py+0Po5y02ouz3rz7D4ZTAQA7) Comet Bay College School ](https://remedystudio.com.au/our-work/comet-bay-college-website-design) --- ## Website handover done properly keeps the site working for years ![Centre Care }}](https://remedystudio.com.au/assets/uploads/images/CentreCare.png) ![Centre Care](data:image/gif;base64,R0lGODlhwgEBAPAAAP///yZFySH5BAEAAAEALAAAAADCAQEAAAIThI+py+0Po5y02ouz3rz7D4ZTAQA7) A proper website handover gives your organisation the confidence to manage the site once it is live. The team learns on the real CMS before the project closes, while the people who built it are still present and changes can still be made. The value is the structure around it: a recorded walkthrough, written guide, launch documentation, asset ownership, and post-launch checkpoints. Your team knows what was built, how to use it, what to watch after launch, and when to move into ongoing care. [ Get in touch ](https://remedystudio.com.au/start-a-new-project) **built in website support from the start** ## Launch support that keeps the website usable after go-live Every Remedy website project includes a structured handover and post-launch support period. Your team knows how to use the site, the organisation knows what it owns, and the first 90 days after launch have a clear rhythm. 01 ### The website works for whoever is in the role Your organisation receives handover materials that help future staff understand the website without starting from scratch. The recorded training video shows how the CMS works in practice, and the launch documentation explains what was delivered, where key access details sit, and what the team needs to know after go-live. This matters because the person who attends training will not always be the person managing the website. The handover gives the next person a real starting point. ![Blackduck }}](https://remedystudio.com.au/assets/uploads/images/blackduck.jpg) ![Blackduck](data:image/gif;base64,R0lGODlhwgEBAPAAAP///yZFySH5BAEAAAEALAAAAADCAQEAAAIThI+py+0Po5y02ouz3rz7D4ZTAQA7) 02 ### The team can manage the website before launch Training runs during the build, on the real site, while the people who built it are still present. That timing matters: questions get answered while context is live, small adjustments are made while they are easy to make, and the team arrives at launch having already managed the site. ![REMEDYNOV2519 }}](https://remedystudio.com.au/assets/uploads/images/RemedyPhotos2025/REMEDYNOV2519.jpg) ![REMEDYNOV2519](data:image/gif;base64,R0lGODlhwgEBAPAAAP///yZFySH5BAEAAAEALAAAAADCAQEAAAIThI+py+0Po5y02ouz3rz7D4ZTAQA7) 03 ### 3 post-launch check points keep things running smoothly Three post-launch check points are built into every project: 30 days for a first read on how the site is performing in real use, 60 days for a care plan decision based on actual data rather than projection, and 90 days to formally close the in-scope period and confirm the ongoing arrangement. Each has a defined agenda, so the conversation produces a specific outcome. ![Georgiana Molloy }}](https://remedystudio.com.au/assets/uploads/images/GeorgianaMolloy.webp) ![Georgiana Molloy](data:image/gif;base64,R0lGODlhwgEBAPAAAP///yZFySH5BAEAAAEALAAAAADCAQEAAAIThI+py+0Po5y02ouz3rz7D4ZTAQA7) **website launch features** ## What every website project launch includes Every Remedy website project finishes with the structure, records and checkpoints needed to keep the site useful after go-live. The handover package is created while the project knowledge is still fresh, so your team keeps the thinking, access, training and next steps that usually disappear once a build is closed. ### CMS training during the build A team who can update the site before launch, trained while the system is still being shaped and the build team is present to answer questions ### Official documentation A plain-English reference covering every key decision and how the site works, written by the build team while the project is fresh, for the current team and whoever comes next ### Website training documentation A permanent record of how to manage the site, available for every future staff member without needing to restart from scratch ### Documented workflows The processes for managing content are written down, so the organisation has an operating guide. ### Redirect map Search traffic carries across cleanly when URLs change, so the visibility built up over time is not lost in the transition to a new site ### 30-day review An evidence-based read on how the site is performing in the real world, the natural point to introduce Insight reporting or SEO if not already in scope ### 60-day review A review plan based on two months of real usage, so the ongoing arrangement reflects what the site actually needs ### 90-day project close The in-scope support period formally closed, outstanding items documented, and a clear ongoing arrangement confirmed [ Find out more about our website reporting ](https://remedystudio.com.au/services/remedy-website-reporting) **how it works** ## What each stage produces 01 ### Website training during the build At the end of this stage, the team has used the real site, asked questions while the people who built it are present, and confirmed final adjustments. By go-live, content updates are routine. 02 ### Formal handover package. A plain-English reference covering every key decision and how the site works, written by the build team while the project is fresh, for the current team and whoever comes next 03 ### 30-day review. At the end of this stage, the organisation has a clear read on how the site is performing and a structured conversation about what comes next. 04 ### 60-day review. At the end of this stage, the organisation has an evidence-based picture of the site's maintenance needs from two months of real usage, and clarity on the care plan arrangement. 05 ### 90-day project close. At the end of this stage, the in-scope support period is formally closed, outstanding items are documented, and the project moves into a sustained relationship. ![REMEDYNOV2517 }}](https://remedystudio.com.au/assets/uploads/images/RemedyPhotos2025/REMEDYNOV2517.jpg) ![REMEDYNOV2517](data:image/gif;base64,R0lGODlhwgEBAPAAAP///yZFySH5BAEAAAEALAAAAADCAQEAAAIThI+py+0Po5y02ouz3rz7D4ZTAQA7) --- **Frequently asked questions about website post-launch support** ### What is covered during the in-scope post-launch support period? In-scope post-launch support covers issues arising from the build itself – bugs, unexpected behaviour, or adjustments needed once real people start using the site. The boundary between in-scope support and new work is agreed during scoping and documented before launch. The 90-day milestone marks the end of the in-scope period, with that boundary confirmed, so the conversation is structural, not contentious. ### What happens if the person managing the site leaves? The launch document, training video, and documented workflows give the next person a usable reference from day one, produced by the build team while the project is fresh, so the documentation reflects the actual site rather than a reconstruction from memory ### Does every project get the same handover structure regardless of size? Yes. The training session, handover package, launch letter, training video, and 30/60/90 structure are standard for every project, but each process changes depending on the size. ## Start with a conversation. If you're planning a website rebuild or preparing for future growth, we'll help you map the next stage with clarity and confidence. It starts with a conversation about where your organisation is heading and how your website can keep up. [ Talk to Remedy ](/contact-us)