Field notes

What to have ready before we arrive

Fieldwork moves at the speed of your documentation. A short pack, prepared once, saves both sides a week of unanswered requests.

Two colleagues discussing papers at a meeting table

We send a request list with the scoping letter. The items that most often delay a Lumut or on-site engagement are not exotic. They are the organisation chart for payment owners, a list of production settlement runs in the period, access to a read-only copy of the application or to exported run artefacts, and a named contact who can obtain files from the acquirer.

You do not need to write a new manual for us. Existing close checklists, prior internal papers, and the last reconciliation file are enough to start. If a document does not exist — for example there is no freeze record — say so. Inventing one after the request arrives wastes time and usually becomes a finding anyway.

Access is arranged through your operations owner. We do not install tools on your network and we do not need a privileged login. Read-only access for the period under review, or a structured export, is the normal pattern.

If several merchants or entities share one application, tell us at scoping. Sampling across merchants is a different design from sampling within one company, and the fee letter should reflect that before we book the first week.

More field notes