Plain and Precise Legislative Language: Voice, Tense, Conditions and Connectors

Plain and precise legislative language is not a matter of making a Bill sound less formal. It is the discipline of expressing one legal result so that a reader can identify the actor, action, condition, time and consequence without guessing. In Kenyan legislative drafting, the draft must also fit the Constitution, its enabling authority and the existing statute book. The aim is controlled meaning: choose voice, tense, connectors and conditions because each changes the legal effect, not because a phrase looks familiar.

State the legal proposition before writing the clause

Begin in ordinary language. Who is required or authorised to act? What is the act? When does it apply? What follows if the condition is met or not met? If those questions cannot be answered in a short sentence, the policy instruction is not ready to become legislative text.

Separate the general rule from its exceptions, discretion, procedure and enforcement. A sentence that creates a power, imposes a duty, lists preconditions and prescribes a penalty is usually doing too many jobs. Subsections allow each legal relationship to be tested independently.

Use voice and tense to show responsibility

Active voice is normally clearest: “the Cabinet Secretary shall publish” identifies the decision-maker. Passive voice can be justified where the event matters more than the actor, but it should not conceal who must decide, notify, pay or keep a record. Where responsibility is shared, name the actors and their separate functions.

Present tense generally suits a continuing legal rule: a licence “authorises” or a person “commits” an offence. Use future-facing language only where a later event or period makes it necessary. A deadline must identify its trigger and calculation point. “Within fourteen days after service” and “before the expiry of fourteen days” may produce different results, so the intended sequence must be chosen deliberately.

Choose must, may, and or for legal effect

“Must” expresses a duty; “may” ordinarily confers discretion or permission. Neither word completes the analysis. A discretion may require criteria, reasons, notice, consultation or review. A duty may require a recipient, evidence, time limit and consequence for non-compliance. State those elements rather than assuming they follow from the verb alone.

“And” makes requirements cumulative; “or” identifies alternatives. Avoid “and/or”, which often hides an unresolved policy choice. If either alternative or both are intended, say so directly. Where alternatives have different consequences, use separate paragraphs so the reader does not have to reconstruct the drafter’s logic from a long chain of connectors.

Make conditions and exceptions visible

A condition should identify the triggering fact and the consequence that follows. “If” and “only if” are useful where they express a genuine gateway, but they are not substitutes for identifying the decision-maker or evidence required. Put a condition before the consequence where the reader must satisfy it first.

Long provisos are often a warning that the rule has not been organised. State the ordinary rule, then put a narrowly drawn exception in a separate subsection. Keep it near the rule it qualifies, but do not bury it at the tail of a sentence after several alternatives. The reader should be able to see the ordinary case, the exception and the result of falling outside it.

Test the clause in its legal setting

Read the draft as the administrator, regulated person and reviewer. Can each identify the required step, relevant time, information needed and consequence of action or inaction? Test each cross-reference, defined term, schedule, commencement clause and regulation-making power against the current consolidated text.

Finally, review the words in the sentence, the sentence within its section, and the section within the instrument. If a colleague gives different answers about the actor, condition or consequence, restructure the provision. Precision comes from a controlled legal relationship, not from longer sentences or older vocabulary.

Definitions should reduce rather than relocate uncertainty. Define a word when the instrument needs a special or repeated meaning; do not define an ordinary word merely to give it a capital letter. A definition should be tested wherever it is used, including in schedules, amendments and transitional clauses. If it changes the ordinary meaning too radically, place it close to the operative provision or reconsider whether a more direct rule would be clearer.

Cross-references require a second reading. A cross-reference can be accurate but still difficult to use. Ask whether it directs the reader to a condition, exception, power or procedure, and whether the destination provision uses the same actor and defined terms. After renumbering a Bill, test every reference again. A wrongly retained reference can quietly change scope or leave a necessary step without legal authority.

Draft discretion as a bounded decision. When an authority may grant, refuse, vary or revoke something, say who holds the power, the matters that may be considered, any procedural safeguards, and the legal result. This does not require a complete code for every decision, but it avoids a bare “may” that leaves affected persons unable to identify the limits of the discretion.

Use parallel lists only for parallel consequences. A list is effective when each item satisfies the same governing proposition. If each category has different evidence, timing or consequence, separate the rules. Repeating a governing verb can be clearer than making the reader carry it through a long page of paragraphs.

Review amendments from both directions. Read the proposed amendment as an insertion into the existing Act, then read the amended Act as a whole. Check whether words being repealed appear elsewhere, whether a new definition affects older provisions, and whether commencement or transitional language is required. Plain language is not achieved by simplifying one clause while creating conflict in another.

Write time rules as an operational sequence. A date, notice period or duration should reveal the event that starts time, the person who must act, the method of service or calculation where relevant, and the consequence of missing the period. Expressions such as “promptly” or “as soon as practicable” may be appropriate for a flexible administrative duty, but they should not replace a fixed period where certainty is required.

Keep the subject of a sentence stable. Long legislative sentences often become unclear when the actor shifts halfway through. If an authority begins the sentence, the same authority should normally perform the later verbs. Where a regulated person or court then has a task, start a new sentence or paragraph. Pronouns should be used only where the referent is unmistakable.

Draft consequences as carefully as duties. A provision imposing a duty should make clear whether non-compliance invalidates an act, triggers an offence, permits enforcement action, requires a fresh decision or has no prescribed consequence. The answer may follow from another provision, but the cross-reference must be exact. A vague consequence encourages inconsistent administration.

Use examples cautiously. An example may assist a reader to apply an already clear standard, but it should not introduce a condition or limit that the operative text omits. If the example is necessary to understand the rule, the rule may need restructuring. Likewise, explanatory headings help navigation but cannot safely narrow broadly drafted operative words.

Read for unintended breadth. A phrase such as “including”, “in relation to” or “for the purposes of” can expand a rule substantially. Test the outer boundary: which ordinary case does the provision clearly cover, and which adjacent case should it exclude? If the answer is uncertain, define the boundary through conditions, examples that do not alter the rule, or a more specific category.

Use repetition only when it prevents ambiguity. Repeating a key verb, actor or condition can be clearer than relying on an implied carry-over across several paragraphs. But repetition should be exact. If one paragraph says “must” and another says “may”, or one refers to an “application” and another to a “request”, the difference should be intentional and legally justified.

Keep transitional language concrete. When a new rule affects existing licences, proceedings, rights or instruments, identify what continues, what changes, who decides and from what date. Broad language such as “despite any other provision” should be used only after the conflicting provisions have been identified and the intended priority is clear.

Use a final implementation simulation. Walk through an ordinary case, a borderline case and a non-compliance case. Identify the document filed, decision made, notice sent, time calculated and remedy used. If the provision does not supply an answer, the gap may be substantive rather than editorial and should be resolved before the text is finalised.

Official source: Interpretation and General Provisions Act.