People who look for an advocate, whether for a trademark, a copyright question or any other matter, often arrive at the first meeting with a bag of loose papers and a story told from memory. The meeting then spends its first half hour on sorting rather than on substance. A standard file-preparation routine, a short written runbook, fixes this. It also protects against a quieter risk: when the person who normally keeps the family’s or the business’s papers is unavailable, nobody else knows what exists or where it is. The questions below address how to build that routine. This is general information on organising documents, not legal advice.
What is a file-preparation runbook, in this context?
It is a short, ordered list of steps for assembling the papers and facts you would bring to a consultation, written so that anyone you trust could follow it. It covers what to collect, how to order it, how to summarise the situation, and what to record afterwards. It cannot say what the law provides or what you ought to do; those questions belong to a qualified advocate.
Why write it down instead of just doing it?
Because the knowledge of where things are tends to live in one head. The person who handled the last dispute remembers which receipt matters, which email thread has the key attachment and which date was the turning point. If they are travelling or unwell when a new issue arises, others lose days reconstructing the history. A written routine lets a colleague, a relative or a business partner prepare the file in the same way every time.
What should the first page contain?
A one-page summary, written in plain language. Include who is involved, what the matter is about in two or three sentences, the dates that appear to matter, what outcome you are hoping to discuss, and the name of the person responsible for the file. Think of it as the page a stranger would read to understand the situation in under two minutes. Resist the urge to argue the case; just describe it.
Which documents belong in the bundle?
Start with identity and authority papers, then the documents directly connected to the matter, then correspondence, then anything that looks peripheral. For a business matter, for instance, that might mean registration papers, relevant agreements, invoices and the messages exchanged. Order them by date within each group, give each a short label, and keep a simple index at the front. The advocate will tell you what else is needed; your job is to make the first meeting efficient.
How should the timeline be written?
As a short list of dated events, one line each, with the source document beside it. “Date, what happened, where the paper is.” Do not add opinions. A neutral timeline is the most useful single page you can bring, because it lets the advocate see the sequence at a glance and ask the right questions. Mark gaps honestly, for example “date uncertain, check email”.
How do I choose whom to meet?
Choosing an advocate is its own task, and reputations are best checked through bar credentials and direct enquiry. As a starting point for orientation, city-wise listings can help you see who practises in a given area; for instance, a regional overview of intellectual property advocates practising in Guwahati or a comparable page on advocates in Madurai who handle IP matters shows the kind of information such listings give. Treat any list as a starting point and confirm details yourself. Once you have chosen, send the first-page summary ahead of the meeting, so the advocate can prepare.
What questions should the runbook prepare me to ask?
Add a short section called “Questions for the meeting”. Typical examples are: what documents are still needed, what the likely next steps are, how fees are structured and billed, how updates will be shared and how quickly messages are answered. Writing the questions beforehand means you are less likely to forget them under the pressure of the meeting. Leave space to record the answers.
What should I record after the meeting?
A half-page note, written the same day: what was discussed, what the advocate asked for, who is doing what and by when, and the next date. File it at the front. If someone else takes over the matter later, this note, rather than a vague memory of a conversation, is what lets them continue seamlessly.
How do I protect sensitive information?
Keep originals in a safe place and work from copies where possible. Do not write passwords or sensitive identifiers in the runbook itself; just say where they are kept and who is allowed to open them. Be cautious about sending confidential documents through casual messaging apps, and ask the advocate’s office how they prefer to receive papers. Confidentiality is a basic expectation in legal work, and a good routine reflects it.
Who else uses written routines like this?
Almost every field that depends on repeatability. Data teams are a clear example, since a job that fails overnight should not wait for one engineer. For a look at that culture, TheDataOps.org publishes pieces on keeping data pipelines dependable, which is the mindset worth borrowing. The principle is identical: describe the routine, test it on someone else, keep it up to date.
What if the matter involves a business rather than an individual?
Then add two things to the routine: who is authorised to speak for the business, and where the official records are kept. Companies and partnerships often discover during a first meeting that nobody can say who signed what, or which version of an agreement is the current one. Put a short “authority and records” page behind the summary, listing the people allowed to give instructions, the location of signed agreements and the person who holds the registration papers. When those facts sit in one place, a change of staff or a long absence will not stop the matter in its tracks.
What if I am short of time?
Do the summary and the timeline first, and bring whatever else you can lay hands on. Those two pages carry most of the value, and the rest can follow in the days after the meeting. A partial routine, followed honestly, beats a perfect one that never gets written. Mark clearly which items are still missing, and note who will collect them, so the gaps do not quietly turn into surprises later.
How do I test the routine?
Ask a trusted person who was not involved to assemble a file for an imaginary matter using only your page. Do not help. Note every question they ask and every place they pause, and change the page to answer it. Do this once and the routine improves visibly; do it twice and it usually works unaided.
How often should it be reviewed?
At least once a year, and after every real use. Put the review date on the page and name who does it. Update it when you learn something: a document that turned out to be essential, a format an office prefers, an index that made things quicker. Remove anything outdated, since a confident but wrong instruction is worse than none.
What does a finished routine look like?
- Write the one-page summary and the dated timeline.
- Collect identity papers and the documents connected to the matter.
- Order them, label them and write the index.
- List questions for the meeting.
- Send the summary ahead and confirm the time.
- After the meeting, write the same-day note and file it at the front.
- Diarise the next dates and the review of this routine.
Seven lines can be followed by almost anyone, and they turn a stressful first meeting into a productive one. The routine will not decide anything for you, but it makes sure that when a decision is needed, the facts are in order and somebody other than one tired person knows where they are.
Related posts:

Half-Finished Case Paperwork: A Diagnosis and a One-Sentence Fix

DetectionOps in Late 2026: A State-of-Practice Review for Legal Tech

Eight Lessons in ObservabilityOps From a Legal Directory Site

Legal Document Version Control: Where the Trend Is Heading

After a Court Order: Questions to Plan With Your Lawyer Early
