Ending a tenancy: the order of operations that avoids a dispute
Ending a tenancy goes wrong in predictable places — notice, access, the final inspection and the deposit. A sequence that keeps each step provable.
Deleted the wrong paragraph, or pasted over an hour of work? Version history gets it back — here is how it works and how to avoid needing it.
Almost every lost document is lost the same way: nothing crashed, nobody deleted a file. Someone selected all, pasted the wrong thing, kept working, and only noticed twenty minutes later. Undo has moved on by then, and the file on disk is the broken one.
That is what version history is for. It is not a backup of the file — it is a running record of what the document looked like at different moments, so you can go back to any of them.
In Ettex, snapshots are written automatically while you edit — at most once every 15 seconds, only when the content actually changed, and the last 30 are kept. This is the everyday form of document version control, and the reason approvals should point at a frozen version.
Manual versioning depends on remembering to do it at exactly the moment you are least likely to: mid-edit, in a hurry. It also multiplies files, and once two people have their own copies, merging them is a bigger job than rewriting the paragraph.
Automatic snapshots invert that. You do nothing while things go well, and the record is already there on the day something goes wrong. The cost is that history is bounded — you get recent history, not an archive going back a year. For documents where the long trail matters, keep the milestone versions as documents of their own.
Spreadsheets and presentations are snapshotted too — a sheet version records how many cells were filled, a deck version how many slides it had. The same “that got much smaller” heuristic works for a deleted sheet range or a slide someone removed before a review.
Ettex keeps the last 30 snapshots of a document. How much time that covers depends on how heavily you edit — a document you write in one sitting may have all 30 from that afternoon.
No. The newer snapshots stay in the list, so if you restore the wrong version you can go forward again.
The document has not been edited yet. Snapshots start once you change the content — type something, wait a few seconds, and the first one appears.
Version history covers changes inside a document, not the document itself. A deleted document goes to Trash in the document list — restore it from there, then use versions to get the right content back.
Yes. Snapshots are written on your device as you edit, so history is there whether or not you are connected.
Version history is one of those features you ignore until the day it saves an afternoon of work. It costs nothing to know where the tab is before that day arrives.
Ending a tenancy goes wrong in predictable places — notice, access, the final inspection and the deposit. A sequence that keeps each step provable.
A franchise agreement licenses a brand and a method in exchange for fees and control. What to read before signing, and what the franchisor is really selling.
A product requirements document says what is being built and why. The sections worth keeping, the ones that waste a week, and how to stop it going stale.