The gap between a folder and a matter
A new matter lands as a folder of files - a signed agreement, three amendments, an email thread, a couple of scanned PDFs, someone's notes. Before any real legal work happens, a lawyer spends hours on the first read: who the parties are, which dates bite, what the file is actually about. That reading is necessary - and it is the same work every time, on every new matter.
PONS closes that gap. Drop the folder in and it comes back as a structured matter: the parties, the key dates, the value, the facts, a tailored questionnaire, and a starting task list - each item cited to its source in the file. Not a summary you skim and forget - a working object the rest of the matter runs on.
Drop the folder in, get a matter baseline
PONS reads everything it can extract text from and pulls the structure into a matter baseline: the parties and the role each plays, the key dates - signing, effective, renewal, notice, expiry - the value at stake, and the core facts that define the matter. Anything it cannot read cleanly, like an image-only scan, is flagged rather than silently skipped, so the baseline never quietly rests on documents that were never actually read.
The baseline is a starting point, not the last word. Every item shows where it came from, so reviewing it means checking against the source rather than taking it on faith. You correct the mislabelled party, fix the date that turned out to be a placeholder, and the corrected baseline becomes the version everything else builds on.
PONS does the reading; you start from structure instead of a blank page.
A questionnaire and a task list shaped by the file
From the baseline, PONS builds a questionnaire tailored to the matter in front of you - not a generic intake form, but questions shaped by what the documents say and what they leave out. A notice period defined but no trigger date on file? It asks. A party referenced but never identified? It asks. You answer what matters, skip what does not, and the answers feed straight back into the matter. The reading you would have done anyway becomes structured input instead of loose recollection.
It also generates a starting task list from the matter type, the jurisdiction, and the dates in the baseline. Tasks arrive already connected to the deadlines that drive them - a notice deadline pulls its task forward, and a step that depends on an earlier one shows up as a dependency, not a surprise. You add, remove, and reorder to fit how you run the matter, but you start from something shaped to the file rather than a blank checklist.
One place, from intake to resolution
The matter is the system of record. A note added against a party stays attached to that party. A document dropped in later is read and folded into the same structure. Come back after two weeks on something else and the context is still assembled - you are not rebuilding your understanding from a folder again.
Drafting starts from that same context: the actual names, dates, and terms you reviewed, not a generic template you correct line by line. And the matter carries its economics too - rates, time entries, the pricing model, and the recorded outcome when it closes (outcome predictions are on the roadmap, not shipped) - so the file that holds the work also holds what the work was worth.
That is what turns a folder of files into a matter you can run: the first read done in minutes, the structure ready, and every item traceable back to its source.