OGP-40 Rapid

Explain a term, clause or process in plain English

Ask what a provision is doing, what a piece of jargon means in context, or how a routine step in a matter usually runs, and get a plain-English explanation you can sense-check against your own knowledge and the file.

First-pass summary of an incoming document

Paste a letter, short agreement or clause set and get a structured summary of parties, obligations, dates and anything that reads as unusual, so you know what you are dealing with before you read it properly.

Draft routine client and third-party correspondence

Produce first drafts of acknowledgement letters, chasers, update emails to clients, and standard requests to the other side, in your own tone and with the file details you supply, for you to review before they go out.

Turn attendance notes into a usable file note

Give it rough notes from a call or meeting and get back a tidy chronological note with actions, dates and follow-ups separated out, ready for you to correct and put on the file.

Draft an explanation of a clause for a non-lawyer stakeholder

Ask for a draft note rewriting a provision for a client's operations or finance team — how it works day to day and the points the business will need to decide on — without changing the underlying wording. The fee earner checks and approves the note before it reaches the client.

Build a question list before a client call

Describe the matter type and the facts you already have, and get a checklist of the information still to gather, so a fee earner or paralegal goes into the call with a plan.

Compare two short versions of the same wording

Give it the previous and current wording of a clause and have the differences set out in words, so the changes are written down in front of you before you decide how to respond — you still read the wording itself.

Tidy up a draft for consistency

Check defined terms are used consistently, numbering and headings run correctly, and language is consistent British English — the mechanical pass that eats time before a document goes out for review.

Answer the questions your team keeps asking

Give it your handbook, policy or process document and let staff put the everyday questions to it — what the notice period is, how expenses are claimed, who signs off what — with the answer pointing back to the passage it came from. Anything touching someone's contract, pay or leave still goes to the responsible person before it is acted on.

Draft routine business correspondence

Quotes, supplier chasers, payment reminders, appointment confirmations and customer replies drafted from a short brief, for a person to check and send.

Summarise supplier or platform terms into a starting list of points

Turn a long set of terms into a starting list of the commercial points a manager will want to look at — commitment length, notice, charges, what happens on exit — as a prompt for the conversation with a professional rather than a substitute for it. Terms it does not raise have not been cleared.

Turn meeting notes into actions

Convert rough notes into a clean list of decisions, owners and deadlines that can be pasted straight into your project or task tool, for the note-taker to check against what was actually agreed.

Rewrite copy in plain British English

Take internal or technical wording and rework it for customers, staff or a website page, at a set reading level and length, without losing the substance.

First drafts of internal process notes

Describe how something is done in your business and get a structured written procedure back, giving you a starting document to correct rather than a blank page.

Pull structured information out of unstructured text

Extract names, dates, amounts and reference numbers from emails, forms or scanned-and-typed text into a consistent table for your records, with the source text kept alongside so every entry can be checked.

Triage inbound enquiries

Sort incoming messages into categories, mark the ones that need a person, and draft a suggested reply for each — a human still approves anything that goes out.

A paralegal has forty minutes of notes from a client onboarding call and needs a file note plus a follow-up email before the end of the day.

The notes go in as they were typed. OGL-31 returns a structured file note with the facts, the client's instructions and the open points separated, plus a short follow-up email listing the documents the client still needs to send. The fee earner reviews both, corrects what needs correcting and sends them — the drafting work moves across to a review.

An SME operations manager has been sent a nine-page set of supplier terms and has to tell the director by tomorrow whether to sign.

The engine produces a plain-English summary of the commercial mechanics — term, renewal, notice, charges, what happens if they leave — and lists the points it could not read clearly. The manager takes a short written briefing to the director and to the firm's solicitor, who reviews the terms before anything is signed, instead of starting that conversation from a blank page.

A firm is answering the same twenty questions from clients about a standard process, over and over, by email.

The standing answers are drafted once with OGL-31 and reviewed by a supervising solicitor. From then on the engine tailors a reply to each enquiry from the approved wording, and a fee earner checks and approves it before it leaves the firm, so the team is editing rather than writing from scratch and the approved language stays consistent.

Best for

• Everyday questions that come up again and again during the working day
• Routine correspondence and file notes that a qualified person will review before use
• Making legal or technical wording readable for clients, staff and non-specialist colleagues
• Teams who want the whole office using an engine without watching the cost of every question
• First drafts, checklists and summaries that give you something to correct instead of a blank page

Not the tool for

• Anything sent out, filed or relied on without a qualified person reviewing it — the output is a draft, not advice
• Long, layered analysis across a bundle of documents, or a negotiation where the wording itself is the point — use the deeper analysis and drafting engines in the range for that
• Deciding a client's legal position, deciding what does or does not need a solicitor, or standing in for a solicitor's judgement on a matter
• Confirming that something is compliant, valid or enforceable — it cannot verify that, and its output is not legally checked or court-ready