Where they started
Changes to the daily vehicle hire page were requested through informal messages, often without identifying the exact wording that needed replacing.
Migration and upkeep
Recorded approvals for daily vehicle hire changes
For daily vehicle hire, approval and publication now refer to one recorded version. The follow-up email chains that used to accompany every edit have largely disappeared.
- Client
- Budget daily car hire office
- Region
- Akron, Ohio
- Team
- 10 staff, one locally managed operation
- Timeline
- 25 working days, from content approval
- Quoted
- Lucas Harwood, Front office coordinator
The engagement
Before the build
What kept going wrong
Day to day with daily vehicle hire, requests meant different things to different people. Approval happened in principle, then publication happened in practice, and the two did not always match.
What we built
Every change is captured as one brief record: where, from what, to what, approved by whom. Updates concerning rental conditions and collection instructions follow the identical route.
Where this lives in a plan
Features used
- Structured change request
- Named approver
- Before-and-after preview
- Publication check
How the 25 working days ran
25 working days after content approval, including staff review and handover. Four stops, from signed-off wording to the day it went live.
Content approved
The 25 working days count starts here, once the team has signed off the wording the site will use.
The build
Structured change request, named approver, before-and-after preview and publication check.
Staff review and handover
The team's own staff reviewed the work and took it over, inside the same 25 working days.
Live
For daily vehicle hire, approval and publication now refer to one recorded version. The follow-up email chains that used to accompany every edit have largely disappeared.
Approving a daily vehicle hire change now means reading the old line and the new line. I see exactly what will appear before it does.
Questions about this case study
How long did this take for the budget daily car hire office?
25 working days after content approval, including staff review and handover. Because the count starts at content approval, the time the team spent agreeing the wording is not inside it, and their own review before launch is.
What exactly was built?
Every change is captured as one brief record: where, from what, to what, approved by whom. Updates concerning rental conditions and collection instructions follow the identical route. The pieces it used: structured change request, named approver, before-and-after preview and publication check.
Is this part of a GetRentalWebsite plan?
The work here maps to weekly updates to fleet and rate text and hosting, security and speed, managed on the features page, which every plan carries. Plans start at $127 a month, with the $697 build fee invoiced only after launch. How it is shaped for your own operation is agreed on the demo call.
Why is the business not named?
Case studies on this site describe the client by the kind of operation and the city, here a budget daily car hire office in Akron, Ohio, and quote the person we worked with, Lucas Harwood, front office coordinator. The business name, web address and logo are left out on purpose.
Want the same fix at your rental desk?
A live walk-through of the site you would get, built around how your team already works. Plans from $127 a month, the $697 build fee invoiced only after launch.