Website onboarding
Review the platform, hosting, access, dependencies, and important user journeys to establish what the maintenance service covers.
Norml helps teams keep their websites maintained and checked as content, software, and business needs change. We agree the coverage for updates, backups, functional QA, technical support, and ongoing improvements so recurring work has an owner.
Book a callSoftware updates need compatibility checks before they reach the live website.
Forms, navigation, and other important journeys need regular verification.
Backups need clear ownership and an understood recovery process.
Content changes and new requests need an organized review and release process.
Your team needs a technical contact who understands the website’s setup.
Maintenance starts with a review of the website, access, hosting, and known issues. The agreed coverage defines recurring checks, supported systems, how requests enter the queue, and which larger changes need a separate scope.
Review the platform, hosting, access, dependencies, and important user journeys to establish what the maintenance service covers.
Manage in-scope platform and plugin updates with compatibility checks and a rollback approach appropriate to the website.
Check backup ownership, retention, and restore arrangements for the systems included in the agreement.
Verify priority pages, forms, navigation, and other agreed journeys so issues can be recorded and addressed.
Investigate reported problems, document the findings, and agree the corrective work according to the support scope.
Organize approved website changes with clear requirements, review, release checks, and a record of what changed.
The agreed scope identifies which of these deliverables your project needs.
A website access and maintenance scope record.
An agreed recurring update and QA checklist.
Backup and recovery responsibilities.
Issue findings and records of completed work.
Verified releases for approved changes.
A prioritized list of follow-up improvements.
Our process
Confirm access, platform versions, hosting, backup arrangements, important journeys, and known issues.
[ 01 ]Define recurring tasks, request handling, supported systems, and ownership of external dependencies.
[ 02 ]Perform the agreed checks and updates, keeping records of findings and changes.
[ 03 ]Check affected journeys after changes and summarize completed work, unresolved issues, and required decisions.
[ 04 ]Review new requests and recurring findings, then agree which improvements belong in the upcoming work.
[ 05 ]