Skip to content

Support & Maintenance

This SOP covers how Inkblot handles ongoing support, bug fixes, and maintenance for live projects. It is part of the Inkblot SOP Library — a reference set of SOPs that are activated selectively as needed.

After a project launches, Inkblot provides ongoing support to ensure the site continues to perform well and evolves with the client’s needs. Support work ranges from critical bug fixes to minor content updates and feature enhancements. Projects in the Live or Live - Pending Changes status in ClickUp are covered by this process.

TierDescriptionExamples
CriticalSite is down or a core function is broken, affecting end usersServer errors, payment processing failure, site inaccessible
HighMajor functionality issue that significantly impacts usabilityBroken forms, navigation failures, major layout issues
MediumNoticeable issue with a workaround availableMinor display glitches, non-critical feature bugs, content rendering issues
LowCosmetic issues or minor improvementsTypos, spacing adjustments, small visual polish
Feature RequestNew functionality or enhancements beyond the original scopeNew page templates, integrations, additional features
TierResponse TimeResolution Target
CriticalWithin 4 business hoursWithin 1 business day
HighWithin 1 business dayWithin 3 business days
MediumWithin 2 business daysWithin 1 week
LowWithin 1 weekNext available sprint/cycle
Feature RequestWithin 1 week (acknowledgement)Scoped and scheduled separately
  • Clients report issues via email to their primary Inkblot contact, or via ClickUp if they have workspace access
  • Adriana (Project & Operations Manager) ensures the issue is logged as a task in ClickUp under the relevant project
  • Include: description of the issue, steps to reproduce, screenshots or screen recordings, urgency level
  • Jonathan (Web Dev Lead) reviews the issue and assigns a priority tier
  • Determine whether the issue is a bug (covered under support) or a feature request (needs separate scoping)
  • Assign the task to the appropriate team member
  • Communicate the expected timeline to the client
  • Developer creates a fix branch (e.g., fix/broken-contact-form)
  • Follow the standard Development Workflow and Deployment SOP
  • For critical issues: expedite the review process; Jonathan can review and merge directly
  • Verify the fix on the Vercel preview before deploying to production
  • Deploy to production and confirm the issue is resolved
  • Acknowledge receipt of the issue within the response time for its tier
  • Provide updates when the fix is in progress and when it has been deployed
  • Confirm resolution with the client and close the ClickUp task
  • For feature requests: provide a summary of scope, estimated effort, and proposed timeline

Regular maintenance tasks to keep live sites healthy:

TaskFrequencyOwner
Dependency updates — Update npm packages, Astro, Sanity, and other dependenciesMonthlyJonathan / Lene
Security patches — Apply critical security updatesAs needed (immediate)Jonathan
Performance review — Check Core Web Vitals and page load timesQuarterlyJonathan
Content audit — Review for outdated content or broken linksQuarterlyAdriana (coordinate with client)
Backup verification — Confirm CMS data and code backups are currentMonthlyJonathan
SSL/Domain renewal — Ensure SSL certificates and domains are renewed before expiryAs neededJonathan

Jonathan de Kock (Web Dev Lead) owns the technical support and maintenance process. Adriana van Rooyen (Project & Operations Manager) coordinates client communication and issue logging.