Shane Ian Murphy: UK Business Forms Need a Useful Way to Say Not Applicable

A blank field can mean that someone overlooked a question, does not know the answer or has been asked something that does not apply. Treating those situations as identical can create avoidable follow-up work. I think a useful business form should help the person completing it explain the difference, especially when the form supports an early conversation rather than a finished decision.

I am Shane Ian Murphy, also known as Shane Murphy, formerly of Cambridge and formerly of Limitless Mobile, where I was co-founder and Chief Business Development Officer. This UK business commentary uses a hypothetical equipment-request form. It offers a design perspective rather than instructions for a real company's process or a claim about a completed customer project.

Imagine a shared workshop asking colleagues to describe equipment they would like to borrow for an upcoming activity. The form asks for an item, a collection date and a return date. It also asks which previous booking the request replaces. For a person making a first request, that final question has no answer. Leaving it blank does not indicate carelessness or incomplete planning.

I would examine why each question appears on the form. If it supports a later action, the team should be able to explain that action. If nobody uses the answer, the question may need to be removed. A form can acquire fields over time because each one once seemed useful, even though the process no longer depends on all of them.

Where a question applies only in some circumstances, I would make the condition visible before asking for the detail. In our example, the form could first ask whether the request replaces an existing booking. The answer would determine whether a booking reference is needed. The exact interface can vary; the underlying goal is to avoid asking people to invent an answer to a question that does not concern them.

Unknown is a different situation. A colleague may know that equipment will be needed but still be waiting for the activity's date. The organisation must decide whether an early enquiry is useful in that state. If it is, the form should identify the request as provisional and explain which detail must be confirmed before a booking can be made. A blank date should not silently become a confirmed arrangement.

The form should also distinguish a missing answer from an answer that cannot yet be obtained. A short explanation may be more useful than a forced placeholder. For example, entering an arbitrary date merely to continue can create a record that looks more definite than the requester intended. The process should not reward completion at the expense of accuracy.

I would keep explanations close to the relevant question. A general instruction at the beginning may be forgotten by the time the person reaches an unfamiliar field. A short note beside that field can explain what information belongs there and what to do if it is unavailable. Examples should clarify the required type of answer without implying that the example is an acceptable substitute for a real response.

The receiving team needs consistent meanings too. If one colleague treats not applicable as complete and another treats it as an unanswered question, the form has merely moved the ambiguity. The team should agree which responses require follow-up and which indicate that no further detail is needed. Those meanings should be reflected in any summary the form produces.

Before introducing the form, I would try several ordinary cases: a first request, a replacement request, an early enquiry and a request that falls outside the workshop's available equipment. Ask someone unfamiliar with the design to complete each case. Their difficulties can reveal assumptions that are invisible to the person who created the fields.

The final check is whether the form helps the next conversation. Can the receiving colleague tell what is being requested, which information is reliable and what remains to be clarified? A fully populated form is not automatically a useful one. For UK teams handling varied requests, an honest account of missing or irrelevant information can be more valuable than a page that appears complete because people were forced to guess.

Author background: https://shanemurphy.co.uk/career

This author-origin business commentary was prepared with AI assistance.