Free checklist

NZ SME tech checklist

A practical setup checklist for tradies, appointment businesses, consultants, and small teams that want their website, email, phones, accounts, and support notes to be easier to run in Christchurch and greater Christchurch.

Use this to start a quote

Setup foundations

The checks that prevent messy tech later

This is not a replacement for a full technical audit, but it gives small businesses a clear starting point before buying tools, launching a site, changing DNS, or setting up phones and email.

Website

Make the enquiry path obvious

  • Clear services, areas served, and contact options.
  • Mobile-friendly layout with fast access to quote or call actions.
  • Basic SEO titles, descriptions, sitemap, and internal links.
Email

Use proper business email

  • Domain email instead of personal-only email addresses.
  • SPF, DKIM, and DMARC checked before sending important mail.
  • Mailbox handover notes for phones, laptops, and webmail.
Phones

Reduce missed calls

  • VoIP routing that can send calls to the right person or mobile.
  • Voicemail and after-hours handling that customers understand.
  • Call quality checks for SIP, Wi-Fi, fibre, and router issues.
Accounts

Keep access tidy

  • Separate staff accounts instead of shared logins where possible.
  • MFA on email, admin tools, social profiles, and cloud services.
  • Recovery details documented before an account is locked out.
Network

Know what to check first

  • Separate Wi-Fi, router, fibre, DNS, and provider symptoms.
  • Keep router, ISP, domain, DNS, and VoIP provider details handy.
  • Capture useful evidence before escalating a fault.
Handover

Document the setup

  • Record domains, hosting, DNS, email, phone, and software providers.
  • Keep setup notes readable for non-technical staff.
  • Review the notes after any major change or provider move.

Practical handover

What to gather before changing providers or asking for help

Most SME technology problems become easier to solve when the basic ownership and access details are written down first. This section is designed as a quick handover pack for owners, office managers, and support people.

Domains and hosting Note the registrar, hosting company, cPanel or control-panel login path, renewal date, DNS provider, and the person who can approve changes.
Email and Microsoft 365 Record the admin portal, tenant name, licensed users, shared mailboxes, aliases, recovery options, and who has multifactor authentication enabled.
Phones and internet Keep the ISP account number, fibre ONT location, router model, VoIP provider, call-routing notes, and after-hours voicemail wording together.
Security basics Check password-manager use, MFA coverage, admin account separation, recovery email addresses, and who receives security or billing alerts.
Backups and continuity Write down what is backed up, where it is stored, how often it runs, who checks it, and how a restore would be tested after a laptop or account problem.
Change history Keep a simple dated log of DNS edits, website changes, email migrations, router replacements, provider tickets, and support handovers.

First-pass triage

How to separate common symptoms before escalating

A short triage note can save time because the same symptom can come from several places. For example, an email delivery problem may be DNS, mailbox authentication, spam filtering, a compromised account, or a sender-reputation issue.

Email not arriving

Check DNS, filters, and account access

  • Confirm MX, SPF, DKIM, and DMARC records before changing mail settings.
  • Check quarantine, forwarding rules, storage limits, and recent password resets.
  • Save message headers or error text before raising a provider ticket.
Website issue

Separate hosting, DNS, and browser symptoms

  • Test the site on mobile data as well as office Wi-Fi.
  • Confirm whether the domain, hosting account, SSL certificate, or CMS changed recently.
  • Capture the exact URL, screenshot, and error message before making changes.
Calls dropping

Check the network before blaming the handset

  • Record whether call issues happen on all phones or only one device.
  • Check fibre status, router logs, Wi-Fi coverage, and SIP registration state.
  • Note the time of day, caller number, and whether audio fails one-way or both ways.

Service lanes

Choose the right support path from the checklist

Once the first-pass notes are written down, route the issue to the closest support lane. That avoids changing DNS for a device problem, rebuilding a laptop for a Microsoft 365 issue, or opening a provider ticket before the evidence is ready.

Services overview

Use the services hub when the symptom crosses several areas and you need a clear starting page before changing accounts, DNS, devices, or provider settings.

Christchurch IT support

Use local support when the issue involves onsite devices, Wi-Fi, printers, office layout, account handover, or hands-on troubleshooting.

Remote IT support NZ

Use remote support when the work is account access triage, screenshots, controlled changes, provider-ready notes, or documentation that can be handled online.

Microsoft 365 support NZ

Use Microsoft 365 support when the problem is sign-in, MFA recovery, mailbox rules, admin ownership, shared mailboxes, or tenant handover.

Email deliverability support

Use deliverability support when messages bounce, land in spam, fail SPF/DKIM/DMARC, or depend on website forms, invoicing, CRM, or newsletter senders.

DNS and routing support

Use DNS and routing support when the symptom involves nameservers, TTL, propagation, MX/TXT records, partial reachability, or provider routing evidence.

Backup and migration

Use backup and migration support before risky resets, device replacements, provider moves, or laptop repairs where files and account handover matter.

Computer repair Christchurch

Use computer repair support when a device is unstable, slow, overheating, failing to boot, or needs diagnosis before the business changes systems around it.

SEO consulting NZ

Use SEO consulting when the checklist exposes gaps in page titles, Search Console coverage, sitemap discovery, structured data, or local service pages.

Email security and recovery

Use the recovery reading path when suspicious access, forwarding rules, MFA changes, mailbox persistence, or first-day incident evidence are involved.

Website launch checklist

Use the launch checklist when the next problem is redirects, analytics, sitemap discovery, Search Console checks, or post-launch handover.

Want help applying this?

Use the guided quote workflow to turn the checklist into next steps.

Start the quote workflow

Tools and proof

Turn checklist notes into repeatable assets

A checklist is most useful when it becomes a maintained system: tools for regular checks, launch notes for websites, and public project notes that show how technical work is documented.

Related context

Profile, projects, and practical guides

These pages connect the checklist to current professional background, project note evidence, and more detailed setup resources.