Data Recovery Case File · Case 1400 · Say What You Need

Everything Is Not a Specification

His enquiry asks four things in six lines, and the third one is the question this archive has been circling for fourteen hundred cases. A failed drive removed from a machine by a technician who tried and failed to retrieve anything from it: "Ideally I could do with the data off it, but there is a question of how financially viable that is for non-vital documents. How likely do you think it is you could recover data, what payment methods do you accept, and how do you know if it will save the right files?" Almost nobody asks that last one — and it has a concrete answer that also settles the first.

The decode: what he is actually asking, and why it usually goes unanswered

The first two questions have ordinary answers. Likelihood is established by a free assessment rather than estimated over email, and payment is administrative. Both are answerable and neither is interesting.

The third is different. He is not asking whether the work will be competent. He is asking whether the thing that comes back will contain the thing he wanted — which is a separate question, and one that most people feel without putting into words. It is the anxiety underneath every enquiry in this archive: you hand over a device, a sum is quoted, something is returned, and you have no way of knowing in advance whether the file you actually cared about is in it.

Why that question normally has no answer: because of what gets asked for. The request is almost always recover everything — and everything cannot be confirmed. A job scoped to everything can only be reported as a quantity: so many gigabytes, so many files, such a percentage of the surface read. Not one of those figures tells you whether the document you needed came back. You find out by looking, afterwards, once the money is spent.

The answer is to name it. Three files. A folder. A project. A date range. A file type. Anything specific enough to be located and opened. A recovery scoped to named material can be confirmed before the rest proceeds — the target is reached first, opened, and shown to you, and only then does the remainder of the work continue. His question stops being unanswerable the moment there is something to answer it about.

And this settles his cost question too, which is the part he has not realised. He is weighing viability against non-vital documents — a phrase that means he has not decided what he wants. Naming it is how you find out whether you want it enough. If you can write down three things you would open first, the job has a shape, a price, and a way of being checked. If you sit down to write them and nothing comes, that is an answer as well — and a great many people discover at that moment that the anxiety was larger than the loss.

The honest other half: sometimes the answer is that it is not worth it. A free assessment should be able to conclude don't, and say so plainly. A trade that only ever answers yes is not giving anybody information, and somebody told honestly that their content is replaceable is better served than somebody handed a figure and left to work it out alone.

One practical thing before anything else, given the history: a technician has already run software against that drive. Worth asking what was run and whether anything was written — a repair, a rebuild, an initialisation — because any of those changes what remains possible.

The doctrine of case 1400: nobody asks you what you need

Fourteen hundred enquiries, and almost none of them say what they want. They describe a device, a symptom, a moment of loss — a drive that clicks, a card that will not read, a phone thrown at a wall — and then they ask for the data back. All of it. Whatever is there.

That is not because people do not know. Everybody in this archive could name what they were really after: the photographs of one particular person, the project files, the dissertation chapter, the wedding, the year of accounts. They do not say it because nobody asks. The form asks what device it is and what went wrong. The conversation is about the fault. And "everything" is what you answer when the question has never been put to you.

What that costs is not mainly money. It is the ability to know. An unscoped recovery cannot be quoted precisely, cannot be sequenced sensibly, cannot be stopped at the right moment, and — most of all — cannot be checked. It produces a delivery you have to go through yourself, hoping, which is the exact experience he is trying to avoid by asking the question in the first place.

So the test, and it takes two minutes before commissioning anything. Write down the three things you would open first. If you can, you have a scope, a price, a sequence and a way of confirming success — and you have converted a leap of faith into a transaction. If you cannot, you have learned something worth more than the recovery would have cost.

Why this is case 1400. This archive has spent its length on what people are told and who was answering which question — the repair answer to a recovery question, the support script optimised for diagnosis, the prompt written to restore a volume rather than to save a file. This is the question from the other direction: the one you should be asked and are not. He asked it himself, of a stranger, while wondering whether any of it was worth the money. That is the right instinct, and it deserved an answer.

On the bench

Prior software activity and any write were established before assessment, a retrieval attempt potentially having included a repair, rebuild or initialisation, any of which changes what remains possible. The owner was asked to name three items to be opened first — an unscoped recovery being reportable only as a quantity, which cannot confirm whether a required document returned. Capture was sequenced to named material and confirmed before continuation, completion verified against the named items rather than by volume, and the position stated before any charge.

The outcome

The prior handling established, the scope named before any work, and completion verified against the owner's own list. Free assessment, one fixed written figure including VAT; where a drive has to be opened, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode, and the doctrine of case 1400: "everything" is not a specification. A job scoped to everything can only be reported as a quantity, and a quantity cannot tell you whether the file you cared about came back. Name three things you would open first — that gives the work a shape, a price and a way of being confirmed. And if you sit down to name them and nothing comes, that is an answer too.

Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.