Rental Calendar Saved Views: Build a Daily Handover
Use Rentshelf calendar filters, saved views and CSV export to prepare focused rental handovers for pickups, delivery and overdue booking follow-up.
✦ Summarize with AI
Choose your assistant. Opens an external site; it may require sign-in.
ChatGPT ↗Perplexity ↗For Claude, Gemini or Grok, copy the prompt and paste it into your assistant.
In this article
- 1Design the view around a staff decision
- 2Filter before saving
- 3Use names that explain the scope
- 4Export the checked view for a handover
- 5Keep the calendar as the current reference
- 6Give the handover an explicit cutoff
- 7Check an empty view before cancelling preparation
- 8Retire views that no longer match the work
Quick summary
- Turn a busy operations calendar into repeatable staff views with filters and saved views.
- Export the active month and filters when preparing an operational handover.
- Treat a downloaded CSV as a snapshot that needs refreshing when bookings change.
Design the view around a staff decision
A calendar containing every rental is useful for an overview, but the colleague preparing collections needs a smaller set of records. Rentshelf saved views let you reuse calendar filters for recurring operational tasks. The goal is to make a daily decision easier: what needs preparing, what is currently out, or what needs follow-up?
Start with the actual handover between shifts. Write down what the next person must know and which records belong in that handover. A short list with a clear scope is more useful than a large export that every team member has to interpret differently.
Filter before saving
The operations calendar supports filters including product, status, customer, delivery method, tag and date range. Use the combination that reflects the work. For example, a delivery view can focus on the relevant delivery method and dates, while an overdue review can begin with the overdue status.
Inspect the records before saving the view. Check the active month as well as the filter dates: a familiar view name should never be taken as proof that the displayed period is the one you intended. When a result looks unexpectedly empty, review the whole filter set before concluding that there is no work to do.
- Maintenance entry — Inspect the actual blocked quantity before relying on an entry to reduce availability.
Use names that explain the scope
Save useful combinations with names that describe the task, such as “Delivery preparation” or “Overdue review”. Avoid personal names or vague labels such as “My filter”. Other staff should understand why a view exists without asking its creator.
Saved views reuse a filter configuration. Review dates when reopening them rather than assuming every date range advances automatically. When your operating process changes, update or replace the view so that its name continues to match the records it shows.
Export the checked view for a handover
Rentshelf calendar CSV export respects the active month and active filters. Apply the intended filters, inspect the calendar and then export. If you need a broader list, clear the restrictions you do not want before downloading.
Open the app from Shopify admin when exporting. The download should be a CSV attachment. If it fails or returns an unexpected page, reopen the app and retry rather than forwarding an invalid file to staff. Once downloaded, label the file with its period and preparation time so the receiving team knows what it covers.
- Confirm the month, date range and operational filters.
- Check a known booking that should appear.
- Check that an unrelated booking is excluded.
- Download and open the CSV before sharing it.
- Refresh the export after material booking changes.
Keep the calendar as the current reference
A CSV is a snapshot. A booking changed after export will not rewrite the file already on a colleague’s device. Agree on when the team must return to the app for the current booking record, especially before a pickup or a return decision.
At the end of a shift, review what remained unresolved rather than merely counting exported rows. This turns saved views into a working habit: a consistent scope, an identifiable handover and a current record to check when something changes.
Give the handover an explicit cutoff
An illustrative morning handover might cover today's warehouse collections, exported at 08:30. A booking accepted at 08:45 will not be in that file. Write the cutoff on the handover and agree who checks for later changes before items leave. This is especially important when the person printing a list is different from the person serving the customer.
Include unresolved exceptions beside the list: a unit waiting for inspection, an address awaiting confirmation or a customer asking to change dates. The export identifies bookings; the exception note explains work that may not be obvious from a row. Use the booking reference to connect the two, and avoid scattering extra copies of customer details across informal chat messages.
Check an empty view before cancelling preparation
An empty calendar can mean there are no matching bookings, but it can also mean the month, status and date filters contradict one another. Start by clearing the least essential filter, then confirm the period. Compare one known booking with the filter conditions. This is faster than repeatedly refreshing a view whose saved scope is simply wrong.
A useful training exercise is to create a view for one known booking, save it, change the month and reopen it. Ask the colleague to explain what remains filtered and what period is visible. Record observed behavior instead of assuming a label such as “this week” always follows the current date. Saved configuration and live business meaning are different things.
Retire views that no longer match the work
Review the saved-view list when roles or delivery arrangements change. Two similarly named views with different status filters are an easy source of inconsistent handovers. Keep a small set of clearly owned views, and explain which one is the default starting point for each task.
An export containing personal information should remain in the appropriate staff workspace. Share only the fields and period the receiving role needs, and follow the business's retention process. The convenience of a spreadsheet does not make every historical booking relevant to today's driver or collection desk.
Try the workflow with one booking and a staff handover
Open the booking instructions and follow the record through preparation, handoff and return. Ask us about any step you cannot reproduce.
FAQ
What does the calendar CSV export include?
It respects the active month and current filters. Review these before exporting, especially when you need a complete list rather than a focused handover.
Does an exported CSV stay synchronized?
No. Treat the downloaded file as a snapshot and export again when you need updated booking information.
How should staff name saved views?
Use a task-based name that describes the purpose. Recheck date filters whenever the view is reused so the period matches the current handover.
Why might a saved calendar view be empty?
Check the active month, date range and all filters before concluding there are no bookings. Use one known booking to test the view's scope and remove filters that are not needed for the task.
Should a driver receive the full booking history?
Usually the useful handover is a focused period and delivery scope. Give the role the information needed to fulfill that work, keep unresolved exceptions identifiable, and use the current app record for later changes.