Cutting a register down to what matters, and keeping that view for tomorrow. Once a project is a few months old, every register is long, and this is the lesson that keeps them usable.
Filtering
A filter narrows the register to the rows that match a condition: open RFIs, documents at revision C, inspections due this week. Filters stack, so "high priority and overdue and assigned to my organisation" is three conditions rather than a search.
Grouping
Grouping folds the same rows into collapsible sections: documents by discipline, contracts by organisation, observations by status. It answers a different question from filtering. A filter asks which rows; a group asks how the rows divide up.
Saving a view
A filter and grouping combination you use every week is worth saving. A saved view remembers the filters, the grouping, the columns and the sort, and it is one click to come back to. Name them for the question they answer, not for the fields they use: "Overdue with the engineer" beats "status filter 2".
A note for guests
Saved views are a host-side feature. As a guest you can filter and group exactly as described here; you simply cannot keep the combination as a named view.