On-call rota: covering the out-of-hours without burning the team
An on-call rota decides who answers at 3am. How to size it, what to pay, what counts as working time, and the handover that stops the same fault being rediscovered.
Folder hierarchies fail the moment a file belongs in two places. Filters, search and a naming habit beat them — here is the setup.
Every shared drive starts the same way: someone builds a neat folder tree, everybody agrees it is sensible, and within a month there are four folders called Final, two called Archive, and a file that genuinely belongs in both Clients and 2026 but can only live in one.
The problem is not discipline. A folder tree forces one dimension — usually project or year — onto files that people actually look for by type, by recency, by who sent them, or by what they were called. Filtering picks the dimension at the moment you search, which is why it wins.
In Ettex, Storage lists everything you have across the apps — documents, sheets, decks, PDFs, images and uploads — with filters for type, source app, update date and size, plus grouping by any of them. At larger scale the same problem is what digital asset management solves with metadata rather than folders.
Filters narrow, names identify. A few habits make the difference between search that works and search that returns eleven candidates:
Most people work on maybe ten files at once, out of thousands. Starring those ten gives you a list you can open without searching at all — and because favorites in Ettex are one list across every app, it does not matter whether you starred the file in Storage or in the editor.
Group by is the other underused move: grouping a filtered list by source app or by date turns a flat wall of names into a handful of labelled blocks, which is far easier to scan than any sorted list.
Notice that all three are about moving or governing files in bulk — not about finding them. That is the honest division of labour: containers for policy, filters and search for retrieval.
For finding things, rarely. For handover, retention rules and access boundaries, yes — those need a container you can point a policy at.
Filter by update date rather than searching. Sort or group by date and the file you touched yesterday is at the top — no name required.
Stop trying to place it. Name it so both projects' keywords appear, and let filters do the rest — that is exactly the case a single folder cannot represent.
Only if you have one list that spans them. In Ettex, Storage aggregates files from every app, so a filter applies across documents, sheets, decks, PDFs and uploads at once.
Keep an eye on the storage overview. Files too big to keep in the browser are flagged as local-only, so you know which ones exist on one device rather than everywhere.
You will not miss the tree. Pick the dimension that matters at the moment you are looking, name files for the way you type, and keep ten favourites for the work in front of you.
An on-call rota decides who answers at 3am. How to size it, what to pay, what counts as working time, and the handover that stops the same fault being rediscovered.
A canned response answers a repeated question consistently. Which ones to write, how to keep them from sounding automated, and the rule about never sending one unedited.
How stock is valued changes reported profit and tax without anything physical changing. FIFO against weighted average, what cost includes, and the write-down nobody wants to make.