patch
patch / Before your visit

A little context
goes a long way.

You do not need to be a technical expert to describe a computer problem. These details make the first conversation more useful.

The computer

The make and model, if known, and whether it is a laptop, desktop or all-in-one.

What happens

The behavior you have noticed, when it began and whether it happens consistently.

What the computer is for

The tasks that matter to you and any planned changes in how you use it.

Private information

Keep credentials, recovery codes and personal file contents out of the brief. No device access is requested here.

Questions before
the work.

Do I need to know the cause?

No. A description of what happens, when it started and the device involved is enough for the initial conversation.

Should I put passwords or codes in the brief?

No. Keep passwords, recovery codes, account credentials and personal file contents out of the brief.

How is the repair cost agreed?

After assessment, we explain the findings, proposed work and cost. Additional work is discussed before it proceeds.

Can you guarantee that a device is repairable?

Repair options depend on the condition, parts and work required. We explain what the assessment supports rather than promising an outcome in advance.

What about the information on the computer?

Tell us if keeping particular files or settings is a priority, without sharing their contents. We discuss how the proposed work could affect your data before proceeding.

Will a brief confirm a visit or a repair?

No. It creates an overview for your review. Visit arrangements and any work need to be agreed separately.

Let’s start with the device

Tell us what
it’s doing.

A short description of the computer and the concern is enough to build a useful repair brief.

Build your repair brief