Platform
Tidewater OS is not a collection of tools bolted together. Each part writes into the same property record, which is why a completed task changes a forecast, an approved document creates a warranty, and a question can be answered with a citation.
What is in this house, and where?
A property is broken into zones and locations, zones hold systems, and systems hold assets. Each asset carries manufacturer, model, serial number, install date, useful life and a replacement estimate. When a system is replaced the old one is not deleted — it is retired, and the chain of what replaced what stays readable.
What should happen next, and when?
Maintenance tasks describe what ought to be done; recurrence understands intervals and seasonal windows. Completing a task writes a service event and moves the next due date forward, so a forecast is a consequence of real work rather than a wish list.
What actually happened here?
A permanent record of work performed: what, when, by whom, on which property and against which system or asset. Nothing in the history is rewritten later; corrections are additions.
Where is the paperwork?
Warranties, manuals, invoices, permits and inspection reports, deduplicated and categorised. Documents can arrive by upload or through a property's own intake address. Extraction reads them and proposes records — a warranty term, an asset serial, a vendor — and a person approves or rejects each proposal in a review queue. AI proposes; people decide.
Who works on this, and can we call them tonight?
Trades, contacts, after-hours availability, licence and insurance standing, and the history of what each vendor has actually touched. Sensitive internal notes are visible only to the roles entitled to them.
What are we covered for, and until when?
Agreements and protections are tracked separately because they behave differently. Both surface on the renewal and expiration horizon, and both link back to the document that proves them.
Where is the main shutoff?
The operational knowledge that fits nowhere else — shutoff locations, access procedures, quirks of the building — marked verified or unverified, and gated by sensitivity so codes and security details are not open to everyone.
Can I just ask?
Natural-language questions answered from the authoritative record, with citations to the source record or document. Every answer is scoped to what the person asking is permitted to see, and the property in question is resolved on the server, never taken on trust from the browser.
What will this cost us over the next ten years?
Useful life, install dates and replacement estimates turned into a forecast, with the assumptions and the missing data stated plainly so a planning conversation starts from what is known.
What do we send the principal?
Print-ready operational reports, CSV exports, an executive property summary suitable for sharing, and a separate owner portal with digests — optionally under your own organization's brand.
What about the person in the mechanical room?
A dedicated field experience with its own entrance: scan an asset, look up an emergency shutoff, capture a photo, close a task, log an inspection — designed for one hand and poor signal.
What is being missed?
A prioritised, explainable attention inbox that resolves items as the underlying condition clears; controlled automation rules; and an append-only audit trail recording who changed what, when, and on which property.
The fastest way to judge the platform is to watch a house you know get loaded into it. Tell us what you look after and we will arrange that.