Routine Website Updates
Agreed content, component and configuration updates without reopening the whole project.
We manage agreed updates, fixes and checks after a website goes live.
NovaCraft reviews requests, prioritises impact, tests supported changes and documents releases so ongoing website maintenance remains controlled and visible.
Maintenance is not a promise that nothing will ever break. It is a clear process for reviewing, prioritising and resolving the work that appears after launch.
We define what is covered, how requests are handled and when larger changes should become a separate project.
Support scope is agreed around the platform, team and level of ongoing change.
Agreed content, component and configuration updates without reopening the whole project.
Investigation and resolution of reproducible issues within the supported codebase.
Planned updates where frameworks, packages or platforms need routine maintenance.
Periodic checks for obvious regressions in loading, assets and front-end behaviour.
Review alerts and reported issues so the right work is prioritised rather than every request becoming urgent.
Small enhancements informed by real usage, feedback and changing business priorities.
Support tools are selected around the existing stack so updates can be reviewed, tested and documented before release.
Used where the supported website already runs on these tools, allowing changes to be reviewed and deployed with version history.
Used to identify regressions, technical search issues and performance changes that may need maintenance work.
Used to record requests, approvals, recurring tasks, design references and changes that need a clear client handover.
Teams whose website changes regularly but does not justify a full internal development team.
Products that need structured iteration after an initial launch.
Teams running campaigns and content that require dependable website support.
A natural continuation when the launch needs ongoing care and improvement.
A maintenance plan may include:
The delivery method stays visible to both teams. Scope, responsibilities, feedback, approvals and handover are documented from the start.
We document deliverables, responsibilities, dependencies, review points and exclusions before production begins, so every participant works from the same agreed scope.
Files, notes, decisions, links and current priorities stay in one shared workspace, giving both teams a consistent source of project information.
Each week we record completed work, current tasks, blockers, decisions required and the next review point, keeping progress visible without constant meetings.
Feedback is consolidated by the client decision owner, reviewed against the agreed objective, then recorded before the next production stage begins.
Requests outside the approved scope are documented with their impact on timing, effort and dependencies before either team commits to the change.
Before handover, we review agreed acceptance criteria, test required journeys, document remaining actions and confirm ownership for launch or ongoing support.
Working instructions
Coverage is agreed before the plan begins and can include routine updates, supported technical fixes, monitoring and small improvements.
Sometimes. We first review the existing stack, access, code quality and known issues before confirming support.
Usually not. Larger features or redesigns are scoped separately so maintenance capacity remains predictable.
Not by default. Any availability or response commitment is agreed explicitly in the support plan rather than implied on the website.
Tell us what platform you are running, what support you need and whether NovaCraft built the original project.
We usually reply within one business day.