Operations and compliance, every page in the demo
By The Briesa team · 4 min read
Every page, dialog and write of the first three phases now works in the demo agency. What that covers, area by area, and what comes after it.
The roadmap began with a full UI over the Demo Agency: every sidebar page and property tab drawn from its seed data, with a coming-soon banner until its phase ships. With release 0.7, the first three phases have shipped in the demo. Every page, dialog and write of the foundation, operations and compliance now works there.
It runs on the demo’s own data while the live database is wired underneath it, and every write leaves an entry in the audit log. Three parts of the sidebar gained the most:
The foundation. The General and System groups: the dashboard, properties, contacts and documents; settings, teams, members, staff accreditations and CPD, and the audit log browser.
Operations. Tasks, the calendar, meetings with their open items carried to the next one, and KPI targets with their progress.
Compliance. Policies with versions and sign-offs, checklists on the property, the registers, both trust accounts with reconciliation, and the audit pack.
Three phases, by sidebar group
On 9 September the roadmap’s phases were recut by sidebar group. The foundation is the General and System groups, then Operations, then Compliance, then AML, then Management, then Sales, then the platform. Every phase ships something a paying customer can use.
A phase is done when its gate can be shown to a customer on screen, not when the build is finished. That is the bar 0.7 was held to: each of the three can be clicked through in the demo, page by page.
Phase 0 · The foundation
General and System: the shell, the records every later phase hangs off, and the settings that run the agency.
Phase 1 · Operations
Tasks, the calendar, meetings and KPIs, with the task engine every later phase creates into.
Phase 2 · Compliance
Policies, checklists, registers, trust accounting and the audit pack.
What is in the demo
Here is each part of the sidebar, the phase of the roadmap that built it, and what now works in the demo:
General and System
- Phase
- Phase 0, the foundation
- What works in the demo
- The dashboard, properties, contacts and documents; settings, teams, members, staff accreditations and CPD, and the audit log browser.
Operations
- Phase
- Phase 1
- What works in the demo
- Tasks, the calendar, meetings with their open items carried to the next one, and KPI targets with their progress.
Compliance
- Phase
- Phase 2
- What works in the demo
- Policies with versions and sign-offs, checklists on the property, the registers, both trust accounts with reconciliation, and the audit pack.
| Area | Phase | What works in the demo |
|---|---|---|
| General and System | Phase 0, the foundation | The dashboard, properties, contacts and documents; settings, teams, members, staff accreditations and CPD, and the audit log browser. |
| Operations | Phase 1 | Tasks, the calendar, meetings with their open items carried to the next one, and KPI targets with their progress. |
| Compliance | Phase 2 | Policies with versions and sign-offs, checklists on the property, the registers, both trust accounts with reconciliation, and the audit pack. |
Operations
Operations is the day’s work: tasks as a list or a board, the calendar by month, week or day, meetings, and the targets each person is working to.
The roadmap set this phase three things to show on screen. A meeting logged with a task that appears in the assignee’s list and on Reports. The previous meeting’s open tasks at the top of the next. And a KPI target with its progress, green, amber or red, on Reports. In the demo a meeting carries its open items to the next one, and each target shows its progress.
In the roadmap, tasks are the engine every later phase creates into: the work a checklist, a review date or a meeting raises lands in the same list.
Compliance
Compliance is where an agency’s obligations are kept, and it is the phase the roadmap marks for its first paying customers.
Policies. A policy keeps its versions and its sign-offs, so who signed which version is on the record.
Checklists. They sit on the property, beside the record they are about, rather than in a list of their own.
Registers. Each register is a page of its own, at its own address.
Trust. Sales and rentals trust are separate accounts, each with its own ledger and its own reconciliation.
The audit pack. What an auditor asks for, gathered from the record. The roadmap scopes it by property, by period or by the whole organisation.
An audit entry on every write
Every write in the demo leaves an entry in the audit log: who, what and when, in the same place for every page. The audit log browser in the System group reads it back.
That is a rule of the build rather than a feature of this release. Nothing ships without the audit log and row-level security covering it, and compliance records are never hard-deleted.
Summaries written from the records
Three documents are written for you: the policy draft, the gap report and the weekly briefing. Until a model is wired, each is drawn from what is on file, and each says it is not legal advice.
The roadmap sorts what the system writes by a traffic light. The policy draft, the gap report and the briefing are green: the system may produce them itself. Anything sent to an outside party waits for approval, and some decisions stay with a person, among them trust disbursement approval, audit pack submission and register sign-off. Every output cites its source, says it is not legal advice, and is read by the principal before it is used.
Availability
The demo agency is open to anyone, with no account behind it. Open it from the demo page, change something, and reload: what you changed is still there, in your browser and nowhere else.
The sidebar now shows what shipped: the groups that are built, with Insights beside them. Next on the roadmap are AML, then Management, then Sales, then the platform.
Try it yourself
Further reading
- 1.The release notes for 0.7, in short.
Read the notes - 2.Every screen of the workspace, area by area.
Open the showcase - 3.How Briesa keeps an agency’s compliance.
Read more - 4.Why the property is the file.
Read the post - 5.Why the demo moved into the browser.
Read the post
More from the blog
- Why the demo moved into the browserIn two days the demo agency moved twice: first into a branch inside every service, then out of the server altogether. What we got wrong the first time, and why the second answer holds.Read more
- The property is the fileWhy Briesa files the transaction under the property, and every other system does it the other way round.Read more
- Reconciled by the month, not by the miracleWhat we learned building sales and rentals trust accounting to the NSW rules, and why the audit pack should be an export.Read more