How to Explain a Legal Issue Clearly: A Practical Method for Lawyers

To explain a legal issue clearly, begin with the answer the reader needs, then show the rule, the facts that matter and the practical consequence. Do not begin with every possible doctrine or quotation. A client deciding whether to sign, respond, file or settle needs to know what the law requires, what remains uncertain and what should happen next. For a court or regulator, the same discipline produces a document that identifies the real question before advancing the analysis. Clear explanation is therefore not a matter of using simpler words alone; it is a method of selecting, ordering and qualifying legal information.

Identify the decision before explaining the law

Every legal explanation has a reader and a decision. An internal note may ask whether a proposed transaction needs consent. A demand-letter response may need to preserve a position without conceding liability. Written submissions may need to show why a court has power to grant, or refuse, a particular order. Those are different tasks even where they arise from the same facts.

State the practical question in a sentence before researching or drafting. “Can the buyer terminate after this notice?” is more useful than “What is the law on termination?” The first formulation directs attention to the contract, the notice, any cure period, the relevant facts and the remedy. It also exposes information that is missing. If the date of service, the version of a clause or the identity of the contracting party is unknown, say so. A confident answer built on an untested assumption is not clear advice.

The writer should also decide what the reader must do with the explanation. A document may call for a recommendation, a risk assessment, a proposed step, an instruction to obtain evidence, or a defined question for counsel. That purpose determines the level of detail. The most complete discussion is not always the most useful one.

State the rule in a form the reader can use

Once the issue is defined, identify the source that governs it: the Constitution, statute, regulations, contract, procedural rule, binding decision or a combination of these. Lead with the operative proposition, not a long extract. If the outcome depends on conditions, set them out as conditions. If the rule gives a decision-maker discretion, do not present it as automatic. If the law has changed or the point is unsettled, distinguish the current rule from the competing argument.

A useful explanation separates authority from analysis. Authority answers, “What is the legal source?” Analysis answers, “What does that source mean for these facts?” The two should be connected, but neither should be disguised as the other. Quoting a provision without explaining its consequence makes the reader do the lawyer’s work; asserting a conclusion without locating the rule makes the conclusion difficult to test.

For Kenyan public-law and litigation contexts, clarity also serves fair process. Article 50 of the Constitution protects the right to a fair hearing, and Article 48 requires the State to ensure access to justice. Those provisions do not prescribe a universal writing style. They do, however, reinforce the practical value of making the case, response and requested action intelligible to the person who must answer it or decide it.

Separate facts, inferences and uncertainty

The strongest legal explanations label the footing for each important proposition. A signed agreement, registry extract, witness statement or filed pleading may establish a recorded fact. A party’s account of an event may be an allegation. A conclusion drawn from several facts is an inference. A legal result follows only after the applicable rule is applied to the proved or assumed facts. Blending these categories can make a document sound decisive while concealing its weak point.

Use careful language where the record is incomplete: “on the documents provided”, “if the notice was served on that date”, or “subject to confirmation of the registered owner”. These qualifications are not evasions. They tell the client exactly what must be checked before reliance is placed on the conclusion. Conversely, where a point is established, state it plainly. Excessive hedging can be as unhelpful as overstatement.

A short factual chronology is often the best bridge between law and advice. It should contain only events that affect the legal test: who did what, when, under which instrument, and with what documented consequence. Background may help a reader understand the commercial relationship, but it should not obscure the fact that activates the rule.

Apply the rule step by step

Application is where explanation becomes advice. Take each material condition in the rule and connect it to the fact that satisfies, defeats or leaves it uncertain. In a notice dispute, for example, the analysis may ask whether the contract required writing, which address it specified, when delivery occurred, whether a cure period ran, and what consequence follows from non-compliance. The point is not to turn every issue into a checklist; it is to make the chain of reasoning visible.

Where more than one conclusion is reasonably open, explain the stronger and weaker routes. A client is better served by “there is a credible argument, but it depends on proving X and faces Y” than by a categorical prediction. The same candour is important in advocacy. Deal with adverse authority or an inconvenient document directly, then explain whether it can be distinguished, answered on the facts, or requires a different remedy.

Procedural advice should be presented in order. Name the step, the person responsible, the deadline or triggering event, the material required and the consequence of inaction. Timelines should be checked against the current instrument and any applicable directions before they are given as advice. A precise sequence prevents an explanation of rights from becoming an unusable explanation of process.

Finish with an answer and a defined next action

End by returning to the question at the beginning. State the conclusion in direct terms, identify the qualification that matters most, and recommend the immediate action. That action may be to obtain a missing document, issue a response, preserve evidence, seek an extension, negotiate a defined term or obtain specialist advice. The conclusion should not introduce a new legal issue that the analysis has not addressed.

Before sending or filing, test the document from the reader’s perspective. Can they identify the question, rule, critical facts, conclusion and next step without searching for them? Are names, dates, amounts, references and quotations accurate? Does the recommended action match the remedy or commercial objective? Have confidential material, privilege, service requirements and attachments been checked? This final review is often where a technically correct explanation becomes a reliable professional document.

Legal writing does not need to be ornate to be authoritative. It needs to be accurate about the law, candid about the record and deliberate about the reader’s decision. That combination gives clients practical guidance and gives decision-makers a fair opportunity to understand the case being made.

For an important matter, keep the research trail with the final explanation. Record the version and date of the legislation or rule checked, the cases considered, the documents relied on and the assumptions left open. That record makes later review quicker and helps ensure that an apparently simple answer remains defensible if the facts, instructions or procedural posture change.

Official source: Constitution of Kenya, 2010 (Kenya Law).