Picture a small legal practice that decides to move its enquiry process online. Someone on the team volunteers to build a simple intake form, the sort that collects a visitor’s name, the kind of matter and a short description. Over two weeks, the form is refined, tested and made beautiful. On launch day, the first real visitor gets stuck at the third question and gives up. Nobody had watched an outsider use it. The scene is made up, yet anyone who has launched a web form will recognise it, and it leads into the questions people tend to raise about showing legal-tech work while it is rough. What follows is general information on workflow design, not legal advice.
Why show a rough intake form before it is finished?
Because the person who builds a form can no longer see it as a stranger does. The builder knows what each label means, which fields are optional and why the order was chosen. A newcomer knows none of that. Showing the form while it is still a sketch, perhaps a list of questions in a document, lets someone else tell you where they would hesitate. At that stage, moving or deleting a question costs nothing.
What counts as a rough draft here?
A plain list of the questions in the order a visitor would see them, with a line stating the purpose of each. No styling, no software, no logic. If the practice later builds the form in a tool, the structure will already have been tested on paper. A one-page draft can be read in five minutes, which is exactly why people agree to read it.
Who should look at it?
One or two people with different views. A colleague who talks to prospective clients every day will know which questions people struggle with. A person with no legal background will tell you which words are confusing. Resist the urge to circulate it across the whole office. A crowd produces competing preferences, and a small intake form built by a committee tends to grow longer with every opinion.
What should I ask the reader to focus on?
Everything hinges on the answer here, because it determines how useful the review will be. Spell out the response you are after. For example:
- “Is there any question here that a visitor might not understand?”
- “Is the order natural, or would you expect something else first?”
- “Ignore the wording of the introduction. I only need to know whether anything is missing or unclear.”
- “Which question would you be tempted to skip?”
Narrow questions get usable answers. “What do you think?” gets a polite “looks good.”
Is it safe to share form drafts that touch client information?
A sensible concern. The draft should contain only the structure of the form, never real client details. Use invented placeholder text if you need an example. Any testing with real visitors or real records needs the firm’s own rules on confidentiality and data handling, which are outside what a general article can settle. If you are unsure, ask whoever is responsible for those rules before sharing anything that might contain personal data.
Can this approach apply to a directory-style website?
Yes. Directories that help visitors find legal professionals in different cities face similar design choices: how to group listings, what to show first, how to describe a category. Looking at how a large directory arranges its city pages, for example a page organised around intellectual property practitioners in Guwahati or the matching page covering Madurai, can show a reviewer how listing pages are structured. A draft of your own layout compared against such examples, then shown to a reader, tends to reveal missing sections quickly. Anyone choosing a legal professional should rely on their own checks and on the official bodies that regulate the profession, not on any listing alone.
What if a comment feels wrong?
Record it word for word and leave it for a while. Later, consider whether it exposes an assumption you never tested. If a reader says a question is confusing, the question is confusing to that reader, whether or not you intended it to be. If the comment is purely a matter of taste, you can keep your choice. When two readers disagree with each other, ask each what worried them. The worries are usually compatible even when the proposed fixes are not.
What does a good request message sound like?
Short and concrete. For instance: “Attached is a rough list of the questions for our enquiry form. It is unfinished on purpose. Could you spend ten minutes telling me which question you would find hardest to answer? Please ignore the introduction text for now.” The message states the status, the task, the time and what to skip.
Where can I find people to test a rough draft?
Beyond your own office, look at community gatherings, workshops and professional meetups. Event websites make them easier to find, and KeralaOrbit is one such site for Kerala, that mixes what’s-on pages with a venue section, community discussion and blog posts. Bring a one-page draft and one question. Keep any client or matter details out of the conversation entirely.
What changes between a paper draft and a built form?
Quite a lot, which is a reason to test early. On paper, you see questions and order. Once built, you also face required fields, error messages, mobile screens and what happens after someone presses submit. Each of those deserves its own look, but none of them matters if the underlying questions are wrong. Settle the questions first on the page, then build, then ask a reader to try the working version. Splitting the review into two stages keeps each one small and each one focused on a different layer of the problem.
It also helps to decide, before building, which questions are essential and which can wait for a later conversation. Reviewers tend to trim a draft more readily than its author does, because they feel none of the effort that went into each question.
How many rounds of review are enough?
Often a single pass will do, and occasionally two. Go again only when round one reshaped the form, for instance by removing a section or reordering the questions. If the first round produced only wording tweaks, move on to building. The aim is to find the big flaws early, not to chase perfection through endless drafts.
What if nobody has time to read it?
Make the reading smaller. Cut the draft to ten questions, or to one section, and ask a single yes-or-no question about it. People who cannot spare fifteen minutes can often spare two. You can also offer to talk it through while walking down a corridor; an informal conversation sometimes yields more than a formal review.
A word on tone
How the form sounds counts for nearly as much as how it is laid out. Visitors contacting a legal practice are often anxious, and a cold or jargon-heavy question can end the conversation. Ask your reader to say how each question feels, not only whether it is clear. Phrases such as “does this sound friendly or intimidating?” bring out reactions that no checklist captures, and they are easy to fix at the draft stage by changing a single sentence.
Back to the opening story
In a better version of the story, the volunteer sends a plain list of questions to two colleagues on day two, asking which one they would find hardest. Both name the third question, which asked for a description of the matter in a single line. The volunteer replaces it with two shorter prompts. The form launches on the same date, and the first visitor finishes it. It cost one short conversation, held when changing a question meant changing a line of text.
Quick recap
- Draft the structure on a page, with no styling or real data.
- Choose one person who knows the audience and one who does not.
- Say exactly what you want judged and what to skip.
- Sort comments by structure, content and wording, in that order.
- Go back to the readers only if the structure moved a lot.
The method is modest, and it works because it moves the discovery of problems to the cheapest moment available: before anything has been built.
Related posts:

Eight Steps to Budget for Practical Costs Before You Meet an Advocate

Before You Meet an Advocate: Three Ways to Hold Your Worries

Six Myths About the Advocate's Work Diary, Examined

Career Skills for Advocates: Declining Work Without Closing Doors

DataSecOps in 2025: Four Shifts Lawyers Should Track
