The timetable is the specification

Products aimed at legal work are usually specified by task: read the documents, extract the figures, draft the schedule. That framing misses the constraint that actually governs a financial remedy matter. The work is not a set of tasks; it is a sequence with dates attached, and the dates are set by rule rather than by preference.

For a disclosure system, that sequence is the specification. What has to be ready, and what may not be shared yet, changes at each step. A system that produces the right document at the wrong point in the sequence has not saved anybody time.

The sequence

A financial remedy application under the Family Procedure Rules runs, in outline, like this. Before an application is issued, the applicant ordinarily has to attend a MIAM — a mediation information and assessment meeting — unless an exemption applies. Once the application is issued, the court sets a First Appointment, and the steps before it are timetabled backwards from that date.

Both parties exchange Form E, the sworn financial statement, on the same date. After exchange, each side may serve a questionnaire: a request for the further information and documents they say they need, framed by reference to the issues in dispute. The questionnaire is filed alongside a statement of issues, a chronology, and Form G, which states whether the party considers the First Appointment could be used as a Financial Dispute Resolution appointment instead.

The First Appointment is a directions hearing. Its purpose is to fix what still has to happen: which questionnaire requests are allowed, what expert evidence is needed, what valuations must be obtained. The FDR that follows is a without-prejudice negotiation hearing, at which the judge gives an indication and cannot later try the case.

Two features of that sequence matter more to system design than any individual date.

Exchange is simultaneous, so the record has to be held apart

Form E exchange happens at the same time on both sides. This is not an administrative convenience; it exists so neither party can shape their own disclosure around the other's.

For software, simultaneity means a disclosure record cannot be one shared object with permissions on top. Before exchange, each party's record must be genuinely separate, with no path by which one side's content influences the other's. Pivot models this as a phase, not a moment: the period during which records are held apart is a state the matter is in, with different behaviour from the state after exchange.

The consequence is that merging is an event with a before and an after. Cross-party findings — the same asset described differently by two people, an entity that appears in one side's documents and neither side's Form E — do not exist before that event and cannot be previewed. Any system that could show you those findings early would be a system that had leaked.

The questionnaire is the route, so timing decides what is available

Before proceedings, disclosure between parties is largely voluntary. Once an application is issued, further documents are obtained through the questionnaire and the directions the court makes on it, not by asking again more firmly.

That makes the window between Form E exchange and the questionnaire deadline the point of maximum leverage in the matter, and it sets a hard requirement on the system: by that point the record has to know which entries are uncorroborated, which are contradicted, and which entities appear in the documents but in nobody's Form E. Those three categories are the questionnaire. Producing them a week later produces them after the request has gone.

This is why Pivot's document reading and state assignment are timetabled to complete against exchange, rather than being treated as background processing that finishes when it finishes.

Matters move backwards, and a forward-only model breaks

It is tempting to model a matter as a pipeline: intake, build, exchange, merge, hearing, order. Pipelines are easy to reason about and easy to display.

Real matters return to earlier states. Further documents arrive after the First Appointment and reopen questions that appeared settled. A pension report changes a valuation the schedule was built on. A party discloses an account they had not mentioned. Occasionally a sealed order is challenged, and material non-disclosure — a party having withheld something they were obliged to disclose — is one of the grounds on which a court can revisit a financial order.

So the disclosure record has to support re-entering a phase. In practice that means: state assignments must be recomputable when new documents land; generated documents must be regenerable with the change between versions explicable; and the record must retain what it previously said, because when a figure moves, the question asked next is when it moved and on what basis.

A forward-only model cannot answer that question. It has already overwritten the answer.

Dates that are not deadlines but behave like them

Alongside the rule-set dates, a matter carries dates that constrain the work just as firmly. Valuations have effective dates, and a schedule built on a valuation that has aged past its useful life will be challenged. Expert directions carry their own timetable, and the expert's report has to arrive early enough to be used at the hearing it was ordered for. Documents have to be with the court a set period before a hearing for the judge to have read them.

None of these are things a system can be indifferent to and still be useful. Each one is a point at which the record must be in a particular state.

What follows for the product

Treating the timetable as the specification produces a specific set of design commitments. The matter has phases with different sharing rules, and the phase is part of the data rather than a label in the interface. Document reading is scheduled against exchange. The questionnaire inputs are computed, not composed by hand. Regeneration is a first-class operation. And a matter can go back a phase, because matters do.

None of that is visible in a task-shaped specification. All of it is visible the moment you write the dates down.