Where they started
The previous site's knowledge left with its designer. Updating daily vehicle hire information meant guessing or waiting.
Migration and upkeep
Daily vehicle hire documentation the team can actually use
For daily vehicle hire, the team holds a usable operating reference from day one after launch. A colleague covering an absence can find the right person and follow documented steps without reconstructing the project's history.
- Client
- Business district car hire branch
- Region
- Frederick, Maryland
- Team
- 7 staff, one locally managed operation
- Timeline
- 25 working days, from content approval
- Quoted
- Russell Hollyoak, Customer inquiries lead
The engagement
Before the build
What kept going wrong
Day to day with daily vehicle hire, nobody internally knew the procedures: who approves, how to request, what to check. Ordinary maintenance waited on one person's diary.
What we built
The handover packages a page inventory, update instructions and a contact list, plus a short guided check of the route to an availability response from the hire desk. Ownership of rental conditions and collection instructions sits with a named person and a named backup.
Where this lives in a plan
Features used
- Page inventory
- Maintenance notes
- Backup reviewer
- Form check instructions
- Support contacts
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
Page inventory, maintenance notes, backup reviewer, form check instructions and support contacts.
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, the team holds a usable operating reference from day one after launch. A colleague covering an absence can find the right person and follow documented steps without reconstructing the project's history.
I judge a project by what happens after launch. The daily vehicle hire documentation means the site survives my vacation.
Questions about this case study
How long did this take for the business district car hire branch?
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?
The handover packages a page inventory, update instructions and a contact list, plus a short guided check of the route to an availability response from the hire desk. Ownership of rental conditions and collection instructions sits with a named person and a named backup. The pieces it used: page inventory, maintenance notes, backup reviewer, form check instructions and support contacts.
Is this part of a GetRentalWebsite plan?
The work here maps to hosting, security and speed, managed and weekly updates to fleet and rate text 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 business district car hire branch in Frederick, Maryland, and quote the person we worked with, Russell Hollyoak, customer inquiries lead. 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.