Changelog

???? Admin Override now works on Change Requests — Staff with the Admin Override permission (without needing a full system administrator account) can approve, reject, or return a change request outside the normal layer rules, force-release another reviewer’s claim, and use the same override paths on deviation review. Without the permission those overrides stay blocked.

???? Create Documents can actually save a new document — Staff with Create Documents could see the Submit button but received Access Denied when saving. Saving a new document now works with Create Documents alone.

???? Create Documents now shows the Submit button — Staff with only the Create Documents permission could open the new-document form but the Submit button was missing. Submit now appears for Create Documents as well as Edit Documents.

???? Add a meter straight from its property, with the right lists in each place — You can now add a meter directly from a property's page: open the property and use "Add Meter", and the property is filled in for you automatically. On the meter form, the location lists now come from the places you already keep this information. For a common area, the Tower, Floor and Room come from Asset Management's location list. For a customer unit, the Unit list comes from the property's own units (organised by floor). Each list still appears only when it applies.

???? Certificates for every course you finish, and a register of every one issued — Finishing a course now earns a formal certificate, issued automatically the moment the last lesson is ticked off and the closing Knowledge Check is submitted. Nobody has to request it and nobody has to approve it. The certificate carries the learner's name, the course, the result, the date, and — where a baseline was taken at the start — the evolution from the first score to the last, so it records how much somebody grew rather than only that they turned up. Each one gets its own certificate number and a verification code, and can be opened or downloaded as a print-ready page designed to be framed rather than filed. A new Certificates screen sits alongside the trails: staff see the courses they have concluded, and anybody who can already see the team's progress sees the full register — every certificate issued, who holds it, for which course, with what result and on what date — filtered by course or by date range, with totals for certificates issued, learners certified, courses covered, average result and activity in the last thirty days. A certificate is a record of a moment, so it is issued once and never rewritten: retaking a Knowledge Check afterwards to improve a score leaves the original certificate, its number and its result exactly as they were.

✨ Rate and Add-on Type Sync — The amenity setup now automatically follows the current customer type list for rates and add-ons, so new customer types appear without manual form updates.

???? Task list column order stays in sync — Choosing which columns to show and dragging them into order now keeps the table matching the column picker, including after the list refreshes and when newer columns were added later.

???? Fully Validated, Closed and Expired documents are locked — Documents in those statuses can no longer be edited by the Property Manager. A new permission, Edit Locked Documents (Valid / Closed / Expired), controls who may still edit them; the permissions scoped to an active deviation or change request keep working while that process is under way.

✨ Dashboard rebuilt around the Compliance Statuses — New scorecards (Total, Compliant, Awaiting Actual Documents, 3rd Party Control, Pending Review, Expired, Compliance Rate, Expiring in 30 Days — including approved extension dates), a compliance-colour breakdown chart, Valid-documents charts by category and department, a 10-row Recent Activity list and an Expiring Soon list based on the effective expiry date.

???? Material management joins the Academy — the difference between saving a document and spending stock — A new tile covers the property stores end to end across all eleven of their screens: the catalogue of materials, the stores themselves, and the six kinds of document that bring stock in, send it out, move it between stores, correct it and return it. The rule everything else depends on is that a quantity changes when a document is approved and never merely because somebody typed it — and the tile is direct about the part that is easy to miss underneath. When no review route has been set up for a kind of document, that document is approved the instant it is saved and the stock moves there and then, with no reviewer and no queue. On this property no route has been set up for any of the six, so saving is spending, and everybody involved believes the review step is there. Four more rules routinely catch people out. A store can be switched out of sight while still holding stock, which leaves real quantities counted in the valuation and impossible to issue, and two of the stores here that read like the real ones are switched off exactly that way. Approving is not a permission anybody can be granted — an approver has to be named on the document — so a document left without a request can never be approved by anyone at any level, and there is one such transfer sitting on this property today, described as completed, whose stock never moved and now cannot. The low-stock warning only looks at items that already hold stock, so the item that has run out completely is the one item it can never warn about, and the daily check here is switched off with nobody nominated to receive it. And a correction can only adjust a count that already exists — stock never recorded has to be received, not adjusted into being. The tile closes with an honest read of the stores as they stand: a carefully built catalogue of 136 materials with considered reorder levels, one recorded delivery in, not one recorded delivery out, and therefore no repair cost anywhere on the property that includes the parts it consumed.

???? Database Mgt joins the Academy — and the switch that actually publishes — A new tile covers the property help library, which the menu calls Database Mgt and everything else calls the Knowledge Base. It teaches writing an article, organising the categories, the review workflow and what residents see. Most of it is devoted to one distinction that causes nearly every problem on the feature: the approval status and the switch that makes an article visible are two separate things, and it is the switch that publishes. So an article marked as approved can be invisible to everybody, and an article that never went through review at all can be live — which is the case on this property right now, where a password-reset article with no review status is readable by anybody, without even signing in, because guest access is switched on. The tile gives the four independent gates that decide whether a reader ever sees an article and the order to check them in, warns that switching a category off hides every article inside it at once, and explains that the helpfulness score is limited by network connection rather than by reader, so everybody sharing a building connection gets one vote between them. It also notes what the library currently looks like to a resident opening it: nine categories, three of them empty and two sharing the same name.

???? Asset management joins the Academy — sixteen screens and forty-five rules — A new tile covers the asset register end to end: how equipment is classified and tagged, where it lives, what condition it is in, the five other kinds of inventory that sit alongside it, and everything the register is supposed to feed. Several of its rules are routinely misread and the tile is direct about them. There are two entirely separate status questions, not one — whether equipment may leave the store, and whether it is any good — so "how many assets are broken" is answered by a column most people never look at. There are likewise two separate ways of recording where something is, and choosing an owner silently switches between them. Only equipment marked as deployable can be handed out, which is the one refusal that stops a broken machine reaching somebody. A component is fitted into an asset while accessories, consumables and kits are lent to people, and that single distinction is what makes six similar-sounding screens make sense. The tile is also candid about the state of the register here, because it changes which screens can answer a question: two hundred and fifty-eight assets are flagged as needing routine servicing, not one maintenance record has ever been created, no audit has ever been run, no valuation has ever been calculated, nothing is currently requestable, and eleven of the sixteen screens are empty. Read alongside the work-order tile, where the schedules meant to produce that servicing have generated nothing, it gives anybody joining the property an honest picture on day one instead of month three.

???? Work order management joins the Academy — the biggest rule book in the product — A new tile covers work orders end to end, with seventy-two business rules across twenty-six lessons, because almost none of them is guessable and each one refuses an action, locks a record or hides something. The four that cost real money get the most room. Only somebody assigned to a work order may run its timer, which is the commonest reason a technician standing in front of the equipment cannot log the hour they are about to work. Once a work order has been billed it locks permanently and corrections have to move to the invoice — and nobody on this property has met that yet, because two hundred and thirty-four work orders are marked chargeable and not one has ever been charged. Deleting a recurring work order deletes every occurrence it ever produced, so "delete this one job" can quietly mean deleting thirty. And a schedule existing is not evidence that it is producing anything: sixteen preventive schedules are set up here and there is not a single occurrence anybody can work. The tile is also candid that the status list has an eighth entry nobody documents — an Invalid state that is read-only, uncountable and cannot be deleted by anybody at all — that the status numbers are not in the order they are displayed, that a photograph cannot be posted without a comment, and that a work order not attached to a project can never be shown to a customer however its visibility switch is set.

???? Transaction summary joins the Academy — and PMP is complete — A new tile covers the one report that counts the whole property on a single page: eight grids of type against status, from complaints and bookings to visitors, parcels, work orders and compliance documents. It teaches how to read a grid without getting the axes the wrong way round, why a total that looks high is usually correct (it counts demand, including the cancelled ones, and the status columns are the breakdown), why one column in some sections is deliberately left out of the totals, and that every cell can be clicked to reach the real records behind it. Two warnings carry most of the weight. Leaving the dates empty does not mean this month — it means everything ever recorded, and an all-time total looks exactly like a monthly one, which is the easiest mistake on the screen. And the history this report depends on only exists if snapshots are being captured: they cannot be created after the fact, so a month nobody captured is gone for comparison purposes. On this property a daily schedule has read "enabled" since February and has produced one snapshot in its life, with nothing anywhere to say so — which is why the tile ends on a five-second monthly check of the newest snapshot date. With this tile the whole Property Management Portal menu is now covered.

???? Ticket reports joins the Academy — A new tile covers the complaints reporting screens: the live dashboard and its headline figures, the focused status view, the report generator with its eight ready-made templates and saved presets, scheduled delivery, and the full timeline on any single ticket. Four of its lessons exist because this feature quietly decides what you are looking at before you read it. On this property the dashboard opens filtered to two statuses, so the forty-seven complaints being worked on right now are missing from the landing view — and since this screen also replaces the platform home page, that is the first thing everybody sees each morning with nothing to say anything is hidden. Its figures are remembered for an hour, so closing tickets and refreshing changes nothing, and staff have been redoing work they had already done. The filters you set follow you between visits, so a Friday filter still narrows Monday. And two colleagues can read the same report and get different totals, because one may only be permitted to see their own tickets. The tile finishes with the three habits that defeat all of it in about fifteen seconds, and is honest that two of the feature's five screens are missing from the menu entirely, that reporting on work is switched off here, and that average resolution time counts nights and weekends — so it must never be quoted as working hours.

???? Reports Studio joins the Academy — A new tile covers the self-serve reporting tool end to end: the three choices that build a report, the filter you cannot download without, previewing, the three formats and when to use each, the archive of everything you have ever produced, and the saved reports that can run on a timer. Most of the tile is devoted to the three things that quietly reshape a report and never say so. A date range longer than the allowed span is not refused — the end date is moved back and the file comes out looking perfectly normal, so a request for three years returns one. An export bigger than the allowed size is not refused either; it simply stops at the ceiling, and nothing on the file or in the archive marks it, so a file that opens cleanly can be missing records with no way to tell afterwards. And because a report only ever shows the properties somebody is allowed to see, two colleagues can run the identical report and get different files, both correct. The tile also explains the one habit that catches all three before they cost anybody anything, why archived files disappear after a year without warning, and why a saved report will never fire until an administrator switches scheduling on — which on this property has not happened.

???? Personnel manning joins the Academy — A new tile covers the largest area in the product, all thirteen of its screens: the people on site, the companies that supply them, the shifts they work, the roster that puts them on those shifts, whether they turned up, why they were away, their paperwork and the reports over the top. It is deliberately blunt about four things that quietly cost sites real money. A person whose employment status was never filled in disappears from every roster with no message and nothing that will ever find them — more than a fifth of this property. An absence that was filed but never approved still counts against the person, and two-thirds of the absences here are in exactly that state, waiting for an approval that nothing will ever chase. The screen called Timesheet has nothing to do with site personnel at all — it reports hours that office staff logged against work orders, so no amount of filtering will ever show a contractor on it. And a whole set of working-hours rules sits in the system looking exactly like configuration while being read by nothing, so the only numbers that actually decide anything are the grace window and the shift. Also covers what the time-and-attendance terminals do on a property that has not registered any, why an attendance percentage only describes the people who were rostered, and the honest list of what happens automatically — which is far shorter than most people assume.

???? Resident accounts joins the Academy — A new tile covers the directory where staff answer the question they are asked most: can this resident actually get in? It separates the three things everyone calls "the customer" — the home, the account and the person — and is blunt about the consequences: an account is created with every home but a person never is, so a great many rows show a customer nobody can invite. It teaches the seven status badges and which of them this property has never once reached, then draws the line staff most often cross — one button sends the activation that creates a login, and the button beside it sends a completely different message, will send it to people who have never signed in, and will send it again every time it is pressed. Also covers the name shown in the list and the rule behind it, the switch that withdraws access without losing any history, what the email-delivery column is and is not telling you, bringing hundreds of people in from a spreadsheet and back out again, what a resident can change for themselves, the four separate permissions this one screen needs, and the honest list of what the system does on its own — which is far shorter than most people assume.

✨ Service requests now teaches its reporting screens too — The service tile gained lessons for its Dashboard and its audit log, matching the amenity tile. The Dashboard lesson explains why its status cards never add up to the total — three of the six statuses have no counter at all, so a manager asking how much work is in progress or was cancelled has to use the request list instead. The audit log lesson covers the screen that is not on the menu at all: what it records, that it captures the value before and after a change, and why it is currently empty.

✨ Amenity booking now teaches its reporting screens too — The amenity tile gained two lessons for the two screens residents never see: the Dashboard and the Audit Log. The Dashboard lesson is candid that every counter on it is all-time rather than upcoming, so an approved figure includes every booking that already happened and cannot answer "what is coming this weekend". The Audit Log lesson explains what is recorded, that it captures the value before and after a change, and why the screen is currently empty — the recording was added part-way through this year, so the trail starts from then rather than from when the property opened.

???? Statements and payment joins the Academy — A new tile covers the money side of a resident relationship: the difference between a single charge and a full Statement of Account, how to produce and send a statement for any period, how and when a charge becomes overdue, and what a resident can actually see and do about their own balance. It is deliberately blunt about two things that cost the most when misunderstood — residents cannot pay through the app or the portal on this property, so the front desk needs the right answer ready, and every payment received has to be entered by a person, which means the whole account book is only as accurate as that habit. Also covers where charges come from (including the ones the front desk creates by approving a booking), correcting a charge properly, recurring dues, and the fact that nobody is being chased automatically.