Nothing lost to memory
Dates and amounts logged as they happen are more reliable than trying to reconstruct a three-month dispute from recollection many months later, under real pressure.
Available now
In build
The whole team
Nineteen specialists, each with a defined job and an honest status label.
See all nineteenThe business owner has a clean, chronological record of what happened, when, and with whom for an ongoing dispute or matter, ready to hand to an advocate.
Works with
What it does
The owner logs events as they happen (a missed delivery, a bounced cheque, a delayed payment) with dates, amounts, and any related documents attached. Vakil compiles these into a chronological timeline and a fact summary that an advocate can review quickly instead of piecing the story together from scratch.
A landlord dealing with a tenant who stopped paying rent three months ago has a phone full of half-remembered dates — was the first missed payment in April or May, did she send that reminder text before or after the second missed month — and none of it is written down anywhere an advocate could use.
Vakil's fact organiser exists to fix exactly that. As events happen — a missed payment, a notice sent, a phone call made — she logs them with dates, amounts, and any related documents attached, and Vakil compiles the entries into a chronological timeline and fact summary. It records what she tells it. It does not decide whether those facts add up to a legal claim, and it will not estimate how a dispute is likely to go. That reading of the facts belongs to the advocate she eventually hands the timeline to.
Vakil runs this directly on the platforms your customers already use — no separate app for them to install.
How it works
Add each event — a missed payment, a notice sent, a conversation had — with its date, any amount involved, and the people concerned, as close to when it actually happens as possible for accuracy.
Upload receipts, notices, messages, or letters connected to each event, so the whole timeline carries its own supporting evidence alongside the entries rather than scattered somewhere else entirely, across many separate devices, apps, and inboxes.
Entries are ordered by date into a clear timeline and a fact summary, giving a single, organised account of exactly what happened and precisely when it happened, right from beginning to end, with no gaps.
Share the compiled record at the start of a consultation so the advocate can review a clear sequence of events instead of reconstructing the whole story from scattered messages and someone's own fading personal memory.
Why it matters
Dates and amounts logged as they happen are more reliable than trying to reconstruct a three-month dispute from recollection many months later, under real pressure.
An advocate opening the file sees a compiled timeline immediately, rather than starting the meeting piecing the story together from scratch out of scattered notes.
The timeline records what happened without characterising it as a claim or a case, keeping the record neutral and useful regardless of how the matter eventually unfolds.
The detail
The organiser's entire function is recording and arranging — it takes what the landlord tells it about a missed payment, a sent notice, or a phone conversation, and places each entry correctly in time alongside its supporting document, if one exists. It performs no analysis of what those facts mean. If she logs three consecutive missed rent payments, Vakil shows three dated entries in sequence; it will not tell her this pattern constitutes grounds for eviction, because that requires applying tenancy law to her situation, outside what a fact-organising tool is built to do.
This boundary holds even when it would be easy to cross. A landlord logging a missed payment might reasonably want to know right then whether that payment alone is enough to act on — and Vakil will not answer that, because doing so would mean estimating the strength of a legal position, exactly the kind of judgment reserved for an advocate reviewing the full timeline and the actual lease terms. The organiser's discipline is to stay useful precisely by staying quiet on that particular question.
Accuracy of the underlying record matters more here than in most other tools, because a gap or a misdated entry can mislead an advocate who has no way of knowing the record is incomplete. If the landlord forgets to log a phone call where the tenant promised to pay, the timeline will look more one-sided than the full picture, and the advocate reviewing it won't know what's missing unless told separately. The organiser can only compile what it's given.
Industry use cases
6 industries where Vakil applies this directly.
A car service center owner uploads a supplier parts agreement into the plain-english-document-explainer to understand the payment and return terms before their scheduled call with an advocate about a recurring late-delivery issue.
See the automotive playbookA wholesale distributor whose buyer has not paid an invoice 60 days past the agreed term uses the delayed-payment-notice-preparation capability to draft a factual reminder letter and reads the linked explanation of the MSEFC reference process before deciding whether to pursue it.
See the b2b sales playbookA financial advisory firm uses the compliance-deadline-tracker to see upcoming annual filing dates for their private limited company, then separately runs a referral-partner agreement through the document coverage checker before their advocate reviews it.
See the banking and finance playbookA freelance designer uploads a new client's service contract to the plain-english-document-explainer to understand the IP-ownership and payment-milestone clauses, then later uses the delayed-payment-notice-preparation tool when an invoice goes unpaid past its due date.
See the freelancers and consultants playbookA furniture seller whose delivery partner damaged a high-value shipment uses the consumer-complaint-preparation-helper to structure their complaint against the courier before submitting it through the National Consumer Helpline.
See the home decor and furnishing playbookA landlord dealing with a tenant who stopped paying rent uses the consultation-briefing-fact-organizer to log the missed-payment dates and notices sent, then uses the jurisdiction-and-authority-finder to understand generally whether their state's rent law or a civil suit route is the relevant path, before consulting an advocate.
See the real estate playbookMore from Vakil
The business owner understands what a contract, notice, or legal letter actually says and what it asks of them, without waiting for a lawyer callback just to understand the basics.
Learn moreThe business owner walks into a paid lawyer consultation with an organized list of questions and facts, so the lawyer's limited time is spent advising rather than gathering basic information.
Learn moreThe business owner gets a plain-language overview of a legal topic relevant to their business (e.g., what a security deposit clause typically covers) before they need it urgently.
Learn moreThe business owner knows exactly which documents and pieces of information to collect for a common business task (hiring, renting, registering) before starting it, avoiding wasted trips and delays.
Learn moreThe business gets a professionally structured starting draft for a common business document (NDA, service agreement, offer letter) instead of writing one from a blank page.
Learn moreThe business owner sees which standard clauses (termination, liability, confidentiality, dispute resolution) are present, weak, or absent in a contract before signing it, so they know what to specifically ask a lawyer about.
Learn moreQuestions
No, and it's built specifically not to. The fact organiser records and arranges what you tell it into a chronological timeline — it never characterises those facts as constituting a legal claim, and it never estimates how strong a matter is or how it might turn out in the end. That reading of the facts is exactly what you bring an advocate in for, using the timeline as their starting point for analysis.
The timeline is an organised factual record, useful for briefing an advocate quickly and clearly, but whether and how it can be used as evidence in a proceeding is a legal question your advocate needs to answer for your specific matter. Documentation practices, authentication, and admissibility rules matter for that purpose in ways the fact organiser isn't built to address on its own.
The timeline can only reflect what you enter, so a forgotten event simply won't appear, and the record will look more one-sided than the complete picture actually is in reality. It's worth mentioning anything you remember but didn't log directly to your advocate when you hand over the timeline, since they have no way of knowing what's genuinely missing from a record that looks complete.
Yes. However clear a sequence of missed payments or broken promises looks to you personally, determining fault and what it means legally requires applying the relevant law — tenancy law, contract law, whichever genuinely applies — to your specific facts, which is exactly the judgment an advocate provides. The timeline makes that consultation faster and better-informed; it doesn't replace the need for it at all.
The rest of your stack
No rip-and-replace — organize facts and dates for a legal matter works alongside the systems already running your business.
Coming soon