Calgary website maintenance: make the monthly scope explicit
A useful Calgary website maintenance proposal makes recurring responsibility testable. Before comparing plans, record the platform, hosting relationship, domain and DNS ownership, business-critical pages, forms, analytics, approval contacts, backup evidence, connected vendors, and current faults.
Included recurring work
List each agreed update, check, report, content allowance, and monitoring task with its frequency and owner. Do not assume that hosting, support, maintenance, and new development are the same service.
Requests and releases
Define the request channel, authorised approvers, response targets, maintenance windows, post-change checks, exception handling, and rollback path that apply under the agreement.
Recovery and account control
Keep the domain, hosting, analytics, billing, code, and recovery accounts under customer ownership. Identify what is backed up, who can restore it, and when a restoration check was last recorded; a successful backup job alone is not recovery evidence.
Excluded and separately scoped work
Keep routine care distinct from redesigns, migrations, new features and substantial repairs. State whether takeover repairs, malware cleanup, accessibility remediation, new integrations, and substantial content work need a separate estimate.
North Star has no Calgary office. Recurring care is delivered remotely from its Prince George and Grande Prairie operations. Any travel, physical access, or locally coordinated work is identified and scoped separately before scheduling.
Compare the published care tiers, then request a Calgary website maintenance scope review with the website URL, platform, current concern, required recurring work, and approval contact. Do not send passwords through the enquiry form.