Real Estate Management
Platform, Roles & API
Four access roles with genuinely different reach, audit logging across users and documents, a client portal scoped to a customer's own file, and a REST API over the eight core entities.
The full reference
Every module.
👥
Who owns what, and in what share
Clients & owners
- Client records — Full name, ID number, contact details, mailing address and notes, with contact preferences held against the record.
- Ownership — Ownership percentage and share in the land, so fractional and joint ownership is modelled rather than described in a comment.
- Communication history — Every message, call and letter recorded against the client, so context survives a change of case handler.
- Consultants — The external professionals on a case, their agreements and what they are owed.
▦
Block, parcel, plan
Land assets
- Property details — Block (Gush), parcel (Helka) and sub-parcel numbers, plan number, municipality, district and address.
- Ownership details — The owners list with percentages, joint-ownership agreements and current legal status.
- Search by land — Find by block, parcel or plan number as readily as by client name — because that is how the enquiry usually arrives.
◷
The procedure, tracked
Planning cases
- Case record — Project name and number, description, creation date and the assigned manager.
- Planning information — Planning status, current phase, target completion date, municipality and the planning authority handling it.
- Status workflow — New, data collection, initial review, planning submission, municipality review, committee review, approved, rejected, completed.
- Tasks — Title, description, assignee, due date and priority, with open / in progress / waiting / completed / cancelled states.
- Deadlines & reminders — Upcoming dates surfaced on the dashboard and pushed as reminders rather than relied on.
▧
The digital archive
Documents
- Legal — Land registry extract (Nesach Rishum), joint-ownership agreements, powers of attorney and legal opinions.
- Planning — Committee decisions, planning applications, maps, zoning documents and architectural plans.
- Financial — Invoices, receipts, consultant agreements and payment confirmations.
- Upload & versioning — Drag-and-drop and multi-file upload, with version control on every document.
- Search — Full-text search, plus search by client, by block or parcel, and by document type.
- Metadata & audit — Upload date, uploader, category and expiry, with document access logged.
💳
Payments, costs and the management view
Money & reporting
- Payments — Outstanding, overdue and paid, tracked against the case and the consultant.
- Client reports — Active clients, new clients and communication history.
- Financial reports — Expenses, consultant costs and outstanding payments.
- Project reports — Active, delayed and completed projects.
- Executive dashboard — Active projects, upcoming deadlines, outstanding payments, recent documents, planning-status summary and recent activity.
- Export — Excel and PDF export for anything that has to leave the system.
🔐
Roles, audit and the API
Access & platform
- Roles — Administrator, project manager, consultant and viewer — four roles with genuinely different reach, not one role with switches.
- Authentication — Email sign-in with password reset and optional multi-factor authentication.
- Audit logging — User activity tracking, document access logs and a full change history.
- Client portal — Customer-facing access to their own files and invoices, and nothing else.
- REST API — Clients, properties, projects, documents, payments, consultants, tasks and notifications.
Under it
Platform & architecture.
| Backend | FastAPI, with its own database and authentication |
|---|---|
| Frontend | Next.js |
| Data | PostgreSQL |
| Documents | Secure document storage with versioning, backup and an audit trail |
| Access control | Role-based, across four roles, with document access logged |
| API | A REST API over the eight core entities |
| Delivery | A dedicated repository, built and deployed through the platform’s agent runners |
| Deployment | A lean single-container application, served to the customer over the platform edge |
Built and delivered end to end on the Tracstone platform: its own repository, its own database and authentication, built by agent runners and deployed as a single lean container the customer owns.