On The 8 Spot

One place for proposals, cases, approvals and the asset registry

A case study in prototyping the internal systems of a government disposition office, starting from its rules and its real paperwork

Download the long edition (EPUB, 38 KB)

At a glance

Situation An office that sells and leases state assets tracked proposals in a hand-kept workbook, deadlines by memory, and approvals in letters, while its asset registry could only be read through exports
Approach Three connected prototypes built from the office's guidelines and checked against real documents: an asset registry importer with reports, a proposal register, and a case tracker with approval routing and statutory deadlines
Window 23 September to 22 October 2026
Output 13 registry reports, a proposal register, a case tracker with approval, broker, blacklist and reporting modules, named staff accounts with an audit log, 135 automated tests, and a set of staff training materials
Status Prototypes on invented demo data, with a written list of what production would still need. None is deployed

The situation

The office handles the disposition of government assets: public auctions, negotiated sales, unsolicited proposals and other modes allowed by its guidelines. Three kinds of information were scattered:

The guidelines are specific about time. Deadlines run from milestone dates, brokers have a rating and sanction ladder, and a blacklisting procedure has its own fixed periods. That makes the rules suitable to compute rather than remember.

How the work was run

  1. Load the registry first. An importer for the registry's export files produced a reference dataset, and 13 HTML reports were generated from it: overview, regional summary, title status, appraisal health, a compliance dashboard, land use, data quality, maps and registry viewers. Every report page has a light, dark or automatic theme.
  2. Encode the process as data. The guidelines' flow, thresholds and deadlines were written down as a register of rules. A deadline engine computes every applicable deadline from a case's milestone dates, so nobody tracks them by hand.
  3. Build the case tracker around those rules. Every disposition mode is a case. Cases move through the office, the technical committee and the council, with a status model for that chain. Further modules cover broker accreditation (applications, authority to sell, annual ratings, the sanction ladder and a fee calculator by bid bracket) and a blacklisting procedure with each step's deadline computed.
  4. Add the proposal register. Every proposal appears in one list whether it came through the web portal, by letter or by email. Each has stages, a completeness check that reuses the portal's own requirement rules, matching of its lots to the registry, appraisal tracking, a reply log and one-click opening of a case.
  5. Check the design against real paperwork. Scanned approval letters for two real disposition packages and the proposal workbook were read and compared with the prototype. The findings produced a list of numbered requirement changes, each marked as built, partly built or not built.
  6. Make it multi-user. The shared password was replaced by named staff accounts with salted password hashes, a minimum length, lockout after five wrong attempts, two roles, and an audit log of sign-ins and every change to data. Every history row records who acted.
  7. Add a management report. Live figures cover cases by track, status and deadline severity, proposals by stage and channel, time to first reply, expiring appraisals, and council cycle times.
  8. Train and brief. A staff training manual, a slide deck with a presenter's briefer, and a concept deck for the finance department were generated from the same sources, with reading editions in Word and EPUB.

What the real documents changed

Where it could have gone wrong, and how it was handled

What was left open

Takeaways

  1. Compute the deadlines. Rules that depend on dates are better calculated than remembered.
  2. Test the design against real paperwork. The most important model change came from reading two real approval packages.
  3. Keep the registry as the shared key. Titles, lots and survey numbers needed one normaliser or nothing would join.
  4. Report the waiting time. The cycle time between steps was the question leadership would ask, and it was cheap to measure once dates were recorded per case.
  5. Say what is a prototype. Separating what is built, partly built and not built made the next decisions easier.

About these numbers

Test and report counts, dates and requirement changes come from the project's repository and design notes. Registry figures were read from real documents in October 2026, are rounded, and are aggregate only; no party, buyer or lot is identified here. The systems described are prototypes on invented data. They have not been security tested or used on live cases.