The work

A job has a start, a check, and a return.

Whether the request is a data file or a system fault, we keep the same shape: you say what you need, we do that piece of work, and we send back what changed.

What we need before we start

  • SystemThe name of the system, or the kind of file.
  • OutcomeWhat “done” looks like: a cleaned file, a restored screen, a short report.
  • DeadlineThe day you need it, if there is one.
A large open office with rows of desks, laptops, and people working at screens
An office floor where support requests are handled at the desk.

Data work

We take the file you send. We check the columns against the brief. We remove duplicates, flag empty fields, and put the rows into the layout you asked for.

The return is the file plus a short note: how many rows came in, how many went out, and what was left out and why.

Dark server cabinets with glowing green lights and loose cable bundles
Cabinets that store the data sets between processing runs.

Technology support

You tell us the system, the time it failed, and what the user saw. We look at that system only.

If we can restore it, we say what we changed. If the fault is in a system we do not look after, we say that in the same reply.

What we will not take on

Public tickets

We do not run a help line for people outside the firms we support.

A new product

We do not build a consumer app or sell a licence from this site.

Unnamed files

A file with no owner and no purpose is sent back unopened.

After the job

We keep the emails and the file while the job is open, and for a short follow-up if the same file comes back. You can ask us to delete an older set.

A new job is a new email, even if it is the same system.

Start a job

Write from the firm

Use the contact form and name the company in the PwC network you are writing for. Put the system or the file type in the first line.

A woman pointing at code on a laptop while a colleague watches the screen
Two people checking a screen before a reply goes back.