Releases

3.206.0 current

8 November 2026

• A customer can have Xero email them the invoice from the pay link, for their accounts team to pay. Under the ways to pay, Email me the invoice instead makes the invoice for whoever the customer chose on the page, with no tip added, and then shows where Xero will send it: the email address on the invoice's contact in your Xero, partly hidden unless they are signed in. Send it asks Xero to email it from your Xero with your usual invoice email; JollyDrivers sends nothing of its own. The trip's history shows the invoice was emailed and that the customer asked on the pay link. Once emailed this way the invoice can't be changed on the page, so the copy the accounts team holds stays good, and one invoice can be emailed three times a day from the link. If the contact has no email address in Xero, the customer is asked to get you to add one. It shows wherever the trip page's Email option (the Xero invoice email switch) and pay links are on.

3.205.0

8 November 2026

• Book a quote for the customer when they say yes by phone. A quote's card has a new tile, The customer said yes, above Withdraw the quote, for the driver on it, whoever made it and the operator's office. It books the quote the way the customer's own Accept would: the same booking number, confirmed with its driver through the usual compliance check, or left for the office to confirm. It asks first, and one press books every trip on the quote. The trip's history says who booked it for the customer, never that they accepted it themselves, and the card then says "Booked for the customer, who said yes." Nothing is sent to the customer: send the confirmation from the trip page when you're ready. Once the quote's hold has run out, a driver who has been booked at that time since gets a question, Book it anyway?, instead of a refusal. Whoever pressed it isn't texted or emailed about it, and anyone else who is told hears who booked it.

3.204.0

8 November 2026

• A driver can cancel a booking from the Dispatch app, and a driver's reason for cancelling is now kept. At the foot of Trip progress in the app, a Cancel booking card (Cancel task on an attendance job) has the trip page's reasons, an optional note and a red swipe that won't move until a reason is chosen, with a 5-second Undo. It shows whenever the trip page would let the driver cancel the job, including one you haven't confirmed yet; a delivery is still cancelled in JollyDrivers. It needs signal, nothing is sent to the customer, and a ride back booked as its own booking stays. Whether from the app or the trip page, a driver's cancellation now shows on the timeline as "Cancelled by driver" with the reason and note beneath, for you and the trip's drivers and never the rider; until now only an operator's reason was kept. A new switch on the Dispatch page, Cancel, ships off and asks first. It needs the app's next build; phones on older builds see no change.

3.203.0

8 November 2026

• The Dispatch app can keep the job you've just finished on screen. After Completed is swiped in the app, the job stays, with Text the pay link and Next job where the swipe was, so there's time to text the customer the pay link, and the pay link window opens by itself once when the link can be texted. Next job goes on to the next one. If it isn't tapped, the finished job goes by itself two hours after Completed, or as soon as another job is under way. A no-show, or a job completed in JollyDrivers, moves the app on as before. A new switch on the Dispatch page, Finished job, ships off. It needs the app's next build, which also drops the card for a last trip that isn't paid; phones on older builds see no change.

3.202.1

7 November 2026

• The Trip record on a pay link shows when the trip ended in the time where it ended. On a trip from Coolangatta that ends in Murwillumbah, it now says the trip ended at 5:14 pm AEDT · NSW instead of 4:14 pm AEST · QLD, as the trip's timeline already does. When the trip started still shows the pickup's time, and on a group invoice each trip shows its own. JollyDrivers' own tax invoice PDF prints the same lines, and nothing sent to Xero has changed.

3.202.0

7 November 2026

• Call and Text for everyone else travelling. Each person on a trip's Also travelling list who has a mobile now has Call and Text of their own: on the trip page's Comms, under the passenger, and in the Dispatch app's Call or text window, between the passenger and the customer who booked, in the trip's own order. Both open the driver's own phone at that person's mobile, and the trip's timeline notes each call or text with their name, as it does for the passenger. JollyDrivers itself still sends nothing to these numbers, and an operator sees these people without Call or Text, as with the passenger. Phones already on the Dispatch app show them straight away; its next build lets a long list scroll under the window's heading.

3.201.1

7 November 2026

• Training refresh reminders don't text a driver who has replied STOP. The Jolly Academy reminder that a course is due for a refresh now checks the SMS opt-out list before it texts, as the compliance expiry reminders do. A driver on the list gets the reminder by email instead, and a driver with no email gets nothing. If the list can't be read, no text is sent and the email is tried. The reminders are still switched off until they are turned on.

3.201.0

7 November 2026

• Drivers can text the customer the pay link from the Dispatch app. A Pay link button sits after the fare on the job, and on the card for a last trip that isn't paid, while the link can take a payment. It opens a small window that shows who the text goes to and the message, in the same words as the trip page's Text it. Open messaging app opens the driver's own messaging app with the number and the words filled in, and the driver presses send there. Where someone else booked and the passenger has a number of their own, either can be texted. The trip's timeline says the pay link was put in a text, via Dispatch. Texted from the card after Completed, the invoice is raised in the background, as when it's sent from the trip page's Payment drawer. JollyDrivers sends nothing itself, and the window needs signal. A new switch on the Dispatch page, Pay link, ships off and asks first when it's turned on. It needs the app's next build.

3.200.1

7 November 2026

• The Driver app's pages show its new job screen. The pictures on the Driver app page are new, and it says how the job works now: tap a stop for directions, and tap the passenger's name for Call and Text, with no Navigate, Call and Text buttons along the bottom. A new picture shows Call or text opened from the name. The front page and How it works say "Directions, Call and Text" to match.

3.200.0

7 November 2026

• Drivers can change an unpaid fare from the Dispatch app, on a booking they made. Tapping the fare on the job opens a small window with the fare now and a box for the new one. Save works the way the trip page's Fare window does: it's refused if somebody changed the fare meanwhile, it asks first before lowering a fare that has already been billed, and the timeline shows the change as the driver's, via Dispatch. Nothing is sent to the customer, how the customer will pay stays on the trip page, and it needs signal. Once any money has been taken, the fare is changed on the trip page. A new switch on the Dispatch page, Change fare, ships off and asks first when it's turned on. It needs the app's next build, which also moves Call and Text onto the passenger's name.

3.199.1

6 November 2026

• On a trip, the Drive time and Driver & Vehicle cards start closed. Tap a card's heading to open it. Closed, Drive time still shows the planned drive ("3h 13m planned"), and when the drive you've chosen needs a different pickup it says that too ("needs a 4:26 am pickup").

• Driver & Vehicle names the driver and the car under its heading, for example "John Gentner (Jolly) · 2021 White Kia Carnival", on a phone as well. With no car yet, no driver yet, or a driver picked on the website, it says so in the same place. The plate is inside the card.

3.199.0

6 November 2026

• Every public page now has the same look, with one header and one footer. Driver app, Rider app, How it works, Compliance, About and Sign in run across the top, with FAQ and Blog added in the menu on a phone. The blog, Releases, the privacy documents and the compliance guide carry them too; under them, the guide's pages are as they were.

• How it works is rewritten around the two apps. It shows how the Driver app, the Rider app and JollyDrivers fit together, follows one booking from the rider's price to the record, takes the road from driver to operator a stage at a time, and has Your AI in full: what an assistant can do with and without an account, and how it is kept in check.

• About and the FAQ are shorter and up to date, starting with how riders book: with their operator, on the operator's own website. Each FAQ answer opens with a tap.

• The privacy documents are plain pages in the site's look, with their published words unchanged, and no longer open behind the app's loading screen.

• The blog and Releases take on the new look with their words unchanged.

3.198.0

6 November 2026

• The Driver app and the Rider app each have a page of their own on jollydrivers.com.au. /driver-app takes the Driver app one thing at a time, each with a real screen: the job in front of you, Navigate, Call and Text, a swipe for each stage with Undo, no signal, the flight on an airport job, the card after a trip that isn't paid, your jobs, Ask, and putting it on your phone. /rider-app does the same for the operator's own website on the rider's phone, shown as Jolly Frog's: every driver's price, booking, one sign-in, your trips, following the car, paying, trip updates, and what the operator sets in JollyDrivers.

• The front page is shorter and leads with the two apps, each on a block of its own with its phone and a link to each thing it does. Then come the journey from driver to operator, a short band for operators, compliance in Queensland and New South Wales with the state tiles, and how to get in touch. The detail moved to the pages it belongs to, and every compliance claim the page made is still on the site.

• The new pages share one header and one footer: Driver app, Rider app, How it works, Compliance and About, with a menu on a phone. The other public pages take on the same look in the next release.

• The pictures are real screens: the Driver app's of sandbox test trips, and the Rider app's of jollyfrog.net.au. Its signed-in screens show a sandbox trip through a stand-in, because a sandbox operator's site texts no sign-in code.

3.197.1

6 November 2026

• The compliance guide now says the check when a driver is assigned can refuse as well as warn. It used to say JollyDrivers only warns. Each operator chooses on Settings → Compliance: Advisory, the default, tells you and lets you go ahead with your name on the record; Enforce refuses the assignment; Off shows nothing but still records every check. The guide's Queensland and New South Wales pages say the same.

• Where the guide says JollyDrivers still falls short, the old "only warns" line is now what enforcing doesn't cover: a trip JollyDrivers can't check, and an attendance job like walking a dog, are only warned about, never refused.

3.197.0

6 November 2026

• A saved draft can become a quote. The Submit Booking window on a draft trip now has Send as a quote beside Submit. It turns that same booking into a quote, with the same booking number, route, price, driver and notes, so nothing is typed again. The trip page then shows its quote card, where you send it to your customer by email or text, and they accept or decline it like any other quote. Nothing goes to the customer until you send it.

• The driver's time is held from the moment it becomes a quote, for the hours in their pricing settings and never later than an hour before pickup, as with any quote. The trip's timeline says "Turned from a draft into a quote".

• A draft needs a price first: without one it says "Add a price first" and stays a draft, with Submit still there. A draft that's part of a group, or whose pickup has passed, isn't made a quote. Only passenger trips are quoted, and only while Quotes is switched on. On a phone the window's three buttons sit one above the other.

3.196.0

6 November 2026

• Riders can add stops on the way when they get a price on your website. Once your website has its update, Get a price has Add a stop between the pick-up and the drop-off, up to three. Each stop has the same address search, and buttons to move it up or down or take it off. Every driver's price is worked out for the whole trip exactly as your own booking page's quick quote works it out, and Book makes the booking with every stop in order. It works for point-to-point trips and for airport pick-ups and drop-offs. On an airport drop-off found by its flight, the pickup time is worked back over the whole drive, stops included.

• After that it's a trip with stops like any other. The Route card, a card for each stop in Trip progress, the tracking page, the confirmation and the pay page all show them. There's no waiting at a stop: a stop is a quick set-down or collection.

• Your website's Book screen now shows where the trip goes: From, each stop as Via, then To, above the price, with or without stops.

• The Quick Quote Multi Stop switch, which already lets riders add stops on your booking page, does the same on your website. With it off, the website offers no stops.

3.195.0

6 November 2026

• Name the other people travelling on a trip. The passenger window (the pencil beside the passenger) has a new Also travelling section. Add someone by picking them from your customers or typing a name, give them a mobile if you like, and a +1, +2 for people with them who don't need a name, so "Sam +2" is Sam and two others. Who booked the trip and who the main passenger is don't change, and naming anyone is optional.

• A typed name is only a name on that trip. It isn't added to your customers. When a name or mobile you type is one of your customers, the window offers "Link to … in your customers" and links them only when you tap it. A mobile is an Australian mobile, or an overseas number starting with + and its country code.

• The passenger count still prices the trip. Add more people than the count and it goes up in front of you, before you save. It can't go below the people on the list until you take someone off.

• The trip page shows each party under the main passenger: "Sam +2", with their mobile to tap and call. The +N beside the main passenger is now just the people with them. A name you linked opens that customer's card, and the card lists the trip as "Travelling with" the main passenger. Send upcoming trips still lists only the trips a customer booked or is the passenger on.

• Nothing is sent to these mobiles. They're kept so that a fare can be split between the people travelling later, or one of them can pay the whole fare.

3.194.1

6 November 2026

• Extra drive time on the trip's Drive time card now moves in 5-minute steps, from none to +2 hours, so you can add +5, +10 or +35 instead of jumping by quarter hours. The booking chat's summary card keeps its +15 to +120 buttons.

3.194.0

6 November 2026

• A new front page for jollydrivers.com.au, written for drivers and operators. It opens on "Start as a driver. Step up to operator when it suits you." with three buttons, I drive, I want to become an operator and I already run an operator, and each leads to what matters to that person and a way to get in touch. Riders now book on their operator's own website, so a rider who lands here by mistake is told to book there.

• The journey, in three stages: Drive, Grow and Step up. A meter fills as you scroll through them. Step up says what each state asks of a new operator: a booking entity authorisation (BEA) from TMR in Queensland, and BSP authorisation in New South Wales. It also says what stays with you: the same account, your documents, training and cars, your customers and fare book, and your trips, earnings and hours.

• How the three parts fit together. JollyDrivers is the one record, the driver app is the job on the road, and the operator's own website is the rider's app. One booking is followed through all three, from the rider booking it to the invoice in the operator's Xero. The three phones at the top are real screens of one test trip, the same trip in each app.

• Everything the page said about compliance is still there. That covers the six steps of a trip under Queensland or New South Wales rules, the state tiles and the links to the guide and to where JollyDrivers still falls short. One line is truer than before: the check when a driver is assigned warns or refuses as the operator has chosen. It used to say it only warns. The compliance guide's own pages haven't changed.

• The story slides, the usual suspects and the flip cards have gone from the page. What they said now sits in the journey, the compliance section and the paths. Your AI, the figures, the blog and the straight answers stay.

3.193.0

6 November 2026

• A Drive time card on the trip page. Under Flight status (or where it would be on a trip without a flight), the card shows Google's drive for the trip's own pickup time three ways: Best case (light traffic), Expected traffic and Worst case (unusually heavy traffic). Tap the one to plan on. Your choice is kept on the booking, and the Route card, the drop-off time, the confirmation, the tracking page and the clash and driving-hours checks all follow it. It starts on Expected traffic, so nothing changes until you choose.

• Extra drive time is a slider now, from none to +2 hours in 15-minute steps, on the same card. It saves when you let go, and the card shows the total drive planned.

• On an airport drop-off each choice shows when to leave, and when the drive you've chosen needs a different pickup, a Set pickup button moves it, with the same check as before. Choosing a row never moves the pickup or sends your customer anything on its own.

• The card shows to whoever may change the trip's time, while the pickup is still ahead, with the Traffic Drive Time switch on. JollyDrivers now asks Google three questions per prediction instead of two.

3.192.1

6 November 2026

• The trip's Route card now gives the drop-off on the planned drive. With traffic time or your extra minutes on a trip, the card's footer showed the planned drive (say 2h 40m), but the drop-off time and the drive between the stops still used Google's plain figure (2h 8m), so the drop-off came out half an hour early. Both now use the planned drive, the same as the confirmation your customer gets. A trip with nothing added reads exactly as before.

• Your customer sees the same drive on their own trip page and in My bookings, the planned drive in place of Google's plain one.

3.192.0

5 November 2026

• Plan a trip's drive on the traffic at its own pickup time, and add your own minutes. With the Traffic Drive Time switch on, the booking chat asks Google how long the drive is likely to take at the trip's pickup time, not its average for any hour, and the summary card offers Extra drive time, +15 to +120 minutes, for when you know the road better than Google does. The planned drive sets the airport arrival and the time left before the flight, the pickup worked back from a flight, the confirmation, the quote page, the tracking page and the clash and driving-hours checks. Google's worst case shows as a line of information ("In heavy traffic this drive can take up to …") and never moves a time. The trip's Route card shows the planned drive and lets you change the extra minutes later. The price never changes. Off until switched on.

3.191.0

5 November 2026

• Ask in the Dispatch app can write up a problem for the JollyDrivers team. Tell Ask something in JollyDrivers or the app isn't working, or should work differently, and it offers to write it up. The report shows under its answer as a card, word for word as it will go, with a Send button. Nothing is sent until you press Send: Ask can't send it for you. Ask to change it and a new card takes its place. Once sent, Ask says which report it became, with My reports under it. The card comes with the next build of the Dispatch app.

3.190.0

5 November 2026

• Send your customer your website, in place of inviting them to JollyDrivers. On a trip, the people drawer now offers "Send Jolly Frog's app link" where it used to offer "Invite … to JollyDrivers". It texts the customer " from Jolly Frog: see your trips, pay and book again at" your website's sign-in, "- add it to your home screen." They sign in there with their own mobile, and their trips with you show up. It goes as one plain text, and the trip's timeline shows when it went. Copy link copies the address instead, and records nothing.

• It shows only where the trip's operator has a website with sign-in. With no website there is no button, for now.

• The invite buttons on the customers list and the customer card are gone. A customer card is yours rather than one operator's, so the link goes from a trip, which says whose website it is.

• Nobody is asked to set up a JollyDrivers account from a driver's invitation any more. A link already sent still works until it runs out, a week at most.

3.189.0

4 November 2026

• Pond, a fifth look for your website. Night water with light moving over it, and the districts you work in as lily pads, bigger the busier they are. Tap a pad to see its name and suburbs. On the home page a frog leaps onto a pad and the water opens onto your page, once a visit and in under two seconds. It skips at a tap, and never plays in the installed app or for anyone whose phone asks for less motion. Choose it on Settings → Website → Look; it starts as Not on my site, so nothing changes until you do.

• Districts on Settings → Website. Under Where you go, name the areas you work in, such as Gold Coast or Tweed, and choose the postcodes in each from your map. Each district shows how busy it is from 1 to 5, never how many trips. Pond draws them as its lily pads; the other looks don't use them.

3.188.2

4 November 2026

• Pasting a long rider terms or privacy policy no longer drops the connection. On Settings → Website, pasting anything over about 16,000 characters brought up the reconnecting dialog. The words never reached JollyDrivers, so you couldn't preview or publish them, even though they still showed in the box. Each box now takes up to 40,000 characters, and a paste that long goes through.

• Each box shows how much it holds, for example "13,866 / 40,000". If you paste more than 40,000 characters, the box stops there and a warning under it says the end of what you pasted may be missing, so you can check before you publish.

3.188.1

4 November 2026

• During an update, JollyDrivers can now tell the update whether anyone is part-way through paying. In 3.188.0 the payments pause refused new payments as it should, but JollyDrivers wasn't allowed to write its answer where the update looked for it. So every update waited a blind half-minute, and the trial run couldn't say whether it was a good moment. The answer now goes in the folder JollyDrivers already writes its logs to. The update waits for a payment under way, and the trial run shows how many pay pages are open, payments under way and trips ending around now. The deploy script on the server needs copying up once more for this.

• A problem writing that answer is logged once, not every two seconds. System Health still counts each one.

3.188.0

4 November 2026

• Payments pause for the minute a new version of JollyDrivers goes live, so a customer paying isn't caught halfway. A customer with their pay link already open could press Pay just as the site went down, and the payment was cut off with their invoice half made. Now, just before the site goes down, Pay, Pay by bank transfer, adding a tip, Get my tax invoice and Charge saved card all say "Paying is paused for about a minute while JollyDrivers updates. This page will carry on by itself." The update waits up to a minute for any payment already under way to finish before the site goes down. Someone already on Xero's payment page isn't affected. Request invoice and Mark as paid on a trip don't pause.

• A payment made while JollyDrivers was stopped now shows as paid within minutes, not the next morning. A minute after it starts, JollyDrivers asks Xero about every invoice a pay link sent someone to in the last two hours that isn't marked paid, in case Xero's message arrived while it was down.

• The "back shortly" page reloads itself every 20 seconds, so a customer who opens their pay link during an update lands back on it by itself.

• The trial run before an update now says whether it's a good moment: how many pay pages are open, how many payments are under way, and how many trips are ending around now. This is part of the deploy script on the server, which needs copying up once.

3.187.0

4 November 2026

• Your website's Trips screen can now list every trip a rider has coming up, not just the next one. JollyDrivers sends the website each trip after the next one, up to 20: its day and time, where it goes and where the booking is. A trip counts as the rider's when their mobile is on it, so trips somebody else booked for them, such as a PA, are listed too. The website shows them in a Coming up card once its own update is live; until then it keeps saying how many more there are. The car, the driver, Cancel, live tracking and Pay stay on the next trip, and the website never shows who booked a trip.

3.186.1

4 November 2026

• Send as a quote is easy to see in Booking Chat now. On the summary card at the end of a driver's booking chat it was drawn in the operator's own brand colour, which for most operators is nearly black, so on the dark card it could barely be made out. It now looks like Save as Draft above it, with light words and a light outline. "Name this place" under each address on the same card had the same problem and is fixed the same way. What the buttons do hasn't changed.

3.186.0

4 November 2026

• A customer's card now shows the trips somebody else booked for them, and Send upcoming trips includes them. When a PA, or anyone else, books a trip with your customer as the passenger, it appears in that customer's Trips list and in their upcoming trips email, marked "Booked by" and the booker's name. The booker's own card still lists it, marked "For" and the passenger's name. Who pays doesn't change: the trip is still billed to whoever booked it.

• Send upcoming trips offers to copy in whoever booked a trip for the customer. One tap adds them as a Cc, and nobody is added unless you tap it. The offer only appears when the booker's card has an email address, and it goes away if you untick their trips.

• Your assistant counts those trips too. A customer's schedule lists the trips booked for them and says who booked each one, and the customer search counts them among the customer's trips.

3.185.1

4 November 2026

• Your assistant can now send up to ten problems and change requests a day, up from five. The limit still counts the last 24 hours for each person, and it is the same for everyone who reports through an assistant. Ideas for the wishlist still don't count towards it, and the Report a problem page still has no limit.

3.185.0

4 November 2026

• Ask in the Dispatch app can now put buttons under an answer. When Ask asks a driver to choose, such as which licence they mean or a yes or no, the choices come as buttons, and tapping one sends those words as if typed. When going somewhere is the driver's next step, a button opens it: My Documents, Qualifications, My vehicles or Driving hours, or an outside page on JollyDrivers' own list. Ask can only name a place on that list and JollyDrivers makes every address, so nothing Ask writes can send a driver anywhere else. An empty conversation offers four questions to tap. Nothing more about a driver goes to the AI company. The buttons come with the next build of the Dispatch app. This release has a database change, which goes in first.

3.184.1

4 November 2026

• A driver picked on your website no longer gets "Trip not found" from their Quotes page. A quote a rider asks for on your website holds the driver whose price they picked, but that driver isn't on the trip until they take the job, so tapping it opened a page that turned them away. It's now a card that tells them they were picked, and that if the customer accepts they'll be offered the job. Every other quote opens its trip as before.

• A website quote's trip page names the driver it's holding. Driver & Vehicle used to say no driver was allocated. It now names the driver the rider picked, and says nobody is on the trip until the customer accepts, when it's offered to them.

3.184.0

4 November 2026

• System Admin has a Privacy controls page. It lists every switch that touches personal information, with what each one holds, where it goes and which of your lawyer's nine questions it bears on. It shows how long the daily clear-out keeps each kind of record, with a button that counts what the next run would remove without removing anything, and what files are stored, by kind, and whether each is encrypted. You can make a private link to a read-only summary for your lawyer: it names nobody, works for 30 days unless you choose otherwise, and you can stop it at any time. The switches still change on Platform Settings. This release has a database change, which goes in first.

3.183.0

3 November 2026

• The platform admin's Quotes page now shows every quote in full. Each one says which operator it's for and whether a driver, the office or the website made it, the admin can pick one operator's quotes, and Show older brings back quotes that ended more than 30 days ago. The admin bookings list links to it. An operator's and a driver's Quotes page are unchanged.

3.182.1

3 November 2026

No changes recorded for this release.

3.182.0

3 November 2026

• Drivers can now erase a conversation with Ask and start again. JollyDrivers deletes the words straight away, not just from the phone, and Ask forgets them too. Erasing doesn't give back any of the day's questions, so the daily limit still holds. The Start again button comes with the next build of the Dispatch app.

3.181.1

3 November 2026

• Each stamp on a trip's timeline now shows the time where it happened. Heading off, arriving and boarding show the pickup's time, a stop in between shows that stop's, and the end of the trip shows the drop-off's. So a trip from Coolangatta that ends in Casuarina shows its completion in NSW time, as the Route card already does. Everything else on the timeline, such as the booking being made, a driver assigned, a text or an invoice, stays on Queensland time. Every time still says its zone, and on a trip across the border, hovering over a time on a computer shows it on the other state's clock too. The customer's own trip page reads the same way.

• Changing a stamp's time now says which clock you're on. Now, Best guess and the "Must be on or before" line each show their zone, and a time you pick is read on the clock where that stage happened, not always on Queensland's. On a trip across the border, a switch under the time lets you choose the QLD or the NSW clock, and the line under it gives the same moment on the other one.

• A stamp you change moves straight to its place in the timeline. It used to stay where it was until the page was reloaded.

• Your AI assistant reads a time on the same clock. "Completed at 8:25" on a trip that ends in NSW means 8:25 NSW time, and each time it reads back names its state.

3.181.0

3 November 2026

• Riders can ask for a price by email on your website. Each price can have Email me this price under Book. The rider proves their mobile, or is signed in, as for Book, and JollyDrivers emails them the price as a quote with Accept and Decline. It counts as one of their bookings for the day. The driver whose price they picked has the time held for them, for that driver's quote hours. When the rider accepts, it comes to you as a booking request and is offered to that driver, as a booking from your website is. The button shows on your website once the website's own update is out.

3.180.0

3 November 2026

• One quote can now cover several trips. An open quote's card has Add another trip, which opens New booking filled in with the same customer and the route the other way round, ready for the trip back; change anything you need and press Add to the quote. The customer gets one email listing every trip with the total, and one Accept or Decline answers all of them. The quote still holds the driver's time only once: an earlier trip brings the end of the hold forward, and a later one never makes it longer.

• Your AI assistant can make and send a quote. Ask it for a quote instead of a booking and it makes one, at the fare you agreed; a ride back goes on the same quote. Nothing goes to the customer until you ask it to send the quote, and it shows you who it goes to before it does.

3.179.0

3 November 2026

• Quotes can now be made from the booking screens, and they're still switched off. New booking has Send as a quote beside Create booking, and a driver's booking chat has it beside Submit. Either one makes the quote and opens its trip page, where its card sends it to the customer.

• A Quotes list. Open quotes come first, soonest pickup at the top, with whether each has been sent and how long the time is held; quotes that ended in the last 30 days follow. It's linked from the bookings board and My Trips. A driver sees the quotes they made or drive, and an operator sees all of theirs.

• Choose how long a quote holds your time. Your fare book's settings have a Quotes box: from 1 to 48 hours, or blank for 6.

3.178.0

3 November 2026

• Quotes can now be sent and answered, and they're still switched off. A quote's trip page has a card to email it, text it or send it by WhatsApp, and to withdraw it. The customer opens it on a page of its own, sees the trip, the price and how long the time is held, and accepts or declines it. Accepting confirms the trip with its driver, or leaves it with you to confirm when no driver is named. After the hold runs out they can still accept if the driver is free. The driver gets a text and your office an email when the customer answers, or when the hold runs out with no answer. Nothing on screen makes a quote yet.

3.177.0

3 November 2026

• Quotes are on their way, and switched off. This is the groundwork for sending a customer a trip and its price as a quote, to accept or decline, instead of booking it. A quote holds its driver's time for the hours in their pricing settings, 6 unless they change it and never past an hour before the pickup, and a rider's prices on your website leave that driver out for that time. Nothing on screen offers a quote yet, and with the Quotes switch off nothing changes.

3.176.2

3 November 2026

• Download on the Dispatch page now only shows when it's needed. It's the way to put a build up through Plesk when JollyDrivers can't publish it, so on Releases it appears only after Check says JollyDrivers can't write to the app's folder, or after a publish fails or doesn't finish. One line above the builds says what it's for. Publish and Roll back haven't changed.

3.176.1

3 November 2026

• The payment button on a trip now shows what the pay link will charge. It used to show the fare alone, so a larger-group charge or an extra didn't show on the button even though the pay link billed it. Once there's an invoice, the button shows the invoice. On a trip whose pay link pays for a whole group, the button shows this trip's part, and the Payment drawer says how many trips the link covers and what it comes to.

• Changing the number of passengers now updates the larger-group charge. Cutting a party from five to four takes the charge off, and growing one to five puts it on. Before, the old charge stayed until the price or the route changed. A trip that's been paid keeps its lines as they were, and an invoice that's already been raised doesn't change.

3.176.0

2 November 2026

• Dispatch can now show drivers their upcoming and past jobs. It's a new part on the Dispatch page called Jobs, off until you turn it on. A driver gets a list a page at a time, with who each job is for, a short pickup and dropoff, the fare and a green tick when it's paid, and each one opens in JollyDrivers. They only ever see their own work. Nothing changes for a driver until a new build of the app is published.

3.175.0

2 November 2026

• The Dispatch page now has a place for Ask, the assistant in the app. Its switch and its list of named drivers sit beside who has the app, so nobody has to edit a setting by hand. It's still off, and only the drivers you name will get it.

• Dispatch can now be told whether Ask is open. It's closed while a trip is under way, and JollyDrivers says so rather than the app deciding. Nothing changes for a driver until a new build of the app is published.

3.174.0

2 November 2026

• Your own AI assistant can now tell you about your vehicles and driving hours. If you've connected one, ask which cars are on your account, what each carries, or how your current driving block stands against the cap you set. It gives the figures, in the same words as your Driving hours page, and can't change anything.

• The driver assistant learned the same two things, and it's still switched off. A driver's first-use notice now says their vehicles and driving hours go to the AI company too.

3.173.0

2 November 2026

• JollyDrivers' side of an assistant for drivers is in, and switched off. A driver will be able to ask, in plain words, where their documents and qualifications stand, with no AI subscription of their own. It answers from JollyDrivers' own checks and can read but not change anything. Nobody can use it yet: the screen in the Dispatch app comes later, and it reaches only drivers you name.

• A driver is told before anything is sent. Each driver sees a notice before their first question, saying that what they type and where their documents stand go to an AI company in the United States. No document or photo is sent, and medical and police records are kept out of it. Conversations go after 30 days.

3.172.1

2 November 2026

• Driving hours now knows Queensland and NSW are an hour apart in daylight saving. A rest between a job in one state and a job in the other used to read an hour long or an hour short, which could make a block look much shorter or longer than it was. Rest gaps, blocks, daily hours and the heads-ups now go by the real moment each job happens.

• Some heads-ups will change. False ones go. A real one the old reading missed can show up for the first time, on the Trip page and in Over your driving cap. This only touches drivers with jobs both sides of the border, from October to April. Hours for past weeks since 4 October can change too, because they're worked out each time the page opens.

• The two nights the clocks change now read right as well. An NSW driver's rest over those nights counts the hour the clocks gain or lose.

• Days stay on each job's own clock. An NSW job at 12:30 AM Tuesday shows on Tuesday, even though it's still Monday in Queensland. When a block starts in one state and finishes in the other, Longest driving blocks shows the state beside each time.

• A trip JollyDrivers can't place in a state says so. It still counts, read on Brisbane time, and the Hours by day panel says how many trips were read that way.

3.172.0

1 November 2026

• A rider's tracking page now checks every 10 seconds, not every 30. A driver's milestone shows there within about 15 seconds of the swipe, the 5-second Undo included. Google isn't asked any more often, the map picture stays as it was, and the estimate's orange dot moves as it did.

• Pay for this trip stands out on the finished tracking page. On an unpaid trip it's now a solid bright button straight under Trip complete, above the trip's summary. On a paid trip, View your tax invoice stays a quiet tile where it was. The link and the words are the same.

• JollyDrivers now tells your website how far along a trip is: waiting, confirmed, on the way, arrived or on board. That's what lets the Trips card lead with the milestone once a trip is under way. Nothing changes on your website until its own update lands, and the words riders read are the same.

3.171.1

1 November 2026

• Schedule check now knows Queensland and NSW are an hour apart in daylight saving. A 10:00 PM job in Coolangatta and a 10:00 PM job at Fingal Head used to read as the same moment, so a pair that fit showed a red Won't work with the jobs in the wrong order. Clashes, booking and assigning warnings, and the who's-free answer on a quote now go by the real moment each job happens, and blockouts count in their own state.

• Some clashes will appear for the first time. The old check also missed real clashes the other way round, such as a Queensland pickup followed by an NSW pickup. If a new red card shows up on Schedule check, it's worth a real look. A website quote near the border can also show a driver as free or busy differently from before.

• When a clash crosses the border, each time says its state. Schedule check, the booking chat and the email to the operator show "10:00 PM NSW". A pickup is on its own clock and a finish is on the drop-off's. A clash inside one state reads as it always did.

• A job JollyDrivers can't place in a state says so. If nothing on a job or an older blockout says which state's clock it's on, what touches it shows Can't assess and never reads as clear.

3.171.0

1 November 2026

• A rider can pay for their trip from the Trips screen on your website. The customer who booked sees Pay for this trip on their next trip, from when it's confirmed until it's paid, and a To pay card lists up to three finished trips for 30 days or until they're paid. It opens the trip's own pay link on JollyDrivers in a new tab, so the website never sees the fare or a card. A passenger on someone else's booking doesn't see it. It stays off until the SiteRiderPay switch is turned on, which waits for the website's half.

• "No, paid another way" now counts for something. When a driver gives that answer at the Completed swipe, the trip's timeline keeps it and the rider stops being offered Pay for that trip, on the To pay card and the finished tracking page. It records no payment: the trip stays unpaid until somebody marks it paid, and a pay link the rider already has still works. If somebody sends the pay link afterwards, by Share, WhatsApp or a text, Pay comes back.

• In a group, that answer stops the trips being billed together. The other trips are then paid from their own links, so paying one can't bill the trip the driver said was paid. The group's page says why, and if the link goes out for that trip afterwards the group can be billed together again.

3.170.1

31 October 2026

• A late flight is no longer mistaken for yesterday's. When a flight ran late and its landing was saved as later than the pickup, the trip looked up the same flight number on the day before, so the Flight status panel and a passenger's tracking page could show yesterday's flight, usually as landed, on the day it was running late. A flight landing after its pickup is now looked up on the pickup's day. A flight landing just before midnight for a pickup just after it is still looked up on the night it lands, and every other trip is looked up on the same day as before.

3.170.0

31 October 2026

• The Dispatch app can show the flight on an airport job, and a driver can ask for a fresh check. The flight becomes part of the route: before the airport on a pickup, after it on a drop-off. It says where the flight stands, when it is expected, and when that was last checked, and one tap checks again. It shows once the app's next version is published and Flight status is switched on, on the Dispatch page. It ships off.

• Checks are paced by how close the flight is. None until 12 hours before it, then one an hour, one every 15 minutes inside 2 hours and one every 5 inside 30 minutes, and none once it has landed, left, or been cancelled or diverted. JollyDrivers holds that, not the phone. Only a press can look a flight up: the app's refresh never does, and a check nobody needs costs nothing.

• What a passenger sees hasn't changed. The flight on a tracking page is still read once, when the driver sets off, and it says so. The driver's own checks don't touch it.

3.169.1

31 October 2026

• The Dispatch app can show whose job it is. JollyDrivers now tells the app which logo goes beside the operator's name on a job, and makes a small copy for the phone, so a driver who works for several operators can see at a glance. It shows once the app's next version is published. An operator with no logo shows the name alone, as it does today.

3.169.0

31 October 2026

• Dispatch, a phone app for drivers, is built and switched off. It opens straight to the job in front of you and nothing else: the time, the passenger, the stops, the flight and the notes, with Navigate, Call and Text through your phone's own apps, and the Trip Progress swipes. It installs from the browser. Nobody has it until it is switched on and they are added.

• It keeps working with no signal. The job still opens, and a swipe waits on your phone with its true time, says "not sent yet" and sends itself when signal returns. A swipe that arrives more than 10 minutes late keeps its time and moves nothing for your passenger. One more than a day old is turned down, and the app says why.

• A job running late stays in front of you until its expected finish, and the app says how late it is. Asking your assistant for your next job has the same fix: a job you haven't started no longer drops off the moment its pickup time passes.

• Your swipes write the same stamps as the trip page, and the timeline says "via Dispatch". You can use either. The trip page and its rules are unchanged. Deliveries, payment, editing and everything else stay in JollyDrivers, and the app has a button straight there.

• A job you handed to another driver isn't your next job. It stays on your trip list, and it no longer shows as the job in front of you, here or when you ask your assistant.

• System Admin has a new Dispatch page. Turn each part of the app on or off with no new version, and choose which drivers have it, so a change can be tried on one driver first. It also shows the build each driver's phone last ran and when, and the last 7 days' swipes: how many were sent, how many arrived late, how many were refused and why.

• New versions of the app wait on that page. Each one is built automatically from the app's own code, and GitHub's signature proves where it came from. Nothing reaches a driver until a person publishes it, with a typed word. Going back to an earlier version works the same way, and a publish that fails leaves the live version working and says what happened.

3.168.0

30 October 2026

• Choose who gets the tracking link: the customer who booked, the passenger, or both. On a trip booked by one person for someone else, where each has a mobile of their own, Send the link now starts with Send to and a tick box for each of them. The passenger is ticked to start, so nothing changes unless you tick the customer. With one person, or one number, the card is as it was.

• Each person gets their own message. The passenger's is as before. The customer's says whose trip it is: "Hi Deanne, you can follow Sam's trip with …". WhatsApp has a button for each person ticked and opens that person's chat, and the buttons stay open until you have done both.

• Text it sends one text to each person ticked, in their own words, with every usual check on each one. If one can't be sent the other still goes, and the window says which. From This device it opens your messages for one person, then the next.

• Share stays one button. With both ticked its message doesn't greet anyone by name, because you pick who in your phone's share sheet.

• The trip's timeline says who it was for, and New link warns that the old link stops working for both people if it went to both. Both get the same link and see the same tracking page.

3.167.0

30 October 2026

• Move a trip to another customer and keep the passenger. Booking tools on a trip now has Move to another customer. Pick who books it and pays for it from now on, from your customer book or as a new name, and the person on it stays the travelling passenger, with this trip's phone and email. The next invoice goes to the new customer.

• An invoice on the trip is voided when it moves. The window says so before you save: a draft is deleted in Xero and anything else is voided. No new invoice is raised then; raise it when you normally would. A trip with any payment recorded, or in a group, can't be moved, and the window says why.

• Once it has moved you're offered the updated confirmation, addressed to the new customer. Cancel sends nothing.

• Operators can move their own bookings too, picking from the customer book of whoever made the booking. A driver moves the trips they made, and the admin can move any.

• Changing "Booked by" in the passenger window now keeps whoever was travelling. Until now the trip's contact switched to the new booker unless you also ticked Someone else and picked the passenger again. Picking the original booker again puts it back as it was. Where an invoice stands, the window now points you to Move to another customer.

3.166.2

30 October 2026

• Texted codes can no longer slip past their limits by being asked for all at once. A number still gets at most 3 codes an hour (10 for approving work to be built), and one address at most 10, however many requests arrive at the same moment. Until now a burst of requests could each be let through before any of them was counted. The texts, the limits and the words shown when a code is refused are all unchanged.

3.166.1

30 October 2026

• A booking on your website is finished even if the rider closes the page. Once JollyDrivers starts making it, the booking reaches you, is offered to the driver the rider picked and gets its answer whatever the rider's phone does. Pressing Book again shows the same reference. Until now, closing the page at the wrong moment could leave a booking at Received with nothing more done to it, and every retry was told it was still being made.

• Your website's code step no longer shows who your customers are. Whenever a code can't be texted (the day's 20 codes to new numbers are used up, or too many have been asked for), the rider is told "We can't text a code just now. Call or text us to book." with your Call and Text, whoever the number is. A code that has run out now reads as a wrong one. System Health still tells you when the day's 20 are used up. Your website needs no update for this.

• One code books one trip. A code's proof could be sent back spelt slightly differently and book again; now it is refused, and the rider asks for a new code.

3.166.0

30 October 2026

• The Trips card on your website can show where the car is. While a rider's next trip is under way and its driver has pressed Update location, the card shows the top of the trip's tracking page (where the trip is, what is next and the map) and Follow your car, which opens that page. It goes from the card when the link ends: the trip completed or cancelled, a change of driver, or 12 hours. Your website needs its next update to show it; until then the card is as it was.

• Nothing new is made or kept. It is the same tracking page the driver would send and trip updates already open, shown only to the rider whose trip it is, and only while your website's sign-in and tracking links are switched on. There is still no link until the driver presses Update location.

3.165.0

30 October 2026

• Riders can stay signed in on your website before they've booked with you. Anyone who types their mobile and the code JollyDrivers texts to it can now press Stay signed in, whether or not that mobile is on one of your bookings. Until now only a mobile on one of your bookings could, so a rider who hadn't booked yet, or whose only booking had been erased, saw their details but had nothing to press.

• A rider who signs in before their first booking gets the same as any other. Account shows and saves their name and email, Trips is empty until they book, and they can book without a code, up to 3 a day. A code to a mobile on none of your bookings still counts toward the Book form's 20 a day.

3.164.1

30 October 2026

• The Submit Booking window no longer has the quote and invoice boxes. "Request a quote at submission" and "Request an invoice at submission" are gone. The quote box only ever ended in a warning, and the invoice box put the invoice into Xero before the trip had run. Raise the invoice from the trip's Payment panel, as on every other trip.

• A booking not yet submitted no longer asks "Would you like an invoice?" Its only job was to tick that box in advance. A draft saved with "Invoice" chosen is now submitted without one: raise it from the trip afterwards.

3.164.0

29 October 2026

• A completed trip's pay link now shows its trip record. Under the trip it says who drove, the car and its number plate, and when the trip started and ended, on the pickup's local time. On a Queensland trip it also shows the driver's QLD driver authorisation (DA) number. JollyDrivers' own tax invoice prints the same lines. With the fare and the route the page already shows, that is the itemised receipt a Queensland passenger can ask for.

• Your Xero invoices don't need the driver or the car on them. No Queensland, New South Wales or tax rule asks for either on a tax invoice, and an invoice raised before the trip can't know who drove. You can take the driver and vehicle details out of the Terms on your Xero invoice template.

• The DA number comes from the driver's own document. It is shown when the driver typed it on the Driver authorisation (QLD) document they shared with you; otherwise the line is left out and nothing is guessed. A driver who has left your fleet no longer shows one. A time JollyDrivers filled in for a step the driver skipped says "(estimated)".

• Your safety plan now counts the drivers whose DA number JollyDrivers holds, instead of saying there is nowhere to keep one. The number is optional on the document, so keep every driver's number in your own register as well.

3.163.0

29 October 2026

• JollyDrivers can now invoice operators for its booking fee, and it is switched off. When an operator's period ends (the 1st of each month, unless they are set to fortnightly or weekly), JollyDrivers raises their booking-fee invoice as a draft in JollyDrivers' own Xero, with a statement of the bookings attached. Nothing reaches the operator until the draft is approved and sent in Xero. Nothing changes until the Platform Fee Invoicing switch is turned on, and no booking fee is payable before 1 January 2027.

• JollyDrivers' own Xero is connected on System Admin → Booking fee, where the account and the GST rate for the fee are chosen too. JollyDrivers will not connect an operator's books as its own, or its own books as an operator's.

• An invoice is never raised twice. If Xero does not answer, JollyDrivers looks for the invoice in Xero before trying again. A fee taken back after it was invoiced is credited on the next invoice.

3.162.0

29 October 2026

• Saved cards for regular customers are built, and switched off. An operator can connect their own Stripe account on Settings → Accounting. A customer can save a card once, on Stripe's own form, from their pay link or their account's payment page. On a completed trip billed to them, the operator taps Charge saved card and confirms. The charge is made on the operator's own Stripe account, JollyDrivers takes nothing from it, and the payment is recorded on the Xero invoice. Nothing changes until the Card On File switch is turned on.

• Stripe keeps the card, not JollyDrivers. The card goes from the customer's phone straight to Stripe and is kept on the operator's account; JollyDrivers only keeps which card it is, such as "Visa ending 4242". A card saved for a company pays for trips billed to that company. The customer can remove it at any time, and removing it takes it off at Stripe too.

• Nothing is charged unless it can be recorded. Before charging, JollyDrivers checks that the operator's Saved-card Stripe account is set in Xero and that Xero shows exactly the amount on the button. A card that is declined, or whose bank wants the customer to confirm, records nothing, and the trip suggests the pay link instead.

3.161.1

29 October 2026

• Four switches that were locked can now be changed in Platform Settings. Confirmation Request, Deliveries, Retroactive Cancellation and Fatigue Warning were filed under "Needs the operator's system first", waiting on Jolly Frog's system, which was switched off on 16 September. They are now ordinary "Unfinished or unproven" switches: you type the switch's name to change one. None of them has changed: each is on or off exactly as it was.

• Fifteen switch descriptions now say what the switch does today. They talked about Jolly Frog's relay, its messages and switches that no longer exist, or the website work had overtaken them: among them Direct Confirmation, Direct SMS, Operator Acceptance, the four above, Media and the four website switches. Two worth knowing: Retroactive Cancellation is offered to a trip's driver and to admins, not to operators, and Fatigue Warning does not decide whether a trip's page warns about driving hours, which it does either way.

• Leftover settings and notes from the old link to Jolly Frog's system have been cleared out. Nothing else changes.

3.161.0

28 October 2026

• You can share System Health's figures with your hosting company by link. On System Admin → Health, the new Share these figures panel makes a private link to a read-only copy of the page that opens without signing in. It shows the outside check, how long pages, API routes and tools are taking, the background jobs, and how quickly the database answers, so when the server is slow they can look for themselves instead of waiting for screenshots.

• The copy leaves out everything private. No errors or what they logged, no dates things run out, no build number, nothing a job said when it failed, and nothing that can be changed. Its headline is judged on what it shows, so it never says something needs a look that they can't see.

• Each link ends on its own after 14 days, or however many days you choose up to 90, and Stop sharing ends it at once. The panel lists each open link with who it's for (only you see that) and when it was last opened. Switching System Health off closes every link.

3.160.0

28 October 2026

• A rider signed in on your website can book without a code. "Stay signed in" now also lets that phone (or browser tab) book trips with you for its own mobile without being texted a code each time, up to 3 a day. Its words say so, and that anyone holding the phone could book in the rider's name. Every booking still waits for you to confirm it, under the same rules as before: the price worked out again, your rider terms, 15 minutes' notice.

• They can cancel a request until you confirm it. A booking the rider made on your website shows "Cancel this request" on their trips card until you, or the driver they picked, confirm it. It's cancelled with the reason "Passenger cancelled", and the trip's timeline says the rider cancelled it on the website. Nobody is texted: you'll see it on your board.

• A phone that stayed signed in before today keeps booking with a code until the rider signs in again. Your website shows the new Book screen once it has learnt it; until then it goes on asking for a code.

3.159.0

28 October 2026

• Your website can now show your own rider terms and privacy policy on its own pages. Once you've published them on Settings → Website, your site's feed carries the words of the version in effect, and the site shows them at /terms/ and /privacy/ in its own look, with the version number and the day it took effect. Earlier versions are listed there and still open on JollyDrivers, so the version a rider agreed to can always be read.

• Your site renders the words exactly as JollyDrivers' own pages do: no markup, no pictures, and links only to web, email and phone addresses.

• It happens only while your website's one sign-in is switched on. With nothing published, your site links JollyDrivers' pages as before.

3.158.0

27 October 2026

• A rider following their trip on your website now sees who is driving. Once you've confirmed the trip and a driver is assigned, the trip card shows the driver's public name (the one they chose on their Public profile card, else the first word of their name) and the car's colour and photo, beside its make, model and plate. Never the driver's legal name or anybody's number. It shows only while your website's one sign-in is switched on, and only to the rider whose trip it is.

• The driver's photo shows there only with their yes. The words on a driver's Public profile card now also say that a rider following their trip on your website sees their public name, and their public photo with their yes. A driver who said yes before these words changed stays on your website as before, and their card asks them to agree to the words as they are now before their photo shows on a rider's trip.

• Trip updates name the driver too. On the same terms, "Your driver is on the way" now reads, for example, "Sam is on the way in the white Kia Carnival, ABC123." and "Your driver is here" reads "Sam is here in the white Kia Carnival, ABC123." Whatever isn't known is left out.

• Your website shows the driver's and car's photos once it has learnt the new parts of the trip card; until then it goes on showing the card as before.

3.157.0

27 October 2026

• On an airport pickup, the trip tracking page now says how long the booking allows after landing, and why. Under the booked pickup time it says, for example, "60 min after your flight was booked to land, to collect checked luggage", or "for carry-on bags only", or "to get through the airport" when luggage wasn't asked. The minutes are the gap between the booking's landing time and its pickup time, as your trip's Route card shows them. It says what the booking allows, not when the driver will be there: the Expected time above it still says that.

• "That is about 44 minutes after your flight was due to land" now sits under the Expected time it is about. It used to come after the booked pickup time, where it read as if the booked time were that long after the landing.

3.156.4

27 October 2026

• A passenger booked without a phone number now gets their own card in your customer book. When a trip was for someone else and that person had no phone, JollyDrivers could link the trip to a different customer who also had no phone saved. The trip then offered to invite that other customer to JollyDrivers, showed them as the traveller, and counted on their card. A blank phone is now saved as no phone, and a trip is never linked to a card that isn't the person's.

3.156.3

27 October 2026

• A rider's new name or email on your website now reaches their upcoming bookings with you. When a signed-in rider changes their name or email on Account, or at the sign-in's "Is this you?", JollyDrivers writes it onto their bookings with you that haven't started and aren't cancelled, where their mobile is the passenger's own number and the booking is still under the name they had before. "Remove my email" takes the email off those bookings too.

• Each booking that changes says so on its timeline: the rider changed the passenger's name or email on your website, from what to what. Nobody is texted or emailed about it. A driver or office with calendar invites turned on sees their calendar entry take the new name, as with any change of name.

• Past bookings, bookings made for someone else, bookings where the mobile is only on a customer card, and every customer card in your book stay as they are.

• Times on your website now say which clock they're on. The rider's next trip on Trips, and the "Your booking … is confirmed" notification, end with the pickup's clock as JollyDrivers' own pages name it, such as "Wed 28 Oct at 9:55 pm (AEST · QLD)". How long a browser tab stays signed in is on Brisbane's clock and now says so: "28 Oct 2026, 1:50 am (AEST · QLD)".

3.156.2

27 October 2026

• A tip, or a new name, on an invoice that already exists now works on the pay page. When a customer adds or changes a tip, or chooses someone else to invoice, on an invoice that is already approved, or on a group's invoice, JollyDrivers cancels that invoice in Xero and makes a new one for the same trips with the change on it, then sends them to pay the new one. Before, the tip was written onto the old invoice and paying it could fail, and once an invoice was approved the customer couldn't see or change who it was for.

• Who the invoice is for now shows on the pay page until it is paid, with the same choices as before an invoice exists, for a group's invoice too. The page says that changing it, or the tip, cancels the invoice and makes a new one. Pressing Pay with nothing changed pays the invoice as it is.

• Each change to an approved invoice leaves a voided invoice number in Xero, and each trip's timeline says which invoice replaced which. A draft is deleted instead and leaves nothing.

• An invoice is left as it is when anything has been paid on it, when JollyDrivers didn't raise it, when its group has changed since, or when the customer chose to pay it by bank transfer quoting its number. In that last case the page tells them to contact you.

• JollyDrivers checks the new invoice can be made before it cancels the old one, so a change it can't carry through leaves the customer with the invoice they had.

3.156.1

27 October 2026

• Your rider terms come with your website's sign-in. When a rider proves their mobile with the one sign-in, your website now gets your rider terms in effect with it: the same line, link and version the Book form shows above Book. So the Book form can use the sign-in and still hold the rider to the terms they saw. Nothing changes while the Site Rider Account switch is off, and it still is.

3.156.0

26 October 2026

• BEAR wait times, for Queensland's quarterly report. A BEAR wait times card on the operator's Compliance page works out the two figures Part 5 of the BEAR report asks for: the average wait in whole minutes, and the percentage of trips that waited more than 20 minutes. Pick a quarter (it opens on the last one finished) and type the two figures into BEAR. JollyDrivers sends nothing to TMR.

• The figures follow TMR's rule strictly. A trip's wait is how late the car was at the pickup against the booked time, and 0 if it was on time or early, with no allowance for a late flight: move the pickup time before you go. A booked time changed after the car arrived doesn't change the wait. A Pick up now booking JollyDrivers timed from the driver's position waits from when it was booked.

• Only Queensland pickups count, and only arrivals a person recorded: a swipe, a time typed on the stage, or a driver's AI assistant. Arrivals JollyDrivers estimated when a stage was skipped are left out, and the page says how many trips the figures rest on and how many were left out and why. A quarter with no recorded arrival says there is nothing to average, not 0.

• The trips that waited more than 20 minutes are listed to check before filing, with a note when At pickup and On board were swiped within a minute of each other, or the pickup time was moved after it had passed. Download every trip gives a spreadsheet of each one, counted or not.

• It is off until the BEAR wait times switch is turned on in Settings.

3.155.0

26 October 2026

• A Dreams list for the System Admin. A Dreams tile beside Bug reports keeps big ideas that have no scope and no promise to build, so they aren't forgotten. Only the System Admin can see it. A dream can be reworded, with its earlier words kept, and put away and brought back. Nothing on it is ever deleted.

• A wish can be made from a dream. It goes on the wishlist as an ordinary wish under the System Admin's name, and needs a scope and approval like any other before anything is built. The wishlist doesn't say it came from a dream; the wish's admin screen does. The dream stays, and can make more wishes.

• The System Admin's AI assistant can read the list, keep a new dream, reword one or add to it, and make a wish from one, each only after reading back exactly what it will save and the admin agreeing.

3.154.0

26 October 2026

• A booking from your website is offered straight to the driver the rider picked. Your website shows each available driver with their price, and the rider books with one of them. That driver now gets the job as an offer as soon as the booking is made: it's on their Job offers page and in the offers count on My Trips and the dashboard. One tap on Accept confirms it with them and their vehicle, and the rider sees it confirmed, as when you confirm by hand.

• If the driver declines, or can't be offered the job (they've left your fleet, or job offers are switched off), the booking waits for you as before: assign it or offer it to someone else. You can still assign another driver before they answer.

• Nothing texts or notifies the driver about the offer yet, and your new-booking email still arrives as before.

3.153.0

26 October 2026

• One sign-in on your website, and an Account screen for your riders. A rider proves their mobile once, with a code JollyDrivers texts it, and only then sees the name and email you already hold for that mobile to check: the name in full, the email partly hidden (j•••@gmail.com). A new rider types theirs once. They can then stay signed in, on their phone in your website's app, or in a browser tab for up to 12 hours. That one yes keeps their name and email for their next booking.

• On Account they see their details and when their mobile was confirmed, turn trip updates on or off without another code, sign out, and Forget this phone. Ask you to delete their details signs that mobile out of your website at once, removes its saved details and trip updates there, and puts an Erasure request in the privacy register, passed to you, with 30 days to answer. Records of their trips that the law requires are kept, and any JollyDrivers account of theirs is untouched.

• The sign-in's code can go to any Australian mobile at the usual limits, and counts in the same 20 a day to new numbers as the Book form's. Nobody learns a name by typing in a number: nothing comes back before the code.

• Trip updates turned on with a sign-in stop when that sign-in does, so a sign-in taken from a phone can't keep hearing about a rider's driver.

• It comes with a switch, Site Rider Account, which ships off. Your website needs its next update and the privacy documents need their lines before it goes on.

3.152.2

25 October 2026

• A trip you've been assigned is now on My Trips. When an operator puts you on a passenger trip you didn't book yourself, such as a booking from their website, it now shows on My Trips, in your dashboard's trips count, in the search and to your assistant. Before, you could only reach it by its link. Trips assigned to you before today now show too.

• A trip you booked yourself stays on your list if the operator moves it to another driver, as before, and now shows on theirs as well.

3.152.1

25 October 2026

• Pricing has moved to Payment. Open Payment on a trip: under "Change the price" are "Check against my fare book" and "Always charge this for this trip", so everything about what a trip costs is in one place. They are no longer in Booking tools.

3.152.0

25 October 2026

• The price has a window of its own. Open Payment on a trip: the fare is at the top, with how the customer will pay under it. Tap "Change the price" to change either. Lowering the price of a booking that has already been billed asks you first, as before. After saving you can send the customer an updated confirmation.

• The window says what it does not change: a confirmation the customer already has, and an invoice already raised, which stays at the old price until you void it and request a new one. A price you type is kept as yours, so changing the route won't re-work it.

• Edit booking is gone. Every part of a booking now has its own window: the passenger (the pencil beside them), the time and flight (tap the pickup time), the route (the Route card) and the price (Payment). A delivery keeps "Edit the delivery" for what is carried, the people at each end and proof of delivery.

• An admin changing a finished or deleted delivery is no longer asked for a reason, as in the other windows. Each change is still on the timeline.

3.151.0

25 October 2026

• The flight is found the way your website finds it. Tap the pickup time on an airport trip, type the flight number, check the day and press "Find flight": each flight with that number that day shows as a card with the airline, where it flies from and to, its time and its terminal. One is picked for you; where there are two, pick yours. You can still type the time yourself.

• The flight picked sets the airport's terminal. If the trip was booked at Brisbane's domestic terminal and the flight uses the international one, the airport stop moves to the international terminal when you save. A flight at a different airport is refused, because that is another trip: cancel the booking and book it again.

• Ticking checked luggage starts the wait after landing at 30 minutes, as on your website, and an international flight starts it at 45. Once you have chosen a wait yourself, it stays as you chose.

• An airport drop-off has "At the airport before take-off": your usual, a choice from 45 minutes to 3 hours, or any other number. It is saved with the booking, and the window offers the pickup that it, the flight and the drive to the airport add up to.

3.150.0

25 October 2026

• A trip's stops can be added, taken off and put in another order from the Route card. Press "Change the route": each stop has up, down and remove buttons, made for a thumb rather than dragging, and "Add a stop" finds the place in Google's list and puts it in before the drop-off. To change where a stop is, tap the stop itself, as before.

• On an airport trip the airport stays at its end of the trip and nothing moves past it, because it follows the flight. Tapping the airport on the Route card no longer changes its address: you can still name it.

• A change that would make either end of the trip an airport, or stop one being an airport, is refused with the reason: that is another kind of trip, so cancel the booking and book it again.

• The stops can't be changed once the passenger is on board, or once the trip is finished. If the pickup becomes a place on another clock, you are asked which time to keep, as when you move the pickup itself. After saving you can send the customer an updated confirmation.

• Edit booking no longer has the stops. It keeps the price and how the customer will pay, and a delivery's items and the people at each end. A trip with no customer card has nothing left in it, so it is no longer offered there.

3.149.0

25 October 2026

• The passenger has a window of its own. Tap the pencil beside the passenger on a trip's summary to change who booked the trip and who is travelling, their phone and email for this trip, how many passengers, the notes, and how the request came in (how, when, who asked and what they sent). On a delivery or a job it is the booker's window.

• Every name you give there is kept in your customer book. Pick the person from the book, or type a new name and press "Add as a new customer": they are added when you save, unless the book already has them under that name, phone or email. Picking someone fills in the trip's phone and email from their card, and where the trip holds different details from the card, "Use the card's details" takes the card's.

• Who booked a trip can't be changed while it is in a group or has an invoice that hasn't been voided, and the window says why. A change of who booked it shows in the trip's timeline, and a bill-to of the previous customer's comes off.

• A trip that now has someone else travelling no longer shows in the previous passenger's My Trips, unless the phone is still theirs.

• Edit booking is smaller. The passenger, the date and time, the flight, the billing choice, the bill-to, the notes and how the request came in have gone from it: each is changed in one place on the trip page now. It keeps the stops, the price and how they'll pay, and a delivery's items. "Set travelling passenger" and "Refresh customer details" have gone from the people drawer, because the passenger window does both.

• Only the person whose customer book it is, and the admin, choose names from it. An operator on a driver's trip sees who booked and who travels, and can change the rest.

3.148.0

24 October 2026

• The tracking page your passenger opens is now a timeline. At the top: what you last swiped, in big letters ("On board"), and the next expected time ("Next: the airport about 9:35 pm"). Then the map, with your car and its number plate on top of it until the passenger is on board. Under the map, the trip step by step, like the Route card on your trip page: when you set off, the pickup, each stop on the way and the destination, with the distance and drive time between them.

• It is plain which times are yours, which are estimates and which are only booked. A swipe of yours has a filled dot with a tick, an estimate a dashed orange ring and an Estimate tag, a booked or timetabled time a grey ring. Every time shows its clock beside it, "(AEDT · NSW)" or "(AEST · QLD)", whoever is reading it.

• On an airport trip the flight is part of the timeline, with plane icons. A pickup's flight comes first: where and when it took off, the time in the air, and its landing. A drop-off's comes last: how long before it leaves, the flight, the time in the air, and when it lands there, on that airport's clock ("Sun 5:55 am (UTC+8 · Singapore)"). Before the passenger is picked up, a drop-off shows the flight number and departure time on the booking; the flight itself is looked up once, when you set off for a pickup and when the passenger is picked up for a drop-off.

• Sharing is now a share icon at the top of the page, which opens a sheet saying what whoever you send it to will see.

• Once the trip is complete the page folds into a summary: how long and how far, where the passenger was picked up and dropped off, the pay or tax invoice button and the map, with the whole timeline folded away under "Full timeline".

• Each stop on the way is listed as "Stop on the way", never with its address, so the page now shows how many stops there are.

3.147.1

24 October 2026

• Customers now get their trip updates when you swipe. A customer who turned on trip updates on your website is meant to be told when you swipe En route and when you swipe At pickup. Until now a swipe in Trip progress never sent either: only a stage your AI assistant recorded "now" did. A swipe now sends them, even one that took a while to arrive over poor signal. A stage filled in as an estimate, or given an earlier time with a card's clock, still sends nothing.

• The same fix lets a swipe of En route (an airport pickup) or On board (an airport drop-off) look the flight up for the tracking page. That still waits for the Track Link Flight switch, which is off.

3.147.0

24 October 2026

• Trip progress has a card for each stop in between. On a trip with a stop on the way, the drawer now has "At stop 2" (then "At stop 3", and so on) after On board. Swipe it when you get there, with five seconds to Undo, like any stage. As at the pickup, you choose the stop's own address or Use GPS before you swipe, and the card's clock gives an earlier time or corrects one. The trip stays On board until Completed.

• Recording a trip afterwards estimates the stops too. Swipe Completed, or a later stop, with stops not swiped, and JollyDrivers fills them in, marked estimated, after showing you the times: each is the stamp before it, plus the drive to that stop, plus any wait booked at the stop before. Completed's best guess now comes from the last stop and its wait, so a booked wait is no longer left out of it.

• Swiping a stop's card moves your tracking link on to the next stop, so the tracking card's "Reached stop" button has gone. Undoing the stop moves the page back.

• Your AI assistant can record a stop too, with the same rules, and lists the stops reached when you ask how a trip is going.

• Each stop reached is on the trip's timeline, where it can be corrected or undone like a stage, the newest first. On board can be undone only once the stops after it have been.

3.146.2

24 October 2026

• The pay page shows every stop on a trip, not just where it starts and finishes. A stop on the way now has its own line on the trip's card, "Via", between From and To, so the customer paying sees the stop they asked for. On a page that covers several trips, each card lists its own stops, in order.

• The tax invoice a customer downloads from a paid link names those stops too: its route reads from the pickup, via each stop, to the destination.

3.146.1

24 October 2026

• Your website's map of where you go is worked out once a day, not every five minutes. Your website checks JollyDrivers for changes every five minutes, and each check used to go through every trip you have had to draw that map, which took seconds each time. The map is now worked out once a day and kept, so a check takes a moment. A finished trip reaches the map within a day; a place you add yourself still shows straight away.

• The Website tab says when the map was last worked out, under the list of places: "Worked out on 24/10/2026; refreshed daily."

3.146.0

24 October 2026

• On an airport drop-off, the tracking page says when the car will reach the airport, and how long that leaves before the flight. Once the passenger is on board and the car is heading for the airport, the page says "Expected at the airport about 4:10 pm" on the airport's own clock, and under it "That is about 1 hour 50 min before your flight is due to leave at 6:00 pm". With a stop on the way, it starts once the car is heading for the airport. It goes by the departure time on the booking, so it works without any flight lookup.

• The page can also show the flight. When you record On board on an airport drop-off with a flight number, JollyDrivers looks the flight up once, and the page shows it until the trip ends: the flight and where it is going, whether it was on time, delayed or cancelled, when it was due to leave, the airport and terminal, and when it was checked. The time before departure then goes by the flight's expected time. It is not looked up again, and the page says so. Your own trip page keeps its live flight panel.

• The flight comes with the same switch as an airport pickup's, Track Link Flight, which is still off. Each airport drop-off uses at most one flight lookup.

3.145.0

24 October 2026

• The tracking page says when the car is expected, as a time. Where it said "Estimate: about 9 minutes away now", it now says "Expected at the pickup about 3:25 pm (about 9 minutes)", and once the passenger is on board, when the car is expected at the destination or the next stop. The time is your last Update location plus Google's drive time in the traffic of that moment, so it changes each time you update.

• Every time on a live tracking page is now on the clock of the place the car is heading for: the pickup's on the way there, the destination's once the passenger is on board. Someone reading it on a phone that keeps another clock, in New South Wales during daylight saving say, sees the place's name beside each time: "3:25 pm Queensland time". A finished trip's summary is unchanged.

• On an airport pickup, the page can show the flight. When you record En route on an airport pickup with a flight number, JollyDrivers looks the flight up once, and the page shows it until the passenger is on board: the flight and where it is from, whether it was on time, delayed, landed, cancelled or diverted, when it was due to land, the airport, and when it was checked. It is not looked up again, and the page says so. Beside your expected time it says how that stands against the landing. Your own trip page keeps its live flight panel.

• The flight comes with a switch, Track Link Flight, which ships off. It needs the tracking link and the flight tracker on, and the privacy documents need their line before it goes on. Each airport pickup uses at most one flight lookup.

3.144.0

24 October 2026

• Your rider terms now show on your website's Book form. Once you have published terms, a rider who books on your website sees "By booking you agree to your rider terms" just above Book, with a link to them, and books with the next press. The booking keeps which version they agreed to and when, the trip's timeline says so, and the trip page shows it with a link to that version.

• If you publish new terms while a rider is booking, nothing is booked until they have seen the new ones: the form shows the new line and they press Book again.

• Confirmation emails and their PDFs link your terms under the privacy line.

• Your website's footer shows Terms beside Privacy, and where riders type their details the small print links your own privacy policy as well as JollyDrivers'. Your website needs its next update for these, and they come with the Operator Legal Pages switch.

3.143.0

24 October 2026

• Publish your own rider terms and privacy policy. A new Terms and privacy card on Settings → Website takes the words for each, shows a preview, and publishes them as version 1, then 2, and so on. A published version never changes: to correct one, publish again. Each has a public page anyone can open without signing in, at jollydrivers.com.au/sites/your-name/terms and /privacy, and every earlier version stays at its own address, so you can always show which words were in effect on a given day.

• Your website's Privacy link goes to your own policy once you have published one. Your terms on the website, and the line about them above Book, come with the next release.

• What you write shows as text, with headings, lists, bold, and links to web pages, email addresses and phone numbers. HTML and pictures are not shown.

• It comes with a switch, Operator Legal Pages, which ships off. Your website needs its next update before it goes on.

3.142.0

23 October 2026

• Riders can book on your own website, without leaving it. Under each price your website shows, Book opens a short form: the passenger's name, an email if they like, anything the driver should know, and their mobile with the code JollyDrivers texts it. A price asked with a flight keeps its flight. The booking reaches you as a request waiting for you to confirm, like one from your booking page and under the same rules, at least 15 minutes ahead among them, and the rider sees "Booked: waiting for you to confirm" with the reference.

• A price can change between showing and booking. If it has, nothing is booked: the rider sees the new price and presses Book again.

• The code can go to any Australian mobile, so a first-time rider can book. Each number and each visitor has a limit on codes, and your website texts only a limited number a day to numbers on none of your bookings. After that it asks new riders to call or text you, and System Health says the limit was reached. One code makes one booking, and pressing Book twice makes one booking.

• It works in a browser as well as in your website's app. In the app, after booking, the rider can show their trips on that phone straight away. Nothing they type is kept on the phone.

• It comes with a switch, Site Booking, which ships off. Your website needs its next update and the privacy documents need their lines before it goes on.

3.141.0

23 October 2026

• Your website can stop sending visitors to JollyDrivers to book. A new switch, Website Booking, decides whether operators' websites link to their JollyDrivers booking page, and it ships off. While it is off, your website shows no "Book a ride" anywhere. Get a price takes its place in the header, the footer, the business-card page and the 404 page, and becomes the main button at the top and the bottom of the home page. The trip tickets open the price form.

• Prices on your website still work, with every driver's price and who's free then. They come without Book buttons, with "To book, call or text us" and your own Call and Text buttons under them. Where your website used to send people to JollyDrivers for a price (stops on the way, or a price that couldn't be given), it offers your Call button instead.

• Your contact card and what search engines read leave the booking link out, and "Bookings and payments by JollyDrivers" is no longer a link.

• JollyDrivers' booking page itself still opens for anyone who has its address. When JollyDrivers takes new users, switch Website Booking on in Settings and your website links to it again at its next build.

• The website's new builder has to be on the server first. Then this release takes the links off at your website's next build, within five minutes.

3.140.0

22 October 2026

• Your riders see their next trip with you when they open your website's app. Once a phone shows their trips, the app opens on the trip that's under way, or else the next one: the day and time, each stop as booked, where the booking is (waiting for you to confirm, confirmed, driver on the way, arrived, on board), and the car and its number plate once you've assigned a driver. It says how many more trips they have booked after it.

• It shows only bookings with you that have the rider's mobile on them, as the person who booked, the customer or the passenger. Never the fare, the notes, the reference, or anybody's name or number.

• A trip whose driver is running late stays on the card for two hours after its pickup time. The card updates whenever the rider comes back to the app.

• It is behind the same Site Rider App switch, which is still off, and reaches your website once the website's builder is updated. It has not yet been tried on a real phone or a real trip.

3.139.0

22 October 2026

• Your riders can keep their trips on their phone, in your website's app. After the code step on the Trip updates card, a rider can also tap Show my trips on this phone. From the next release, that phone shows their next trip with you as soon as they open the app.

• It is a yes of its own, recorded with the words they saw, for your business only, and separate from trip updates: either can be on without the other. Stop showing my trips on the card stops it straight away.

• The phone holds a pass that works for your business only, and only to read that rider's trips. JollyDrivers keeps only a fingerprint of it and replaces it every day, and it runs out after 90 days, when the rider proves their mobile again. If an old copy of a pass ever comes back, the phone is signed out.

• System Admin → Rider passes shows how many phones are signed in for each operator, signs them all out for one operator or for everyone, and removes every pass and trip-updates phone for one mobile on a privacy request.

• It is switched off until the Site Rider App switch is turned on in Settings, after Site Push Notifications. It has not yet been tried on a real phone.

3.138.0

22 October 2026

• Trip updates now reach your customers' phones. Once a customer has turned trip updates on in your website's app, their phone tells them when a booking with their mobile is confirmed, when the driver swipes En route and when the driver swipes At pickup. The driver's updates name the car and its number plate and nothing else: never the fare, an address, or the driver's name or number. A tap opens the trip's tracking link when the driver has made one, and your website otherwise.

• An update goes once the driver's swipe is saved, after the five-second Undo, and only for a swipe made at the time: a stage filled in afterwards, or given an earlier time, sends nothing. Each update goes once a trip, and nothing waits on it: the swipe saves as quickly as before.

• Each update is written on the trip's timeline, saying what was sent and whether the phone took it. Your customer's own trip page leaves that line out. Texts and emails are unchanged.

• It is behind the same Site Push Notifications switch, which is still off. It has not yet been tried on a real phone or a real trip.

3.137.0

22 October 2026

• Trip updates on your customers' phones, from your own website. Once a customer has put your website on their phone's home screen, it shows a Trip updates card: they type their mobile, type the code JollyDrivers texts it, and allow notifications. Send me a test shows them it works straight away. The notifications themselves come in the next release.

• A code goes only to a mobile that is on one of your bookings, and the card says the same thing either way, so nobody can use it to text strangers or to find out who your customers are. Your website shows the card only when it is opened from a phone's home screen, so it looks the same as before to everyone in a browser.

• Each customer's yes is recorded with the words they saw, for your business only, and Turn off on the card takes their phone off the list. Nothing they get by text or email changes.

• It is switched off until the Site Push Notifications switch is turned on in Settings, and it needs JollyDrivers' sending key set on the server first. It has not yet been tried on a real phone.

3.136.0

22 October 2026

• The admin dashboard shows how many flight-lookup units are left, and when they reset. The Third-party spend panel reads AeroDataBox's own count: units left out of the plan's 5,000 and how long ago that was read, the day the quota resets, and the pace over the last week with what it leaves at the reset. It turns amber when that pace would run out first, or once 80% is spent, and red when nothing is left.

• The figures follow the plan's own renewal date rather than the calendar month, so on the 1st they no longer empty out and the row no longer says "Never checked".

• Check now asks AeroDataBox for the latest count without spending a unit.

3.135.0

21 October 2026

• Airport prices on your website can start from the flight number. A visitor types their flight number and the day and presses Find flight, and JollyDrivers finds the flight at one of your airports, with its scheduled landing or take-off time. They choose how long after landing your driver meets them, or how long before take-off they want to be at the airport, and on a pick-up whether they have checked luggage. The prices, and who's free, are worked out for the pick-up time that gives, and the times are shown above the prices.

• The meet time starts 20 minutes after landing, 30 with checked luggage and 45 off an international flight; a drop-off starts an hour before a domestic flight and three before an international one, and the pick-up time allows for the drive. Each time says whose clock it is on when the trip crosses the border in summer.

• Book carries the flight into the booking, so the chat doesn't ask for it again, and the trip page shows the flight's live status as it does for a flight added in the chat. A Brisbane flight's booking goes to its own terminal.

• Flight lookups use JollyDrivers' own flight-data account, never a key on your website, with a daily allowance for all websites and a limit for each visitor. Past either, or without a flight number, the visitor types the time, as before.

• It is switched off for now, and reaches your website once the website's builder is updated.

3.134.0

21 October 2026

• Prices on your own website. Save a Google Maps key of your own on Settings → Website and your website gets a "Get a price" section. Visitors choose an airport pick-up, an airport drop-off or point to point, the addresses, when and how many, and see every driver's price, cheapest first, with who's free, without leaving your site. Book opens your booking page with that trip and driver already filled in.

• The key is yours, and public: your visitors' browsers use it for address search, and Google bills those searches to you. Lock it in your Google account to your website's address and to Maps JavaScript API and Places API (New). JollyDrivers only passes it to your website and never uses it.

• A price's Book link works for an hour; after that it opens a fresh quote. A trip with stops on the way is priced on your booking page, from a link under the form. Without a key, your site's "Get a price" button opens your booking page as before.

• It is switched off for now, and reaches your website once the website's builder is updated.

3.133.0

21 October 2026

• A link that opens your booking page straight on the quick quote. Add ?start=quote to your booking link, for example jollydrivers.com.au/book/yourname?start=quote, and it opens on "See what your trip costs" instead of the menu. Your website can then have a "Get a price" button beside "Book a ride", so a visitor sees live prices from your drivers in one tap. Back takes them to the menu as usual.

• If the quick quote is switched off, the same link simply opens your booking page as it always has, so a link on your website never breaks.

3.132.0

20 October 2026

• Give your website a favicon of your own. On Settings → Branding, under Icon, there is a new Favicon: upload a small square picture and your website's browser tab and phone home-screen shortcut show it, instead of the first letter of your business name. You see it at the sizes a tab uses, on a light and a dark background, before anyone else does.

• A picture that isn't square is fitted into a square with see-through margins, never cropped. Remove takes it off again.

• It reaches your website once the website's builder is updated. JollyDrivers' own pages, such as the pay page, keep JollyDrivers' icon in their tab.

3.131.1

20 October 2026

• Your logo or icon shows larger on the pay page. It is now 40 pixels tall and as wide as it needs to be (up to 160), the way your website's header shows it, instead of being shrunk into a small square. A wide icon is about twice the size it was.

• The faint square behind it is gone, since your picture brings its own shape. JollyDrivers' own mark on the upload and trip-tracking pages is unchanged.

3.131.0

20 October 2026

• Save an icon beside your logo. On Settings → Branding, under Logo, there is a new Icon: your logo without its words, on a see-through background. Press Suggest from my logo and JollyDrivers cuts one from your logo, leaving off the line of small words under the pictures and clearing a dark background, then Keep this saves it. Or upload your own.

• The icon goes where your logo sits beside your business name: the pay page, the confirmation emails your customers get, and the booking chat's welcome. A stacked logo no longer shrinks its words to a few pixels there. The icon is kept sharp and see-through, as a PNG, which email programs show more reliably than your logo's format.

• Your website's header and footer will show it too, once the website's builder is updated. Until then, and for anyone without an icon, the website keeps cutting its own icon from your logo.

• It is optional: without an icon, every page and email looks exactly as before. Replacing your logo keeps your icon, and Settings says when the icon was made before the logo.

3.130.2

20 October 2026

• "Always charge this for this trip" now works on trips that were typed in. A trip entered from an email or a text had no map position saved for its stops, so the dialog said it couldn't seed an agreed price even though the trip page showed the route. It now finds each end from the airport the stop is linked to, the same address on one of the customer's other trips or saved places, or, as a last resort, one Google lookup.

• An agreed price now applies to those trips too. The same gap meant a price you had already agreed never matched a typed-in trip, so it priced from your fare book instead. A customer with no agreed price never causes a lookup.

• When a trip still can't be used, the message says why: which end couldn't be found on the map, or that the trip isn't linked to a customer. Editing that stop and choosing the address from the suggestions fixes it.

• New bookings to or from an airport now keep the airport's position on the stop. Nothing is written onto trips you already have.

3.130.1

20 October 2026

• Toll and Fee Surfacing can be switched on from the settings page again. It was locked behind a padlock as waiting on Jolly Frog's system, which was switched off in September. It now sits under Migration steps, next to driver pricing, and you type its name to change it, like the other switches there.

• Its description says what it does today: tolls, airport fees, commission, the NSW levy, extras and the larger-group premium, on screen, on the customer's confirmation and on the Xero invoice. Turn it on before driver pricing; turning it off stops new charges, but charges already recorded stay on their bookings.

• Nothing is switched on by this release. It stays off until you turn it on.

3.130.0

20 October 2026

• Add places to the map of where you go. On Settings → Website, under "Where you go", search for a suburb or postcode and press Add. The place goes on the map behind your website's headline at the lightest shade, so the areas you serve show before your trips there do.

• Added places are marked Added in "What the map would show", with an (x) to take one off again. A postcode your trips already put on the map keeps its own shade; adding a suburb there only names it when JollyDrivers didn't know what to call it, so a postcode left off for that reason can now go on.

• Up to 50 added places. The map centre can be one of them. Nothing is kept until you press Save website, and your website never says which places were added or how many trips there were anywhere.

• It is part of the Website tab, so it appears only while the Operator Site Feed switch is on.

3.129.0

20 October 2026

• A fourth look for your website: Atlas. The Look card on Settings → Website now offers Atlas after Radar, Daylight and Departures: a night drive on a dark map, naming the places as the car passes them. Choose it Shown first, In the picker or Only by link, like any other theme.

• Nothing changes on your site until you choose it. Every website starts with Atlas set to Not on my site, so it appears only after its operator picks a place for it and presses Save website.

• It is part of the Website tab, so it appears only while the Operator Site Feed switch is on.

3.128.0

19 October 2026

• Pick your colours by eye. On Settings → Website, tap the square beside Main colour or Accent colour to open a colour picker: drag across the colours or tap one of the ready-made ones, then Use this colour. No more copying a code across from another website.

• Typing or pasting a code still works, and a new (x) in the box empties it, back to JollyDrivers' own colours. An empty colour opens the picker at JollyDrivers' own. Nothing is kept until you press Save website, as before.

• It is part of the Website tab, so it appears only while the Operator Site Feed switch is on.

3.127.0

19 October 2026

• Drivers on your website. An operator's website can now show the drivers who want to be on it. A driver appears only while three things hold: they drive for that operator, the operator chooses to feature them, and they have said yes themselves.

• A Public profile card for drivers. On their account, a driver says yes or no to each operator's website, with the exact words of what that means shown beside it. They choose the name the site shows (the first word of their name if they type none), a photo just for websites, a few words about themselves, and which languages, qualifications and Academy certificates appear. Each certificate links to the page anyone can check it on.

• Feature on website. On each driver's fleet page, the operator switches them on or off for the website, and a line says why a driver isn't on it yet: no yes from them, not featured, or the website switched off.

• What stays private. The site never shows a driver's legal name unless they typed it as their public name, and never their phone number, email or anything about their compliance documents. Their photo can be opened only while they have said yes to a website. Saying no takes them off at the site's next update, usually within minutes.

• Languages and qualifications appear only while the Driver Qualifications switch is on. All of this is part of operators' websites, behind the Operator Site Feed switch.

3.126.0

19 October 2026

• Choose your website's look. A Look card on Settings → Website lists every theme the website can draw, in the website's own order: Radar, Daylight and Departures today, each with a swatch of its colours and a line about it. For each one the operator picks Shown first (exactly one), In the picker, Only by link, or Not on my site. Choosing Shown first on another theme swaps the two.

• The picker appears only when there is something in it. Visitors can switch the home page to any theme in the picker. With none there, there is no picker, and there is no separate switch for it. A new operator's site wears the first theme on the list and nothing else.

• Only by link is unlisted, not private. A link-only theme opens only from its own link, so the operator can try it before anyone else sees it. The card says plainly that the website's feed is public, so anyone who reads it, or has the link, can open the theme.

• A link to your site in each look. Once the website is on, every theme on it has a link on the card that opens the site in that theme.

• A new theme never goes on a site by itself. A theme added to the list in a later release is offered on the card but stays off every site until its operator puts it there. A theme taken off the list leaves every site, and where it was shown first, the list's first theme takes its place.

• The card is part of the Website tab, so it appears only while the Operator Site Feed switch is on, which still ships off. Photos and videos for the themes come later.

3.125.0

19 October 2026

• A Website tab on Settings. An operator switches their website on, gives its address, and writes what it says: a headline, a few paragraphs about the business, a phone number (and whether customers can text it), WhatsApp, an email address and opening hours. Their main and accent colours are set here too, and the booking page uses them as well.

• Areas, trips and links. Each council area the operator and their drivers cover can be given a friendlier name and featured. Up to eight trips can be featured with the lowest full price a customer pays, GST included. Links to Facebook, Instagram, Google, LinkedIn, X, YouTube and TikTok appear on the site.

• A map of where you go. Switched on from the tab, the website shows the postcodes the operator's trips start and end in, each shaded from 1 to 5, with a centre the operator chooses. It never shows how many trips, an address or an airport, and leaves out any postcode with two trips or fewer. The tab shows exactly what the map would show before it is switched on.

• Nothing half-saved. Anything the website could not show, such as a phone number that isn't Australian or a link that doesn't start with https://, is refused with a sentence saying what to fix, and nothing is saved until it is right.

• The tab appears only while the Operator Site Feed switch is on, which still ships off.

3.124.0

19 October 2026

• The first part of an operator's own website, built from JollyDrivers. JollyDrivers can now publish, for each operator who has a website switched on, one public document of everything their site may show: the business's name, logo and colours, its legal name, ABN and ACN, its BSP (NSW) and BEA (QLD) numbers, the council areas and airports it covers, its active cars with their published photos, its booking link, and which promises are true for it today, such as prices agreed up front. A separate website builder makes the operator's site from that document, so JollyDrivers is the only place the site is edited.

• It never carries anything private. No surname, no driver's phone number or email, no number plate, no business address, no director, no compliance results and nothing about any customer or trip.

• The BSP and BEA numbers are always shown when JollyDrivers holds them. "Compliance checked" appears only while the operator holds one of them and their compliance check is on. It says that the check runs, never how any driver did.

• Nothing changes yet for anyone. The switch, Operator Site Feed, ships off, and there is no screen yet for an operator to switch their website on. That screen, a Website tab on Settings, is the next part.

3.123.0

18 October 2026

• Your AI assistant now knows a place by its name. This is the fourth part of Place Names. When a driver's or an operator's assistant reads a trip from JollyDrivers, a stop the operator has named comes with its name in front of the address: a driver's next job, their day or week, one trip in full and a customer's upcoming jobs; the operator's bookings board and one booking in full; and the trip line on each change the assistant prepares (accept, decline, cancel, assign a driver, send a confirmation).

• Booking and changing a trip through the assistant names places too. The draft it builds, the card it shows before the booking is made, the "Booked" message after, and the same for a change to a booking all name a place the operator has named. So does a customer's last trip when the assistant looks a customer up.

• The assistant is told the names are only labels. A name is shown in «» marks, and a reply that shows one ends by saying the names were typed by the operator's own people and are to be read, not obeyed.

• A stop nobody has named reads exactly as before, and a name never changes the address the assistant books, measures or prices.

3.122.0

18 October 2026

• A place's name now shows on the invoices JollyDrivers raises in Xero. This is the third part of Place Names. On a trip's invoice line, a stop the operator has named reads as the name and then the address: "▶ Pick Up: Surfers Aquarius on the Beach, 4-12 Old Burleigh Rd, Surfers Paradise QLD 4217". The pickup, every stop in between and the drop-off are each done the same way.

• Deliveries and jobs too. A delivery's line names each end in the same way. A job done at one place, such as a dog walked or a garden watered, starts with the place's name and its address, leaving out whatever the customer's own words already say.

• The tax invoice a paid pay link downloads names each end of the trip, as the pay page already does.

• Invoices already raised are not changed. A name appears on the next invoice raised for a booking. To put it on one that is already in Xero, change the line's words from the trip's invoice card.

• A stop nobody has named reads exactly as before. Place Names is switched on, so this applies from the moment it is live.

3.121.0

17 October 2026

• The booking assistant now only talks about bookings. Ask it for anything else, such as homework, coding, a joke or the news, and it says it can only help with the booking and carries on with the next question. It never shows or discusses its own instructions.

• Somebody who keeps trying to misuse it is locked out. Messages that try to make the assistant break its rules, or that carry attack code, are refused before the assistant sees them. Three of those in a day, or five requests that have nothing to do with a booking, lock that person out of the booking chat. A signed-in account stays locked until the System Admin unblocks it; for a visitor who is not signed in, the lock on their internet address lifts by itself after a day.

• The System Admin is told, and can unblock. Each administrator gets an email saying who was blocked, where, and exactly what they wrote. System Admin > Chat blocks lists every block and has an Unblock button.

• A visitor who is not signed in can send only a few bookings: three from one browser tab, five an hour from one internet address. Signed-in drivers, operators and riders are not limited this way.

• One busy visitor can no longer take the assistant offline for everyone. One internet address now has a daily allowance, and drivers and operators who are signed in keep working even on a day the assistant is closed to visitors.

• Driver tools only on your own operator's page. A driver booking on another operator's page is treated as a rider there: no agreed price, no backdating and no fee waivers.

• The lock-out has its own switch, Chat abuse lock-out, which is on.

3.120.0

17 October 2026

• A driver's home screen can show every tool as a small icon. With the new Compact dashboard switch on, each tile on a driver's home screen can be an icon with one word under it, four across on a phone, so the whole screen fits on about one page instead of seven. Icons and Cards at the top switch between the two, and each phone or computer remembers its own choice: a phone starts on icons, a computer on cards. A tile's count, such as upcoming trips or documents still to do, shows as a small number on its icon. It is off until it is switched on in Settings.

3.119.0

17 October 2026

• A moment can now play every time. On Media's Moments screen, "How often on one phone" has a new first choice: Always. A moment set to Always plays each time its page opens, for everyone ticked under "Who sees it". The limit of two moments a day on one phone does not stop it, and it does not use either of them up, so the other moments still get their two.

• Everything else about a moment stays the same: nothing plays on a phone set to reduce motion, a phone saving data gets a card's still picture and no transition, and one tap skips it. The System Admin's AI assistant can prepare Always too, saved switched off as before.

• Nothing plays differently until the System Admin sets a moment to Always.

3.118.0

17 October 2026

• The System Admin's AI assistant can now help make the Media studio's animations, behind a new switch that ships off. Connected to JollyDrivers as the admin, it can read the Studio, the Library and where each animation plays. It can add an idea, and prepare where an animation plays, each only after reading back exactly what it will save and the admin agreeing.

• It can upload what it made through a one-time link. The assistant asks for a link for one animation, then posts the clip and its still picture to it, or hands the link over to be opened on a phone to pick the files. The files go through the same virus check as the Studio's own upload, and the animation waits in the Studio as Made. A link works once, for 30 minutes.

• Only the System Admin approves an animation, makes it live or switches a moment on. Where an animation should play is saved switched off when an assistant prepares it, and a moment that is already on is never changed by an assistant. The Studio and the Moments screen say what an assistant added, uploaded or prepared.

• This release has a database change, which must be in before it is deployed.

3.117.0

17 October 2026

• The Media studio takes Lottie animations as well as video. A Lottie is an animation the phone draws from shapes rather than a video it plays: a few kilobytes, and sharp on any screen. On a piece's page the System Admin can upload one (a .json file of at most 1 MB) with its still, approve it and place it on a moment exactly as a video. It goes through the same virus check, and a file that holds code, pictures, sound or fonts from elsewhere is refused with a sentence saying what to do instead.

• A Lottie moment keeps every rule a video keeps. It never shows on a phone set to reduce motion, a phone saving data gets the still, it is silent, one tap skips it, and it counts towards the same cooldowns and the same two a day. JollyDrivers serves the player for it from its own address, and a phone fetches that only when a Lottie is about to play.

• Nothing plays differently until the System Admin places a Lottie on a moment.

• JollyDrivers' colours, fonts, logo and wordmark are now written down once, in a brand kit that both the app and its animations follow, so the two can no longer drift apart. Nobody sees a change: the app's amber is the brand's.

3.116.1

16 October 2026

• Tapping Pay or View your tax invoice on a tracking link no longer leaves the JollyDrivers animation on the screen. The passenger was stuck under the animation until they refreshed the page. The pay page or the tax invoice now opens with the usual short splash, which fades. The same fix covers "How we handle your information" on a driver's document upload link, which had the same fault.

• If a page ever does arrive with the animation over it in this way, the animation now fades away by itself.

3.116.0

16 October 2026

• The Calendar's animation can now play as a transition into the page. On Media's Moments screen the System Admin chooses how Calendar opened shows: as the small card it has been, or as a transition. A transition plays in the middle of a dark screen as the Calendar opens, while the calendar loads behind it, and fades to the real calendar when it ends, so the animation's calendar page with today's date becomes the real one. If the calendar is still loading then, the last picture stays for at most one more second.

• A tap anywhere, or Escape, skips it at once. It plays only if it can start within a second, and never on a phone set to reduce motion, on a phone saving data, or on the first page after the app's own opening animation. It counts towards the same two a day as the cards. Every moment stays a card until the admin chooses otherwise, and only Calendar opened can be a transition. The Moments screen can try it either way without changing what anybody else sees.

• The × has gone from the moment card. A tap anywhere on it still closes it, and it still goes by itself.

• On a phone, a moment's form on the Moments screen now fits the screen. A long animation title had pushed its fields past the right edge.

• This release has a database change, which must be in before it is deployed.

3.115.0

16 October 2026

• A Media studio for the System Admin, behind the Media switch, which ships off. A Media tile under Platform opens three screens: the Studio, where an animation goes from an idea to a brief to its files to approved; the Library, for what is live and what was retired; and Moments, the four places in the app where a live animation may play: the Calendar opening, a booking sent from the chat, a trip completed, and a pay page showing paid.

• Only the System Admin approves an animation, and making it live is one tap. Approving needs its alt text, a still picture, and a tick to say nothing in it is invented: no made-up customer, review or quote, nobody's face or voice without their written yes, and nobody made up shown as a driver.

• A moment is a small card that one tap skips, never a screen in the way. It is silent, never shown on a phone set to reduce motion, a still picture on a phone saving data, and at most two a day on any one phone. Each moment has its own rules: which animation, who sees it, between which dates, how often, and whether today's date is drawn over it. JollyDrivers counts how often each animation is shown each day, never who saw it.

• The boot splash is the Library's first piece, added the first time Media is opened. It still plays when the app starts, from its own file, exactly as before. The first new animation is made for the Calendar: the JollyDrivers mark becomes a calendar page and today's date appears on it. It goes in through the Studio like any other.

• Files are virus-checked, kept on JollyDrivers' own server and served only from JollyDrivers' own address. Nothing is rendered on the server.

• This release has a database change, which must be in before the switch is turned on.

3.114.2

16 October 2026

• A ride there and a ride back later, booked through a driver's AI assistant, now makes two bookings. One booking is one continuous trip. The assistant gives the return time as before, and JollyDrivers shows the way there and the ride back on one summary and creates both with one approval: each with its own route, calendar check and fare (the fare given is each way), on the same customer card. Neither is marked as a return, which the app itself stopped doing in August. A trip where the driver stays with the customer and brings them back is still one booking, with the place they turn round as a stop.

• A return time given without a date is now on the day of the pickup, not today.

3.114.1

16 October 2026

• The Settings page and the list of what JollyDrivers can do now describe the tracking link as it works since 3.114.0: a completed trip's link shows a summary for 30 days, the updates made with the passenger on board are kept for it, and the arrived and finished places appear there in words. They used to say the page simply finished, that no trail was kept, and that a stage's place was never shown to a passenger.

3.114.0

16 October 2026

• A tracking link now shows a summary of the trip once it has finished. Where it used to say only "This trip has finished", the page shows when the driver arrived at the pickup and where, when the passenger got in, when and where the trip finished, how long it took and how far it was by road.

• With a map of the trip. A green pin where the driver arrived, a blue dot for each time the driver pressed Update location with the passenger on board, a red pin where the trip finished, and Google's road through them. It is not a record of every road driven: the phone is still never followed, so the more often the driver updates, the closer the line is to the roads taken.

• And a button to pay, or to the tax invoice. "Pay for this trip" opens the trip's pay link. Once the trip is paid it says "View your tax invoice" and opens the same link, which is the tax invoice by then. There is no button where the link could not take a payment.

• Whoever holds the link sees the summary, for 30 days after the trip finished, addresses and all, because the link is made to be passed on. After 30 days the page says only that the trip has finished, and the places kept for it are wiped.

• For drivers: Update location presses made with the passenger on board, when the phone is sure of itself to 100 metres, are now kept with the link until 30 days after the trip is completed, so the summary can show the road. Nothing from before the pickup is kept, and if the trip ends any other way they are wiped as before.

• This release has a database change, which must be in before it is deployed.

3.113.3

15 October 2026

• Each trip on a customer's "Your upcoming trips" email now says who is travelling. The passenger's name sits under the trip's date and time, with the people travelling with them as a count: "Sam Taylor +2" on a trip for three. It is there even when the passenger is the customer the email goes to. The number of passengers is still at the bottom of each trip.

• Deliveries and jobs in the same email have no passenger, so they show no name. The confirmation for a named group of trips is unchanged.

3.113.2

15 October 2026

• On a tracking link, the orange estimate dot now starts straight away. It appears on your driver's last known place as soon as the page shows an update, and moves off along the road from there. It used to wait a minute and then appear well along the road all at once, which on a short drive put it far ahead of the car.

3.113.1

15 October 2026

• On a tracking link, the orange estimate dot now glides along the road. Between updates it moves smoothly at the pace Google's drive time predicts, following the road's bends, instead of jumping every 30 seconds. It still says it is an estimate, and it disappears when the predicted drive time is up: only your driver says the car has arrived.

• A phone set to reduce motion keeps the dot's 30-second steps. Nothing extra is read from the driver's phone and nothing extra is asked of Google.

3.113.0

15 October 2026

• Know when a customer has paid. With the new Payment alerts switch on, the trip's driver gets a text and the operator's office an email once JollyDrivers knows a trip is paid: which trip, how much, how it was paid and any tip for the driver, with a link to the trip. A driver with no verified mobile is emailed instead.

• It comes from the payment, not from pressing Pay. It goes when Xero says the invoice is paid, however the customer paid it (the pay link, Xero's own invoice email, a bank transfer matched in Xero, a payment keyed into Xero), when somebody records a payment with Mark as paid, and when a tip added after the fare is paid. A group invoice is one message, not one per trip.

• Nobody is told about a payment they recorded themselves, an owner-driver is told once, and no message has the customer's name, number or address in it. Each trip's timeline says who was told and how.

• Turn it off for yourself on your Account page, under "When a customer pays". A person who runs the operator can turn the office email off there too.

• It is switched off until the Payment alerts switch is turned on in Settings, once this release's database change is in. A part payment made in Xero is not seen until the invoice is paid in full.

3.112.0

14 October 2026

• Tap the pickup time on a booking's page to change it. The date and time at the top of the page now has a small pencil at the end, as the stops do. Tapping it opens a window for when the trip is: the date, and the time on the clock at the pickup, with its time zone shown (for example AEDT, NSW).

• On an airport trip, the flight is in the same window. Change the flight number, the landing or departure time, checked luggage and, on an airport pickup, the wait after landing. Tapping "Flight lands" or "Flight departs" on the Route card opens it too. A new flight number takes the old flight's time off, because that time belonged to the old flight.

• Check flight fills the time in. It looks the flight up for that day and fills in its scheduled landing or departure time. It is an offer, never a must: you can always type the time yourself.

• The pickup follows the flight when you say so. Move the landing or departure time, or the wait after landing, and the window suggests the matching pickup with a button to move it. It asks again when you save.

• It tells you what matters before you save: that the time has already passed, that nothing is sent to the customer, and, for the operator and the trip's own driver, whether the new time clashes with the driver's other jobs. A clash is a warning, and you can still save. A pickup at or after the booking's return time is refused. After saving on a booking that has gone out, it offers Send updated confirmation, as the stop window does.

• "Edit airport pickup buffer" has left the tools drawer. The wait after landing is in this window now, with the same choices.

• Who may change the time is as before. Edit booking still has the time and the flight too.

3.111.1

14 October 2026

• Moving a pickup across the NSW and Queensland border now says what it does to the time. A pickup keeps its time on the clock where it is, so in summer, when the two states are an hour apart, moving 7:30 AM from Tweed Heads to Coolangatta made it an hour later without a word. The stop's window and Edit booking now say so before saving, for example: "The new pickup is on Queensland time. It stays at 7:30 AM on the clock there, which is an hour later than it would be on New South Wales time."

• You choose which time to keep. Keep 7:30 AM there, which is chosen to start with and is what happened before, or keep the same moment (6:30 AM there). In Edit booking the same choice comes up when you save.

• In winter, when the two states keep the same time, nothing is said. When the new address's time zone can't be told from the address, it says to check the time.

3.111.0

14 October 2026

• Tap a stop on a booking's page to change it. On the Route card, each pickup, drop-off and stop is now one button with a small pencil at the end. Tapping it opens a window for that stop alone. "Name this place" no longer sits under every address.

• A new address has to be picked from Google's list. Search for it and choose it; Save stays off until you do, and nothing typed by hand is taken. The new address changes this booking only.

• The place's name is in the same window. Give the place a name, change it, or empty the box to take it away. The window says what a name does: it shows beside that address on every booking to it, for every customer. Choosing a new address switches the box to that address's name, or leaves it blank.

• On a booking that has gone out, it says what is not changed. Changing the address sends nothing to the customer, and the confirmation they have still shows the old address. It also says the price and any invoice stay as they are. Once saved, it offers Send updated confirmation, which opens the usual send window; nothing is sent until you send it there.

• An airport end is changed in Edit booking. Turning an airport pickup or drop-off into a street address, or the reverse, changes what kind of trip it is, so this window says so and points you to Edit booking. Airport to airport and street to street are fine here.

• Who may change an address is as before: the operator until the trip is finished, whoever made the booking, and the admin. Naming a place is still for the operator and its drivers. In the booking chat, Name this place is where it was.

3.110.2

14 October 2026

• The Payment button at the top of a booking's page shows the fare. Where it had a $ sign, it now says what the booking costs in whole dollars, such as $87. The exact figure, cents and all, is still on the top line of Payment. A booking with no price yet keeps the $ sign.

• A small green tick on the button's corner means the booking is paid in full. A booking that is part paid has no tick, because money is still owed on it.

• On a phone, the bar that follows you down the page shows the same.

3.110.1

14 October 2026

• A booking's page is shorter. The billing card (the one headed Invoice, Cash or Card) and the Pay link card have gone from the page. Everything they did is under Payment, the $ button at the top: the pay link and every way of sending it, each invoice and what you can do with it, and Mark as paid.

• Flight status and Extras have moved up. They now sit under the passenger and pickup summary, above Driver & Vehicle and the map. On an airport drop-off, the suggested pickup time moved up with Flight status.

• The fare and the Paid chip are no longer on the page itself. They were on the billing card's heading. Both are on the top line of Payment. A booking with tolls or airport fees still shows its fare on the Fees card.

• Where the Send confirmation window, the booking chat and your AI assistant pointed you to the Pay link card, they now say Payment.

• A group's page keeps its Pay link card.

3.110.0

14 October 2026

• The tracking page now estimates where your car is between your updates. After you press Update location, the page your passenger sees keeps the place and time you gave it, and adds a line such as "Estimate: about 9 minutes away now" and an orange dot on the map. It is worked out from the drive time Google gave when you updated. Nothing is read from your phone for it.

• It says it is an estimate, and it can be wrong. It keeps moving at Google's pace even if you have stopped or gone another way, and the page tells your passenger so. Press Update location whenever you want the real place shown: the estimate starts again from there.

• It never says you have arrived. Only your At pickup swipe does that. If Google's drive time runs out first, the dot goes and the page says the car would be there by now and that you have not said so yet.

• Once your passenger is on board the page estimates the drive to the destination without a press. It starts from the pickup at the time you swiped On board. An Update location on the way replaces it with where you really are.

• Trips with stops in between now have a tracking link too. Once your passenger is on board, the card has one more button, for example "Reached stop 2 of 4". Tap it when you get to that stop and the page moves on to the stop after it. It reads nothing from your phone, it asks you first, and it cannot be undone.

• Your passenger only ever sees the next stop. A stop before the last one is called "the next stop". The page does not show stops further ahead or say how many there are.

• The estimate and the Reached stop button come with the tracking link, which is still off until it is switched on in Settings.

• None of this has been tried on a phone or on a real drive yet. It was checked by tests and in a desktop browser at phone size.

• Security updates to three of the Microsoft libraries JollyDrivers is built on, published on 13 October. Nothing you use looks or works differently.

3.109.0

14 October 2026

• A tracking link you can send your passenger. On a passenger trip you are driving, once you have swiped En route, a "Tracking link" card sits at the top of Trip progress. Press Update location and JollyDrivers reads where your phone is, once, and makes a link. Send it by WhatsApp, a text or your phone's own Share. It is off until it is switched on in Settings.

• What your passenger sees. The link opens a page with no sign-in: a map of where your car was when you last updated, the stop you are heading for, a line such as "At 3:02 pm your driver was about 14 minutes away", and your car with its number plate. It carries your operator's business name. It does not show your name, your number, the passenger's name, the booking number, the fare or any address in words.

• It shows where you were, not where you are. The page says so, and says when you last updated. Press Update location again whenever you want it brought up to date. Each press gives your passenger a fresh place and a fresh time away. Nothing is read from your phone between presses.

• Your swipes move the page along too. At pickup makes it say "Your driver has arrived". On board turns it to the trip to the destination. Completed finishes it.

• Your passenger can pass the link on, so somebody waiting for them can follow the trip. The page says nobody is watching it and to call 000 in an emergency.

• The link stops working when the trip does: at Completed, a cancellation or a no-show, if En route is undone, if the trip goes to another driver, and 12 hours after it was made. "New link" on the card stops the old one at once, for when it went to the wrong person.

• Only the newest place is kept, and it is wiped when the link ends. There is no trail of where you have been. The trip's timeline notes that a link was made and how you shared it, never where you were, and a text you send with the link is kept without the link in it.

• Only you can do this. The card is shown only to the driver of the trip, on their own phone. An operator or the admin looking at your trip does not see it and cannot update your location for you. Only somebody holding the link sees the page.

• For now it is offered on passenger trips with one pickup and one destination. Trips with stops in between, deliveries and attendance jobs do not have it.

• The "Tracking test" card from 3.107.0 has gone. The test did its job: it showed that a phone tells JollyDrivers nothing while another app is in front, which is why this link works by a button.

• It has not been tried on a phone yet. It was checked by tests and in a desktop browser at phone size, so a real trip is the test.

3.108.0

14 October 2026

• The pay page only offers paying your driver in person where that is allowed. The "Paying in person?" card (cash, or a card on the driver's reader) now shows only for a trip picked up in New South Wales. Queensland does not allow a payment to be taken in the car, so a Queensland trip is paid through the page: by card, or by bank transfer or PayID where the operator offers it.

• Where the page used to say "pay your driver", it now names the operator when the trip cannot be paid in person. That is the message when paying online is not set up, when the invoice could not be made, and when part of the booking is already paid.

• Operators: a new switch. Settings, Booking Form, "Tell my customers they can pay the driver in person". Turn it off and your customers are not offered it on any trip. It is on unless you turn it off.

• The admin has a switch above that one. With it off, no customer of any operator is offered paying in person, and the operator's switch is hidden. An operator can turn the offer off for their own customers and cannot turn it on when the admin has it off.

• Nothing changes in what you can record. Cash, a card on a terminal and a bank transfer are still recorded on the trip page, in every state.

3.107.0

13 October 2026

• A tracking test on the trip page: the first step towards a link your passenger can follow. The plan is a link you send a passenger when you set off, which opens a map showing your car on its way. That page is not built yet. A web page is often stopped from seeing where a phone is once another app is in front, and your maps app will be in front while you drive, so this release finds out how your phone behaves first. It is off until it is switched on in Settings.

• How to run it. On a passenger trip you are driving, once you have swiped En route, a "Tracking test" card appears near the top of the trip page. Press Start, allow location if your browser asks, and drive as you normally would. The screen is kept on while the trip page is showing.

• What the card tells you. How many readings your phone sent, the longest gap between two of them, and how many were sent while the page was behind another app or the screen was off. It also says whether your phone agreed to keep the screen on, and how often the phone had to load the page again.

• Nobody is shown where you are, and no position is kept. Not your passenger, not your operator and not the admin. JollyDrivers checks each reading against the trip and throws it away. Your phone keeps the counts and times on the card, and nothing else.

• Only you can start it. The card is shown only to the driver of the trip, on their own phone. An operator or the admin looking at your trip does not see it and cannot start it for you.

• It stops by itself when you press Stop, when the trip is completed, cancelled or marked a no-show, and after 12 hours. It pauses while you are on another JollyDrivers page and picks up when you come back to the trip. The result stays on the card until you press Clear.

• Passenger trips only. Deliveries and attendance jobs are unchanged.

• It has not been tried on a phone yet. The card was run in a desktop browser with a made-up position, so a real drive is the test.

3.106.0

13 October 2026

• You can now correct a wish you raised. Open your wish on the Wishlist and there is an Edit button. It opens the same two boxes you filled in when you added it, so you can fix the title or say it more clearly.

• Only while nothing has been decided. Once a wish has been planned, approved, done or declined, or once somebody else has pressed "Me too" on it, its wording is fixed. That way nobody ends up backing words they never read. If that happens while you are editing, Save tells you why and nothing is changed.

• Only your own wishes. Nobody else sees the Edit button, so the Wishlist still does not say who raised what.

• Your AI assistant can do it too. Ask it to reword one of your wishes: it reads the old and the new wording back side by side, and saves only when you agree.

• For the admin: a wish's wording can be tidied on its own report screen while nothing has been decided, and the person who raised it is told it was tidied. The earlier wording is always kept on the report's trail. If a wish is reworded after its scope was drafted, the screen says so above the box where you approve the scope.

• Problems and change requests cannot be edited after they are sent, as before.

3.105.0

13 October 2026

• You can now stop being told each time the admin starts acting as you. If you have switched on "Let the JollyDrivers admin act as me" on your Account page, there is a second switch under it: "Tell me each time they start". It is on, as it always was. Turn it off and you are no longer sent a text (or an email) each time the admin's assistant starts acting as you.

• Nothing else changes when it is off. Every time the admin acts as you is still listed on your Account page, with their name and what they did. The line for a start now says when no notice was sent because you chose that.

• Only you can change it, on your own Account page. The admin cannot, and neither can any AI assistant.

• It is set for each admin separately, and if you withdraw your permission and give it again, the notice comes back on.

• For the admin: when you start acting as somebody who has turned the notice off, your assistant is told they have chosen not to be told, so it is not mistaken for a notice that failed to send.

3.104.0

13 October 2026

• Your AI assistant can now change a booking, not only make one. When a customer rings to move their pickup, change their flight or change an address, ask your connected assistant to change the booking. It opens the booking, makes the change with you, and reads the old and the new back side by side before anything is saved. Until now the only way through an assistant was to cancel the booking and make it again.

• It is the same booking afterwards. The reference stays, and so does the trip's whole timeline. Each change is added to it as made by you through your assistant.

• What it can change: the pickup time, the flight number, the pickup, the drop-off and any stops in between. A time said without a date ("move it to half past nine") stays on the booking's own day.

• What it checks before you agree: the new route and when you would arrive, in the drop-off's own time; whether the changed job clashes with the driver's other jobs; and whether the booking has an invoice that may need re-issuing.

• What it leaves alone: the customer, who is travelling, the fare, how it is paid, the number of passengers and the driver. Those are still changed on the trip page. A return time is not set this way either: book the way back as its own trip. A booking that already has a return time keeps it, and its pickup cannot be moved to that time or past it.

• Who can change what is as it is on the trip page. A driver can change a booking they made themselves. An operator can change any booking in their own book. A booking that is still a draft, or one that is finished, cancelled or declined, cannot be changed this way.

• Your customer is sent nothing. A confirmation they already have still shows the old details, so ask your assistant to send a new one if they should have it.

• Changing the flight number takes the old flight's landing or departure time off the booking, because it belonged to the other flight.

• There is no new switch. If your assistant can already make bookings, it can now change them. For an operator it also needs the switch that lets an assistant change bookings in their book.

3.103.0

13 October 2026

• Send the pay link as you finish a trip. When you swipe Completed on a passenger trip, the Trip Progress drawer asks "Send Alex the pay link?" (with your customer's first name). Under it are the three ways of sending you already have in Payment, WhatsApp, Text it and Share, and "No, paid another way". It is off until it is switched on in Settings.

• The invoice is ready before your customer opens the link. Once the trip is saved as Completed and you have sent the link, JollyDrivers raises the invoice in Xero straight away. Until now it was raised when the customer slid to pay, and they waited a few seconds while that happened. Now their slide takes them straight to the payment page.

• "No, paid another way" raises nothing, so a trip paid in the car never gets an invoice it does not need. Completed is saved either way, after the usual five seconds to Undo, whether or not you answer.

• Sending the link from Payment on a completed trip does the same, so skipping the question and sending it later comes to the same thing. Sending it before the trip is done changes nothing: that invoice is still raised when the customer pays.

• You are not asked about a trip that is already paid or has no price, about a delivery or a job, or where the operator has not connected Xero. A trip in a group that one link pays on one invoice still has that invoice raised when the customer pays.

• If the invoice cannot be raised, the trip's timeline says why, nobody is interrupted, and it is raised when the customer pays, as before.

• A customer who adds a tip still waits a moment while the tip is put on the invoice. And once an invoice exists, the pay page no longer offers a change of who it is for: to bill someone else, void it on the trip and request it again for them.

• With the switch on, a customer who slides to pay while their invoice is still being raised is held for up to 20 seconds and then sent on to pay. Before, they were told to refresh the page.

• With the switch on, an invoice whose payment link Xero had not handed over has it fetched when the pay page is opened. Before, the page said "Your invoice is being prepared" and nothing changed that.

3.102.0

13 October 2026

• A place's name now goes out in what JollyDrivers sends. This is the second part of Place Names and uses the same switch, which is off until it is turned on in Settings. Nothing changes for a stop nobody has named.

• Confirmations. In the email, its PDF and the plain-text version, a named stop shows the name with the address under it. That is so for one trip, a group, an itinerary and a paid receipt. Tapping the stop in the email still opens the address in maps.

• Texts to a passenger. Where a message says the pickup or the drop-off ("I'm on my way to..."), it says the place's name in place of the start of the address.

• The pay link's message names a place the same way: "from Gold Coast Airport to Peppers Salt Resort".

• Calendar invites for drivers and operators. The title says the name (an airport still shows its code), and the details give the name in front of the address. The event's location is still the address alone, so the calendar can find it. An invite already sent keeps its words until the booking next changes, or you resend it.

• Job offers and the list of trips when sending an itinerary show the name in front of each address.

• The heading of a confirmation ("Surfers Paradise → Bilinga") is still the two suburbs.

• Not yet: invoices and the search boxes still go by the address alone.

3.101.1

13 October 2026

• A place chosen from Recent locations is saved like one you searched for. In the booking chat, tapping an address under Recent locations used to save its words and nothing else. The stop now also keeps what JollyDrivers already knew about that address from an earlier booking: where it is, its postcode and suburb, and which place Google says it is.

• This holds when the chat's assistant writes the address back a little differently, with ", Australia" on the end or "Dr" as "Drive". It is the same address either way.

• A delivery or a job made from the New delivery form, and a trip booked from a Quick Quote, now keep which place Google says each address is. Both already kept where it is and its postcode.

• On New Booking, tapping one of a customer's recent pickups or destinations over an address you had already picked from the list no longer leaves the first address's Google place on the stop.

• Nothing on a booking looks different, and no price changes today: fares are still entered by hand. What changes is what is stored behind each stop from now on. It helps Recent locations show each place once, and once fares are worked out automatically a place chosen from Recent locations will be priced as it was when it was first picked. Bookings already made are left as they are.

3.101.0

12 October 2026

• Give a place a name. This is behind a switch, Place Names, which is off until it is turned on in Settings. With it on, each stop on a booking's page has "Name this place". Type the name people know the place by, like "Surfers Aquarius on the Beach" for 4-12 Old Burleigh Rd, and JollyDrivers remembers it for that address.

• Every booking you have to that address then shows the name: the ones already made, and new ones however they are made. On a stop's own row the name is shown with the address under it. Where the whole address is shown elsewhere, the name comes first and the address follows. Where only a short form of the address is shown, the name is shown in its place.

• It is shown on the booking's page, the passenger's own trip page, the lists of bookings, deliveries and trips, the calendar, the progress drawer, the booking chat, the recent places on New Booking, the earnings and ledger pages, the pay page, and where a trip is picked or shown for a complaint or an incident.

• A line on a driver's ledger or the booking fee ledger keeps the words it was posted with. A line posted after a place is named says the name, there and on the driver's statement. A line posted before keeps the address.

• The operator and its drivers can name a place, change the name with the pencil beside it, or remove it. In the booking chat the same is offered on the summary, before the booking is made.

• A name belongs to the address, so it is shown on every booking to that address, whoever the customer is. It suits a venue, not a customer's home, and the box where you type it says so.

• The address itself is not changed, so prices, routes and directions are worked out exactly as before.

• Not yet: confirmations, texts, calendar events, invoices and the search boxes still go by the address alone. Those follow in later releases.

3.100.0

12 October 2026

• Bigger text in the progress drawer. Trip progress, Task progress and Delivery progress are read in the vehicle, so their text is now larger for everybody: the stage names, the times, the stop addresses, the passenger's name, the place buttons and the words on the swipe.

• The time a stage was stamped at, the place saved with it and the stop addresses are now in the full text colour, not grey, so they are easier to read in sunlight.

• A text size you can choose. The new "Aa" button at the top of the drawer steps through three sizes: standard, large and extra large. Your phone remembers the one you chose. It changes this drawer only; the rest of JollyDrivers stays as it is.

• At extra large, the booking's address and "Use GPS" sit one above the other, so the address is shown in full.

• Buttons and the swipe are the same size as before. Only the text grows.

3.99.0

12 October 2026

• Log fuel from a photo of the receipt. This is behind a switch, Fuel Receipt Photo, which is off until it is turned on in Settings. With it on, "Log fuel" on a vehicle's fuel log first asks: a photo of the receipt, or enter it by hand.

• From a photo, JollyDrivers reads the date, the litres, the amount paid for the fuel and the station, and opens the usual form filled in. Nothing is saved until you have checked it and pressed Save.

• If you wrote the odometer reading on the receipt, that is read too, with a note asking you to check it. If you didn't, you are asked for it: an entry made from a photo needs an odometer reading.

• The photo is kept with the entry. A receipt icon on the entry opens it, and you can take it off when you edit the entry. Deleting the entry deletes the photo.

• If the photo can't be read, the form opens empty with the photo still attached, and you type the details in.

• The photo is sent to JollyDrivers' AI provider to be read. Where it was taken is removed from it first.

• Entering a fill by hand is unchanged.

3.98.2

12 October 2026

• In the Payment drawer the QR code is behind a card. The pay link no longer opens with the code on screen. Press "Show QR code" to see it, and "Hide QR code" to fold it away. It is folded away again each time you open the drawer.

• Share, WhatsApp, Text it, Copy, Open and New link are cards there too, each with an icon and a line saying what it does, like the rest of the drawer.

• The Pay link card on the booking's page is unchanged.

3.98.1

12 October 2026

• The What's new page shows the right time beside "deployed" again. Since 10 October that time had been about eleven hours too early. It was when the version was built, read off the wrong clock, and not when it was put live. The same time is on System Admin, Health, as "Put on this server", and that is fixed too.

• Behind the scenes: the tool that puts new versions live now records the moment it does so. Nothing else changes for anyone using JollyDrivers.

3.98.0

12 October 2026

• Text it sends the pay link to the customer who booked. On a trip booked for someone else, the pay link's "Text it" greeted the customer and sent the text to the passenger's phone. It now goes to the customer's own number.

• You choose who gets it. Where the customer and the passenger have different mobile numbers, the sheet has a "Send to" list with both. The customer is chosen to start with. Pick the passenger and the words change to greet them. Words you have already changed by hand are kept.

• The timeline names who a text went to, for example "Text sent to Sam (the customer) from My mobile".

• "Send an update" is unchanged: on my way, running late and the rest still go to the passenger.

3.97.0

11 October 2026

• A booking has a Payment button. The $ button beside the tools and comms buttons at the top of a booking opens a drawer with everything about the money: Mark as paid, the pay link, the invoice and Record external invoice. It is there on a phone and on a computer, and in the bar that follows you down the page.

• Mark as paid and Record external invoice have moved there from the tools drawer. Checking a price against your fare book is still under tools.

• The pay link is ready when you open the drawer. Where a booking already has a pay link, its QR code and the buttons to send it are on screen straight away, with nothing more to tap. Where it has none yet, tap "Show pay link" to make one. On a booking paid in full the code is one tap away.

• Everything you can do to an invoice is a card you can read. Approve, email it from Xero, text its link, open it, see its line descriptions, check it against Xero, change the due date and void it each have a name and a line saying what they do. On the Billing card these are still a row of small icons.

• The Billing card and the Pay link card are still on the page. Making a new pay link in one place now updates the other, so neither is left showing a link that has stopped working.

3.96.1

11 October 2026

• On a phone, a booking's status button is back at the top of the page. It sits on the right of the row with the tools and comms buttons, where it is on a computer, and no longer floats over the bottom of the screen. Tap it to open Trip progress or Delivery progress as before.

• The status in the bar that follows you down the page opens the progress drawer too. Tap it wherever you have scrolled to; closing the drawer leaves the page where it was.

• The long reference code is no longer beside the booking number at the top of a booking. It is still on the System card, as "Reference".

3.96.0

11 October 2026

• The Actions drawer on a booking is now two drawers. The Actions button has become two icon buttons at the top of the booking: a tools button for managing the booking, and a speech-bubble button for contacting the people on it. Both are also in the bar that follows you down the page on a phone.

• Every action is a card that says what it does. In place of the rows of buttons, each action has an icon, its name and one line of description. Edit booking comes first, then Rebook this trip, Mark as paid and Record external invoice. Submitting, pricing and the danger zone look the same.

• Rebook has a "Return trip" switch. It shows the route turned round, for example "Gold Coast Airport → 12 Phillip St". Switch it on and press Rebook, and the rebook page opens with the reverse direction already chosen. You can still change it there.

• The new Comms drawer is headed by the customer: their name, number and email, with Call, Text and Email underneath. When somebody else is travelling, the passenger has a card of their own under the customer's.

• Email opens a short menu of what can be sent: the booking confirmation, or the receipt once the booking is paid, and the invoice from Xero when there is one. Nothing is sent from the menu, and you still see who it is going to before it goes. Only a person with an email address has an Email button. Where the customer has none, their card has an "Email about this booking" row, so a confirmation can still go to an address you type.

• Text is one button. For the passenger it opens Send an update where that is switched on, and your phone's own messaging app where it is not. For a customer who is not the passenger it opens your phone's messaging app with their number, because Send an update only ever texts the passenger's number.

• Set travelling passenger and the invitation to JollyDrivers are now on the customer's card. Log an SMS, Log a phone call, Add a private note and the two calendar buttons moved to the Comms drawer.

• The buttons no longer show a count of actions. For an operator, "Decline booking" on a booking that has already been accepted is now near the foot of the tools drawer, under "Change the answer". On a phone, the bar that follows the page shows the customer's name above the time, so a long time no longer pushes the name out.

3.95.2

11 October 2026

• A stage you forgot to mark is now estimated from the real drive to the pickup. If you mark En route, forget At pickup and On board, and then mark the trip Completed, JollyDrivers fills in the two you missed and labels them "estimated". The arrival used to be written down as 20 minutes after you set off, however far away the pickup was, so a 44 minute drive was recorded as 20. It is now the time you set off plus the drive from where you were to the pickup address.

• When there is no drive to go on, the estimated arrival is the pickup time. That is the case when no place was saved with your En route stage. If you set off after the pickup time, it is one minute after you set off.

• An estimated On board now follows the arrival. It is three minutes after you arrived, or the pickup time if you arrived early. Before, it ignored an arrival that was estimated at the same time, which could show you waiting half an hour at the pickup.

• The "Best guess" offered when you set a stage's time by hand follows the same rules, and so do stages recorded through your assistant. Deliveries are estimated the same way. Stages already recorded on past trips are not changed.

3.95.1

10 October 2026

• The booking chat is less likely to ask for a typed answer where it meant to offer buttons. Towards the end of a booking — most often on the very last question, "Ready to submit?" — the chat could show a typing box where a choice belonged, so you had to type an answer to a two-button question. It now keeps the cards it has already offered in front of it as the conversation goes on, which is what stops it losing the habit on a long booking.

• Behind the scenes: when the chat does ask a question without the buttons that belong with it, that is now written to the log. Nothing recorded it before, so there was no way to tell how often it happened, or whether anything done about it had helped.

3.95.0

10 October 2026

• You now choose the place before you swipe a stage. On the En route, At pickup and Completed cards in Trip progress, the driver of the trip has two buttons side by side: the booking's own place (Home, the pickup address or the destination) and "Use GPS". Neither is chosen for you. The swipe says "Choose a place first" and cannot be swiped until you tap one, and you can change your mind as often as you like before you swipe. On a delivery the cards are En route to pickup, At pickup and Delivered.

• The place you chose is named under the swipe. A long address is cut short on its button so that the two buttons fit on one line. Once chosen, the street and suburb are shown under the words on the swipe.

• "Use GPS" shows where your phone thinks it is before you swipe. Tap it and the card looks for your phone, then shows the street and suburb it found. If that is not right, tap the booking's place instead. When the phone is not sure of itself the card shows the suburb and says "approximate". What you see is what is saved: the phone is not asked again when you swipe.

• A GPS reading is good for two minutes. Left unswiped for longer, the card lets it go and asks you to choose again. Tapping "Use GPS" a second time looks again.

• If the phone finds nothing, the card says why and nothing is chosen. Tap the booking's place, or "Use GPS" once more.

• The stage to swipe next has an amber border, so it stands out from the other cards. The place button you chose is amber too.

• An operator or an admin stamping a stage for a driver has nothing to choose and sees the cards as before. On board and No-show are unchanged, and so is a driver with no home address saved, whose En route still uses the phone. The place buttons are part of saving stage locations, so they are there only while that is switched on. The amber border is there either way.

3.94.0

10 October 2026

• A text to a passenger can be sent from your own phone's messaging app. On a booking's Send an update sheet, on a phone or a tablet, "This device" is a new place to send from. It opens your messaging app with the passenger's number and the message already filled in. You press Send there, and you can change the words first. The text comes from your own number and stays in your own message thread, and replies come back to that phone. It needs no number set up for you in JollyDrivers. On a computer the option is shown greyed out. The booking's timeline notes that the message was opened on the phone, with the words; it cannot say whether you sent it.

• My Messages: keep your own wording for each point of a trip. A new page for drivers holds the texts you send for On my way, Running late, I've arrived, Meeting a flight and Pickup reminder. Keep several under each, for instance one for each airport with its own pickup instructions, give each a name and put them in the order you like. Only you see them.

• Placeholders fill in the names and times. Write [FirstName], [PickupAddress], [PickupTime], [DriverName] and the others listed in the editor, and they are filled in from the booking when you pick the message. The editor shows how the message will read, and points out a word in square brackets that is not a placeholder.

• Step through your messages when you send. On the Send an update sheet, a heading with more than one message shows arrows and "2 of 3". Yours come first and JollyDrivers' own wording is always the last one.

• The numbers and names you could already send from are unchanged. Both new features are switched off until the platform admin turns them on.

3.93.0

10 October 2026

• The progress drawer now starts with a brief of the job. Under the heading of Trip progress you see the passenger's name and every address on the trip, in order: a green dot for the pickup, a yellow dot for each stop on the way and a red dot for the destination. Delivery progress and Task progress show the customer's name and the job's addresses the same way. The brief stays where it is while the stage cards scroll under it.

• The addresses in the brief are short. Each is the street and the suburb, without the state, the postcode or the country, in small type so that most fit on one line. A long one runs onto a second line.

• Tap an address and Google Maps opens with directions to it. The address you tapped is the destination, and Maps starts from where you are when it knows. It opens in a new tab; a phone with the Google Maps app may open it there instead.

• The route and the map on the booking's own page are as they were.

3.92.0

9 October 2026

• A delivery or an attendance job can be marked as paid as soon as it is submitted. Until now Mark as paid only appeared once the job had been started, so a customer who paid up front could not be recorded until the driver set off. Passenger trips are unchanged: they can be marked as paid once they are confirmed.

• "Offer to drivers" is no longer shown on a booking that already has a driver. Offering one left it stuck at Offered, where nobody could accept it. Take the driver off first if the job should go to someone else.

• A driver can accept or decline an offered job on the booking's own page. When a job has been offered to you and you can open its page, the Actions list now starts with "Accept this job" and "Decline". Today a driver can open a booking's page only if they created it or are already its driver. The Job offers page works as before.

3.91.2

9 October 2026

• The driver search in account setup shows photos too. When a new rider looks for their driver while setting up their account, each driver found now shows their profile photo in the circle. A driver with no photo still shows their initials.

3.91.1

8 October 2026

• A delivery's page no longer says "1 Passenger" over the customer's name. It says "Customer", as an attendance job's page already did. Nobody travels on a delivery, so there was no passenger to count.

• The page a customer opens from My Deliveries no longer says "Passenger" either. On a delivery or an attendance job it said "Passenger" over the name and "1 passenger" under the route. It now says "Customer" over the name and shows no passenger count.

• The calendar's peek panel no longer calls the person who booked a job its "Recipient". On a delivery with no recipient named, and on every attendance job, the name shown is whoever booked it, and it now reads "Customer". A delivery that names who is receiving it still says "Recipient".

• Passenger trips read as they did in all three places.

3.91.0

8 October 2026

• A delivery now has a Delivery progress drawer, the same as Trip progress. On a delivery, the status ("Submitted", "In transit" and so on) is now a button. Tap it and the stages open as cards, in order: En route to pickup, At pickup, Collected and Delivered. On a phone the button stays at the bottom right of the screen while you scroll, as it does on a passenger trip.

• A stage is stamped by swiping, with Undo for five seconds. Everything Trip progress does, Delivery progress does: the time recorded is the moment you swiped, skipping ahead asks before it estimates the stages you missed, Collected or Delivered before the pickup time asks you first, and the clock on a card stamps a stage at an earlier time or corrects one already stamped.

• Each stage saves a place the way a trip's does. En route to pickup saves the driver's home, At pickup saves the pickup address and Delivered saves the drop-off address. Collected saves none. The delivery's own driver has "Use my location" on those three cards, to save where their phone is for that one swipe. This is part of saving stage locations, so it applies only while that is switched on.

• Delivered still asks for proof of delivery first, when the booking needs it: a photo, a signature or the recipient's PIN.

• "Delivery failed" and "Returned to sender" are in the drawer too, under the stages, each with a red swipe. Delivery failed asks why after you swipe. Returned to sender appears once the goods are collected. Cancel delivery is at the bottom and needs a reason before its swipe will move.

• "In transit" and "At drop-off" are no longer stages you stamp. Once the goods are collected the delivery reads "In transit" until it is delivered. The At drop-off button had never saved anything.

• A delivery's status is said in a delivery's words on its page: "Submitted", "In transit" and "Delivered", where the top of the page said "Sent", "On board" and "Completed".

• An operator or admin gets the same swipes as the driver. Their swipe saves the booking's place. Their own device is never asked where it is.

• The stages only go forwards. Tapping "On my way to pickup" after "At pickup" used to put a delivery back to En route. A delivery saved as a draft has no stages to swipe until it is submitted.

• The Actions drawer no longer has the delivery buttons. Everything else in it is as it was, and its line under the title now says the status in words ("En route", where it printed "EnRouteToPickup").

• The number on the Actions button for a task was three too high and now counts the buttons that are there.

• Passenger trips and attendance jobs keep the drawers they had.

3.90.1

8 October 2026

• The driver search on My Drivers shows photos too. Each driver found by the search now shows their profile photo in the circle, as the list below it does. A driver with no photo still shows their initials.

3.90.0

8 October 2026

• Riders now see their drivers' photos. "Your drivers" on the rider dashboard and the cards on My Drivers show each driver's profile photo in the circle, the same photo already shown on a trip. A driver with no photo still shows their initials.

3.89.2

8 October 2026

• The app no longer sits on "Reconnecting (1 of 50)" with nothing to press. On a phone, coming back to JollyDrivers after a while could leave that message on screen for good, and the only way out was to close the app and open it again. Now, if a reconnect has not been answered within about 15 seconds, the app stops waiting and loads the page again by itself.

• After a long break it does not try to reconnect at all. If the app has been asleep for longer than the server keeps your place (about 17 minutes), it loads the page again straight away when you come back to it.

• There is a Reload button on that message from the first second.

• With no signal, or while the server is still waking up, it waits. The message changes to "JollyDrivers is not answering yet" and the page loads as soon as the server can be reached, where a reload sent into no signal used to leave an error page.

• A page that is loaded again starts fresh: anything typed and not saved is gone, as it was before when a connection was lost for good. The booking chat is still never reloaded for you, so you can read what was said; it has the Reload button.

• The part of JollyDrivers that reads uploaded photos has been brought up to date. The older version had known security faults in parts JollyDrivers does not use; the new one fixes them. Photos, documents and logos upload and display as before.

3.89.1

8 October 2026

• The Sandbox test operator's drivers no longer show up when a rider searches for a driver. The search on My Drivers and the driver step of account setup were listing them beside real drivers. A rider can no longer find or add one. A driver who also works for a real operator is still found, shown under that operator.

• A test driver already in your list stays there until you remove them.

3.89.0

8 October 2026

• A rider can now find a driver on My Drivers and add them, at any time. The page has a search box. Type part of a driver's name or their company's name, or their whole mobile number or the whole number plate of their car, and press Add. A mobile number is never shown in the results.

• Adding a driver sends them nothing. It only puts them in your list. "Share my details" is still a separate step, and it now works for a driver you have not travelled with: confirming it adds you to that driver's customer list with your name, mobile and email.

• The driver you chose when you set up your account is now in your list. That choice was saved but My Drivers never showed it, so the page stayed empty until your first trip.

• A driver you added can be removed. A driver who is in your list because you travelled with them stays, and one you are sharing your details with stays until you stop sharing.

3.88.0

8 October 2026

• A booking you saved but have not sent now says so on your dashboard. The card at the top of a rider's dashboard used to show a draft as "Your next trip" with a small grey Draft label. It now reads "Not sent yet", has a dashed border, tells you your operator hasn't received it, and has a Review and send button that opens the same window as Submit on My Bookings.

• A draft that can no longer be sent says that instead. A rider gives 15 minutes' notice, so once a draft's pickup is less than 15 minutes away, or has passed, its card says so and has no send button. It points to the operator's booking page for a new trip, and to My Bookings, where the draft can be deleted.

• A draft that can no longer be sent no longer hides a trip that is coming. The card showed whichever unfinished booking had the earliest pickup time, so an old draft stayed at the top until it was deleted. A booking your operator has, or a draft you can still send, now comes first.

• A "book again" you started and left without a date shows as "Date pending", with a Choose a date button that takes you back to finish it.

• Riders can no longer book with the Sandbox operator. It is a test operator: a booking made with it reaches no real operator. It is no longer offered under Book a ride, and its booking page says "Booking page not found" to a rider and to anyone who has not signed in. Test accounts, drivers, operators and the admin can still open it.

3.87.0

7 October 2026

• A rider can now add their full legal name on their Account page. It is optional: leave it blank and everything works as before. It is kept on records only, and your driver still sees your display name. Drivers, operators and admins must still give one, as before.

3.86.0

7 October 2026

• You can now add Google sign-in to an account that began with a text code. Your Account page has a new "Ways to sign in" panel. If Google is not connected, press Connect Google and choose your Google account. From then on you can sign in with Google or with a text code to your mobile, and both open the same account.

• A Google account is never moved from one JollyDrivers account to another. If the Google account you choose already signs in to a different JollyDrivers account, it is not added and the page tells you so. An account keeps one Google account.

• This is the button the "An account already uses this email" page has been pointing to. That page told people to sign in with their phone and choose Connect Google on their profile, and until now the button was not there.

3.85.0

7 October 2026

• A driver, operator or admin who switches to the rider side is no longer sent to rider setup. Switching to Rider used to take you straight to the welcome questions, as if you were new, before you could look at anything. Now you go where you were heading. This applies to a driver who is active in an operator's fleet, an operator attached to their operator account, and the platform admin.

• Rider setup is still there when you want it. If you have not done it, your rider dashboard shows a card saying it is optional, with a "Set up as a rider" button. Use it when you are booking a ride for yourself and want billing details for your invoices, your receipts and a regular driver. The card goes once you have finished.

• Nothing changes for anybody else. A person who is only a rider is still taken through setup first. So is somebody who chose "driver" when signing up and has not yet been added to an operator's fleet.

3.84.0

7 October 2026

• New, and switched off for now: a driver's Pick up now can work out when they will get there. When a driver books a passenger trip in the booking chat with Pick up now, the summary card reads where their phone is, asks Google for the drive to the pickup in live traffic, and shows the pickup as, for example, "About 3:20 pm, 14 min away". That is the time now plus the drive, rounded up to five minutes. The driver can move it five minutes earlier or later, or go back to plain "Now" when the passenger is already with them. The booking is made for that time, and the trip's timeline says the time was worked out and from what.

• The phone is asked once, and the driver is told why first. The first time, the card explains before the browser asks, and "Not now" is remembered on that phone. The position is sent to Google once, for the drive time, and JollyDrivers does not store it. If the phone gives no position, or one less sure than a kilometre, the card says so and the booking stays on "Now".

• For drivers only. Passengers still choose a time at least 15 minutes ahead. Nothing changes for an operator's New booking page, a connected AI assistant, deliveries or attendance jobs.

• Nothing changes until the platform admin switches it on. The switch is AsapPickupEta, and it ships off.

3.83.3

7 October 2026

• An operator's office and the platform admin are no longer held to 15 minutes' notice in the booking chat. Since 3.83.1 anybody booking through the chat who was not signed in as a driver had to choose a pickup at least 15 minutes ahead. That took in the office booking a car for somebody standing at the desk. Signed in as an operator or as the admin, you can book for any time today again. Passengers, and anybody not signed in, still give 15 minutes. Pick up now is still for drivers only.

3.83.2

7 October 2026

• For the platform admin: codes to approve work now have their own allowance, ten an hour. They used to share the three codes an hour a phone can be sent for anything, sign-in included. Approving is unlocked in one browser tab, so a refresh, a second tab or a new release each needs another code, and after three the screen said "Too many codes have been sent to your phone" and nothing could be approved. Codes of other kinds no longer count against approval codes, and approval codes no longer count against them. A code still works once, lasts ten minutes and allows five tries, and every unlock still sends a fresh text to your phone.

• When an approval code is refused for that reason, the screen says when to try again. It used to say "about an hour" whatever the real wait was. It now gives the time, for example "Try again at 2:35 pm Brisbane time".

3.83.1

7 October 2026

• "Pick up now" no longer books a trip as already completed. For a pickup in NSW the time was stored an hour early while NSW is on daylight saving, and a driver's trip shorter than about an hour was then created as completed before it had started. The pickup time now comes from the clock at the pickup address, and a booking made for "now" is never created as completed.

• The time is the moment you submit, not the moment you pressed the button. Pick up now is the first question, so a long conversation used to leave the pickup minutes in the past. The summary now shows the pickup as "Now", and the booking is given its time when it is made.

• The "already completed" notice on the summary is now right. It appeared on every Pick up now booking, whether or not the trip was then completed. It now appears only when the pickup time plus the estimated drive has passed, which is what decides.

• Pick up now is for drivers. Anybody else booking through the chat chooses a time. The button has also gone from return and flight times, and from the rebook window.

• A passenger's pickup must be at least 15 minutes away. It is checked when the booking is submitted, on the clock at the pickup address. Less than that and they are asked to choose a later time, and the time picker opens on the first time they can have. Sending a saved draft is checked the same way. This covers every chat booking by somebody not signed in as a driver. Drivers, and operators using their own New booking page, can still book for any time, and a driver who arrives early can still start the trip early.

• Deliveries and attendance jobs booked for now get the right time too, and so does a booking a driver makes by telling their AI assistant "now". The assistant's summary no longer says such a booking "will be recorded as a trip that has already happened".

• A trip whose pickup address has no state or postcode is no longer judged an hour early during daylight saving.

3.83.0

7 October 2026

• A swiped stage now saves the booking's own place, with no waiting for GPS. In Trip progress, En route saves the driver's home, At pickup saves the pickup address and Completed saves the destination. Nothing is asked of the phone, so there is no more "No location: not found in time" on an ordinary swipe. On board saves no place, as before. This is part of saving stage locations, so it applies only while that is switched on.

• "Use my location" is there when you want the real position. The driver of the trip has a "Use my location" button on the En route, At pickup and Completed cards. Tap it before swiping and that one swipe saves where the phone is instead. It is for that swipe only and is off again afterwards.

• Each place says where it came from. Under a stage's time the line now ends in "(booking address)" or "(GPS)", or reads "Home (saved address)". A place taken from the booking is never shown as if the phone had measured it.

• A driver's home address is not shown on a trip. En route shows the word "Home" to the driver and the operator alike, never the street.

• An operator who swipes a stage for a driver now saves the booking's place too. Before, their swipes saved no place at all. Their own device is still never asked where it is.

• "Use my location" now gets the time it needs. A fault in the last release cut the phone off a fraction of a second after the swipe, which is why En route and At pickup said "not found in time" unless the GPS was already awake. The phone now has up to ten seconds. A swipe that uses it can take a few seconds longer to save, and its card says "saving now" while it does.

• If the phone finds nothing, the stage says so. It does not fall back to the booking's address, so "(GPS)" always means a real reading.

• A driver with no home address saved: En route asks the phone instead, as it did before. Save a home address under Availability to have it used.

• The GPS is no longer woken just by opening Trip progress. It is woken when "Use my location" is turned on.

• The earlier "Not now" note at the foot of Trip progress is gone. Tapping "Use my location" is how to turn location back on for a device that said "Not now".

3.82.1

7 October 2026

• On a phone, the price on a trip card is always in view. A card's top line held the status, the pickup time and the price, and a phone is too narrow for all three, so the price slid off the right-hand edge of the card. On a list that shows a time zone beside each time it could not be seen at all. The status and the price now share the top line, with the price on the right, and the pickup time has a line of its own underneath.

• Every list of trips has it. A driver's My Trips and My Deliveries, an operator's Bookings and Deliveries, the admin's Bookings and Deliveries, and a customer's My deliveries.

• On the smallest phones a long status and a large price take a line each. Nothing is cut off. Cards on a phone are a little taller than they were.

• Wider screens look as they did. On a tablet or a computer the card is unchanged. On a screen in between, the top line stays as it was unless it cannot fit, and then the price moves to a line of its own.

3.82.0

7 October 2026

• A driver's My Trips opens with one filter control. Past, Today, Upcoming and All sit on their own, each showing how many trips it holds, with the order button beside them. The search box and the Status and Payment rows are no longer on screen until they are asked for. On a phone the filters take two short rows where they took most of the screen. My Deliveries is the same.

• "Filter by" brings in the rest. Search, Status, Payment and Show cancelled are under one button. Each takes a row only while it is in use, with a button on the row to take it away again. "Clear filters" appears once two are in use, and leaves Past, Today, Upcoming and All where you set them. A filter left on from a previous visit comes back with its row showing.

• Show cancelled now covers the list as well as the three panels at the top. It has moved from above the panels into "Filter by". Cancelled trips are left out of both until it is switched on, and choosing the Cancelled status switches it on too. Where a list is empty only because of that, it says how many cancelled trips are not shown and has the switch beside it.

• Show cancelled is off again each time the app is opened. It stays on while you move around the app, so opening a cancelled trip and going back does not put it away. The other filters are still remembered on that phone or computer.

• My Trips no longer opens filtered to Confirmed. It opens on every trip in the chosen window, less the cancelled ones. A filter already chosen on that phone or computer is kept.

• An operator's Bookings and the admin's lists keep the filters they had.

3.81.0

6 October 2026

• Trip progress now says where each stage was swiped. Under the time on En route, At pickup and Completed, the driver and the operator see the nearest street address to where the driver's phone was at that swipe. This is part of saving stage locations, so it shows only while that is switched on, and passengers never see it.

• The Stage locations card and its map are gone from the trip page. The place is in Trip progress instead, beside the time it belongs to.

• A rough position shows the suburb, not a street. When the phone was not sure of itself to within 100 metres, the line reads like "Near Tweed Heads (approximate)", because the nearest address to a rough position can be a street the driver was never in.

• On board no longer records a position. The car is about to move, so the phone is not asked at that swipe. Positions already saved for On board are kept and are no longer shown.

• The phone's best reading is kept, not its first. After a swipe the phone is watched until the stage is saved, and the most accurate position it gave in that time is the one recorded. Opening Trip progress also wakes the phone's GPS, once you have allowed location, so the first swipe does not start from cold.

• If every position says "approximate", check the phone. On Android: Settings, Apps, your browser, Permissions, Location, and turn on "Use precise location". Without it the phone only gives the browser a position good to about 2 km.

• Positions saved before this release have no address. They read "Position recorded" with how accurate the phone said it was.

3.80.0

6 October 2026

• The JollyDrivers mark now draws itself in when you open the app. The opening screen plays a short animation: the badge appears, the car and its smile are drawn, and the name settles in beneath. It lasts about four seconds.

• It plays once, not on every page. You see it the first time you open JollyDrivers in a tab. Refreshing, or opening another page in the same tab, shows the short opening screen as before.

• Where the animation cannot play, the opening screen is the one you know. A phone that will not start it (an iPhone in Low Power Mode, a slow connection) shows the still mark and name instead, and so does a device set to reduce motion.

3.79.0

6 October 2026

• "Tips owed to you" now shows what the amount is made of. Inside each operator's card, a driver sees their two newest tips still being held: the passenger of the trip, how it was paid, the day it was received and the amount. Tap one to open its trip.

• More than two, and there is a link to the rest. "See all tips" opens the Tips page, where every held tip is listed. Two or fewer and there is no link, because nothing is left out.

• The Tips page names the passenger too. Each held tip there now starts with the passenger of its trip, for drivers and for operators, on the Tips page and on Payouts.

• The name is the trip's passenger. A tip is recorded against a trip, not against the person who paid it, so when somebody else paid for the trip the passenger's name is still the one shown.

3.78.2

5 October 2026

• A driver now asks for their tips with a slide. On "Tips owed to you", each operator holding tips has a card of its own, with the operator's name, what they are holding and a track that reads "Slide to ask for" the amount. Slide the round button to the right to ask. It replaces the button that was tapped, so a stray touch asks for nothing. It is the same slide as on a trip's progress and on a pay link.

• Asking still moves no money. As before, the operator pays from their own account and records it, and the amount comes off the card when they do. Taking a request back is unchanged.

• Where the tips will be paid is easier to read. Your PayID is on a line of its own with a Change button beside it, which opens Getting Paid. A driver with no PayID sees that said plainly, with an Add button.

3.78.1

5 October 2026

• The admin's Bookings list can be filtered by payment too. It has the same Payment row as My Trips and the operator's Bookings: Unpaid, Partially paid and Fully paid, in any combination. It works beside the payment method picker, which is about how a booking was meant to be paid, where the new row is about how much has been received. The choice is remembered with the list's other filters. The admin's Deliveries list is unchanged.

3.78.0

5 October 2026

• Trip lists can be filtered by payment. A driver's My Trips and an operator's Bookings (and both Deliveries lists) have a new Payment row under Status with three choices: Unpaid, Partially paid and Fully paid. Tick any combination. Completed with Unpaid and Partially paid shows the finished trips that still have money owing.

• What each one means. Fully paid is a trip whose recorded payments cover the fare, or whose invoice is marked paid. Partially paid is a trip with some money recorded and some still owing, the ones whose card says "Part paid". Unpaid is everything else, including a trip with an invoice sent but not yet paid.

• Clear filters takes it off, along with the rest. A driver's choice is remembered on that phone or computer, like their other filters.

3.77.1

5 October 2026

• A driver's home page opens with its two top cards closed. "Your documents" and the tips card used to sit open above everything else and push the tiles down the page. Each is now a bar that opens when tapped, like the cards on a trip.

• The tips card is now called "Tips owed to you", and the total is on its bar. The amount shows under the title without opening the card. Opening it shows what each operator is holding, the button that asks them to pay it, and where it will be paid. On the Tips page the same card still starts open.

• "Your documents" keeps its status and its count on the bar. Whether you are cleared, and how many documents are done, read without opening it. What is missing and the links to My Documents and My Vehicles are inside.

3.77.0

5 October 2026

• A trip can now show where the driver was each time they swiped a stage. When a driver swipes On my way, I'm here, On board, Completed or No-show in the Trip Progress drawer, their phone is asked once where it is, and the answer is saved with the stage. The trip page then shows a pin for each stage, how far it was from the pickup or the drop-off, and how accurate the phone said it was. This gives a stage evidence of where it happened as well as when, which helps with a disputed no-show, a question about waiting time or a late arrival.

• It is off, and nothing changes for anybody until it is switched on. It sits behind a new switch, Trip Stage Location. It collects where drivers are, so drivers should be told before it is turned on.

• A stage always saves. The phone is given five seconds, during the Undo wait, so the stamp is not held up. If the driver says no, the phone cannot find itself in time or the browser has no location, the stage saves as usual and the trip says "No location" with the reason.

• The driver is told why before their browser asks. The first swipe shows a short explanation, and then the browser asks for permission. A driver who chooses Not now is not asked again at every swipe; a line at the foot of the drawer lets them turn it on later.

• Undo removes the position with the stamp, and nothing of either is kept.

• Only a swipe by the trip's own driver records a position. A stage timed with the clock on a card carries none, because the phone is not where the stage happened. An operator stamping for a driver from the office records none either. Changing the time of a stage afterwards removes its position.

• Only the driver and the operator see it. It is on the trip page in the portal and nowhere else: not on the passenger's page, not on a pay link and not on anything public. Nothing is tracked between swipes and no location is shared live. Deliveries are unchanged.

3.76.0

5 October 2026

• The platform admin can now hand an approved piece of writing-up to a builder that works by itself. When the admin approves a problem, a change request or a wish, there is a new box to tick: let the builder do this by itself. A builder running on GitHub's computers then picks it up within a few hours, with nobody watching, and writes it up as documents. It suits work such as "read the code and write up how this works" or "work out what would have to change, and where". It cannot change what JollyDrivers does: it writes documents in a folder of its own and can change no other file.

• It is off, and nothing changes for anybody until it is switched on. It sits behind a new switch, Unattended Builder, which stays off until the builder has been set up and tried. Nothing changes for drivers, operators or passengers either way.

• Nothing the builder writes is used until the admin has read it. It is given only the words the admin approved, with the code from their phone, and nothing anybody else wrote. What it writes waits on a branch. The admin opens it as a pull request, reads it, and merges it or does not. The builder cannot merge and cannot deploy, and it is handed at most three pieces of work a day.

3.75.0

5 October 2026

• An operator's AI assistant can now be allowed to look up how JollyDrivers works in a small part of its own code. The platform admin's assistant has been able to read JollyDrivers' code since 3.72.0. This release makes it possible to open a short list of files to operators as well: what each status is called, what a delivery or attendance job needs before it can be saved, the trip progress stages and why one is locked, the extra time allowed before an airport pickup, when a flight's status is final, and how "cleared for this operator?" is answered. So a question like "why is this stage locked?" can be answered from what JollyDrivers actually does.

• It is off, and nothing changes for anybody until it is switched on. It sits behind a new switch, Mcp Code Help Operators, which stays off until the platform admin has read the list and turns it on. A driver's or a rider's assistant cannot use it.

• What an operator's assistant reads is a cleaned copy, kept apart from everything else. The notes written in the code for the people who build JollyDrivers are taken out, each copy is checked for anything that looks like somebody's details before it is included, and the copies are kept in a separate archive that holds nothing else. Nothing about signing in, taking payment or the platform's other protections is on the list.

3.74.1

5 October 2026

• Pay on a payment link is now a slide, not a button. The wide Pay button was easy to press by accident, and pressing it makes the invoice. The customer now drags a round handle from left to right to pay, the same way a driver stamps a trip stage. A tap does nothing, and letting go part way sends the handle back. The handle moves a little while it waits, so it reads as something to slide.

• The card and wallet marks sit above the slide in the same frame. They are still only pictures of the ways to pay.

• A keyboard, a mouse, a screen reader and a switch can all still pay. Holding the handle for one second with a mouse, or with Space or Enter, pays. A screen reader or a switch finds an ordinary Pay button that is not on the screen.

3.74.0

5 October 2026

• Nothing reported to JollyDrivers is built until the platform admin approves it, and that now covers problems and change requests as well as wishes. Until now only a wish needed approval before work could start. Reports now arrive through people's AI assistants as well as from the Report a problem page (3.73.0), so every one of them waits for the same sign-off before it can be marked In progress or Resolved. Declining a report still needs no approval. If you reported something, your reports page tells you when it has been approved, as it already did for a wish.

• For the platform admin: you approve a written statement of what will be built, not the report. The report's screen has a box for it. Your assistant can draft it for you, you can change every word, and what you approve is kept with your name and the time. Whoever builds the work is told to work from that statement and nothing else, so nothing written in a report can widen the job. A draft written after you approved changes nothing: it is shown apart and marked as not approved.

• For the platform admin: approving now takes a code from your phone. Text me a code sends six digits to the mobile number verified on your account, and one code unlocks approving for 15 minutes on the tab you typed it into. A button alone could be pressed by anything able to use your browser, so approving now needs your phone as well. You need a verified mobile on your Account page before you can approve anything. No connected assistant can approve, whatever it is asked, as before.

3.73.0

5 October 2026

• You can report a problem through your own AI assistant. Until now a connected assistant could add an idea to the wishlist and nothing else; something broken had to be typed into the Report a problem page. Now you can tell your assistant what went wrong, or what you would like changed, and it writes it up, reads it back to you, and sends it to the JollyDrivers team only when you agree. It appears on your own reports page like any other, and it says it came through an assistant. Up to five can be sent this way in any 24 hours. The Report a problem page has no limit and takes screenshots.

• For the platform admin: what an assistant found in the code is kept apart from what the person said. When the admin's assistant has looked something up in JollyDrivers' own code (3.72.0), it can attach what it found to a report. That note is stored and shown separately from the person's own account, marked as an assistant's reading that nobody has checked, and only the admin sees it.

• JollyDrivers now counts how often the code help tools are used, by tool, area of the code and role, so it can be seen which parts most need explaining. It keeps counts and nothing else: not who asked, not what they searched for, and not which file they opened.

3.72.0

5 October 2026

• The platform admin's AI assistant can now look up how JollyDrivers works in JollyDrivers' own code. This is the first step of a help desk that answers from what the software actually does, not from a manual that may have fallen behind it (WISH-26). The code each release is built from now travels inside that release, so an answer can only describe the version that is running. The assistant can find where the wording on a screen comes from, read the rule behind it, and check which features are switched on. It reads code, and nothing about any person or booking.

• It is off, and it is for the platform admin only. It sits behind a new switch, Mcp Code Help, which stays off until it is turned on in Settings. No operator's or driver's assistant can use it, and whether they ever will is a separate decision that has not been made. The parts of the code that handle signing in and the other protections are left out altogether, so they cannot be read this way.

3.71.2

5 October 2026

• Part payments a driver collects now reach Xero too. As with 3.71.1 this applies only where driver accounts in Xero are switched on, which they are not for anyone yet. Each part the driver is holding is recorded against the booking's invoice as it is taken, and the invoice closes when the last part is in.

• A group paid in cash now asks who has the money. When one driver drove every trip in the group, Mark as paid asks whether the operator or the driver has the cash. Cash the driver is holding is recorded as one payment against the group's invoice, and the invoice is not voided. A group driven by more than one driver is not asked, as before.

• If Xero refuses, the trip says so and gives a way to try again. The operator sees a notice on the trip naming how much the driver collected that is not in Xero yet, with a button to record it.

• A driver's statement is not billed in Xero until what they collected is there. Posting the statement first tries to record anything missing. If something still cannot be recorded, no bill is raised and the statement says why; posting it again tries again.

• This now starts only once the driver's ledger is open. Money a driver collected before their ledger was opened is part of the opening balance and is left out of Xero, where 3.71.1 would have recorded it.

3.71.1

5 October 2026

• Money a driver collects now reaches the operator's Xero as income. This applies only where driver accounts in Xero are switched on, which they are not for anyone yet. When a fare is marked as paid in full and the driver has the money (cash in hand, or a tap on their own terminal), the booking's invoice is now marked paid in Xero from the Driver collections clearing account, and raised first if there was none. Before, cash voided the invoice and a card payment with no invoice recorded nothing in Xero, so the driver's bill was paid out of an account that nothing had been paid into.

• Not covered yet: a part payment the driver collected, and a group of trips on one invoice. Those are recorded in JollyDrivers as before and do not reach Xero this way.

3.71.0

4 October 2026

• Your profile now has a place for your full legal name. Until now JollyDrivers held one name for each person, the display name, and used it for everything, so a nickname could end up on a certificate. Drivers, operators and administrators are now asked for their full legal name on their profile, as it reads on their driver licence. Passengers are not asked.

• New drivers are asked as they join. The welcome page a driver sees after accepting an operator's invitation now asks for both names, with the legal name filled in from what the operator had so the driver only has to check it. The set-up cannot be finished without one.

• The administrator's Users page shows each person's legal name under their display name, and says "No legal name yet" for a driver, operator or administrator who has not given one.

• Your legal name goes on records, and customers never see it. A competency certificate, and the "who did this" line on safety plans, privacy requests, cases, compliance decisions, bank detail changes and PayID changes, now use your legal name once you have given one. Until then they carry on using your display name. Records already made do not change.

• Customers now see the name you chose. The booking confirmation and the passenger's own pages used to show the name your operator typed for you in their fleet. They now show the display name from your profile, which is what the profile page has always said. A driver with no JollyDrivers account is still shown under the operator's name for them.

• Operators are told when a driver's bill name differs from their legal name. A subcontractor's bills and Xero contact stay in the name the operator entered, because the ABN may belong to a business. The driver's page now says so when that name is not the legal name the driver gave, so it can be corrected if it is simply a mistake.

3.70.3

4 October 2026

• The administrator's profile no longer asks which extras they offer. Baby seats, surfboards and pets are for the people who take bookings. An administrator account that is not also a driver or an operator now shows none of that card, the NSW levy choice or the calendar invites choice. Nothing changes for drivers and operators.

3.70.2

4 October 2026

• Driver bills in Xero were waiting for a permission Xero no longer gives. Posting a driver's statement to Xero as a bill checked the connection for an older, broader permission that JollyDrivers cannot be granted, so it would have answered "Reconnect Xero" every time, and reconnecting would not have helped. It now checks for the two permissions a bill really needs, the ones invoicing and payments already use, so a normal connection passes with no reconnect. This feature is still switched off, so nothing you use today changes.

3.70.1

4 October 2026

• Fixed: connecting or reconnecting Xero failed with "Invalid scope". Since 17 September, JollyDrivers had been asking Xero for one permission that Xero does not offer its app, and Xero answers that by refusing the whole request. Nobody had reconnected in that time, so it went unseen until today. JollyDrivers now asks only for permissions Xero accepts, and Connect to Xero works again.

• A connection that was already in place was never affected: invoices, payments and everything else carried on working throughout.

• Once reconnected, tip pay-outs are recorded in Xero for you, as described under 3.69.0.

3.70.0

4 October 2026

• New for drivers: Qualifications. A new page on your menu, beside My Documents, for what you hold beyond the legal minimum: first aid, CPR, a Working with Children Check, an NDIS Worker Screening Check, RSA, a security licence, wheelchair and passenger-assist training, and more. Add each one with its number and dates, and a photo or PDF as proof if you have it. Proof is optional.

• Anything not on the list goes in too. Choose "Other qualification, education or experience" and give it a title of your own: a course, a degree, a trade, years in a job. Add as many as you like.

• One entry per state where it matters. A Working with Children Check, RSA, a security licence and a dangerous goods licence ask which state issued them, so a Queensland Blue Card and a NSW WWCC sit side by side.

• Each one shows as current, expiring soon or expired, and Renew keeps the old one as its earlier version.

• The languages you speak. Pick them from a list on the same page.

• Qualifications never decide whether you can be given a job. They are information for the operators you drive for, and nothing else.

• Who sees them. Only operators you already share your documents with, and JollyDrivers support. Sharing your documents with an operator now covers your qualifications and languages as well, and the sharing box says so. Removing one that an operator has seen withdraws it, as with a document.

• New for operators: find drivers by what they hold. Fleet has a Qualifications page: pick a qualification, a state, a language, or search, and see which drivers match, with "current only" on by default. You see drivers who share their documents with you, and the page says how many don't.

• Operators can approve a qualification or mark it not accepted. The driver sees the decision. An approval belongs to that version, so it stops counting when the qualification expires and a renewal shows as new.

• Through your AI assistant. A driver can ask what qualifications are on their profile and have the assistant prepare a new one, which gives a link to check and save it in JollyDrivers. An operator can ask "who has a current NDIS check?" or "who speaks Mandarin?". The assistant cannot save, share, remove or approve anything.

• For the admin: the qualification catalogue. A new page under System admin lists the standard qualifications, where you add, reword or retire one, and shows the titles drivers have typed themselves so a common one can be promoted into the list.

• Expiry reminders, when they are switched on, cover qualifications too, in their own words.

• National Police Check is not in the qualification list: it is already one of the driver documents.

• All of this is behind a new switch, Driver qualifications, which is off until it is turned on in Settings.

3.69.1

4 October 2026

• The pay page: the card logos are part of the Pay button. Visa, Mastercard, Amex, Apple Pay and Google Pay used to sit under the button and looked like buttons of their own; customers tapped them and nothing happened. They now sit inside Pay, so a tap on any of them goes to the payment page.

• "Add a tip for your driver" has a slow amber shimmer through its words, so it is easier to notice. It is otherwise unchanged, and it stays still for anyone who has asked their phone to reduce motion.

3.69.0

4 October 2026

• New: JollyDrivers records a tip pay-out in Xero for you. When you press Paid out and choose Paid to them, JollyDrivers makes the Spend Money entry in your Xero itself: from your bank account to the driver, out of your Tips held for drivers account, tagged with the driver if you track tips by driver. You still make the transfer in your banking app. When the transfer shows on your bank feed, Xero offers this entry as its match.

• You need to reconnect Xero once. Recording Spend Money needs one more Xero permission than JollyDrivers held. Under Settings, Accounting, connect to Xero again over the top; there is nothing to disconnect first. Until you do, paying out works as it always has and the window still gives you the entry to make by hand.

• Only tips that went into Xero are taken out of it. A tip that was never in Xero is paid out in JollyDrivers alone, as before.

• If Xero refuses or doesn't answer, you're told. The pay-out is recorded in JollyDrivers either way. A refusal says why, and you make the entry yourself. If Xero doesn't answer, JollyDrivers says to look in Xero before making it, and does not try again, so the entry can never be made twice.

• The trip's timeline shows when a pay-out was recorded in Xero.

• JollyDrivers still moves no money. Paying a driver from inside JollyDrivers is not part of this release.

3.68.0

4 October 2026

• New for operators: a pay-out routine for tips. On your Tips page, choose to pay tips out every day or every week on a day you pick. On each due day JollyDrivers prompts you for every driver you're holding tips for, in the same places a driver's own request shows: your home page, Tips and Driver payouts. The default is no routine, where drivers ask when they want to be paid.

• Nothing is paid for you. You still make the transfer and press Paid out, and that clears the prompt.

• A routine starts from its next due day. Choosing "every Friday" on a Saturday prompts you the Friday after.

• If nobody opens JollyDrivers on the due day, it isn't missed. The prompt is there the next time you or the driver look.

• Drivers are told. Their "Owed to you" card says how often you pay out. They can still ask sooner, and once a routine pay-out is due the card says so in place of the button.

• A driver who has already asked isn't prompted for twice.

• This release adds three columns to the database.

3.67.0

4 October 2026

• New for drivers: "Owed to you" on your home page. When an operator is holding tips for you, your home page and your Tips page show the total, split by operator. If nothing is held, the card isn't there.

• New: ask to be paid. One button asks that operator to pay out everything they're holding for you. You can take the request back. Asking doesn't move any money: your operator makes the transfer from their own account and records it, and the amount comes off your card when they do.

• It shows the PayID you'll be paid on, or tells you to add one under Getting Paid if you haven't.

• For operators: you're told who has asked. Your home page lists any driver who has asked to be paid their tips. On Tips and Driver payouts, each driver's held tips now show the request and the driver's PayID, so you can make the transfer and press Paid out.

• Recording the tips as paid out answers the request. Once nothing is left held for that driver, their request closes by itself.

• An owner-driver can ask for their tips too. This uses the Tips switch; there is no new one.

• Not in this release: a weekly or daily routine, and paying from inside JollyDrivers. What payment automation is available to a business this size has been written up for a decision.

3.66.0

4 October 2026

• Booking a job through your AI assistant sends the customer nothing, and the assistant now says so. It had been telling drivers that the customer's confirmation would go out when the job was created. That stopped being true when Jolly Frog's system was switched off in September: no confirmation has gone out on its own since. The summary you approve and the reply after the job is booked now both say that nothing has been sent.

• New: ask your assistant to send the confirmation. When a customer does want one, say so. The assistant shows you who it will go to, who it is from and the subject, and emails it once you agree. It goes to the customer's own addresses on the booking and nowhere else. This uses the switch that lets your assistant book jobs.

• A confirmation can be sent this way once the booking is confirmed. For a finished trip there is nothing to email unless it is paid, when the receipt goes.

• Nothing changes on the trip page, in the booking chat, or for an operator's assistant.

3.65.2

4 October 2026

• The system log no longer keeps customers' addresses, phone numbers or chat wording when something fails. JollyDrivers keeps a technical log on the server for tracing faults. When a route lookup, an address search, the booking chat or a text message failed, the line written there could include the address that was typed, part of what the chat had said, or a full phone number. It now records what failed and how, without those details.

• Phone numbers in that log are shown with the middle hidden, the way sign-in codes have always been logged. Each line still carries the message's reference number, so a text can be traced.

• Erasing a rider no longer writes their name to the log. The record of an erase keeps the account number only. The admin is still shown the name on screen when the erase finishes.

• An error reply from Google, Anthropic, AsiOne or SMSGlobal is kept to its first 500 characters.

• Nothing changes on any page. These details were in the server's log only, which customers cannot see.

3.65.1

4 October 2026

• An operator can now stamp every stage of a trip. On the Trip Progress drawer an operator gets the same swipes as the driver: On my way, I'm here, On board, Completed and No-show, under the same rules and with the same Undo. Until now an operator could only complete a trip that had stopped at En route.

• The stamp is recorded under the operator's own name, so the timeline shows who marked it.

• Nothing changes for drivers, and an operator's AI assistant still cannot stamp stages.

3.65.0

4 October 2026

• Trip progress has a drawer of its own. On a trip, the status ("Confirmed", "At pickup" and so on) is now a button. Tap it and the stages open as cards, in order: En route, At pickup, On board, Completed and No-show, with Cancel set apart at the bottom. On a phone the button stays at the bottom right of the screen while you scroll.

• A stage is stamped by swiping, not tapping. Drag the button on a card from left to right and let go at the end. Let go early and it slides back and nothing happens. With a keyboard, hold Space or Enter for a second; with a mouse you can also press and hold.

• Each card shows where it stands. A stage already done shows its time, marked "estimated" if JollyDrivers filled it in. The next one is highlighted. One you can't use yet is dimmed and says why.

• Undo for five seconds. After a swipe a message offers Undo. Nothing is saved until those five seconds are up, so undoing leaves no trace on the trip.

• The time is the moment you swiped. Your phone records it as the swipe finishes, so a stamp that takes a while to get through on poor signal still shows the right time. A time in the future is never recorded.

• A no-show can only be marked after the pickup time, and in the drawer only once At pickup is stamped.

• On board or Completed before the pickup time asks you first. It may be right, so you can go ahead. On my way and I'm here are never questioned.

• Skipping ahead asks before estimating. Swipe a later stage and JollyDrivers shows the times it would fill in for the ones you missed, and does it in one step if you agree.

• The clock on each card is still there, to stamp a stage at an earlier time or to correct one already stamped.

• Cancelling needs a reason and a red swipe. The swipe won't move until a reason is chosen.

• The Actions drawer keeps everything else. A delivery's stages stay there too, because they need proof of delivery.

• If you use an AI assistant to stamp stages, it follows the same two new rules: no no-show before the pickup time, and it checks with you about an early On board or Completed.

3.64.3

4 October 2026

• The test sign-in used for development can no longer exist on the live site, whatever the server is set to. Developers have a page that signs them in as a practice account without a password or a text message. It has never been reachable on the live site, and that rested on one server setting being right. It now takes that setting and a second switch, which is off in everything that is deployed and cannot be turned on from System Admin, Settings.

• A practice driver invitation only skips the text-message code on a developer's machine. Everywhere else, including the live site, a practice invitation now signs nobody in.

• A deploy is refused if it would carry that switch turned on.

• Nothing changes for anyone using JollyDrivers.

3.64.2

4 October 2026

• The gateway callbacks panel on the SMS inbox can no longer show the webhook password. The panel under System Admin, SMS inbox lists what SMSGlobal sent, with the password it presents blanked out. The blanking only recognised the password when its label was written exactly one way, while the check that lets a call in also accepted the label with a space around it. A call written that way would have been let in and then listed with the password readable. Both now use the same rule, so anything accepted as the password is blanked.

• Calls already listed are blanked again each time the panel is opened, so a call saved by an earlier version cannot show it either.

• Every call saved so far was checked, here and on the live site, and none of them holds the password.

3.64.1

3 October 2026

• Coming back later to an invoice Xero never answered no longer risks a second one. Since 3.63.4 a retry in the first few minutes has been safe. Now, when you try again later than that, JollyDrivers first asks Xero whether the invoice is already there. If it is, nothing more is raised and you are told its number, so you can record it on the trip with Record external invoice. If it isn't, the invoice is raised as normal.

• If Xero can't be asked, nothing is raised. You are told to try again shortly, because not knowing is not the same as it not being there.

• The message after "Xero did not answer" is shorter. It no longer asks you to check Xero yourself before trying again.

• Credit notes and payments are unchanged: for those, the message still asks you to check Xero first if you come back later.

3.64.0

3 October 2026

• Editing a booking on a phone is now a full page. It used to open as a small window in the middle of the screen, too narrow for its own fields: the pickup date was cut short and the pickup time wrapped under its own label. On a phone it now takes the whole screen and slides in from the left, with its title at the top and Cancel and Save Changes at the bottom while the form scrolls between them. The date and the time each get a line of their own. On a computer it is the window it was, with a close button added at the top.

• Dates are written day first everywhere: dd/mm/yyyy. Date boxes followed the settings of the computer JollyDrivers runs on, and the live one writes the month first, so 3 October showed as 10/3/2026. JollyDrivers now sets this itself, so a date reads the same on every screen.

• A date you type is read day first too. On the live site, 3/10/2026 typed into a date box was taken as 10 March. It is now taken as 3 October, and you can type it the short way: 3/10/2026, 3/10/26, 3-10-2026 or 3 Oct 2026. Something that isn't a date is refused with a message under the box. It is never quietly read as a different day.

• Calendars start the week on Monday.

• A time box that is short of room puts the time under its label, where it used to split the time across two lines. On the quick quote on a phone, the date now shows in full.

• Messages about when a commission rate or the booking fee started give the date day first, by the Queensland day.

3.63.4

3 October 2026

• Pressing twice can no longer invoice a trip twice. If an invoice was being raised from two places at the same moment (two tabs, or the trip page and the customer's pay link), Xero could end up with two invoices for one trip. The second is now refused while the first is under way, and says so.

• The same goes for credit notes and payments. A second credit note or a second part payment started while the first is still being recorded in Xero is refused.

• Trying again straight after "Xero did not answer" is now safe. Xero sometimes saves an invoice, credit note or payment and the answer gets lost on the way back. Trying again used to make a second one. For the next few minutes it now repeats the same request, so Xero answers with the one it already has. Xero only remembers a request for six minutes, so if you come back later than that, check Xero first. The message says so.

• Credit notes add up. Credits already issued against an invoice now count, so two credits can't come to more than the fare. The message says how much is left to credit.

• A customer who taps Pay twice is told to refresh, not that paying online isn't available. Their invoice is on its way. And if Xero didn't answer, they are asked to try again in a moment, not to pay their driver.

3.63.3

3 October 2026

• Connecting a driver's Stripe account is now safe from a forged link. The check that ties the connection to the driver who started it could be faked by anyone who knew a driver's number, so a link could have attached somebody else's Stripe account. It is now sealed and expires. Stripe payments to drivers are not switched on, so nobody was affected.

• Privacy requests show the right dates. Received and due dates were shown by the UTC calendar, so a due date read a day early and a request received before 10am showed the day before. Extending a request also moved the new date back a day each time it was saved. Both are fixed.

• The case register lists incidents by the day they happened here. An incident in the morning was listed under the day before.

• A credit note can no longer reach into a tip. Once a customer had added a tip on their pay link, a credit up to the invoice total would also have reversed GST the invoice never charged. A credit is now limited to the fare, and the message says the rest is the driver's tip.

• An invoice's due date is never earlier than its own date, even when it is raised at midnight.

• When your assistant books a trip and can't check your calendar, it says so. It used to say there was no clash.

• An attendance job no longer says "Operator notified". Nothing is sent to the operator, so it now reads "Booked" until it is under way.

• An empty driver ledger says the date it started counting from, not today's date.

• For JollyDrivers' admin: a settings warning about the disbursement notice, a switch that no longer exists, has gone. It could never be cleared.

3.63.2

3 October 2026

• Reclassifying a completed trip as a cancellation now says what happened to its invoice. It used to say "Trip reclassified as cancelled." whatever had happened in Xero, so a void that Xero refused could only be found on the trip's timeline. The message now says the invoice was voided in Xero (a draft: deleted), or that a credit note was issued and for how much, or that the invoice stays as it is because the fee is what it already asks for. If Xero refuses or can't be reached, it says so and gives Xero's reason.

• A credit note on an invoice that was already paid says what is left to do. The customer is owed the difference, and the message says how much and that the refund is recorded in Xero.

• If the invoice was a group's one invoice, the message says so. Reclassifying one trip of a group with no fee voids the whole invoice, the other trips' charges with it. That has not changed, but you are now told how many other trips it covered and that they need a new invoice.

• A part payment by card now goes into Xero. It used to be recorded in JollyDrivers only, so once the rest was paid Xero still showed the first part owing and the invoice went back to awaiting payment. The payment is now recorded against the invoice in Xero, which stays open for the rest, where the invoice is one JollyDrivers manages there.

• Mark as paid on a trip knows what is still owed. Where part of the fare had already been recorded, the window filled in the whole fare again, and treated the real balance as another part payment. It now fills in the balance, says how much has already been recorded, and takes the balance as settling the trip.

• Mark as paid says what a part payment does to the invoice. By card, the payment is recorded against it in Xero and it stays open for the rest. In cash, it is left open at its full amount. The window used to say the invoice would be marked paid, or voided, whatever amount was typed.

• On a booking group, "Clear failed" now means what it says. When a trip's invoice can't be voided, the trip keeps a "Clear failed" label with Xero's reason on the line under it and a Retry button. It used to show nothing once the message had gone. The "Clearing…" label has been removed: Clear is done in Xero at once, so nothing is ever in progress. (Clear appears only where its switch is on.)

• For JollyDrivers' admin: the part-payment switch has gone from System settings, because there is nothing left for it to hold back. The Clear button's switch has moved from the locked group to "Unfinished or unproven", so it can be turned on there with a typed confirmation, and its description now says what Clear does.

3.63.1

3 October 2026

• After a booking is submitted, JollyDrivers says what became of it. The booking chat used to answer everyone with "Booking request sent! Your operator will be in touch shortly." No email tells an operator about a new booking. It appears on their bookings list, and it is either confirmed straight away or waits for someone there to accept it. The message now says which.

• A driver is told when the booking is already confirmed, which is nearly every booking a driver takes: "Booking confirmed", and that nothing has been sent to the customer, so the confirmation is the driver's to send from the trip page. When it isn't confirmed, the message says someone at the operator needs to accept it, and gives the reason if JollyDrivers held it back (no price agreed yet, for one).

• A customer booking their own ride is told it is waiting for the operator to confirm it. A signed-in rider is also pointed to My Bookings.

• The booking's reference is shown, and stays on screen. A longer message with the reference was written after every submit and never displayed, because the page went straight back to its menu. It is now at the top of that menu, with a button that opens the booking, until the next booking is started. A visitor who isn't signed in is shown their reference for the first time.

• A trip entered after it was driven says "Trip recorded as completed." It used to add "and sent to your operator" and "No further action needed".

• A delivery says "Delivery submitted." Nothing accepts a delivery, so nobody is said to be getting in touch about one.

• A submitted delivery no longer reads "Awaiting operator". On lists and on its trip page it reads "Submitted". There is no button an operator presses to accept a delivery, so it was waiting on nobody. It moves on when its progress is recorded.

• Submitting a saved draft says the same things. The Submit window used to say "Booking submitted to" the operator, with an exclamation mark, whether or not the booking had just been confirmed.

• On a trip, "Send delivery request" is now "Submit delivery". And asking the operator again about a booking they declined now says afterwards whether it is waiting or was confirmed straight away. It used to say "waiting on their decision" either way, and the box before it promised the same.

• For operators: the note under "Confirm my passenger bookings automatically" is rewritten. It spoke of "your booking system" replying, and of bookings being accepted twice, which was about Jolly Frog's old system. It now says JollyDrivers confirms the trip as soon as it is submitted, instead of leaving it for you to accept.

3.63.0

3 October 2026

• Nothing changes for drivers, riders or operators in this release. It adds a page for JollyDrivers' own admin, and the page is switched off until they turn it on.

• For JollyDrivers' admin: a System health page. It is under System Admin, behind a new switch on Platform Settings called SystemHealth. It shows on one screen how JollyDrivers itself is running. Each part is marked Fine, Needs a look or Wrong, with a sentence saying why.

• A check that runs outside JollyDrivers. A page inside JollyDrivers can't tell you JollyDrivers is down. So a small script asks the live site six questions every half hour from somewhere else, and raises the alarm itself when they aren't answered. The page shows when it last got through, and any stretch when it didn't.

• Errors, grouped by cause. Every error JollyDrivers logs is counted under what went wrong. The same fault a hundred times is one line with a count, where it happened and what was running at the time. Phone numbers, email addresses and keys are taken out before anything is kept.

• How long things take. For each page, each address a program calls, and each tool an AI assistant can use: how many requests there were, the typical time, and how slow the slowest one in twenty was.

• A heartbeat for every background job. There are 24. For each one the page says whether it is still running on time, when it last did its work and how long that took. A job that is switched off says so, and isn't mistaken for one that has stopped.

• Dates things run out. The security certificates on JollyDrivers' own addresses are read every day. A Xero connection's date is worked out from when it was last used. Domain names and keys are added by hand, because nothing tells JollyDrivers when those expire.

• It says what it can't see. Where something isn't set up, or there isn't enough to judge yet, the page says exactly that. It doesn't show it as fine.

3.62.9

3 October 2026

• On a phone, a booking group's trips are now a list you can read and tap. Each trip has its date and its price on one line, its route underneath, then its status and two buttons that say what they do: Open trip and Remove from group. It was a table, which a phone turned into five lines of labels for every trip, with two small picture-only buttons whose names showed only when a mouse was held over them.

• A button on the group page that can't be pressed now says why, in words under it. Request invoice (the button shown where pay links are off) and the group's Mark as paid are greyed out at times, for example while a trip still has an invoice of its own. The reason used to show only when a mouse was held over the button, so on a phone there was a dead button and no explanation.

• The Add Booking window is easier to pick from on a phone. Each booking shows its date and its price together on the first line, its route under that, then who it is for and its status, and tapping anywhere on a booking ticks it. Before, the date broke over two lines, the price was the last thing in a long caption, and only the small box itself could be tapped.

• The group page's buttons are at least 44 pixels tall, the size a thumb needs: Booking Groups, Send confirmation, Request invoice, Add Booking, Mark as paid, the two on each trip, and Cancel and Add in the Add Booking window. View invoice was a line of text 20 pixels tall and is now a button of the same height as the rest.

• On a wide screen the trips still read one to a line, with Open trip and Remove from group in words where the two icons were. The trips, their order, their prices and what each button does are unchanged.

3.62.8

3 October 2026

• JollyDrivers no longer says "the operator has been notified". Nothing has been sent to an operator about an edit, a payment or a cancellation since Jolly Frog's old booking system was switched off in September. Dozens of messages still said it was, or would be, or had failed. Each now says what really happens.

• Editing a trip says only that it saved. Setting the pickup from the flight, shifting it, changing the airport buffer, refreshing a customer's details and linking a passenger used to warn "The operator will be notified" beforehand and say "The operator has been notified" afterwards. Refreshing a customer's details ended "Nothing was sent — the operator doesn't hold this booking". None of that is said now: "Pickup updated.", "Name updated.". The warning "operator notification failed" has gone too, because there is no notification left to fail.

• Mark as paid says what was done in Xero. Cash on an invoice says the invoice was voided in Xero (a draft: deleted), and card or bank transfer says the payment was recorded against it there, with the invoice's number. It used to say the operator had been asked to do it. If Xero refuses or can't be reached, the message says so and gives Xero's reason, where it used to say the operator notification failed.

• When JollyDrivers doesn't manage the invoice, you are told what to do. That is an invoice it didn't raise, in books that aren't connected here. The group page used to say "No billing email for the operator, so the invoice was left as-is", and the trip page said nothing about the invoice at all. Both now say it was left as it is, and to void it or record the payment where it was raised.

• A part payment says where it is recorded. "The operator hasn't been told about this payment yet" has gone. The message says it is recorded in JollyDrivers only, and that the invoice stays open at its full amount.

• Clearing a trip's invoice on a group says it is done. Clear voids the invoice in Xero straight away. The page used to say it had asked the operator and was waiting for them. The window that opens first, and the one for voiding an invoice from a trip, now say JollyDrivers does it in Xero. Reclassifying a completed trip as a cancellation says what happens to its invoice there. (Clear appears only where its switch is on.)

• "Send request" is now "Raise invoice". That is the button in the Request invoice window, on a trip and on a group. Pressing it raises the invoice in Xero at once. If it can't be raised the message reads "The invoice wasn't raised" and gives the reason, where it read "Could not send".

• An old page has been removed. /book/…/confirmed told a customer "The operator has been notified and will be in touch shortly". Nothing in JollyDrivers has linked to it for a long time, and it wasn't true: no email tells an operator about a new booking, which appears on their bookings list.

• For JollyDrivers' admin: "Resend notification" on a failed booking is now "Resubmit booking", which is what it does. Behind the scenes, six leftover pieces of the old operator protocol that sent nothing were removed, along with every call to them.

3.62.7

3 October 2026

• On a phone, the group invoice window now shows each trip's price, and the total. This is the window that opens from Consolidate into one invoice on a booking group's page, and from the Request invoice button where that is shown. It listed the group's trips in a table that was wider than a phone's screen. The prices and the total sat past the right-hand edge, and could only be seen by dragging the table sideways. Each trip now has its date and its price on one line with its route underneath, and the total is below them.

• On a computer the list reads much as it did: the date, the route and the price across one line for each trip, with the total underneath. The trips, their order, their prices and the invoice that is raised are all unchanged.

3.62.6

2 October 2026

• A blank Notification Email no longer blocks anything. With that field on Settings left empty, four things were refused: sending a customer their upcoming trips, sending a booking group's confirmation, changing an invoice's due date, and Request invoice on a group (the button shown where pay links are off). Nothing was ever sent to that address for any of them. JollyDrivers emails the customer itself, and makes the change in Xero itself. All four now work with the field blank.

• Four windows say what really happens. Group confirmation and upcoming trips say JollyDrivers emails the document, sent as the operator. They used to say the operator would deliver it and might adjust the subject. Change due date says JollyDrivers changes the date in Xero straight away, and that its note is kept on the trip's record. Request invoice says JollyDrivers raises the invoice in the operator's Xero, and that a draft is approved from the invoice panel or when the customer pays from their pay link.

• The Notes box has gone from both Request invoice windows. Anything typed in it was thrown away. It was never saved, and never sent to anyone.

• Saving an edit to a booking says only that it was updated. It used to add "Nothing was sent — the operator doesn't hold this booking" after every ordinary edit, as if something had gone wrong. A booking that has an invoice is still warned that the invoice may need re-issuing if the price or scope changes; that warning no longer opens by saying the operator will be notified.

• For JollyDrivers' admin: the "Also notify the operator" switch on a finished or deleted booking has gone. It sent nothing whether it was on or off. Timeline entries from earlier edits read as they did; new ones show only your reason.

3.62.5

2 October 2026

• JollyDrivers' emails to your office now all go to one address: your Notification Email. That is the field beside Trading Name on Settings. New complaints and incident reports, and the daily compliance email, used to go to the address your customers' replies go to. They now go to your Notification Email, where the rest already went: reminders that your own compliance documents are running out, safety-plan review reminders, the security notice when the bank details your customers pay into are changed, the link to a copy of a driver's documents and, where it is switched on, the note that a driver can't make a trip.

• If your Notification Email is blank, they go to your customer replies address instead. Before, five of them had nowhere to go when it was blank. If both are blank nothing is sent to your office, as before.

• Settings now says what the Notification Email is for. A line under the field, on Settings and on the form a new operator fills in, says what JollyDrivers sends there.

• For JollyDrivers' admin: System settings now gives the new order where it describes the daily compliance email.

3.62.4

2 October 2026

• Nothing you or your customers see changes in this release. Behind the scenes, it makes a copy of JollyDrivers that is used for testing safer to set up, so that it can't contact real people by mistake.

• A new test copy now starts out unable to email or text anyone, or to change anything in Xero. Until now it had to be told, and until it was it counted as the real JollyDrivers. The developer adds their own phone number and email address so they can sign in and read its mail.

• Its starter settings no longer allow email to every address at Jolly Frog. That allowance was left over from Jolly Frog's old booking system, which was switched off on 16 September. A test copy holding real bookings could have emailed the operator's own inbox.

• The line a test copy writes when it refuses to email about a real booking now says so in today's words. It still described the old system.

3.62.3

2 October 2026

• Housekeeping, with nothing to notice in day-to-day use. Nothing changes on the live site.

• For JollyDrivers' admin: the safeguard that stops a test copy of JollyDrivers emailing anyone outside its own short list now checks every address on an email: To, Cc and Bcc. It used to check the first address only, so an email to a listed address with somebody else copied in would have gone to them as well. An email is now held back whole unless everyone on it is listed. The booking confirmation is the one email built that way, and the test copy's own records show it has sent none.

3.62.2

2 October 2026

• When something goes wrong that JollyDrivers didn't expect, you now see a page that says so. Until now the browser was left with a blank white page, which is what Check connection showed on 2 October. The page says the problem is on our side, asks you to check whether what you were doing went through before you try it again, and gives the time to quote if you tell us about it.

• Check connection tells you when Xero can't be reached. On Settings, under Accounting, the button now comes back with "Xero could not be reached just now" when that is the trouble, and says there is no need to reconnect. Your connection is only marked as needing to be set up again when Xero itself refuses it, never because Xero couldn't be reached or was having trouble of its own.

• The same goes for everything else JollyDrivers does in Xero. Raising, approving, voiding or emailing an invoice, recording a payment, changing a due date or the wording on an invoice, tips and driver statements: if Xero can't be reached at that moment, you are told so and asked to try again in a minute, and nothing is sent. Before, these could fail with an error, and voiding or approving an invoice from a trip could stop the page working until it was reloaded.

• Signing in with Google keeps working when the hosting server can't find Google. 3.62.1 gave everything else a second way to find an outside service's address. Signing in was the one thing it didn't cover, and now it does.

• Pressing Check connection or Disconnect after you have been signed out takes you to the sign-in page. Before, the press did nothing and said nothing. Sign in, with Google or with a code sent to your phone, and you are taken back to Accounting with a note to press the button again.

3.62.1

2 October 2026

• JollyDrivers keeps working when its hosting server can't find an outside service. On the afternoon of 2 October the server's own address lookup failed on and off. While it did, invoices couldn't be raised in Xero, customers couldn't pay from their pay link, and route pricing and flight lookups failed, with messages like "Xero could not be reached". Nothing was wrong with Xero, or with your connection to it.

• What changed. When that lookup fails, JollyDrivers now finds the address another way: it uses the address the service was reached on in the last ten minutes, or asks a public lookup service directly. This covers everything JollyDrivers calls: Xero, the booking chat, texts, maps, routes, flights and card payments.

• What stays the same. The security check on every connection is unchanged, so a wrong address is refused rather than trusted. If no address can be found at all you see the same message as before, and trying again a little later is still the answer.

3.62.0

2 October 2026

• You can now say which Xero items your passenger fares carry, or leave them off. Settings, under Accounting, has a new card, "Xero items on passenger fares", with a code for trips of 1 to 3 passengers, 4 or 5, and 6 or more. It's optional: leave a field blank and that fare line goes to Xero without an item. An item you name has to exist in your Xero already.

• Why it changed. JollyDrivers used to put the item codes PAX-X, PAX-XL and PAX-MAX on every operator's fare lines. Those are items in Jolly Frog's Xero. Any other operator's first invoice would have been refused by Xero, because an item has to exist in the Xero it is sent to.

• Nothing changes for Jolly Frog. Its three codes were carried onto its own settings, so its invoices come out exactly as before. They show filled in on the new card.

3.61.1

2 October 2026

• Housekeeping, with nothing to notice in day-to-day use. The comparison that was used to move Jolly Frog's invoicing into JollyDrivers has been removed, along with its records. It checked JollyDrivers' draft invoices against the ones Jolly Frog's old booking system raised, and that system was switched off on 16 September.

• For JollyDrivers' admin: the XeroShadowDiff switch is gone from System settings. Three database tables and two columns that nothing reads any more were dropped, so the site was on its maintenance page for a few minutes while this release went in.

3.61.0

2 October 2026

• Connecting Xero is now all an operator has to do for JollyDrivers to raise their invoices. Settings, under Accounting, used to have a second step called "Raise invoices from JollyDrivers". It stayed locked until ten invoices had been compared with the operator's own booking system, and no operator has one of those any more, so nobody new could ever have finished it. That step is gone. Connect Xero, fill in your account codes, and JollyDrivers raises your invoices in your Xero.

• Disconnect is the way back. An operator who disconnects keeps their own books again: JollyDrivers raises nothing in Xero, and you record invoices and payments on each booking yourself. The Xero card now says this. If a connection stops working, the card asks you to reconnect, and it offers Disconnect as well.

• Nothing changes for an operator who is already connected. Invoices are raised, paid and voided exactly as before.

• For JollyDrivers' admin: the buttons "Switch back to my system raising invoices" and "My booking system is back" went with that step. Where JollyDrivers can't change an invoice, it now says the invoice wasn't raised by JollyDrivers and isn't in a connected Xero, where it used to say the operator's system had raised it.

3.60.1

2 October 2026

• For JollyDrivers' admin: a switch turned on in System settings now shows on the next trip you open, with no browser refresh. The trip page used to read its switches once for each browser tab, so a tab that had already shown a trip kept the old setting, even for a trip opened afterwards. That is why the new Email option on the Invoice card stayed missing until the tab was refreshed. A trip page that is already on screen may still need a refresh, as the Settings page says.

3.60.0

1 October 2026

• Xero can now email an invoice to the customer for you, from the trip page. An approved or paid invoice on a trip's Invoice card has a new Email option. It asks your Xero to send the invoice from Xero's own mail system, with your invoice email wording from Xero, so it doesn't depend on JollyDrivers' own email reaching the inbox. It's for the customers who need their invoice by email.

• It shows where the invoice will go before it goes. Xero sends to the email address on that customer's contact in Xero, which isn't always the bill-to address on the booking, so the address is shown first and it says so if the two differ. If the contact has no email address, it tells you to add one in Xero. A draft invoice is approved first, with the button beside it.

• The trip records it. The timeline shows the invoice was emailed by Xero and to which address (partly hidden). For an invoice covering several trips, each trip shows it.

• For JollyDrivers' admin: this is switched off until you turn on XeroInvoiceEmail in System settings.

3.59.4

1 October 2026

• The route map in a confirmation email now comes from JollyDrivers' own address. The email used to load it straight from Google, through a web address thousands of characters long, which is the kind of thing a spam filter distrusts. It now holds a short jollydrivers.com.au address for the picture, and the map itself looks the same. One thing to know: if a trip's stops are changed afterwards, the map in the earlier email shows the trip as it is now.

• The booking reference is no longer hidden text in a confirmation email. On a phone it used to be hidden at the top and repeated out of sight at the bottom; it now sits under the business name on a phone and beside it on a wider screen, written once. Hidden text is another thing spam filters look for.

3.59.3

1 October 2026

• For JollyDrivers' admin: the "Sending mailboxes" card on the Operators page no longer says replies go to the operator's own address once "Customer replies" is switched on for them. It now says replies come back to the JollyDrivers address, and names the operator's own address as where the verification email goes.

3.59.2

1 October 2026

• Confirmation emails no longer carry an "Add to Google Calendar" link. A diary entry you made yourself doesn't move when the booking does, so it could leave the wrong time in a customer's calendar. It's gone from the email, the PDF and the plain-text copy, for single trips and itineraries alike. The calendar invitations JollyDrivers emails to drivers and operators, which it does keep up to date, are unchanged.

• Three changes to help confirmation emails reach the inbox instead of Gmail's spam folder. Each stop's address is now written once, in full, on every screen size: the email used to hold a second, hidden copy of every address for phones, and hidden text is something spam filters look for. JollyDrivers' mail server now introduces itself by its own domain name rather than the machine's name. And a customer's reply can now come back to the operator's JollyDrivers address instead of an address on a different domain, which Gmail reads as a sign of phishing.

• For JollyDrivers' admin: that last one is a switch per operator, under "Customer replies" on the Operators page, and it is off until you turn it on. Turn it on only after the operator's JollyDrivers mailbox forwards to them in Plesk and you have tested it, or customers' replies will sit unread.

3.59.1

1 October 2026

• Nothing you or your customers see changes in this release. The retired credentials table is removed. It held one record, Jolly Frog's ABN from the old credential form, and that record lives on as Jolly Frog's ABN record in its own compliance: it was moved across on 1 October, and JollyDrivers' admin approved it against ABN Lookup.

• For JollyDrivers' admin: the one-off move-operator-credentials command is gone too. It existed to move that record, and there is nothing left for it to move.

3.59.0

1 October 2026

• Public liability insurance is now optional for your business. Neither Queensland nor New South Wales law requires it, so JollyDrivers no longer asks for it, for passenger or goods work, in either state. "Your own compliance" on your home page stops listing it, and making a booking no longer warns you about it. One you've already filed stays on file and shows as also on file: JollyDrivers can still check it, and you're still reminded before it runs out.

• Goods-in-transit insurance is optional too. It was JollyDrivers' own choice for goods work, not the law, so it is no longer asked for in either state.

• So a business doing passenger and goods work in both states is asked for three documents of its own: its ABN, its booking entity authorisation in Queensland and its booking service provider authorisation in New South Wales.

• Cars doing passenger work in New South Wales now need third-party property insurance of at least $5 million. New South Wales' Point to Point Regulation (clause 22) requires it on every car used for a passenger service, from an insurer authorised in Australia, and for a booked service the booking service provider must make sure it's in place. A comprehensive or third-party property policy usually provides it, if it covers passenger work. Drivers: add it to your car's documents, as you did its CTP. Until it's on file and approved, the car isn't cleared for passenger work in New South Wales, as with any other missing document. Queensland cars aren't asked for it, and nor is goods work.

• The compliance guide says so: the New South Wales page and the side-by-side table on /compliance now name the $5 million third-party property cover (requirements version 2026-10-01.2).

• For JollyDrivers' admin: the requirements on the Compliance page now say plainly when a business's own document is optional — nothing asks for it and nothing warns without it — instead of saying a booking made without it is warned about.

3.58.0

1 October 2026

• Your Compliance page now takes as long to load for a hundred drivers as for one. It used to read each driver's and each car's documents, your decisions on them, your requests and your checks on the register one card at a time, and all of it again after every tap: a fleet of ten drivers and ten cars cost over three hundred reads of the database. Now each of those is read once for the whole page, a couple of dozen reads however big your fleet is, and the same after a tap. Nothing on the page has changed: every card, reason, date and word is exactly as it was.

• Offering a job to your drivers judges them all at once, rather than one after another, and says the same thing about each driver as before.

• For JollyDrivers' admin: the "what if" buttons on the Compliance page judge each operator's drivers or vehicles together rather than one by one, with the same counts.

3.57.0

1 October 2026

• Your business's own compliance documents now live on JollyDrivers, and JollyDrivers checks them. Your home page has "Your own compliance": what your kind of work asks of your business itself — your ABN and public liability insurance, goods-in-transit insurance if you do goods work, your authorised booking service provider authorisation in New South Wales and your booking entity authorisation in Queensland — and where each one stands, in words: not on file yet, waiting for JollyDrivers to check it, cleared until a date, running out, expired, or sent back with JollyDrivers' note. Each has an Upload button. You file them and JollyDrivers decides on them, never you; no other operator and no driver sees them.

• A Queensland passenger operator is now asked for its booking entity authorisation. The compliance review found it missing from what JollyDrivers asks for (requirements version 2026-10-01.1). Which section of the Act requires it is marked as still to confirm.

• You're reminded before your own documents run out, on the same days a driver is — when one enters the expiring-soon window, a week before, on the day, and once after it has lapsed — by email to your notification address, in the same daily run as drivers' reminders. Without a notification address you aren't reminded.

• Making a booking now checks your own compliance, and only ever warns. On the booking and delivery forms and through your AI assistant, JollyDrivers checks your own documents for the trip's state and kind of work, on the trip's own date. If something is missing or has run out you're told — "Your own compliance: … JollyDrivers only warns about this; the booking stands." — and the booking's history says so. The booking is always made, whatever your compliance setting; with it Off, only JollyDrivers' admin sees the check.

• A car you run yourself can now hold its documents. For a car you registered for a driver without a JollyDrivers account, Vehicles has a Documents button: upload its registration, CTP and the rest there, and decide on them as you do for a car a driver shares with you. Your Compliance page lists your own cars beside what drivers share, and a booking assigned to one is cleared on its documents like any car's.

• For JollyDrivers' admin: the Operators page now lists each operator's own documents, to open and to approve, ask for an update or reject; the decision is recorded as JollyDrivers', with the admin's name. The old credential form and "goods verification" panel are gone. The requirements on the Compliance page now preview what changing an operator's own requirement would do to operators, and count the cars operators run themselves.

• The ABN recorded with the old credential form moves across as a record of what was seen on ABN Lookup, waiting for the admin's decision, once the admin runs the one-off move after this release.

3.56.0

1 October 2026

• Every compliance record now has a retention schedule, built to run dry first — and nothing is deleted until our lawyer confirms it. A copy of a document is kept while it's in use and 90 days after: a version a renewal replaced, once every operator you share with has approved the renewal; a document you withdraw (30 days for a medical certificate or police check); and a driver's documents once they have left their last fleet, from the day they left. While you're in any fleet, what you've filed stays, whether you share it or not. A version still counting for an operator while its renewal waits is never touched. What's left is a record without the copy or the number, kept two more years.

• A copy of a medical certificate or police check goes 30 days after every operator you share it with has decided on it (the date JollyDrivers has recorded since 3.55.0), and the record of it keeps counting: the operator's approval rests on the record, not the image. If an operator you've shared with since hasn't decided, it waits for them.

• Details kept only as long as they're useful: the phone number or email a reminder or decision went to, and what you typed in an Academy assessment, go after 90 days (your score and certificate stay); where you last checked in goes after a week (when you checked in stays); a blockout goes 90 days after it ended. The record of who opened your documents is kept seven years, like the rest of JollyDrivers' audit trail.

• An admin can now see what de-identifying a driver who has left every fleet would do, from Admin → Users: what goes and what stays and why — a document an operator relied on stays as a record, without its copy or number, for two years; an Academy certificate stays checkable at /verify. Like the rest of the schedule, it deletes nothing until the retention horizons are confirmed, and says so; after that, it acts once the admin types the driver's name. It refuses a driver still in a fleet, and never touches the account, trips or payments.

• A copy that has been deleted says so. My Documents and the operator's Compliance page show "Copy deleted on … under JollyDrivers' retention schedule; the record of it stays", and opening it shows that record.

3.55.0

30 September 2026

• Operators can now check a document on its official register and record what it showed, rather than rely on a copy. Your Compliance page has "Check on the register" for each document your work needs that has a free official register in the state it's needed in: a Queensland driver authorisation on TMR's driver authorisation register, and a vehicle's registration, Booked Hire Service Licence or New South Wales CTP on TMR's or Service NSW's registration check. One tap opens the register in a new tab, where you look the number up yourself, and one tap records what it showed: "Found and current", "Not found" or "Doesn't match". JollyDrivers records who checked, on which register, when, what it found, the last few characters of the number (never all of it), and when the next check is due: in 90 days, or sooner if the driver's own copy runs out first. JollyDrivers never reads a register itself.

• A check that finds a document current counts on its own, for the operator who made it. It clears the driver or vehicle on that document for your trips until the next check is due, whatever copy is on file, and "Cleared for work?" says so: "cleared on your check of TMR's driver authorisation register on 30 Sep 2026 — next check due 29 Dec 2026". "Not found" or "Doesn't match" rejects the copy on file for you, with a note the driver sees, so they aren't cleared on it for your trips until a later check finds it or you approve a new copy. Your checks are yours: other operators don't see them or count them. Drivers see on My Documents each operator's latest check on their documents and what it found.

• "I checked this on the public register" (3.52.0) works as before. It still says you checked the copy the driver uploaded when you approved it. A check on the register is the other way round: it can be the evidence, with no copy at all.

• Police checks are now filed by reference, with no PDF. A driver adds who issued it, the certificate number, the date issued, what it says (no disclosable court outcomes, or disclosable court outcomes) and the provider's link for checking it, from My Documents or from an upload link. JollyDrivers keeps only the last few characters of the number and a keyed fingerprint to match it, never the whole number, and the check counts for a year from the date issued. Operators see "Check it with the provider" beside it, and ticking "I checked this with the provider" records that link as where they checked. A police check already uploaded as a PDF stays as it is. For it, and for a medical certificate, JollyDrivers now records the day the file may be deleted: 30 days after every operator it is shared with has decided on it. Nothing is deleted yet.

• The certificate the Jolly Academy issues when you pass an assessment is now filed as issued by the Academy, rather than as something you uploaded, and your operator sees "Issued by Jolly Academy on 30 Sep 2026".

• Opening a check on the register, or a police check filed by reference, shows a short record of what was checked rather than a file. An operator's copy of a driver's documents includes their own checks the same way, and every opening is listed under "Who opened my documents" as before.

• The daily compliance email now lists an operator's checks on the register due in the next 14 days, and any up to a week overdue, which don't count until checked again. The email is still switched off.

3.54.0

30 September 2026

• A JollyDrivers Academy certificate now says the driver completed the course, not that JollyDrivers certifies their competency. JollyDrivers isn't a compliance authority, so the certificate and the public check at /verify say what it can truthfully say: this driver completed JollyDrivers' course and its assessment on this date. The certificate also says it isn't a licence, an accreditation or a finding of competency, and that whether it meets a requirement is for the operator and the regulator to decide.

• An admin can now revoke a certificate, and the public check says so. The admin records why, and the check at /verify says the certificate was revoked and on which day, but never why. The document it was filed as stops counting for every operator at the same moment, and the driver's training page shows the certificate as revoked.

• An assessment now starts when you press Start, not when you open the page. Opening the page used to start an attempt, sometimes two. You can take an assessment 3 times in any 24 hours: the page says how many you have left and, once they're used, when you can try again. Coming back to an attempt you haven't submitted carries on with it rather than using another. At the end you see your score, not which answers were wrong. Pressing Submit twice, or submitting the same attempt in two tabs, now issues one certificate.

• A notifiable incident now opens its safety-plan review on the plan for the state and service it happened on. It used to go to the operator's first plan, so a New South Wales incident could land on the Queensland review.

• Your Safety page now tells you when the plan in force cites wording JollyDrivers has since corrected, like the New South Wales fixes in 3.31.7 and 3.31.8, and names the provisions. Publish a new version to put the corrections in force; a partner business is told to ask whoever maintains the plan.

• A driver who leaves your fleet can no longer open the safety plan you shared with them. Your list of who has it keeps the record and says they've left, and if they come back they can read it again. Sharing a plan is now recorded as your act, not as the driver's consent.

• A safety plan shown on screen now drops any link that isn't to a web page, an email address or a phone number, and shows anything typed in { } after text as text. The browser already blocked both; this no longer relies on it.

3.53.0

30 September 2026

• A new driver now sees what their operator needs before they start. The welcome page after accepting an invite lists every document the operator's work asks for, the driver's own and their vehicle's, with what each one is for, worked out from the states the operator's jobs run in and the kinds of work it does. A state JollyDrivers doesn't check yet is named rather than left out. The invite text says how many documents they'll need, and the operator sees the list before sending it. The invite still goes by text to the driver's mobile, so a driver with no email gets all of it.

• Sharing is now one honest choice, and it covers the driver's vehicle too. The welcome page asks once, with nothing chosen for them: "Share and finish" shares the driver's documents and every vehicle on their place in the operator's fleet, and "Finish without sharing" shares nothing. Each says plainly what follows: without sharing, the operator can't clear the driver for trips once it checks compliance. Sharing used to be a switch that was off unless flipped, and it left out the car the operator had just handed over.

• "Am I ready?" now gives the same answer as the check that puts a driver on a trip. It opens on the state and kind of work the driver's operator mostly does, rather than on Queensland passenger work for everyone, and counts a document only once the operator can see it and has approved it. An earlier approval still counting while a renewal waits counts too, and a requirement that doesn't start until later doesn't. It can no longer say "You hold everything required" while the operator can't clear the driver. Every reason is on the page in words, including an operator's note on a document they sent back, and a vehicle's page asks the same question about the vehicle.

• My Documents now answers "Cleared for Jolly Frog?" for each operator you drive for. It says "Yes", or "Yes, on version 1 of your Driver's licence until 5 Dec 2026" where an earlier approval is what's counting, or "Not yet: vehicle ABC123 not shared; Driver's licence awaiting review", naming the kind of work and state wherever the answer differs between them. A driver's AI assistant gives the same answer in the same words.

• A driver's home screen now shows "3 of 7 done". A card lists what's missing, expired, refused, awaiting review or running out, for the driver and for their vehicle, and says which operators can't assign them yet. The My Documents tile counts the same things, where it used to count only the driver's own documents about to expire.

• The "verified" community-check chip is gone from your documents, with the community checks themselves (3.52.0). And when a JollyDrivers administrator acting for you reads your answer to "Cleared for Jolly Frog?" through their AI assistant, each document it rests on shows under "Who opened my documents", like any other read of them.

3.52.0

30 September 2026

• "Verify Documents" is gone, and checking a document on its public register is now part of approving it. It showed any driver or operator other people's document numbers to check. Now, when you decide on a document whose type has a public register (a Booked Hire Service Licence, for now), your Compliance page offers "I checked this on the public register" beside a link that opens the register. Tick it and your decision records that you checked it, on which register and when, and the page says so: "Approved by Sam on 30 Sep — checked on the public register". Checks recorded the old way are kept as history.

• A copy of a driver's documents is never emailed as an attachment any more. "Email a link" on your Compliance page sends your operator inbox a link instead. It works for 7 days, only for someone signed in to your JollyDrivers account, and JollyDrivers checks the driver still shares their documents with you before it makes the zip. Where the link went and every download through it are recorded, and the driver sees each download under "Who opened my documents".

• No zip holds a medical certificate or a police check. Health and police records are downloaded one at a time, from your Compliance page or the page the link opens, and both say so. The files in a zip are named by document and version, never by licence or certificate number, and a zip now also holds an earlier version your approval still counts on while its renewal waits.

• The upload screens now say truly who can see a document: you, the operators you share it with, and JollyDrivers support, with every opening recorded where you can see it, under "Who opened my documents".

• If you let the JollyDrivers admin act as you, your account page now says their AI assistant can read your compliance documents while it does, and each time it does is listed under "Who opened my documents" as JollyDrivers support.

• Attendance jobs, like walking a dog, are never held up by compliance for now, even if you enforce it. You're told when a driver isn't cleared, as in Advisory, and you can go ahead; the record says the job was treated as advisory and why. Deliveries and passenger trips are enforced as before.

3.51.0

30 September 2026

• What JollyDrivers asks each driver, vehicle and operator for now lives in one reviewed rulebook, and nothing changes today. Every document type and every requirement, state by state and for passenger and goods work, is written down in one place with where it comes from. It changes only through a reviewed update to JollyDrivers, each change it makes is recorded in the settings change log, and every compliance check now records which version of the rulebook judged it. Who is cleared for what is exactly as it was.

• Admin → Compliance now shows the rulebook rather than editing it. Each requirement shows its source, the day it counts from, and a note wherever the compliance review questioned it (the New South Wales driver authority, for one). Nothing on the page changes what drivers are asked for. Instead, each requirement has "what if" buttons that say how many drivers or vehicles, at which operators, would start or stop being cleared today if it were removed, made optional or made mandatory, worked out without saving anything.

• A kind of work is checked only in the states whose rules JollyDrivers has written down for it. Queensland and New South Wales are covered for passenger and goods work, as before, and anywhere else is still "not checked", never cleared. A requirement can now be written in ahead of the day it starts and counts only for trips from that day, and a document type that has been switched off is never required.

3.50.1

30 September 2026

• You can now stop counting a driver's earlier approved document after rejecting their renewal. Once you reject a renewal, ask for an update to it, or the driver withdraws it, "Cleared for work?" on your Compliance page offers "Stop counting version 1" beside the document that earlier approval is still clearing them on. It asks you first, in words, with room for a note saying why. Once you confirm, the driver isn't cleared for your trips on that version any more, even though it hasn't expired, so if you enforce compliance they can't be put on a trip until you approve a newer version.

• Stopping an approval never brings back an older one. If you approved two copies of the same document, stopping the newer one doesn't leave the older one counting in its place. The same goes for a renewal you approved and then rejected: the version before it doesn't start counting again.

• Drivers see it too. My Documents and a driver's AI assistant stop saying the version is approved at your company. The message telling a driver about your decision says you've stopped counting the version you approved before, rather than that you rejected their document. That message is still switched off.

3.50.0

30 September 2026

• Renewing a document early no longer stops a driver working. While a driver's renewal waits for your decision, the version you approved before it keeps counting until its own expiry date, so a driver who renews months ahead stays cleared for every trip before then. It keeps counting if you reject the renewal or ask for an update, too, until that date. A trip after the approved version runs out still needs the renewal approved, and the overnight check says so once you switch it on.

• Your Compliance page now opens with "Awaiting your review": every document your drivers have shared that you haven't decided on, the same ones "N to review" on your home screen counts, most urgent first. A renewal shows when the version you approved runs out beside when the renewal does, stacked on a phone, and you can open, approve, ask for an update or reject each one right there.

• "Cleared for work?" now says when a driver is cleared on an earlier approval, for example "cleared on version 1 (approved, expires 5 Dec 2026) — renewal awaiting your review", and when you reject a renewal or ask for an update the page tells you your approval of the version before still counts until it expires.

• Drivers see the same thing. My Documents says, for each operator, "Version 2 is awaiting review at Jolly Frog; version 1 is approved until 5 Dec 2026", or that the renewal was rejected or an update was asked for, and a driver's AI assistant says it in the same words.

• The morning compliance email marks a renewal with both dates, and the message telling a driver you rejected their renewal, or asked for an update, says the version you approved before still counts until its date. Both are still switched off.

3.49.1

30 September 2026

• Every switch on the platform settings page now records who changed it. The UTC drift sweep, the safety plans' drift scan and review emails, and the commission statement sweep and pay switches save the way the compliance switches do: each change is logged with who made it, when, and from what to what, and the page shows who last switched each one. A switch that was already on before this says there's no record of who turned it on, rather than guessing.

3.49.0

30 September 2026

• Your home screen now tells you when a driver's document is waiting for you. The Compliance tile says "3 to review" when drivers have shared documents you haven't yet approved, rejected or asked them to update — a renewal or a clearer copy counts again until you decide on it — and the line at the top mentions it too. If JollyDrivers couldn't count them, the tile says so rather than showing nothing.

• You can now get a short compliance email each morning, and only on a morning something needs you: documents waiting for your decision, documents running out within 30 days, upcoming trips whose driver the overnight check found isn't cleared, and requests your drivers have answered since the last email. It goes to the address your customers' replies go to (or your notification email if you haven't set one), its only link is to your Compliance page, it never shows a document number, and it calls health and police records "a sensitive document". It's switched off for now.

• Drivers can now be told what you decided about their documents. When you approve, reject or ask for an update on a driver's document, or their vehicle's, they're texted — or emailed, if they have no verified phone or have replied STOP — with your note, and a link to upload a new one while upload links are on. Nothing is sent between 9 pm and 8 am Brisbane time: a decision made then goes at 8 am. Each decision is told once, and only your latest on a document. It's switched off for now.

• Expiry reminders no longer text a driver who has replied STOP. They're emailed the reminder instead, if they have an email, the same way the new decision texts work; with no email, the reminder waits until there's a way to reach them.

• Both are on Admin → Settings with switches of their own, each showing when it last ran, what it sent and anything that went wrong, and what it would send right now — counted without sending anything. Switching either records who did it in the settings change log, and switching one on never sends a decision more than a day old or a request answered more than a week ago.

3.48.1

30 September 2026

• The booking summary in the chat now shows each time on the clock of the place it happens, and says which one. The pickup reads in the pickup's state and the estimated arrival in the destination's, each labelled (for example "AEDT · NSW"), and an airport drop-off's time before departure is worked out on the airport's clock. Across the Queensland–New South Wales border in summer it used to show a car arriving a minute before the flight when it would really arrive an hour before.

3.48.0

30 September 2026

• Expiry reminders now come in good time, and once each. A driver is texted (or emailed, if they have no verified phone) when one of their documents, or one of their vehicle's, has 30 days to go, again a week before it expires, on the day it expires, and once after it has lapsed. Each goes once for a document: uploading a clearer copy of the same document doesn't start them again, and a renewal starts them afresh for its new date. They go out once a day, after 9 am Brisbane time, rather than a little later every day.

• Switching the reminders on, or back on after a break, never sends a pile of old news. A document that lapsed more than a week before a run is never sent an "expired" reminder, however long they were off.

• The reminders' switch is now on Admin → Settings, with when they last ran, how many they sent and anything that went wrong, and what the next run would send — counted without sending anything — and the first day a reminder is due. Switching them, or the nightly re-check, now records who did it and when in the settings change log, and a switch that was turned on some other way says there's no record of who did.

• "Expiring soon" now means the same everywhere: within 30 days, on the admin dashboard (it was 14 there), the home screen, "Am I ready?", the Compliance page and a driver's AI assistant, and the first reminder goes on the day it starts.

• A request for a document is now answered only by one uploaded after it was made. Asking a driver to upload their licence again because the photo was blurry no longer closes the moment they upload something else.

• The Compliance page now says everything in words, on the page, with nothing left in hover text a phone can't show: why a driver isn't cleared for each kind of work and state, what you asked for, why and by when, when each document runs out, and what the public register check found. Approve, Request update, Reject and every other button there are now big enough to tap easily on a phone.

3.47.1

30 September 2026

• An airport drop-off across the Queensland–New South Wales border now gets the right pickup time in summer. The pickup worked back from a flight treated the flight's departure as if it were on the pickup's clock, so from northern New South Wales to Gold Coast Airport during daylight saving it suggested a pickup an hour too early. The flight is now read on the airport's time and the pickup given on the pickup's time, in the booking chat, on the trip page's suggested pickup, and when you change a flight's departure while editing a booking.

3.47.0

30 September 2026

• You now choose what happens when one of your drivers isn't cleared for a trip, on Settings → Compliance. Advisory, where every operator starts, tells you and lets you go ahead. Under Enforce a driver who isn't cleared can't be put on the trip, take it when you offer it, or have it confirmed with them on it; a trip in a state JollyDrivers holds no requirements for is never held up. Off shows nothing and refuses nothing, and every check is still recorded. The admin can see each operator's choice.

• Offering a job to your drivers now shows, beside each one, whether they're cleared for the trip's date, and why not when they aren't, before you offer it. That's for trips and tasks alike. If you enforce compliance, a driver who isn't cleared can't be picked, and every driver is still checked again when they accept.

• JollyDrivers can now check every upcoming trip's driver again each night, so a licence that runs out, or a document you reject, after a driver was put on a trip no longer goes unnoticed until the day. When a driver stops being cleared for a trip, the trip says so and it's listed at the top of your Compliance page; when they're cleared again, the trip says that too. Nothing is sent to anyone, and nobody is taken off a trip. The nightly check is switched off for now.

3.46.0

29 September 2026

• A driver's documents are now checked for the day of the trip, in the state it runs in, rather than for today. A licence that runs out before a trip three weeks away no longer counts for that trip, and a New South Wales trip just after midnight is checked on Sydney's date. It applies however a driver goes onto a job: assigned from Bookings or by your assistant, booked with a driver, taking a job you offered them, put back with Undo, or carried onto a rebooked trip.

• JollyDrivers now keeps a record of every one of those checks: what it found for each document, the day it checked for, and who went ahead when a driver wasn't cleared. While compliance enforcement is off, as it is now, nothing is refused because of it.

• Booking a trip or a job with a driver now tells you when they aren't cleared for it, or when JollyDrivers couldn't check because it couldn't tell the trip's state or holds no requirements for it. The booking forms used to say nothing unless enforcement was on. Accepting a booking tells you the same, and so does your assistant.

• A driver who has left your fleet can no longer take a job they were offered before they left. Undo no longer puts a driver who has left back on a booking, and rebooking a trip no longer carries over a driver who has left: the new booking is made without one.

• Removing a driver from your fleet now shows on each of their future bookings' timelines that they were taken off, and by whom.

• If compliance enforcement is switched on, it now covers every way a driver goes onto a job, including taking an offered job, Undo, a rebooked trip's driver and automatic confirmation, which holds a booking back rather than confirm a driver who isn't cleared.

3.45.2

29 September 2026

• Text that's too long is now refused with a message saying how long it can be. That covers the note when you check a document against its public register, the reason when you ask a driver for a document, the note on an approval, a rejection or a request for an update, the details when you log a training course, a short answer in an assessment, and document types in Admin → Compliance. The boxes also stop you typing past the limit. Before, a check with a very long note was lost while the page thanked you for it, a very long request reason was reported as a request you already had open, and a very long decision note showed a technical error.

• When a check, a request or a decision can't be saved for any other reason, you're now told so in plain words and asked to try again, rather than shown a technical error. A check is never reported as saved when it wasn't.

3.45.1

29 September 2026

• A PDF is now checked before JollyDrivers keeps it. It has to be a whole PDF, and one with scripts, attached files or automatic actions built into it, as fillable forms often have, is turned away with a message saying how to save a plain copy or upload a photo instead. Before, anything with a PDF's opening characters somewhere near its start was kept as a PDF, a web page or a program included, and handed as it was to whoever opened it.

• Files attached to a vehicle's service history get the same checks as your documents. A photo of an invoice or a docket is kept without the phone's location in it, a file is judged by what it is rather than what it's called, and anything over 15 MB is turned away by JollyDrivers itself, not only by the page. Files attached to a case, and to a problem report, get the same.

• A problem report no longer takes a GIF, which no other upload has taken since 3.43.1; attach a screenshot as a PNG or JPEG. A report with a file that can't be taken is now turned away whole, naming the file, rather than being saved without it.

• JollyDrivers can now also run every uploaded document and attachment past Microsoft Defender's virus check before keeping it. It isn't switched on yet. Once it is, a file the check flags, or can't check, isn't kept, and you're told so.

3.45.0

29 September 2026

• Removing a document an operator has already seen now withdraws it rather than deleting it. It stops counting, and neither you nor your operators see it any more, but JollyDrivers keeps the record of what was decided about it. The version before it doesn't come back in its place: removing a rejected renewal used to bring back the approval of the one before. A document no operator has seen is still deleted outright, and the confirmation says which will happen before you choose.

• Every decision an operator makes on a document is now kept. Approving, asking for an update and rejecting each add to the document's history, where a new decision used to overwrite the last one. The operator's Compliance page shows their earlier decisions under the latest.

• My Documents now shows who opened your documents: each time an operator you share with, or JollyDrivers support, opened or downloaded one of your documents or one of your vehicles' documents, and when. Every opening and every export is recorded before the file is sent.

• Admins see every opening on the Compliance page, and the admin dashboard warns when one account opens more than 20 different documents within an hour. A flagged document stays in the review queue even if its owner withdraws it.

• Deleting a vehicle now withdraws the documents an operator has seen, rather than deleting them with the car. Its other documents still go with it.

• Admins can erase a document for good, with the reason kept on record, for example for a privacy request. It is the only way to delete a document an operator has seen, and nothing does it automatically.

3.44.1

29 September 2026

• Document upload links can now be stopped, ready for when they're switched on. A link stops working when your verified mobile number changes, when the operator cancels the request it was sent with, or when the vehicle it's for is deleted, and an admin can stop all of a driver's links at once from the Users page.

• An upload link checks who is using it before anything else. Anyone who isn't the driver it was sent to is asked for a new code and nothing they send is kept, and a form posted to it from another website is turned away. A file over 16 MB is turned away without being read.

• A medical certificate or police check and your consent for it are now saved together. If saving the document fails part-way, the consent isn't kept, and any consent you gave before stays as it was.

• The text with an upload code now says never to share the code.

• A document number your AI assistant read from a photo is deleted once its link is used, stopped or runs out, and old links are deleted a month after that.

• When saving a document through a link goes wrong, the page says so plainly and the details are logged for us, rather than showing a technical message.

• An operator's trading name can't include a web or email address. It opens texts and emails to drivers, just before JollyDrivers' own link. An address already in one is left out of those messages.

• Your AI assistant now reads an operator's name as a quoted name, so a name can't pass itself off as an instruction.

3.44.0

29 September 2026

• Compliance documents can no longer be saved unencrypted by mistake. Licences, accreditations, medical certificates and police checks are encrypted before they're stored, and JollyDrivers now refuses to start without a working encryption key, where before it quietly saved plain files. If the key is set wrongly, saving a document fails with a message and nothing is saved.

• Each stored document is now tied to its own record, so a file copied or moved into another document's place is refused rather than shown as that document.

• Opening or exporting documents no longer leaves a copy in the browser's cache, so a shared computer doesn't keep them after you sign out.

• Admin → Settings now shows how compliance files are encrypted: whether they are, which key is in use, and anything set wrongly.

• The encryption key can now be changed without losing access to anything. Documents saved under the old key still open, and a one-off tool moves them all onto the new one.

3.43.3

29 September 2026

No changes recorded for this release.

3.43.2

29 September 2026

• Leaving a fleet now ends your document sharing with that operator. Tapping Leave Fleet on My Fleet used to leave your documents shared, so the operator you'd left could still open, download, email and ask for them, including anything you uploaded afterwards. Leaving now ends the sharing and records that you withdrew it, as it already did when an operator removed you. An admin deleting a fleet membership ends it too.

• An operator sees a driver's documents only while the driver is in their fleet and has shared them, everywhere in JollyDrivers: opening, downloading or emailing them, asking for one, approving one, a vehicle's service history, and the Compliance and Driver training pages.

• My Documents now shows every operator your documents are still shared with, including one whose fleet you've left, marked "left", so you can end the share under Manage sharing. It used to say "Not shared with any operator yet" while a share was still open. Your AI assistant's view of your compliance shows it too.

• The safety plan counts only the documents and training drivers have shared with their operator. It used to read every driver's documents, and its Expiring soon list could name a document and its expiry date that the driver had never shared. A driver's driving-hours settings are only read once they've switched their cap on.

• An operator can open a driver's day-by-day driving hours only if the driver has set a driving cap, as the fleet's Driving hours page already required. Typing the driver's page address used to show them anyway.

3.43.1

29 September 2026

• Photo uploads now take JPEG, PNG and WebP, and nothing else. That is what every upload already asked for, and now it's what each one does: photos of a licence or another document, delivery photos, vehicle photos, receipts, logos and profile photos alike. A TIFF, which is what a scanner or a fax often makes, or a GIF is now turned away with a message saying what to upload instead, where before it was accepted. A document can still be a PDF.

• An animated image is turned away with a message saying so, rather than being stored.

• A photo over about 50 megapixels is turned away, with a suggestion to use a screenshot or a lower resolution. A phone photo at its usual setting is far below that, and one taken in a 50-megapixel mode still fits.

• A security fix for photo uploads. JollyDrivers now reads only the picture in an uploaded photo, never the extra information a file can carry, and works on at most two photos at a time, so a file built to cause trouble can't take the site down or slow it for everyone else.

3.43.0

29 September 2026

• The admin Bookings and Deliveries lists now open the way you left them. The operator, driver and payment method you picked, Show deleted, the status chips, the search, the When window and Earliest or Latest first are all remembered in your browser, so they're still set on your next visit. Going back from a booking also returns you to the same page of results; a new visit starts on the first page.

• The Payment method box on those lists now shows the method you picked. It used to show the text "_paymentMethod" whenever the page opened.

3.42.3

28 September 2026

• A proof-of-delivery photo or signature now opens only for someone signed in who can see that trip, the same as a receipt and for the same privacy reason: a doorstep photo shows somebody's home. The old link, which opened it for anyone who had it and never expired, has been retired. None had ever been sent to anyone.

3.42.2

28 September 2026

• The booking chat no longer tells customers their pay link comes with the booking confirmation. Confirmations stopped carrying a pay link on 27 September, but the chat kept saying they did. It now tells a customer the link comes from their driver or the operator, or as a QR code at pickup, and tells a driver it's on the trip page's Pay link card.

3.42.1

28 September 2026

• Each switch in Admin → Settings that sends messages now says who it messages, such as "emails / texts drivers" or "emails operators", instead of calling everyone customers.

3.42.0

28 September 2026

• Drivers can photograph a new document and let their AI assistant fill in the details. Once it's switched on, a connected assistant reads the number and dates off the photo and gives you a link to JollyDrivers with them filled in. Pick the same photo, check each detail, change anything that's wrong and save. The assistant never files anything itself, and its link works once, for 30 minutes.

• A document now shows when an AI read its details. Operators see it beside the document they're deciding on, and you see it in My Documents, including when you corrected what it read.

3.41.1

28 September 2026

• Proof-of-delivery photos no longer say where they were taken. A delivery photo is turned the right way up and has its location and camera details removed before it's stored, the same privacy step document photos, receipts and vehicle photos already had. Signatures are kept exactly as they're drawn.

• Picking a file that can't be used as a delivery photo now says why, an iPhone HEIC photo included, and so does a photo over 8 MB, which used to fail without saying anything useful.

3.41.0

28 September 2026

• A reminder that a document is expiring can now take you straight to uploading the new one. Once it's switched on, the text or email saying your licence, registration or insurance is expiring carries a link to a page for that one document: photograph the new one, check the dates and save. The link opens only for you, signed in to JollyDrivers or with a code texted to the mobile on your account, and it works once, for two weeks.

• An operator's request for a particular document carries the same link.

• The page shows the photo you picked before you save it, so you can check the dates against it, and a medical certificate or police check asks for your consent first, exactly as in My Documents.

3.40.0

28 September 2026

• Drivers can ask their own AI assistant where their compliance stands. Once it's switched on, a connected assistant can list every document on file for you and your vehicles, say whether each is current, expiring or expired, show what each operator decided about it, and work out what Queensland's or New South Wales' requirements still need, plus anything an operator has asked you for. It only reads. Adding or renewing a document is still done in My Documents, and document numbers are never shown in full.

• Connecting an assistant as a driver now says it covers your compliance documents, as well as your schedule and your trips.

3.39.0

28 September 2026

• JollyDrivers now asks before it takes a medical certificate or a police check. Both are sensitive information under the Privacy Act, so uploading one shows what it's for and who sees it, with an "I consent" box that starts unticked. Nothing is uploaded until it's ticked, and the consent is recorded before the file is kept. Deleting your last copy records that you've withdrawn it.

• Admins can mark any document type as health or criminal record information, so a type added later gets the same step.

3.38.0

28 September 2026

• Photos of your documents no longer say where they were taken. A phone photo uploaded as a compliance document is turned the right way up and has its location and camera details removed before it's stored, as receipts and vehicle photos already were. PDFs are kept exactly as they were uploaded.

• A document that expires now needs its expiry date. A licence, registration, insurance certificate or anything else with an expiry can't be uploaded without one, and an expiry before the issue date is caught. Before, a missing date quietly counted as "never expires".

• Uploading a document an operator asked for now closes their request wherever you upload it. Upload and Renew on "Am I ready?" used to leave the request open.

• Files are checked for what they are, not what they're called. Anything that isn't a PDF or a readable photo is refused with a plain reason, an iPhone HEIC photo included, and a file over 15 MB is refused however it arrives.

3.37.4

28 September 2026

• Once paid, the pay link's page now links the paid invoice itself, the same as the receipt email. The customer sees the invoice number, what they paid and a "View your tax invoice" button, and downloads the PDF from there. A paid invoice with no link of its own still shows the tax invoice on the page, with its PDF, as before.

3.37.3

28 September 2026

• The JollyDrivers admin can now add a wish while acting as a driver from their AI assistant. It used to answer "No such proposal for you" every time, so the wish never reached the wishlist. A wish prepared while acting can be added only while the same admin is still acting as that driver, never from the driver's own assistant, and one the driver prepares themselves is still theirs alone to add.

• Saying "me too" to a wish while acting as a driver now records the admin beside the driver, the same as the wish itself and every stamp, text and booking made while acting.

3.37.2

28 September 2026

• An admin can now erase a rider who signed up by text message. It used to fail with a database error and change nothing. Their phone verification history goes with the account. Problem reports and wishes they raised stay, no longer linked to them, and their "me too" votes are removed.

• When an account can't be erased, the Erase dialog now says why, such as PayID history, a former driver's records, or payment records that have to be kept, and nothing is changed.

• A rider who hasn't set a name is confirmed by typing their phone number. The dialog used to accept an empty box.

3.37.0

28 September 2026

• A receipt for a paid invoice now links the invoice itself. "View your tax invoice" opens it marked paid, ready to download as a PDF, in place of JollyDrivers' own copy of its lines. A receipt for anything else still shows the tax invoice in the email, as before.

• The pay link card on the trip page now looks like the cards around it, and the gap above the next card is back. On a paid trip it starts closed, shows Paid, and says the same link now shows the customer their tax invoice.

• Tax on an invoice line now reads "GST on Income", not Xero's code "OUTPUT", on receipts and on the tax invoice PDF from a pay link.

3.36.4

28 September 2026

• The Tips card is gone from the trip page. Tips now come in on the pay link, and Mark as paid still asks whether money above the fare is a tip. The Tips page still shows what's held for drivers and what's reached them, and every tip stays in its trip's timeline.

3.36.3

28 September 2026

• An incident your office reports about a trip now names the trip's driver, not the person who typed it in. One reported with no trip names no driver.

• The driver sees an incident your office reported only once you let them, with "Let the driver see this", the same as a complaint, and the moment is recorded. An incident a driver reports themselves is still theirs to see straight away.

3.36.2

28 September 2026

• The pay page's list of who to invoice now lines up on the left, each choice with its button beside the name, instead of floating in the middle of its row. "Someone else", "Change" and the other small links read as plain links rather than shouted capitals, the same as "Add a tip for your driver".

• The pay page now shows the ways you can pay, right under the Pay button: Visa, Mastercard, American Express, Apple Pay and Google Pay, each in its own brand's mark.

3.36.1

28 September 2026

• A driver can now remove a car that a complaint or incident names. It used to fail with a database error. The complaint keeps the car's name and number plate, just as the trips it did keep theirs.

• A car your operator's safety plan lists against a service can't be removed until the operator takes it off the plan, and My Vehicles now says so, naming the plan and the service, before asking you to confirm anything.

• Removing a car now tells you what goes with it: its photos, documents, fuel log and service history. Trips it has done, and any complaint or incident that names it, keep its name and plate.

3.36.0

28 September 2026

• The pay page now offers every bill-to a customer has, one tap each. A customer who pays for some trips themselves and for others through their company sees both, with the usual one already chosen. Anyone holding the link sees just the names, with the email partly hidden as before. "Someone else" is still there, and whatever is typed is saved to the customer's card, so it's one tap next time.

• A customer can change who the invoice is for while it's still a draft. The draft is deleted in Xero, which leaves no trace, and a fresh invoice is raised for their choice. The trip's timeline says so. An invoice that's already approved still has to be voided from the trip page.

3.35.0

28 September 2026

• Each trip now keeps the car it ran in. When the driver sets off, or marks the trip done, JollyDrivers records the car and its number plate against the trip. Changing a driver's main car, editing a car's details or deleting a car no longer changes the car shown on trips already done: the receipt, the passenger's trip page, your booking lists and your assistant all show the car the trip actually ran in.

• Trips that had already run have been given the car they were already showing, so nothing you see changes today. What changes is that it now stays put.

• A complaint names the car the trip ran in, not whatever the driver was driving on the day the complaint arrived.

• A booking that names one of the driver's other cars now shows that car. The confirmation, the passenger's trip page and your booking lists showed the driver's main car instead. Searching a list by number plate now finds the trips that car did.

• Taking a car off a driver moves their upcoming trips planned in it onto their main car, so no trip is left planned in a car they no longer have. Trips it already ran keep it.

3.34.1

28 September 2026

• Invoices now reach the right contact in your Xero when one customer has two there, such as themselves and their company. JollyDrivers used to look a customer up by email first. Someone who books both as themselves and through their business often uses one email for both, so it could pick the wrong contact. It now looks for the company's ABN first, and tells a company from its owner by name, ignoring "Pty Ltd" and the like.

• The Xero contact JollyDrivers remembers for a customer is now checked before it's used. If that contact has gone from Xero, or no longer looks like the customer, JollyDrivers finds the right one again. That includes a contact that was matched wrongly in the past.

• Typing a different name to invoice no longer mixes up two customers. If a booking already had someone to invoice and a different name was typed, on the pay page or by hand on the trip page, the invoice could go to the first one's Xero contact, or overwrite the contact remembered for them. The typed details are now saved as a bill-to of their own on the customer's card, and the first one is left alone.

• Editing a customer's saved bill-to now changes the Xero contact it invoices. A saved bill-to used to keep the contact it was first matched to, even after its name, email or ABN changed.

3.34.0

28 September 2026

• Passengers can now tell you when something wasn't right about a trip, without an account. Once the complaint link is switched on, the receipt for a trip that has happened carries a quiet "Something not right about this trip?" line. It opens a page with your name on it. The passenger enters the mobile number on their booking, types the code we text them, and tells you what happened. The complaint lands on your register naming the trip's driver and car, and the passenger is texted a reference number.

• Only someone whose number is on the trip can complain about it. A code is only texted to a number on the booking, and the page never says whether a number is on it, so nobody can find out by trying numbers. One person can have one open complaint about a trip, and can only send a few a day.

• You're emailed as soon as a complaint or incident arrives that your office didn't enter itself, at the address your customers' replies already go to. The email gives the case number, what it's about and which trip, with a link to open it. What was said, and who said it, stay in JollyDrivers rather than in your inbox.

3.33.0

28 September 2026

• A complaint you take by phone, email or in person now records who made it. When you choose how it reached you, the form asks for their name, and their mobile and email if they gave them. Until now JollyDrivers recorded your office as the person complaining, with your own phone and email as the way to reach them.

• A complaint's page now shows you who made it and how to answer them: their name, their mobile (tap it to call), their email, and whether they're happy to be contacted. This was saved from the start but never shown to you.

• Two different people can now each have an open complaint about the same trip. It used to be one per staff member who typed them in, so a second caller about the same trip was turned away. The same person can still only have one open complaint per trip, whether they rang you or raised it themselves.

• A driver shown a complaint about them never sees who made it. They read what was said, but never the name, number or email of the person who said it. Only the way the page was laid out had been keeping those details off their screen. Now they're taken out before the page is even built.

3.32.0

28 September 2026

• The admin bookings and deliveries lists can be filtered by payment method (cash, card, invoice or other), beside the operator and driver filters.

3.31.9

28 September 2026

• A code we text you now only works for what its message says it's for. Until now, a sign-in code could also confirm a change to your PayID, your mobile number or the bank details your customers pay into, even though its text said "sign-in". Anyone can have a sign-in code sent to any number, so someone who had got into your account could have talked you into reading one out. Each code now only works for the thing its message names. If you were partway through one of those changes when this release went live, ask for a new code.

• Complaints: only a mobile number that's been proved yours links you to a trip. Before, someone with an account could be treated as a trip's passenger just by typing that passenger's phone number or email into their own profile. The number now has to be one JollyDrivers has texted a code to, and it has to be exactly the number on the trip. An email address no longer counts, because JollyDrivers never checks one.

3.31.8

27 September 2026

• New South Wales safety plans now give the right date for the Point to Point Transport Regulation's automatic repeal: 1 September 2027. Every Regulation clause a NSW plan lists said the Regulation would be repealed on 1 September 2026, but the NSW Government had already put that back a year, on 19 August. Each clause has been checked against the Regulation in force today and every clause number still holds, so they no longer carry the warning that JollyDrivers hadn't confirmed them.

• Plans already published keep what they said. Republish yours to put the corrected date in force.

3.31.7

27 September 2026

• New South Wales safety plans now quote section 26(5) of the Point to Point Transport Act correctly. The front of every NSW plan printed, as a word-for-word quote from s 26(5), a sentence that isn't in the Act, and the plan's legislation list described s 26 as "the safety duties". Section 26(5) actually says that complying with the Act isn't, by itself, evidence of complying with work health and safety law, and the plan now prints those words. The safety duties themselves (sections 12, 13 and 15) are now listed where they really are.

• Plans already published keep what they said, as a published plan always does. Republish yours to put the corrected wording in force.

3.31.6

27 September 2026

• The compliance guide's state pages now label a feature that's built but switched off "Built — off by default", as the guide's front page always has. They said "Built — switched on by choice", which could read as if it were switched on.

3.31.5

27 September 2026

• The public site now says where JollyDrivers works: Queensland and New South Wales. Its compliance side, meaning the documents, safety-plan templates, courses and incident guidance, is written for those two states' law. The home page, the compliance guide, About, the FAQ and the summary for AI assistants now all say so.

• The compliance guide no longer has pages for the other six states and territories. We hadn't done the work to stand behind them, so JollyDrivers now makes no claims about their law. Their old addresses open the guide's new "Everywhere else" section, and we'll write a state's guide when operators there ask for one.

• Assigning a driver to a trip outside Queensland and New South Wales now says the compliance check wasn't done. JollyDrivers only holds compliance requirements for those two states, so for a trip anywhere else it had nothing to check and said nothing, which looked just like a driver who had passed. The bookings page and your AI assistant now say it can't tell either way. It never blocks the assignment, and trips in Queensland and New South Wales are checked exactly as before.

3.31.4

27 September 2026

• Nothing you or your customers see changes in this release. Behind the scenes, the tool that puts new versions live can now put the "back in a few minutes" page up and take it down again on its own, which an update with a database change needs.

3.31.3

27 September 2026

• Nothing you or your customers see changes in this release. Behind the scenes it fixes the tool that puts new versions live, so an update that needs JollyDrivers offline for a moment no longer leaves the "back in a few minutes" page up longer than it has to.

3.31.2

27 September 2026

• Nothing you or your customers see changes in this release either. It deletes the old list of emails waiting for "Send automatically once approved", a feature removed in 3.31.0 whose leftovers could never be sent. Every email that did go out is still on the trip's timeline.

3.31.1

27 September 2026

• Nothing you or your customers see changes in this release. It removes the leftover code behind the "Your trip is complete" emails, which stopped going out in 3.31.0. Ride confirmations and receipts are exactly as they were: we checked them character for character on real bookings, before and after.

3.31.0

27 September 2026

• No more "Your trip is complete" emails. They were the last emails JollyDrivers sent that asked for money. Once a trip is done, its Send button now only appears when the booking is paid, and then it sends the receipt. For a trip still to be paid, share the pay link from the Pay link card instead, by Share, WhatsApp or Text it. The same goes for groups and for your AI assistant.

• "Send automatically once approved" is gone. It queued a completed-trip email to go out when the invoice was approved. Anything still queued won't be sent.

• Sending a receipt no longer approves a draft invoice in Xero. No email carries a pay link any more, so there's no reason to, and it can't turn a leftover draft into a bill for a trip that was already paid in cash.

3.30.0

27 September 2026

• The pay link is now the receipt. Once a booking is paid, the same link your customer paid from shows their tax invoice, marked paid: your business name and ABN, the date, who it's billed to, the trips, each line, the GST and the total. A Download PDF button saves a copy.

• A group's invoice shows every trip on it, whichever trip's link the customer opens.

• Paid in cash? The link offers "Get my tax invoice". Tapping it puts the cash into your Xero against a paid invoice, because the customer asked for one, and the invoice then appears on the page ready to download.

• JollyDrivers no longer emails a receipt automatically after an online payment. Square or Xero already sends one for the payment, and the link now holds the tax invoice. Customers can still have it emailed from the page ("Email it to me instead"), and you can still send a receipt from the trip page.

3.29.0

27 September 2026

• Booking confirmation emails no longer ask for money. A ride confirmation now shows the trip and the fare, and nothing about paying: no pay button, no invoice number or due date, no payment method. Gmail kept flagging emails that opened with a "Total payable · View & pay" card, even after the button moved onto JollyDrivers' own website, because that is exactly what a fake-invoice scam looks like. The same goes for a group's confirmation and for "Your upcoming trips".

• Send the pay link from your own phone instead. The Send confirmation window now says the email has no pay link and points you to the Pay link card on the trip (or group) page, where Share, WhatsApp and Text it send it the way that customer likes to hear from you.

• Sending a confirmation no longer approves a draft invoice in Xero. It used to, so the email's pay button would work. The draft now stays a draft until the customer pays, when the pay page approves it.

• Completed-trip emails are unchanged for now, pay button included.

3.28.0

26 September 2026

• Share a pay link from your own phone. The pay link card, on a trip and on a group, now has a Share button that opens your phone's share menu with the message ready: "Hi Sam, here's the link to pay for your trips with Jolly Frog", then the link. Send it by WhatsApp, Messages, email or whatever that customer uses.

• A WhatsApp button opens the customer's own chat with the same message ready, when their number is one WhatsApp can use: an Australian mobile, or an overseas number written with its country code. Otherwise WhatsApp asks who to send it to.

• Either way it goes from you, not from JollyDrivers, and the trip's timeline notes that the link was shared. On a computer whose browser has no share menu, you'll see WhatsApp and Copy instead of Share.

3.27.1

26 September 2026

• Pay buttons in emails about a group of trips now open your JollyDrivers pay page, never Xero's. When a group's trips are already on one invoice, its email's "View & pay" used to open the invoice on Xero's website. Gmail flagged one of these as possibly dangerous, because a payment link to a different website from the sender is what fake-invoice scams look like. The button now opens the same pay page as a single trip's email. It shows every trip on the invoice, and takes the customer to Xero to pay. A trip in a group billed on its own invoice gets its own pay page link the same way.

• The line under a pay button is now plain words: "Once it's paid, the same link gives you your receipt." It used to repeat the payment link on the word "HERE!", which is another thing scam emails do.

3.27.0

26 September 2026

• A new public compliance guide at /compliance, with a page for every state and territory: what each one's law asks of the booking business, the driver and the vehicle, with the legislation cited, how far JollyDrivers goes on each duty, and where it still falls short.

• The home page has a compliance section with a tile for each state, and a new "usual suspects" section on the rideshare habits JollyDrivers left out on purpose.

• The public pages now describe switched-off features as switched off: the compliance check warns rather than refuses, and the fatigue warning, the NSW levy line and the document, training and safety-plan reminders are built but not on.

• The "days since the first line" figure is gone from the home page, and the public pages no longer name any other rideshare company.

3.26.3

26 September 2026

• Operators can now record a complaint against any trip on their register. In the complaints and incidents register, picking a trip you hadn't booked yourself ended in "You can only raise a complaint about a trip you booked or travelled on". The form now asks how it reached you: you're raising it yourself, by phone, by email or in person. The register keeps the answer, for incidents too.

• A complaint about a trip now names the driver who drove it, and records the car it ran in. It used to take the driver the passenger picked from a price comparison, which almost no trip has, so most complaints named no driver, and one where you'd sent somebody else named the wrong one. Incidents reported on a trip record its car too.

• A driver can raise a complaint about their passenger on any trip they drove. A driver the passenger only picked at quote time, who didn't drive it, can't.

• Behind the scenes: only an operator's own staff, or the JollyDrivers admin, can record a case as reaching the operator. Anyone else raising one goes through the usual checks on who can complain about which trip.

3.26.2

26 September 2026

• A long invoice line can no longer leave an invoice in Xero that JollyDrivers doesn't know about. JollyDrivers keeps its own copy of every invoice it raises, and that copy held only 500 characters a line, where Xero takes 4,000. A longer line, such as a trip with extra stops, a flight and notes, would have gone into Xero and then failed to be recorded here. The trip would have shown no invoice, and pressing again would have invoiced it twice. The longest line so far was 476 characters, so none has been affected: every invoice raised since the move to Xero has its record. The copy now holds whatever Xero holds.

• If Xero takes an invoice and JollyDrivers still can't record it, you're told which invoice it was, and the trip won't be invoiced twice. Raising it again is refused until someone checks the invoice in Xero and uses Record external invoice on the trip.

• Behind the scenes: once Xero has accepted an invoice, JollyDrivers finishes recording it even if the page is closed, and a group's trips are recorded together or not at all.

3.26.1

26 September 2026

• The group page now offers the group's pay link instead of "Request invoice". Copy it, text it or open it, as on a trip page. The customer sees every trip and pays for them all on one invoice, which is raised when they press Pay, so you no longer need to raise it first. Once the group is on one invoice, the link opens that invoice. When a group can't go on one invoice, the page says why, and each trip is paid from its own link. Showing and approving the group's invoice, "Settled outside the invoice?" and Consolidate are unchanged, and with pay links switched off the page is as it was.

3.26.0

26 September 2026

• New, switched off for now: customers can pay by bank transfer or PayID from the pay link. A "Pay by bank transfer or PayID instead" button under Pay creates their invoice, with any tip on it, and shows your PayID, BSB and account number, the amount, and the invoice number to use as the reference. They never leave the page. When you match the transfer to that invoice in Xero, the page shows paid and their receipt goes, as it does for card.

• Set where customers pay on Settings → Accounting, under "Customers paying by bank transfer". Use your business's own account, the one your invoices are in the name of. It is protected like nothing else in JollyDrivers. Only your own account (or the JollyDrivers admin) can change it, and every change needs a code texted to your phone. New details take effect 24 hours later, and everyone on your account is emailed straight away, so a change nobody made can be cancelled, without a code, before any customer sees it. Removing them takes effect at once, and every version is kept. Customers are told the name their bank should show before they pay, and not to pay if it's different.

• Behind the scenes: a test now fails the build if anything a customer pays through could ever carry a card surcharge, which is banned from 1 October.

3.25.1

26 September 2026

• The pay link now mentions paying your driver by card, not only cash. When the trip's driver takes card, the "Paying cash?" card becomes "Paying in person?": hand your driver cash, or tap your card on their card reader. That's you as an owner-driver, and any other driver once you've set where their card takings go on the Fleet page. For anyone else, and before a driver is assigned, it still says cash.

3.25.0

26 September 2026

• New, switched off for now: the customer can add a tip for their driver on the pay link. It's tucked away as "Add a tip for your driver" beside Pay, and opens to $5, $10, $20 or Other with nothing chosen, and No tip. The tip goes on the invoice they're about to pay as its own line, "Tip for your driver", in your Tips held for drivers account: no GST, not part of the fare, one payment for both, and you absorb the card fee on it. Pressing Pay again with another amount changes it, and No tip takes it off. On a group's invoice it's one line, shared evenly between the trips.

• A tip paid on the pay link becomes the driver's once it's paid and the trip is done. It then shows on the trip and the Tips page as held for whoever drove the trip, already in your tips account in Xero, to be paid out like any other tip. Paid before a driver is found, it goes to whoever does the trip. Until then the trip page's Tips card shows it on its way, and the Tips page shows what's been paid for trips not done yet, so its total still matches the tips account.

• Once a booking is paid, its pay link can still take a tip, on a small invoice of its own that the customer pays the same way. A link that has already been paid a tip says thank you instead of asking again.

• If the fare is paid some other way, an unpaid pay-link tip comes off the invoice first. Cash, the card terminal or a bank transfer settles the fare alone, and anything extra the customer actually handed over is recorded as a tip by Mark as paid, as before. If the tip can't be taken off, the payment isn't put in Xero, and the message says what to do there.

• Behind the scenes: a trip reclassified as cancelled takes an unpaid tip off its invoice first, and keeps a paid one out of the credit note, because a tip isn't fare.

3.24.0

26 September 2026

• A pay link now pays for a whole group of trips on one invoice. When a trip is part of a group that hasn't been invoiced yet, its pay link shows every trip in the group and the total for all of them, and pressing Pay raises one invoice for the whole group before taking the customer to pay it. The group's confirmation email carries that link in its "Total payable" band, and an email about one of its trips quotes the total its link will charge.

• A group is still paid trip by trip when it can't go on one invoice: when it includes a delivery or job, a trip that's cancelled, unpriced, already invoiced or already paid, or when it has only one trip. The group page's own "invoice the group" button works as before.

3.23.2

26 September 2026

• A pay link for a trip on a group invoice now shows every trip the invoice covers. Opening the link for one trip of an invoice that covers several showed only that trip next to the whole invoice's amount, so it read as though one trip cost the lot. The page now has a card for each trip on the invoice, in pickup order ("Trip 1 of 2"), and says how many trips the invoice covers next to its number. Once it's paid, it says all of them are paid.

3.23.1

25 September 2026

• A booking with no payment method now shows Mark as paid. 3.23.0 said such a booking could be marked paid, and everything behind the button allowed it, but the trip page still only offered cash, card and bank transfer on bookings set to Invoice, so the button never appeared. It does now, with the same choices as an Invoice booking.

• An email about one trip on a group invoice now shows the invoice's full amount. When a trip is on an invoice that covers several trips, its confirmation or receipt showed only that trip's share next to a button that opens the whole invoice. It now shows the whole amount, and a receipt lists every trip on the invoice, as the invoice itself does. Emails for the whole group were already right.

• New, switched off for now: with pay links on, the booking chat stops asking how the customer will pay. They choose when they pay, from the pay link in their confirmation, and the chat tells them so if they ask. Your AI assistant already works this way. While pay links are off, the chat asks exactly as before.

• Behind the scenes: with pay links on, an email for a whole group keeps Xero's own invoice link, as intended, because a pay link can't yet take a whole group. And the pay page now records the amount the invoice actually charges.

3.23.0

25 September 2026

• A booking with no payment method can now be marked paid. It is treated exactly like a booking set to Invoice: the same people can mark it paid by cash, card or bank transfer, and a group whose trips have no method can be settled in one go from the group page. The trip page's "No payment method is set on this booking" line is gone, because a missing method no longer stops anything.

• New, switched off for now: a pay link for every booking. The trip page gets a Pay link card with the link, a QR code the customer can scan, Copy, and Text it. Whoever opens the link sees the trip, its price and who it will be billed to, and can change the billing name and email. Only when they press Pay does JollyDrivers raise the invoice in your Xero, then it takes them straight to Xero's Pay now for card, Apple Pay or Google Pay, and emails them a receipt once it's paid. Someone holding only the link sees the billing email partly hidden and none of your other saved details, and New link on the card replaces a link that went to the wrong person. A confirmation for a single booking carries the link as its way to pay, so it no longer has to wait for an invoice.

• New, switched off for now: a receipt for cash, when the customer asks for one. Mark as paid → Cash gets a tick, "The customer wants a receipt or tax invoice", with their email filled in. Ticked, JollyDrivers raises the invoice if there isn't one, marks it paid in Xero with the cash, and emails them the receipt. Left unticked, cash is recorded exactly as it is today. A customer who paid cash can also ask later, from the booking's pay link. Needs the new Cash received account chosen on Settings → Accounting.

• An operator's AI assistant can hand out a booking's pay link with the new pay_link tool, once pay links are switched on.

• Behind the scenes: Xero can now tell JollyDrivers the moment one of your invoices changes, so "paid" shows within seconds instead of at the next check. Nothing changes until the webhook is set up in Xero.

3.22.3

25 September 2026

• An invoice covering several trips now shows its full amount on the customer's Billing and trip pages. Each trip showed only its own share, so a $140 invoice for two trips read $70 next to a View / pay link that charges $140, and Amount due (on the Billing page and its home tile) came up short. Both pages now show what the link charges, as the confirmation email and the pay-link text already do. An invoice recorded by hand against several trips is still counted once, at the amount recorded.

3.22.2

25 September 2026

• Security fix: signing in with Google can no longer send you to another website afterwards. A sign-in link could carry a "go here next" address, and JollyDrivers followed it even when it pointed at a different site. Someone could have sent you a genuine JollyDrivers sign-in link that, once you'd signed in, dropped you on a look-alike page asking you to sign in again. Now only pages on JollyDrivers itself are followed; anything else takes you to your usual home page.

3.22.0

25 September 2026

• Driver payouts now show the tips you're holding for each driver. Pick a driver on Payouts and any of their tips that landed with you are listed above their jobs, with the same Paid out buttons as the Tips page. The driver list shows each driver's tips next to their name. Tips are recorded on their own, not as part of the job payment, even if one transfer covers both: use the same reference for each.

• An owner-driver is owed their tips. Payouts used to say nothing was owed between an owner-driver and the business. That's still true of their jobs, but a tip is theirs personally, so any held for them now show there, ready to pay out.

• An owner-driver's tip can only be recorded as paid to them. "Settled with their balance" is no longer offered for an owner-driver. They never get a statement to settle it on, so it would have left the tip in your Tips held for drivers account in Xero. The payout dialog also says the Spend Money is their tip, not a drawing.

3.21.1

25 September 2026

• Safety plan, compliance and training dates are now Brisbane dates all day. Before 10am (11am in a Sydney summer) JollyDrivers was using the UTC date, which in Australia is still yesterday. So a safety plan review written in the morning was recorded as done the day before, the next review dates worked out from it were a day early, a hazard report received in the morning was dated yesterday, and a training certificate earned before 10am carried the previous day. Anything already recorded keeps the date it has.

• An expired document stops counting on the morning after it expires. A licence or other document that expired yesterday was still treated as current until 10am the next day, including when a driver was assigned to a job.

• Safety plans published from now on print Brisbane dates. Plans already issued keep exactly the dates they printed, and their Word copies and errata pages still match them. The certificate check page shows the date printed on the certificate.

3.21.0

25 September 2026

• Pay out everything you hold for a driver in one go. On the Tips page, a driver with more than one tip held now has an "All paid out" button with the total, so one transfer is one tap instead of one per tip. It records all of them or none. If one has changed since the page showed the total, nothing is recorded and the page says which tip changed.

• Drivers with the same name are listed separately on the Tips page. Tips are grouped by the driver, not by their name, so two drivers called Sam are two groups, as they are two payments.

• Xero can now show your tips account by driver. Add a tracking category in Xero (usually "Driver") with an option for each driver, and enter its name under "Tips by driver" on Settings → Accounting. Each tip JollyDrivers puts in your Tips held for drivers account is then tagged with its driver. A driver's option is their name unless you set another on their Fleet page. The payout dialog tells you the tag to put on the Spend Money. If a tag isn't in your Xero, the tip still goes in untagged, and the message says why.

3.20.3

24 September 2026

• A booking made through an AI assistant now always has a payment method. The assistant used to be able to create a booking without asking how the customer would pay. A booking like that could never be marked paid, because every Mark as paid option depends on the payment method. The assistant now has to ask before it can propose the booking.

• The trip page now says why it can't be marked paid. If a booking has no payment method, you see "No payment method is set on this booking, so it can't be marked paid" where the Mark as paid button would be, and who can set one. Before, the button just wasn't there.

3.20.2

24 September 2026

• A tip only shows the remove (bin) button when it can actually be removed. A tip already in Xero as its own invoice, or already paid out to the driver, still showed the bin, and pressing it could only end in a refusal. Those tips no longer show it. A tip in Xero that was recorded by mistake is corrected by voiding its invoice in Xero.

3.20.1

24 September 2026

• No more "Customers to confirm". When JollyDrivers raises a new customer's first invoice in Xero, it finds the customer already in Xero by email, ABN, phone or exact name and uses them, or creates them when there is no match, and that is the end of it. Since 1.4.31 no invoice has waited for a confirmation, but a card still appeared afterwards asking you to confirm the customer, and a banner on every page said JollyDrivers could not raise their invoices until you did. Neither was true. The panel and the banner are gone.

• Customers are now found by their phone number. The phone check never actually searched phone numbers in Xero, so a customer with only a phone was matched on their exact name or created again. It now looks for the number however it was typed in Xero (0412 345 678, +61 412 345 678, and so on).

• A busy Xero no longer creates a duplicate customer. If Xero doesn't answer while JollyDrivers is looking for the customer, the invoice is refused with "try again shortly". Before, JollyDrivers could take that as "no match" and create the customer a second time.

• When more than one Xero contact matches (for example, two sharing an accounts@ email), JollyDrivers picks the one whose name, phone or ABN also match, instead of whichever Xero listed first.

3.20.0

24 September 2026

No changes recorded for this release.

3.19.1

24 September 2026

No changes recorded for this release.

3.19.0

24 September 2026

• A tip can now be recorded as a tip, not as part of the fare. A passenger who hands over $200 for a $50 job has given a $150 tip, and until now the only place to put it was the fare, so commission was taken from it, GST was charged on it, and the driver's running account said they were holding the operator's money. When Mark as paid is given more than the customer owes in total (the fare, any extras and anything bought for them), it asks whether the extra was a tip. Say yes and the fare is recorded as paid, with the tip beside it. A tip can also be recorded on its own at any time, including after the fare is paid, from the new Tips card on the trip. Every tip is the driver's in full, with no commission and no GST, and one recorded by mistake can be taken back out with a reason. Behind Features:Tips.

• Who has the tip is part of the record. A tip handed to the driver is theirs straight away. One that landed in the operator's account (their card terminal, or a bank transfer) is held for the driver until it is paid out, and every held tip must be paid out before 30 June. The new Tips page shows operators what they are holding for each driver, with a countdown through June and anything held from a past financial year flagged overdue. Drivers see what was handed to them and what is being held for them.

• A cut fare and a tip are shown side by side. If the fare was lowered after the booking was confirmed and a tip was then recorded, the trip shows both, so the operator and the driver can see whether part of the tip was really fare. The operator can move up to the amount of the cut from the tip back into the fare, and the driver sees that on the timeline. Otherwise the tip stays entirely the driver's.

• Tips reach Xero as tips, never as income. Operators nominate a Tips held for drivers account (a liability, BAS Excluded) on the Accounting tab. A card or transfer tip on a fare JollyDrivers invoiced in Xero gets its own document there, marked paid into the account the money landed in. A driver's statement bill passes held tips on to them in a BAS Excluded line, outside the taxable part of a recipient-created tax invoice. When an operator pays a tip on its own, the Tips page records it and says exactly what to enter in Xero.

3.18.0

24 September 2026

• A driver's AI assistant can now tell you everything booked ahead for one customer. Ask "when is Karen next travelling with me?" and customer_schedule lists every job still to come for that customer, soonest first, across every operator you drive for: one under way now, each pickup still ahead, and a round trip whose return is still to come even though its outbound has run. It gives the count, and says plainly when nothing is booked. Give it the customer from find_customer, or a name, mobile number or email; if two customers share a name it lists both and asks which, rather than picking one. Cancelled, declined, finished and draft jobs are left out. Two pickups either side of the border come out in the order they actually happen, not the order their clocks read.

• find_customer no longer calls a future booking someone's "last trip". It used to report whichever of the customer's bookings had the latest date, even one next week or one that was cancelled, so their next job could only be guessed from it. "Last" is now the most recent trip already taken, and each customer shows how many jobs are booked ahead.

• Times from a driver's assistant now say whose clock they are, e.g. "Fri 26 Sep, 9:00 am (NSW)". A pickup's time has always been the pickup's own local time, but nothing said so, and my_schedule described every time as Brisbane time. Across the border that is an hour's difference for half the year.

3.17.0

23 September 2026

• The front page now tells the story: rideshare, the right way up. A six-slide story (how rideshare has worked, the flip, and what changes for drivers, riders and operators), cards that turn over from "the old way" to "the JollyDrivers way" as you scroll, the life of a booking, a section on connecting your own AI assistant with example conversations, and a look under the bonnet. It is animated, but every word is in the page itself, so search engines and AI assistants read all of it. Anyone whose phone asks for less motion gets it standing still.

• The work behind it, counted by the code. The front page shows how many commits, merged pull requests, releases, automated tests and lines of source code have gone into JollyDrivers, and how many days since the first line. The figures are counted from the repository every time JollyDrivers is built, never typed in.

• A blog, at jollydrivers.com.au/blog, with the first two posts: Rideshare, the right way up and Bring your own AI. The latest posts also appear on the front page, and there is an Atom feed for news readers. A post can be written ahead and dated for the day it should appear.

• System Admin → Public site is a new page for everything the public sees: the contact details (moved here from Settings), JollyDrivers' social media accounts, and a launch countdown. Social links appear on the site only once an account's address is entered, and each must be on its own platform's site. The countdown shows on the front page only once a date is set, and disappears by itself when the moment passes. Every change is recorded in the settings change log.

3.16.0

23 September 2026

• jollydrivers.com.au now has a front page. The bare address used to open straight onto the sign-in card, and an AI assistant pointed at it read 87 words — some of them the "connection dropped" message the app keeps hidden. It now opens on a page that says what JollyDrivers does for operators, drivers and riders, how a booking goes from a chat to an invoice in the operator's own Xero, what JollyDrivers deliberately is not, how to connect your own AI assistant, and how to get in touch. It is plain HTML that any crawler or assistant can read without running the app, and it is laid out for phones first.

• Sign-in has moved to jollydrivers.com.au/signin. Nothing else about it changes. If you are already signed in, the bare address still takes you straight to your dashboard, and the installed app opens on the sign-in card as before.

• The public contact details are now set in System Admin → Settings → Public site — contact: an email address, an optional phone number, an introduction and an optional reply-time line. The email address follows the setting everywhere JollyDrivers publishes it — every public page, the summary for AI assistants (llms.txt) and the public AI endpoint — and every change is recorded in the settings change log with the name of whoever made it.

• Behind the scenes: the public pages' source files no longer answer at a second address (/public/about.html and the rest now redirect to the real page), and the front page's "Connect your AI" section only appears while the public AI endpoint is switched on.

3.15.0

23 September 2026

• An operator's AI assistant can now raise a booking's invoice in Xero — always as a draft. propose_raise_invoice works out exactly what the trip page's Request invoice would raise, using the same code, and writes nothing while doing it: the lines with their account codes, the total, the due date, and which Xero contact it goes to — or, plainly, that a NEW contact would be created, which stays in Xero once made. raise_invoice then raises that exact draft, once, within ten minutes, and refuses if anything about it has changed since. A draft sends nothing to the customer and can be deleted without trace; approve it with approve_invoice when it is right. If several Xero contacts could be the customer it refuses rather than guess, and a delivery's invoice is still raised from the trip page. Behind Features:McpOperatorWrites.

• A booking can no longer end up with two live invoices. The trip page only ever offered one, but the rule now lives where the invoice is raised, so no other way in can raise a second while the first stands; void it first and a new one can be raised as before.

• Raising an invoice now shows on the booking's timeline, naming who asked for it and whether it went in as a draft. Before, a single booking's invoice appeared with no line saying who raised it.

• Behind the scenes: a raise refused because an account code is blank no longer leaves a new saved bill-to behind for the customer.

3.14.0

23 September 2026

• An operator's AI assistant can now send the customer their confirmation. propose_send_confirmation works out exactly what the trip page's Send confirmation would send — the ride confirmation, or the completion notice or receipt once the trip is done — to the booking's own customer and passenger addresses, sent as the operator, with the same subject; it lists every recipient, the sender and what happens to the invoice (including, plainly, that a draft invoice is approved in Xero first and that neither the email nor the approval can be undone). send_confirmation then sends that exact plan, once, within ten minutes, and refuses if anything about it has changed since. It never takes an email address, so nothing a customer wrote can redirect a document. It is refused where the page's own checks would stop it — a booking not confirmed yet, a trip whose progress was never recorded, a completion notice whose invoice is not approved — and it is for passenger bookings; a task's confirmation is sent from the trip page. Behind Features:McpOperatorWrites.

• A confirmation sent from an assistant shows it on the timeline, with the admin's name beside the operator's when the admin was acting.

3.13.0

23 September 2026

• An operator's AI assistant can now approve a draft invoice. When JollyDrivers raised a booking's invoice in the operator's Xero as a draft, propose_approve_invoice shows it — the number, the total, the due date and every line — says plainly that approving cannot be undone (an approved invoice keeps its number for good and can only be voided afterwards), and says whether a completion notice to the customer is waiting behind it; approve_invoice then approves exactly that invoice, once, within ten minutes, and refuses if anything on it has changed since. Like the trip page's Approve button, a completion notice that was queued behind the approval goes to the customer straight after. Only a draft JollyDrivers raised itself can be approved this way. Behind Features:McpOperatorWrites.

3.12.0

23 September 2026

• An operator's AI assistant can now cancel a booking. propose_cancel_booking takes the reason from the same list as the trip page's cancel window (the booker cancelled, weather, a duplicate and so on) and an optional note, checks the booking exactly as the page's Cancel button does, and shows what would change — including, plainly, an invoice that cancelling does NOT void; cancel_booking then cancels it once, within ten minutes, through the same door as the page. The timeline shows "Cancelled by operator" with the reason. Nothing is sent to the customer or the driver, and it can be undone from the trip page's timeline. A completed trip is not cancelled this way: turning one into a cancellation settles its invoice, and stays with the driver and the admin. Behind Features:McpOperatorWrites.

3.11.0

23 September 2026

• An operator's AI assistant can now put a driver on a booking. propose_assign_driver finds the driver by name among the operator's active fleet and checks the job the way the bookings page does — the compliance verdict, a clash with the driver's other jobs for this operator, and a party bigger than the vehicle carries — and shows all three in the proposal instead of asking; assign_driver then makes that one assignment, once, within ten minutes. As on the bookings page it is for bookings with no driver yet, and only open ones. Nothing is sent to the driver or the customer; the job appears in the driver's trips. Behind Features:McpOperatorWrites.

• A driver can only ever be assigned from the booking's own operator's active fleet. The bookings page only ever offered those drivers, but the rule now lives where the assignment is written, so no other way in can put a driver from another business, or one who has left, on a job.

3.10.0

23 September 2026

• Operators can now cancel a booking and send the customer their confirmation from the trip page. Both buttons were the driver's and the admin's alone; an operator runs the book and the customer rings them, so they are the operator's too, in exactly the same windows — cancel on any booking that has not finished, and the confirmation (or completion notice, or receipt) from confirmed onward. Reclassifying a completed trip as a cancellation stays with the driver and the admin, because it changes an invoice already issued.

• When an operator cancels, the reason is kept. The trip page has always asked why, and for some time the answer went nowhere. An operator's cancellation now shows on the timeline as "Cancelled by operator" with the reason and any note beneath it.

• A confirmation now records who sent it. Every send used to be written as the booking's driver, whoever pressed the button; the timeline now names the person who actually sent it. Automatic sends are recorded as before.

• The send-confirmation window says what really happens: JollyDrivers emails it to the people listed, sent as the operator. It no longer says the operator will deliver it, no longer mentions a PDF, and no longer refuses to send when the operator has no notification email — that address has played no part in sending since JollyDrivers began sending confirmations itself.

• Creating a booking from an operator's AI assistant again says the confirmation is sent from the trip page — true now that operators have the button.

3.9.0

23 September 2026

• An operator's AI assistant can now accept or decline a booking that is waiting. Two new pairs of tools on an operator connection (or the admin acting as one): propose_accept_booking and propose_decline_booking find the booking in the operator's own book, check it exactly as the trip page's Accept and Decline buttons do, and change nothing — they show the booking, what would change and a proposal to approve; accept_booking and decline_booking then carry out that one proposal, once, within ten minutes, and refuse if the booking has changed in the meantime. Nothing is sent to the customer either way. The timeline records the operator's name "via AI assistant", with the admin's name beside it when the admin was acting. Behind a new switch, Features:McpOperatorWrites, off by default, which covers every operator change made from an assistant; accepting also still needs Features:OperatorAcceptance.

• Creating a booking from an operator's assistant no longer tells you to send the customer's confirmation from the trip page. An operator has no such button — the driver sends it from theirs — and the reply now says so.

3.8.0

23 September 2026

• An operator's AI assistant can now read the book. Four new tools on an operator connection (or the admin acting as one): bookings_board shows the bookings as the board does — today, upcoming or past, filtered by status, to unassigned jobs, or to jobs still owing money — with the driver and paid state on every line; booking_detail opens one booking by reference with route, driver, fare, what has been paid and the invoice if there is one; fleet_status lists every active driver with their vehicle and whether the app rates them available, on a trip, off duty or blocked out right now; unpaid_invoices lists open invoices oldest-due first, flags overdue ones, and adds the completed jobs that owe money with no invoice yet. Everything is read-only and scoped exactly as the operator's own pages are; assigning, accepting and invoicing from an assistant are still to come.

3.7.2

23 September 2026

• Operators can now let the JollyDrivers admin act as them too. The "Let the JollyDrivers admin act as me" switch appears on an operator's account page as well as a driver's, and act_as runs the admin's assistant in that operator's own book — bookings it makes land there, with the admin's name recorded beside the operator's. list_delegations says whether each person would be acted as a driver or an operator. The operator tools an assistant has today are the booking ones; the bookings board and invoices are still to come.

3.7.1

23 September 2026

• Drivers can now see everything the admin has done as them. Under the "Let the JollyDrivers admin act as me" switch on your account page there is a log of every action taken while acting — what was looked at, what was changed, when it started and stopped — newest first. Nothing in it can be edited.

• A Delegation Ledger for the admin, beside the Security Ledger: every stretch of acting as somebody, every call in it, filterable by person and by tool, with a shortcut from the user list for anyone who has granted access.

3.7.0

23 September 2026

• The JollyDrivers admin can now act as a driver from their own AI assistant. Three new tools on the admin connection: list_delegations shows every driver who has switched on "let the JollyDrivers admin act as me", act_as switches the connection to run as that driver — their trips, their passengers, their bookings — and stop_acting switches back. While acting, the admin's own tools are off, and every answer opens with "[as driver: John, by admin Jolly]" so there is never any doubt who is doing what.

• The driver is told, and everything is recorded. When acting starts the driver gets a text (or an email if there is no usable number), and every call made while acting — reads included — is written to a delegation ledger naming both people, the tool and what it answered. Stamps, texts, bookings and wishes made while acting carry the admin's name beside the driver's on their own trails.

• Acting ends by itself after 30 minutes without a call, when the driver turns the switch off, when the admin disconnects the assistant, or when delegation is switched off — and the next answer says why. It cannot be nested.

3.6.3

23 September 2026

• Drivers can now say whether the JollyDrivers admin may act as them. A new panel on your account page, "Let the JollyDrivers admin act as me", has one switch per admin. It is yours alone: the admin cannot turn it on, and you can turn it off at any time. Each change is kept as a dated record, so there is always an answer to "when did I allow this". Behind Features:McpDelegation, off by default. Acting itself is not switched on yet; for now the switch records your choice for when it is.

• The admin's user list shows who has allowed it, read-only, so they can see at a glance whose account they could act for once the tools arrive.

3.6.2

23 September 2026

• The trip timeline, the wishlist trail and "me too" can now record that an admin did something on a driver's behalf. Every stamp, booking, text and wish already names the account it ran under; each of those records has gained a place for a second name, the admin whose hand actually did it, and the timeline reads "John via AI assistant (by admin Jolly, acting as John)" when it is set. Nothing sets it yet — this is the second step towards letting the JollyDrivers admin act for a driver from their assistant (docs/mcp-admin-delegation-design.md), and every existing record is unchanged.

3.6.1

23 September 2026

• Every answer from a connected AI assistant now opens with who it is acting as — "[as driver: John]" — on every JollyDrivers tool, refusals included. Groundwork for letting the JollyDrivers admin act for a driver from their own assistant (design in docs/mcp-admin-delegation-design.md); nothing can act as anybody else yet.

• An assistant that reaches for a tool its connection cannot use is now told what context is missing rather than a bare "not for you": a driver connection is told which role to reconnect as, and the admin connection is told that acting as a driver is not switched on yet. Behind the scenes all fifteen tool classes now get their identity from one place, and a build check stops a new tool reading it anywhere else.

3.6.0

23 September 2026

• Every time in a customer's email now says which state's clock it is. A trip's pickup and arrival, the "as at" line on an itinerary, a delivery's collected and delivered stamps and its deadline all read like "6:30 PM (AEDT · NSW)". Before, the timezone only appeared when JollyDrivers could prove you might misread it — which is a fair rule on screen, where it knows where you are, and the wrong one in an email that could be opened anywhere. On an itinerary listing trips either side of the border it left two clocks an hour apart with nothing to tell them apart.

• A place with no street number — "Coolangatta Beach, Queensland" — no longer loses its state. Addresses like that come back from the map with the state spelled out and no postcode, and JollyDrivers could not read either, so it fell back to showing that stop in the pickup's clock. A Banora Point to Coolangatta trip therefore printed an arrival an hour out.

• Changing a stop to an address in another state now moves that stop's clock with it. A booking's timezone was worked out once and then kept, so editing a drop-off from Tweed Heads to Queensland left it still reading as New South Wales — permanently, and with nothing on screen to say so. One customer's itinerary went out with an arrival time an hour before it will happen. The five bookings already affected have been corrected. If a new address can't be placed, JollyDrivers now says so instead of quietly keeping the old state.

3.5.0

22 September 2026

• A customer's card can now find their other bookings saved under a different spelling of their name, and put the right name on all of them at once. Open the customer, choose Find bookings saved under another name, type the name they were saved under, and tick the ones that are really them. This is the bulk correction that was withdrawn on 3.4.1 for offering to relabel one customer's trips as somebody else's — it comes back on the card rather than firing by itself after a booking is corrected, it starts with nothing ticked, and it searches the name you type rather than guessing which names look close enough. Bookings already showing the customer's name are left out, since there is nothing to fix on those.

3.4.2

22 September 2026

• Behind the scenes: the release index — the depth layer an assistant reads behind this changelog — credited every release with the previous release's pull request, so the record of what shipped where pointed one release off all the way down. Each release now carries the pull request that actually delivered it, and nine releases that had none recorded now do.

3.4.1

22 September 2026

• Setting the travelling passenger now changes that one booking and nothing else. After recording who actually travelled, JollyDrivers went on to offer to apply the same person to every other booking still carrying the old name — 26 of them, all pre-ticked. On exactly the booking this feature is for, that old name is the booking customer's, so it was offering to relabel their own trips as their friend's. The step is gone.

3.4.0

22 September 2026

• A booking can now say who actually travelled, separately from who booked it. Some trips were recorded as if the booking customer had travelled themselves, when really they'd booked it for someone else. The Set travelling passenger action on the trip page now lets you correct that: search for or type who actually rode, and the booking customer stays exactly who they were — still the one who's billed — even on a booking that never had a saved card for them before.

3.3.2

22 September 2026

• The booking chat no longer asks "Ready to submit?" — it goes straight to the booking summary. Once the payment method is answered, the summary card appears with its Submit, Save as Draft and Cancel buttons; that card was always the real confirmation, and the extra question in front of it was where bookings were getting stuck on a blank last turn. A note can still be typed at any point, before or after the summary.

3.3.1

22 September 2026

• Corrected, and it was live for about an hour: the FAQ said JollyDrivers charges $3.30 on each settled booking when it is charging nothing. The fee was set yesterday with charging not starting until 2027, and the page took the amount from the setting but ignored the start date. It now says plainly that nothing is being charged yet, and from when — while still giving the price and the free-under-$30 rule, so nobody has to guess what is coming.

• Fixed: a date typed into Start charging from was read as UTC rather than Brisbane, so charging would have begun at 10am on the chosen day instead of midnight. Any booking settled that morning would have been free.

3.3.0

22 September 2026

• What JollyDrivers charges an operator for a booking is now a setting, not a number buried in the code. System Admin → Booking fee sets the standard fee and, if you want, a different one for a particular operator. Every change is dated and kept: a booking that has already settled keeps the fee that applied on the day, so changing the price never rewrites what was already owed.

• A small job can now be free outright. Set a figure and any booking below it is not charged at all — not a reduced fee, nothing. This replaces the old idea of capping the fee at 5% of the fare, which had the side effect of making the fee a percentage of every fare under $66. Flat above the line, free below it, and never a share of anybody’s fare.

• The fare that threshold is measured against is what the operator actually earned — the fare less tolls, airport access and the levy, which were only ever passing through. A $34 job carrying $6 of tolls counts as $28, and is free.

• Fees now accrue on a ledger once a booking has been paid in full, whether that was cash, a card on the operator’s terminal, a bank transfer or an invoice. Each line records the booking, what it was worked out from and what made it billable, so any figure can be traced back to the job that produced it. A booking that is refunded or deleted has its fee taken back off.

• You can count without charging. Set a date for charging to start, and every booking that settles before it is recorded at the fee it would have carried — owing nothing. Leave the date empty to charge straight away. This is not the same as setting the fee to $0.00, which records the booking as having been worth nothing: with a start date you keep the number, which is the whole point of counting before you bill.

• Nothing is being charged to anybody. No invoice is raised and no money moves — that part is not built. Accrual is also off until it is switched on, and a booking that settles before a fee has been set accrues nothing.

• Each operator now has a statement, month by month, on the same screen: how many bookings were charged, what they came to, how many were waived or not billed yet, and what was not charged. And a CSV download of every line, carrying the booking, the figure the fee was worked out from and why it came out the way it did — so the fees can be read, kept, or keyed into Xero by hand without waiting for anything to be connected.

• A booking that was waived records a line showing $0 and what it would have been, so what the free-below-the-line rule costs is a number rather than a guess.

• The fee on the FAQ now comes from the setting itself rather than from a sentence somebody typed. Change the fee and the public page changes with it — previously it could have gone stale without anyone touching it.

• Corrected: the FAQ said the fee is “held down to 5% of the fare”. With a free-below-the-line rule instead of a cap that is no longer what would happen, and two different claims about one fee could not both stay published.

3.2.4

22 September 2026

• Corrected: How it works still said card payments go through Stripe. They do not. A card is taken on the operator’s own terminal and recorded here against the booking — JollyDrivers does not process the card. It sat in a list beside Xero and Google Maps, which are live, so it read as a description of what happens to your customer’s money.

• Corrected: the same page promised drivers “the operator’s statement to you by email”. Earnings statements are live; the emailed one is not, and the sentence made one claim out of two.

• Corrected: it also still called peer checking of compliance documents “not live”. That was fixed on two other pages yesterday and missed here.

• Added: both the FAQ and How it works now say JollyDrivers is in closed beta, and where to write. The summary AI assistants read has said so for a while; the two pages a person actually lands on did not, so they read as an open door.

3.2.3

22 September 2026

• What JollyDrivers charges is now on the FAQ: a flat $3.30 including GST on each settled booking, never charged to the passenger. On a short run it is held down to 5% of the fare, so it can never be a large slice of a small job. Nothing is being charged yet — this is the price being stated plainly rather than a bill arriving.

• Corrected, and this one matters: several pages said JollyDrivers takes “no commission and no share of any fare” and one said “never a percentage of the fare”. That was wrong. The fee is flat, but the 5% cap means that on a small fare it is a percentage of it — the cap working in your favour, not a commission. The pages now say what is true: the fee never rises with the fare.

• Corrected: the public summary said peer checking of a driver’s compliance documents was “not yet live”. It has been live for some time.

• Corrected: the description of connecting your own AI said every tool is read-only. That is true of the sign-in-free one; the account endpoint can write, and now says so.

• And a test now refuses to let any of those sentences come back. Two releases ago the same wording was fixed in one file and left in five others, because the rule lived in a commit message rather than in the build.

3.2.2

21 September 2026

• Changed: two lines in the description JollyDrivers gives of itself were promises rather than descriptions — one about what JollyDrivers charges, one about where money sits. Both now say what the software does, which is the part anybody can check. Nothing about fares, invoicing or payments changed; only the words repeated back when somebody asks an AI what JollyDrivers is.

• The difference matters because those words are now answered automatically to people who have never signed in. “We take nothing from the passenger” is a commercial undertaking that could stop being true without anybody editing a file. “The fare comes from the operator’s own fare book” is a fact about how it works, and it stays true or the code changes.

3.2.1

21 September 2026

• Corrected: the note below about the map of what JollyDrivers can do said eleven jobs. There are twelve. It was counted off the list a driver sees, which leaves out the one only a platform admin has, and nothing was checked against the map itself. The entry below now says twelve.

• Worth saying why a wrong word got its own release. The map exists because the previous description of JollyDrivers went stale and nothing noticed. The checks added with it prove every part of JollyDrivers is described — they cannot prove the sentence about the map is right, and the very first one was not. Leaving it wrong on a page written to be read by strangers would have been the same failure in miniature.

3.2.0

21 September 2026

• New: ask an AI what JollyDrivers can do and the answer now comes from JollyDrivers itself. There has been a way for anyone’s assistant to ask that since September, but the answer was a paragraph somebody typed by hand, and nothing made it keep up. It now comes from a map of what JollyDrivers actually does — twelve jobs people are trying to do, from taking a booking to getting paid — and anything not fully live says so.

• The map cannot quietly go out of date. Every switch in JollyDrivers and every tile on your board has to belong to one of those jobs, checked on every build in both directions. Add something new and the build stops until somebody says which job it is part of. That is the whole point: the last document that tried to describe JollyDrivers went stale because nothing was checking it.

• Fixed, while we were in there: the check that decides whether a change needs a full build had two files fighting over one name, and the changelog lost. Every release since has been skipping the tests that read it. It does not any more.

3.1.0

21 September 2026

• New: the JollyDrivers changelog is public. Everything you are reading is now at jollydrivers.com.au/releases with no sign-in — so you can send somebody the link, and so an AI asked “is this thing still being worked on?” can answer without an account. That is a question anyone weighing up software asks early, and until today JollyDrivers had no way to answer it. The What’s new page inside the app is unchanged.

• The public page shows what this file says and nothing more. No commit numbers, no database changes, no list of internal switches — that record exists, it is useful, and it is deliberately not on a page anyone can read.

• Some older entries have been reworded, and it is worth saying why. A few quoted real invoice numbers and one real customer’s fare. One printed the word you type to confirm the most consequential thing an operator can do. Four described how our SMS provider proves to JollyDrivers that a message really came from it. None of that belonged in a file written for the people who use JollyDrivers, so it has been taken out of the file itself rather than hidden from one view of it.

• There is now somewhere to write to: hello@jollydrivers.com.au, on the About page and in the summary AI assistants read. Until today the one place that invited people to get in touch pointed them at a page with no way to do it.

3.0.3

21 September 2026

• New: paste a link to a JollyDrivers page into a message, a chat or a post and it now arrives with a title and a short description instead of a bare web address. Two of the three public pages had nothing to show, so they showed nothing — which is a poor first impression of a business you are asking somebody to trust with their bookings.

• The front page now says who JollyDrivers is in a form a machine can read, not only in words. Until today an AI arriving at jollydrivers.com.au had to fetch a second page before it could tell you what company it was even looking at.

• Those two descriptions of the business live in separate files, and nothing joined them up. They are now checked against each other on every build: if they ever drift into describing two different organisations with the same name, the build stops. That is the sort of thing nobody notices for a year.

• The summary an AI reads about what JollyDrivers can do now mentions that it can ask JollyDrivers questions directly, rather than only read about it.

3.0.2

21 September 2026

• New: you can now tell somebody to point their own AI at jollydrivers.com.au and get a real answer. JollyDrivers has had a sign-in-free way for an AI assistant to ask it questions since September — what JollyDrivers is, what an operator, a driver or a rider can each do, how it differs from a rideshare app — but nothing on the site said so, so the only people who could use it were the ones who had already been told the address. The summary for AI assistants, the About page and the crawler instructions now all print it. It needs no account, everything it answers is read-only, and it reads no bookings and no personal details.

• Fixed: the site map left out the front page entirely, and gave two pages a date older than the last time they actually changed — so a search engine or AI could be told nothing had moved when it had. The privacy page had no date at all.

• Fixed: the description that shows when you install JollyDrivers to a phone home screen still called it a “trip request platform for private hire and airport transfers”. That was written in April and describes a different product.

• The Stripe sample pages are no longer offered to crawlers. Nothing secret was on them, but they are scaffolding, not a description of JollyDrivers.

• And none of this is left to somebody remembering any more: a test now reads those files and fails the build if a public page goes missing from the site map, an entry loses its date, or the address stops being printed. Until today nothing in the test suite had ever read them.

3.0.1

21 September 2026

• Fixed: when somebody asked their own AI assistant about JollyDrivers, and it asked us how to connect, it was told that account access “is being built and is not yet live”. It has been live since September, running for a small pilot — so the question an interested operator or driver is most likely to ask was being answered with a no. It now says what is true: the address to add, that it is a pilot you ask to join rather than something open to everyone, and that riders cannot connect an assistant yet.

• The same answer promised “the same address” without ever giving one, anywhere. Both are now in it — the sign-in-free one any assistant can use, and the account one — and a test now holds them to the real endpoint, so renaming it fails the build instead of quietly sending the next person who asks nowhere.

3.0.0

21 September 2026

• JollyDrivers can now help build itself, and nothing it suggests happens until somebody says yes. That is a different kind of software from the one you were using yesterday, which is why the number jumped instead of ticking along. There is no version 2 — the shape changed here, not gradually.

• Your ideas now go somewhere. There is a Wishlist for the thing that isn't broken and has no date on it: the thought you had while doing something else. It is shared, so you can see that somebody already wished for the thing you were about to ask for and back theirs instead of raising it twice. How many people want something is the order the list is in, because on a list of ideas that is the only honest signal there is.

• And they come back to you. When something you asked for goes live, your own reports page says which release it went out in and what else came with it. An idea that was decided against stays on the list with the reason — that is the answer you are owed, and hiding it would only invite the same wish again next month.

• One person approves every idea before anyone builds it, and that cannot be delegated to a machine. An AI assistant connected to JollyDrivers can suggest an idea, read the backlog and do the work — but it cannot authorise its own suggestion, however it is asked. That approval happens inside JollyDrivers and nowhere else. Saying no to an idea needs no approval at all; only saying yes does.

• Every change an assistant makes says so. A decision made by an AI and one somebody typed themselves must never look the same a year later, so the record names both the person and the assistant they used.

• JollyDrivers now keeps a record of why it is the way it is — what each of its hundred-odd releases touched, what it came from, and, where somebody wrote it down, the reason. Where nobody wrote a reason down, it says so rather than guessing.

• Nothing in JollyDrivers runs off on its own. Every improvement above started with a person asking for it.

1.4.98

21 September 2026

• Fixed: the Status list on a report now reads in the order the work actually goes — New, Triaged, Planned, In progress, Resolved, Won't fix, Duplicate, Closed. Planned used to sit dead last, below the three statuses that mean it is over, and on a normal window it was below the fold entirely: you had to scroll past the endings to find the one that says "agreed, not started yet", which on a wishlist is the one you reach for most. Nothing about your existing reports changed — only the order they are offered in.

• While we were there, every other list in JollyDrivers that offers you a set of choices was checked for the same thing. Twenty-one of them, and this was the only one that had gone wrong.

1.4.97

21 September 2026

• New: a wish now has to be approved before anyone builds it. Anybody can still put an idea on the wishlist, and that has not changed. But a wish cannot be moved to In progress or recorded as Resolved until the platform admin has authorised it, on the report's own screen. There is an Approve this to be built button there, and until it is pressed nothing happens.

• This is the one thing a connected AI assistant cannot do for you. An assistant connected in the admin role can set every other status as you — so "only the admin can do it" would not have been a limit on an assistant at all. It could have suggested an idea, approved its own idea as you, built it and shipped it, and every line of the record would have read exactly as if a person had decided each step. Approving is deliberately available in JollyDrivers itself and nowhere else.

• Saying no still costs nothing. Declining a wish — won't fix, duplicate, closed — needs no approval at all. A gate that made refusing an idea as ceremonious as agreeing to one would just mean ideas sat unanswered.

• Bugs and change requests are not gated. Something already broken, or somebody already blocked, should not wait for a signature — least of all anything about money or safety. Only wishes, which are the kind that can breed.

• Approval is recorded with who gave it and when, and the person who suggested the idea is told: being informed that your idea was agreed to is better news than a status change. It can be withdrawn again, which is also recorded — an approval reconsidered is a normal thing, and a gate you cannot close again is one people stop opening.

• There is no setting to turn any of this off. A switch that disables the gatekeeper would not be a gatekeeper.

1.4.96

21 September 2026

• Fixed: an attendance job — a dog walked, a garden watered — was being called a delivery in four places. It isn't one. It carries nothing, goes nowhere, and has one stop rather than a route, and the words on screen now say so.

• The one that stopped you working: opening an attendance job to change its time or its price was refused with "A delivery needs at least one described item". An attendance job correctly has no items, so there was nothing you could do to satisfy that — the only way to edit one was not to. Creating one was always fine; only editing was blocked.

• Every list that shows jobs — your trips, the bookings board, deliveries, the calendar, the admin lists — described an attendance job in a delivery's words: "Delivered" when it was done, "In transit" while it was happening, "Awaiting operator" when nobody was waiting for anything. It now reads "Done", "In progress" and "Operator notified".

• The calendar's peek panel opened an attendance job under the heading "Delivery", and the edit window called it "Edit Delivery". Both now say Task.

• For anyone using a screen reader: the calendar announced every attendance job as "delivery number 000". It now says "task number 000" — and where JollyDrivers hasn't been told which kind of task a job is, it says the general word rather than guessing.

1.4.95

21 September 2026

• The wishlist now shows an admin a Work this link on each idea, straight through to the screen where a decision is made and recorded. The board itself is unchanged and still looks the same to everybody: it is one link, and only the platform admin sees it. Before this, an admin reading a wish had no way to reach the only screen that could act on it — you had to already know the queue existed and go and find the idea again by its reference, which is a thing you can only know if you built it.

1.4.94

21 September 2026

• Fixed, and found by using yesterday's release: when you connect an assistant as the JollyDrivers admin and ask it who it is, it was told about booking a job and looking up addresses — things that connection has no book for and cannot do — and was never told about the support backlog, which is the only reason it exists. It now describes the four things it can actually do, and says plainly that it cannot touch bookings, money, operators, drivers or settings.

• That answer also used to say "Drives for: no operator yet" to an admin connection. True, and it read like something had gone wrong rather than like the design. It now says the connection covers the support queue and has no book of its own.

• Fixed, on the audit trail: a wish added through an assistant was recorded as raised by you, with no mention that an assistant did it — while every other change an assistant makes says so. The promise on the connect screen is that everything is recorded as done by you through that assistant, and a record that keeps that promise for most of its lines and not the rest is worse than one that never made it. A wish you type on the wishlist page yourself is unchanged, and still says only your name.

• Fixed: "raised by a admin".

1.4.93

21 September 2026

• New for the platform admin, switched off for now: JollyDrivers' own support backlog can be worked through a connected AI assistant. Ask it what is outstanding and it answers worst first — how serious, how many people want it, how long it has sat — and it can read any report in full, with everything that has been done about it.

• It can also change a report: its status, how serious it is, what it is about, and what the person who raised it is told. Nothing it decides is written until you have been shown the exact words that person will read, and said yes. Closing something without a reason is refused outright, because a "Won't fix" with nothing beside it is the surest way to stop somebody ever reporting anything again.

• Working notes are different: a note only the JollyDrivers team sees is added straight away, with no approval step, and there is no way to ask for one that the reporter can see. Anything they read goes the long way round.

• This is the first time an assistant can act as the administrator, and it stays narrow. Choosing it is a separate option when you connect, so a driver or operator connection you already have gains nothing. It unlocks the support queue and nothing else on the platform — an admin connection can see fewer bookings than a driver's can, not more.

• The switch that allows it is a real off switch. Turning it off does not merely stop new connections: it is checked every time the assistant asks JollyDrivers for anything, so a connection already running stops working immediately. Losing the admin role does the same.

• Every change an assistant makes is recorded on the report as made by you through that assistant, by name. A change made by an AI and one you typed yourself must never look the same a year later.

• The page you see when connecting an assistant no longer promises it will never act as an administrator, because for this one option that would not be true. It now says exactly where that ends.

1.4.92

21 September 2026

• New: a Wishlist. Report a problem is for something that is broken right now; this is for the other thing — the idea you had while doing something else, that nothing depends on and nobody is waiting for. Write it down, say roughly what it is about, and it keeps.

• The wishlist is shared, so you can see that somebody already wished for the thing you were about to ask for and say "me too" instead of raising it twice. How many people want something is the only honest signal a list of ideas has, so it is the order the list is in. Who had an idea is not shown: it should be weighed on what it is.

• An idea that has been agreed to now says so — Planned — rather than sitting on "we've read it" for months, which is indistinguishable from being ignored. Ideas that were decided against stay on the list with the reason, because that is the answer you are owed and hiding it invites the same wish again next month.

• When something you reported goes live, your own reports page now says which release it went out in and links to what else came with it. It is checked against the changelog that shipped with the running app, so it can only ever name a release that actually exists.

• Report a problem still only offers "something's broken" and "I'd like a change". An idea for one day is a link to the wishlist rather than a third option: the page is open when something has already gone wrong, and that is the worst moment to be asked to sort your own thoughts into categories.

• Behind the scenes, and only visible to a connected AI assistant: JollyDrivers now keeps a second, deeper record of every one of its 98 releases — what each one touched, which change it came from, which switches and database changes it carried, and what it is broadly about. Ask your assistant how invoicing got to where it is, or what JollyDrivers has ever done about text messages, and it answers from that rather than from what it can infer. Where nobody wrote down why something was done, it says so instead of guessing.

• Your assistant can also read your own reports and the wishlist, add a wish once you have read it back and agreed, and back somebody else's. It cannot change a status, a severity or a decision — that stays with the JollyDrivers team, in the app, where it is recorded against a name.

1.4.91

21 September 2026

• New for admins, switched off for now: JollyDrivers can read the privacy mailbox itself, so a request someone emails in appears in the register without anyone typing it up. Each one keeps the date the sender wrote rather than the day it was noticed, which means its thirty days already count the time it spent waiting.

• It reads the mailbox and never changes it. Nothing is marked as read, moved or deleted on the mail server, so what you see in your own mail program is exactly as you left it. The trade is that a fault here can only fail to notice a message — never quietly file one away where you would not find it again.

• Nothing an email says turns into a privacy request on its own. Each message waits for you to say whether it starts a new request, belongs to one you already have, or is not a request at all — and every one of those can be undone. The address is published, so anyone can write to it, and a register that filled itself would be a register nobody could trust.

• Where a message mentions a request reference in its subject, that is shown as something to check rather than acted on. Whoever sent the email typed it.

• Only the deployment holding the real privacy mailbox will ever read it. A test or development copy of JollyDrivers refuses, and says on its own screen that it is refusing — so an empty list never has to be guessed at.

• Junk that reaches the privacy address keeps the record that it arrived, but its text is removed after about three months rather than the seven years real correspondence is kept for.

1.4.90

20 September 2026

• New for admins, switched off for now: a register for privacy requests — somebody asking to see what JollyDrivers holds about them, to have it corrected or removed, to stop being contacted, or to complain. Each one is recorded with the date it arrived rather than the day you typed it up, because a request that sat unopened in the mailbox for a week has already spent a week of the thirty days you have to answer it.

• The register counts those thirty days for you. It shows what is due and what is late, keeps a log of every letter and call either way, and records how you satisfied yourself the person asking was really them — the method, never a copy of their licence. Where a request needs longer you can extend it, but only by saying why and when you told them. Waiting on somebody does not stop the clock.

• The admin dashboard now says so when a privacy request is close to its deadline or past it. That warning appears whether or not the register itself is switched on: a deadline that has already passed is a fact, and a switch should not be able to hide one.

• Nothing is ever deleted from the register — a request raised by mistake is closed as withdrawn, which is itself worth keeping. After seven years the correspondence loses its words while the record that it happened, when, and with whom stays. A privacy register that kept every word for ever would be a poor advertisement for its own subject.

1.4.89

20 September 2026

• Fixed, the same mistake in the pay-link text message: on a group booking billed on one invoice, the text quoted a single trip's share while the link it carried opened the whole invoice. It now names what the customer actually owes. An invoice you recorded by hand is untouched — the figure you typed was already the whole thing.

1.4.88

20 September 2026

• Fixed: on a group booking where every trip is billed on one invoice, the pay button in the customer's email showed a single trip's share instead of the amount they actually owe — half the invoice, with the correct combined total printed further down the same email. The button, the plain-text version and the PDF now all carry the whole invoice. The invoice itself was always right; only what the customer was told to pay was wrong.

1.4.87

20 September 2026

• When you text a customer their pay link, you can now choose who it comes from — your own mobile, your business name, or JollyDrivers' number — from the senders set up for you, and the trip timeline records which one you used. Your own mobile is picked first, because a pay link is the kind of text somebody replies to. If nothing has been set up for you it goes from JollyDrivers' number, as before.

• Fixed: texting a pay link no longer refuses to send when the operator has no notification email set. JollyDrivers sends that text itself and never needs the operator's address — the check was left over from when Jolly Frog's system relayed it. The note box beside it no longer claims to go to the operator either; it is kept on the trip's record.

1.4.86

20 September 2026

• First step towards booking a job through a connected AI assistant, switched off for now: the assistant can turn words into a place JollyDrivers can put on a booking — a street address, a landmark, an airport by name or code, or "home" — and is told the state and time zone that place runs on. Your own saved places and JollyDrivers' airport list are checked before Google, so a regular run costs nothing to look up. When several places fit, the assistant asks which; it never guesses.

• The assistant can also work out which of your saved customers a name, mobile number or email means, and is given just enough to tell two people apart — the last digits of their mobile, their email's domain, and their last trip with you — never a full number. If nobody matches, it says a new customer will be created with the booking. Nothing is created by looking.

• The assistant can now build the booking up with you, in any order — addresses, a pickup time, a return, passengers, a flight, the customer, the fare, how they pay, and how the request reached you (including the customer's own words from a screenshot). After every detail it says what is still missing, in the order the booking chat asks. Times are read on the clock of the place they belong to: a pickup in NSW is NSW time, and when the trip crosses into Queensland the drop-off time is shown in Queensland time. When it has enough, it prepares the booking to read back to you — route, drop-off time, any clash with your other jobs, fare and customer — and nothing is created until you say so.

• When you agree, the assistant creates the booking — the same way the booking chat does: it lands in your operator's book under your name with you assigned, a new customer is saved to your address book only at that moment, the original message is kept on the booking, and the customer's confirmation goes out. A job that already happened is recorded as completed. The trip's timeline shows it was booked by you via your AI assistant. You can also ask for it to be saved as a draft to finish in the app instead.

• Operators can book through their assistant too: the job lands in your own book, confirmed, the same way the New booking page creates it. Name a driver from your fleet to assign them (the assistant checks that driver's calendar for clashes), or leave it unassigned for the app. Nothing is sent to the customer until you send it from the trip page.

• The assistant can look a flight up for an airport job — which of your airports it lands at or leaves from, when in that airport's own time, and the pickup time JollyDrivers would suggest (20 minutes after landing, or the time to be at the airport before a departure) — using the same flight tracking as the airport booking cards, so the same switch and the same allowance apply. Several legs on one number is a question, not a guess.

1.4.85

20 September 2026

• New for admins, switched off for now: each operator can be given their own JollyDrivers sending address from the Operators page. One button creates the mailbox, a second emails the operator a link that confirms it, and if the hosting panel can't be reached the card shows the steps to do it by hand.

1.4.84

20 September 2026

• Trip stages on the trip page now follow exactly the same rules as stages recorded through a connected AI assistant. One visible difference: if you skip a stage, it is filled in with a best guess and marked estimated as soon as you record a later one, not only when you complete the trip. Tap "On board" without having tapped "Arrived" and the arrival appears on the timeline straight away, marked estimated.

• Fixed: completing a task such as a dog walk no longer shows a warning that an operator notification failed. Nothing was being sent, and nothing was wrong.

• The completion and no-show messages no longer say the operator has been notified. JollyDrivers stopped sending those updates when Jolly Frog's system was switched off.

1.4.83

20 September 2026

• A connected AI assistant (such as Claude) can now answer questions about how JollyDrivers has changed, straight from this changelog: what is new, when something arrived or was fixed, and how a feature has grown. Every answer comes with the version and date it rests on.

• Drivers can record a trip stage through their connected AI assistant: on the way, arrived, on board, completed or no-show, now or at a time they say. The assistant shows exactly what it will record and only records it once the driver agrees. The same rules as the trip page apply: nothing in the future, nothing out of order, and any stage the driver skipped is filled in with a best guess and marked estimated on the timeline. Stages recorded this way show "via AI assistant" on the timeline. Delivery jobs still use the trip page.

1.4.82

19 September 2026

• Fixed: a booking group whose invoice is still a draft in Xero can now be marked paid in cash. The draft is deleted in Xero and every trip is marked paid. Before, the Mark as paid button stayed greyed out until the invoice was approved, even when the customer had already paid cash. Card and bank transfer still need the invoice approved first, because Xero won't take a payment on a draft.

1.4.81

19 September 2026

• Fixed: starting a booking from a customer's card now asks the same questions as choosing the customer from the list — how the request came in, and whether that customer is the one travelling (or who is). It used to go straight into the chat assuming the customer was the passenger, and recorded every such request as an SMS.

1.4.80

19 September 2026

• Drivers can send a passenger a ready-made update from the trip page (on my way, running late, I've arrived, meeting your flight, pickup reminder), choosing each time whether it comes from their own mobile or the company name. A connected AI assistant can prepare the same texts and send them once the driver approves. Being piloted before it opens more widely.

• A text JollyDrivers held back (for example on a test account) is now shown on the trip timeline as held back, not as sent.

• The About and How it works pages now say correctly that booking confirmations go by email. They previously said email and SMS.

1.4.79

19 September 2026

• Anyone can now read what JollyDrivers is before signing in: new About, How it works and FAQ pages, linked from the sign-in screen. They are written so that people, search engines and AI assistants asked about JollyDrivers get the real story.

• Behind the scenes: the groundwork for connecting your own AI assistant (such as Claude) to your JollyDrivers account, signing in the usual way. A driver's assistant will be able to answer "what's my next job?" and "what have I got this week?", seeing only what you already see in the app, and connected assistants appear on your Account page where you can disconnect them. Being piloted before it opens more widely; nothing changes for anyone else.

1.4.77

18 September 2026

• Behind the scenes: updates install more reliably. A file the upload tool could not send no longer leaves the site on its "back in a few minutes" page; it is sent another way instead. Nothing you use changes.

1.4.76

18 September 2026

• Fixed: customer emails (confirmation, completion and booking summary) now show each time in the local time of the state it happens in, matching the trip page. A Coolangatta to Murwillumbah trip in summer now reads "5:07 PM (AEDT · NSW)" at the drop-off instead of the Queensland clock's 4:07 PM. Delivery collected and delivered times follow the same rule.

1.4.75

18 September 2026

• Removed (behind the scenes): the retry queue that used to hold a message to Jolly Frog until it could be resent, and two leftover columns from the same era. The queue has been empty since Jolly Frog was switched off and nothing has written to it since. Nothing you use changes.

1.4.74

18 September 2026

• Removed: the code that built messages for Jolly Frog's old system — every message builder, the shared envelope and its version numbers, and the specification and example files they were written against. Nothing you use changes; none of it had run since Jolly Frog was switched off.

• Removed (admin settings): four more switches that only shaped those messages — State-aware wire, Consent receipt, Disbursement notice and Account reference round-trip.

• Changed (a driver's purchases on a trip): the card no longer talks about what the operator's system will pick up. It says the purchase is billed to the customer as its own line, at cost, with no GST.

1.4.73

18 September 2026

• New (attendance jobs): a job like a dog walk or a garden watering now offers the confirmation email and one-tap Complete, as a delivery does. Before, it offered neither.

• Changed (Mark as paid, cancel, change price): the wording no longer says the operator will be emailed. Cash voids the invoice in Xero, card and bank transfer mark it paid there, and a bank transfer still says it comes from the bank account, not the card terminal. Where JollyDrivers doesn't manage the invoice, it says to do it in Xero instead.

• Removed: the retry queue for messages to Jolly Frog's old system, with its "queued for delivery" and "retry delivery" buttons on the trip page, and its switch in admin settings. Nothing is queued now because nothing is sent.

1.4.72

18 September 2026

• Removed: the last messages to Jolly Frog's old system, the invoice or quote request, the request to void an invoice, and confirmations relayed through the operator. Invoices are raised and voided in your Xero, and confirmations go straight to customers, as they already do.

• Changed (Request invoice / Request quote): where an invoice can't be raised in Xero from JollyDrivers, or for a quote, you now get a clear reason instead of a request sent to a system that is switched off.

• Changed (Send confirmation): an operator whose confirmations aren't set to go straight to customers now gets a clear reason instead of a relay through its own system.

1.4.71

18 September 2026

• Removed: the booking and delivery messages JollyDrivers sent to Jolly Frog's old system: new booking, change, cancellation, status (en route, completed, no-show), and the same four for deliveries. Bookings still move to Sent and confirm exactly as before, and a retroactive cancellation still settles its invoice in Xero.

• Changed (trip timeline): those messages no longer leave "sent to operator" lines, because nothing is sent.

1.4.70

18 September 2026

• Removed: three notices JollyDrivers could send to Jolly Frog's old system: that an invoice had been raised in Xero, that a complaint or incident had been recorded, and that a booking had settled directly to the driver. Invoices are still raised in Xero and cases still land in the register, as before.

• Removed (admin settings): the Case notice and Direct settlement notice switches.

1.4.69

18 September 2026

• Removed: the option to have Jolly Frog's old system text a pay link on JollyDrivers' behalf. JollyDrivers sends the text itself, as it already does for you, and "Text the pay link" now shows whenever JollyDrivers' own texting is switched on.

• Removed: the group invoice request message to Jolly Frog. A group is billed as one invoice in your Xero, as it already is; an operator who can't raise invoices from JollyDrivers now gets a clear reason instead.

• Removed (admin settings): the SMS dispatch and Group invoice request switches.

1.4.68

18 September 2026

• Removed: the messages JollyDrivers sent to Jolly Frog's old booking system when a payment was recorded (cash, card, bank transfer, or a payment with no invoice) or an invoice's due date was changed. Payments on invoices in your Xero are still recorded there, exactly as before.

• Changed (Mark as paid): the confirmation no longer says the operator has been notified or asked to void the invoice when nothing was sent.

• Changed (Change due date): on an invoice that isn't in your Xero, it now says the due date can't be changed here, rather than claiming a change was sent.

• Removed (admin settings): the Cash reconciliation, Card reconciliation, Direct payment notice and Due date management switches. Those buttons stay on, as they already were. Bank transfer keeps its switch, which is now an ordinary release switch and still off.

1.4.67

18 September 2026

• Removed: five messages JollyDrivers could send to Jolly Frog's old booking system, which is switched off for good. None were switched on in production, so nothing you use changes. They are the attendance job notice, the driver assignment update, the fleet roster copy, the automatic invoice approval request and the invoice status refresh request.

• Removed (trip page): the "Notify operator" button on attendance jobs, which only sent that notice.

• Removed (admin settings): the five switches for those messages.

1.4.66

17 September 2026

• Removed (admin): JollyDrivers no longer checks the Jolly Frog protocol mailbox for replies, because Jolly Frog is switched off for good. The Protocol Log page loses its Poll Inbox button, auto-poll switch and last-poll panel, and the admin dashboard loses its "Inbox auto-poll" line. The log itself stays, with every message JollyDrivers has sent, including each customer confirmation.

1.4.65

17 September 2026

• Changed (admin settings): the driver accounting switches now keep their order. Driver ledger to Xero can't be turned on while Driver ledger is off, and Driver ledger can't be turned off while it is on, because card takings a driver collected would be booked to a clearing account that nothing ever clears. Turning on Commission RCTI without Driver ledger to Xero now warns that nothing will be issued.

• New: a step-by-step guide to switching driver accounting on, for when the first driver who isn't an owner-driver joins. Each of the four switches on the settings page points to it, and Driver ledger now warns to set a commission before opening anyone's ledger.

1.4.64

17 September 2026

• New (behind Commission RCTI, off by default): when a driver's bill goes to Xero as a recipient-created tax invoice, the driver is emailed their copy straight away. The email holds the whole tax invoice, so it works for drivers without a JollyDrivers login.

• New: the statement page shows that tax invoice to both you and the driver, exactly as it was issued, and it prints with the statement. You also see when and where it was emailed, or, if it wasn't, the date it must reach the driver by and a button to email it.

• Fixed (Driver ledger to Xero): retrying a statement whose payment step failed no longer sends the bill to Xero a second time.

1.4.63

17 September 2026

• New (behind Commission RCTI, off by default): a subcontractor's fleet page can record a recipient-created tax invoice agreement with them. The dialog shows the terms the ATO requires in full and records them only once you confirm the driver has agreed in writing. You can end the agreement there, and changing the driver's ABN ends it.

• Changed (Driver ledger to Xero): a driver's bill carries GST only when it is a recipient-created tax invoice, meaning the switch is on, the driver is a subcontractor with an ABN who is registered for GST, the agreement is recorded, and your ABN is set on Settings → Pricing. That bill is numbered RCTI-JD- and the statement number, and says on it that it is a recipient-created tax invoice, with both ABNs and that the GST is the driver's to pay. Any other bill carries no GST and no RCTI wording, even for a registered driver.

• New: the settings page warns when Driver ledger to Xero is on without Commission RCTI, because drivers' bills then claim no GST.

• Owner-drivers never get one, and their fleet page does not offer it.

1.4.62

17 September 2026

• New (behind Driver ledger to Xero, off by default): a closed driver statement becomes a bill in the operator's own Xero, from a contact JollyDrivers creates for the driver: driving services to the Driver payments account (with GST when the driver is registered), reimbursements to the customer purchases clearing account, adjustments alongside. If the driver collected passenger money in the period, the bill is paid from Driver collections clearing to that extent; a payout the operator records pays the rest from the bank account.

• Changed (same switch): a card payment recorded as received by the driver, on an invoice JollyDrivers raised, is now booked to Driver collections clearing instead of the terminal account, and "Mark as paid (card)" is offered again for drivers whose card takings go to their own account.

• New: two account mappings on Settings → Accounting, Driver collections clearing and Driver payments. Both refuse to post until set. Bills need a permission the Xero connection did not have, so the operator reconnects Xero once; the statement page says so and has a Post to Xero button for retries.

• New: a subcontractor's ABN and GST registration on their fleet page. The ABN goes on their Xero contact; registration decides whether their bill carries GST. Not said is treated as not registered.

• Owner-drivers: nothing is posted in either direction.

1.4.61

17 September 2026

• New (with Driver ledger): statements. On a driver's ledger card the operator closes a statement to the end of a chosen day; it freezes everything not yet on a statement with opening, movement and closing figures, and both sides can open it at any time. A correction to an issued statement appears on the next one; the issued one never changes.

• New: a statement page that prints cleanly, and "Email to driver" which sends it to the driver's address on file and records when it went.

1.4.60

17 September 2026

• New (behind Driver ledger, off by default): a running account between an operator and each driver. The operator opens it from a driver's fleet page, typing an opening balance if one exists. From then on each completed job posts the driver's share, anything they bought for a customer posts as a reimbursement, any payment recorded as received by the driver posts against them, and the operator records payouts and money handed back. The balance is the sum, shown to both sides with whose arithmetic it is.

• New: drivers get a Balance page, one card per operator, with the activity that made the figure. When the operator owes them they can request a payout to their PayID; when they hold the operator's money they can ask for an invoice to settle it. Requests move no money; the operator marks them paid or received with a reference, and that writes the ledger.

• New: on the fleet page the operator sees the same card with record-a-payout, record-money-handed-back, adjustment (with a reason) and refresh. Nothing is ever edited or deleted; a correction is a reversal that points at what it undoes.

• Changed: with the ledger on, the earnings page points at the Balance page instead of showing its own paid split, so a driver never sees two different "paid" figures.

1.4.59

17 September 2026

• New (behind Driver commission rates, off by default): each driver on the fleet page gets a Commission card. Set a rate for that driver — a percentage of their commissionable income, a flat amount per job, or both — from a chosen date, with the history kept underneath. Until one is set the operator default applies, and "Back to operator default" ends the driver's own rate from now.

• Changed: the commission line on a job, and a direct settlement, now use the rate in force when the job was completed, so a rate change never restates a job already done. A backdated rate says on the card how many completed jobs still carry the earlier figure; "Recompute fees" on a trip refreshes it.

• Changed: the operator default on Settings → Pricing is now recorded with a dated history as well as the live value.

1.4.58

17 September 2026

• New: "Mark as paid" now asks who has the money — the operator's account or the driver's own — for cash and card. It is preselected from what JollyDrivers already knows about the driver (the terminal declaration on their fleet page; cash defaults to the driver) and can be changed per payment. An owner-driver is not asked, and a bank transfer is always the operator's. The answer is kept on the payment and shown on the trip timeline as "received by the driver" or "received by the operator".

• Changed: a card payment recorded as going to the driver's own account can no longer be posted against the operator's invoice from the trip page. The money is not the operator's until the driver settles up; recording it in their books arrives with the driver ledger. The no-invoice card path and cash are unaffected.

• Groundwork: every payment recorded before today reads as "not recorded" for this question, never as a guess.

1.4.57

17 September 2026

• Changed: operator commission is now worked out on your income from the trip rather than on the whole price. A toll or airport fee that was absorbed into the price comes out before the percentage is taken, so a $100 fare carrying a $6.40 toll inside it commissions $93.60. Nothing already recorded is changed; the new figure appears the next time a trip's fees are recalculated.

• New: Settings → Pricing has two switches for whether commission applies to extras (baby seat and the like) and to the larger-group premium. Both are on, which is what always happened; switch one off and the driver keeps all of that charge.

• New (groundwork, nothing visible): each toll and airport line can now record who actually paid it, the driver or the operator. Every existing line is marked "unknown" and nothing reads it yet; it is the first step of the driver accounting work.

1.4.56

17 September 2026

• Fixed: delivery receipts now work whether they are configured per message or once for the whole account. An account-level receipt was arriving in a slightly different form and was being refused; it is now read correctly. Proven on a test text: the trip timeline showed "Text delivered to the customer's phone" within a second of the send.

1.4.55

17 September 2026

• New: the SMS inbox page now shows the last calls SMSGlobal made to JollyDrivers, including refused ones, so a missing delivery receipt can be traced without server logs. The first receipt after 1.4.53 never arrived even though SMSGlobal showed the text as delivered.

• Changed: the SMS webhooks now cope with providers that alter the address they are given, so a delivery receipt is no longer refused because of how the request was formed.

1.4.54

17 September 2026

• New: an SMS inbox for the platform admin. Every text that arrives on JollyDrivers's number is kept, matched to its booking where one can be found, and shown on that trip's timeline as "Customer texted back". The admin board shows how many are unread. Until now a reply that was not STOP went to the log and nobody saw it.

• Changed: the Direct Sms setting's warning no longer talks about importing the old operator system's list.

1.4.53

17 September 2026

• New: a text sent to a customer from the trip page now reports back. When the phone receives it the timeline says "Text delivered to the customer's phone"; when it never will (expired, undelivered, rejected) the timeline says so and why. Until now "sent" only meant the SMS gateway had taken the message. Needs delivery receipts switched on in the SMSGlobal account.

1.4.52

16 September 2026

• Changed: the SMS opt-outs page now says what actually happens. A STOP reply adds a number automatically; taking a number back off the list is done on the page by hand. The line about importing the old operator system's list is gone.

1.4.51

16 September 2026

• Fixed: the SMS reply webhook now accepts our provider's notifications however they arrive. Follow-up to 1.4.50.

1.4.50

16 September 2026

• Fixed: replies to the JollyDrivers SMS number (STOP / START) can now reach the opt-out register. The way our SMS provider delivers an incoming message did not match what JollyDrivers was expecting, so replies were being refused. Nothing was lost before this: the provider was never pointed at JollyDrivers until now.

1.4.49

16 September 2026

• Fixed: switching an operator's old booking system off ("My booking system is switched off" on Settings → Accounting) would also have stopped that operator's own customers receiving their confirmation emails. It now silences only the messages meant for the retired system. Found before the switch was ever used.

1.4.48

16 September 2026

• Fixed: a trip that had been billed as part of a group could not be invoiced on its own afterwards — asking for an invoice failed with a database error. Found while testing group consolidation.

1.4.47

16 September 2026

• Changed: settling a whole group by card is offered only when every trip's driver banks card takings into the business's account. One invoice settled by one payment can't be recorded when part of the money went somewhere else — set "Card takings" on each driver's fleet page.

1.4.46

16 September 2026

• New: a driver's fleet page now asks where their card takings land — the operator's account, or the driver's own. JollyDrivers records a card payment into the operator's Xero only when it knows the money reached the operator; otherwise it says so instead of recording it. An owner-driver needs no answer, since they and the business are the same party.

1.4.45

16 September 2026

• Fixed: "Mark as paid" by card or bank transfer was offered while the invoice was still a draft, on a trip and on a group. Xero does not accept a payment against a draft, so it would have failed. Approve the invoice first — the button says so now. Cash is unaffected: it retires the invoice instead of paying it.

1.4.44

16 September 2026

• New: a group's draft invoice can be approved from the group page. It used to say "Pending" with no way to act — you had to open one of the trips to find the approve button. It now reads "Draft in Xero" and has an "Approve in Xero" button of its own.

1.4.43

16 September 2026

• New: a small sync button on each invoice row checks that invoice against Xero on the spot. Opening a trip already checks once, but a void or payment made in Xero while the page sits open was not picked up until the page was opened again.

1.4.42

16 September 2026

• Fixed: a group where only some trips had an invoice called itself "already billed as one invoice", which hid the Consolidate button and left Request invoice greyed out — the group could not be billed at all from the page. It now counts a group as billed as one only when every trip is on that invoice.

1.4.41

16 September 2026

• New: "Consolidate into one invoice" on a booking group whose trips already have invoices of their own. It retires what is there — a draft is deleted and disappears, an approved invoice is voided — then raises one invoice covering every trip in date order. You see exactly which invoices go before anything happens, and a paid invoice is never touched (remove that trip from the group instead).

• Changed: adding bookings to a group no longer offers trips that are already paid. A paid trip has nothing left to bill and can't join a group invoice.

• Fixed: a group showed "Billed as one invoice" when only some of its trips were on that invoice. It now says so only when every trip is covered.

1.4.40

16 September 2026

• Fixed: asking for an invoice left the billing panel saying it was waiting for the operator, even though JollyDrivers had already raised the invoice in Xero — only a browser refresh showed it. The panel now updates on the spot.

• Removed: the "REFRESH · last updated…" row, from under the invoice card and from each leg on the group page. Opening the trip still checks the invoice against Xero, and now says so only when something actually changed.

• Removed: asking for a quote. Quotes were only ever raised by the operator's own system, which is being retired, so a quote request had nothing to answer it. Quotes already on a booking still show.

• Changed: "Request invoice" (was "Request billing artifact") opens with Invoice already chosen, and set to Draft — the invoice is raised in Xero for you to look over, and is approved automatically when a confirmation or completed notice goes out.

• Removed: the two pencil buttons either side of the price on the invoice card. Price and billing method are still editable from Edit trip.

• New: when an invoice is raised, a message names it and its state, for example "INV-0000 is approved in Xero, AUD 000.00" or "INV-0000 is a draft in Xero, AUD 000.00 — approve it to get a pay link."

1.4.39

15 September 2026

• Removed: the "invoice is out of date" notice on the trip page. It kept coming back; change an invoice's wording from the invoice lines window when you need to.

• Removed: the "Invoice header note" box, from the trip's billing card and from the passenger's own trip page. Drivers and operators write whatever they want on the invoice in the invoice lines window instead. A note already saved on a booking still prints on its invoices.

1.4.38

15 September 2026

• New: when a booking's pick-up date, time, addresses or reference change after its invoice was raised, the trip page says the invoice is out of date and lists what it no longer shows. "Update the invoice" opens the invoice lines on the fare line with those changes listed, for you to correct and save to Xero.

• Removed: "Reword with AI" and the saved example library are gone from the invoice lines window. It is now simply the editable description, saved straight to Xero.

• Changed: the description box shows 16 lines.

1.4.37

15 September 2026

• Fixed: "Reword with AI" now actually rewords. It used to hand back the same layout and ignore your direction; it now follows a direction such as "no route detail" or "all on one line", and with no example it writes a short, clean layout.

• Changed: when the booking's details have changed since the invoice was raised (a pick-up time moved, say), the suggestion lists exactly what using it would change on the invoice, rather than changing it quietly.

1.4.36

15 September 2026

• New: on an invoice's fare line, "Reword with AI" rewrites the description, either tidying the current wording or following an example you saved. The date, time, pick-up, drop-off and reference are checked to be copied exactly, and a version with any number that isn't on the booking is never offered. You read the suggestion and choose "Use this" before anything goes to Xero.

• New: "Save this wording as an example" keeps a description you like in a small library shared by the operator and their drivers, to follow on later invoices.

• Changed: the description box in the invoice lines window shows 10 lines instead of 6.

1.4.35

15 September 2026

• New: the invoice card on a trip has a lines button that shows each line of the Xero invoice — draft or approved — one at a time, with its amount alongside. A driver or operator can reword a line's description and save it straight to Xero. Amounts and everything else on the invoice stay as they are; a paid, part-paid or voided invoice opens view-only.

1.4.34

15 September 2026

• Changed: opening a trip now checks its invoice against Xero straight away, so a void, a payment or an approval made in Xero by hand shows on the page without pressing anything. This covers invoices the operator's old system raised too, as long as Xero is connected — they used to say "Waiting for updates…" from a system that no longer answers.

• Changed: the Refresh button reads Xero immediately when pressed, rather than asking you to wait out the cooldown. The nightly check now covers every open invoice in a connected Xero, not only the ones JollyDrivers raised.

1.4.33

15 September 2026

• Changed: under the "View & pay" button on confirmation and completed-trip emails, the note now reads "After payment access your paid tax invoice HERE!" with the pay link on HERE — customers were getting Square's card receipt and not realising the same link shows the paid tax invoice afterwards.

1.4.32

15 September 2026

• Changed: a booking a driver submits from a draft is now confirmed by JollyDrivers itself instead of sitting on "Sent" waiting for the operator system to reply. It is held instead, with the reason on the booking, when there is no price yet or a fatigue warning has not been acknowledged.

• New: an operator or admin can accept or decline a booking from the trip page ("Answer the booking"), including one that was left on "Sent" before this change. Settings → Booking Form → "Confirm my passenger bookings automatically" extends the automatic confirmation to bookings other people submit.

1.4.31

15 September 2026

• Changed: JollyDrivers no longer holds a customer's first invoice for you to confirm the Xero customer. It finds the matching Xero contact (by email, ABN, phone, then exact name) and uses it, or creates a new contact when nothing matches, then raises the invoice straight away — the way the operator system always did. The "Customers to confirm" panel on Settings → Accounting only shows invoices held before this change; confirm those to release them and it disappears.

1.4.30

15 September 2026

• New: when JollyDrivers raises the invoice in Xero, the request dialog asks whether to raise it Approved (as before, a live invoice with a pay link) or as a Draft to look over in Xero first. A draft shows as "Draft in Xero" on the trip, has no pay link yet, and gets a tick button to approve it. Sending a confirmation or a completed notice approves any draft on the trip first, so the customer's email always carries a working pay link; a draft that cannot be approved stops the send and says why. Voiding a draft deletes it in Xero rather than leaving a voided invoice behind.

• Changed: refreshing an invoice from Xero now also picks up the pay link when a draft was approved in Xero by hand.

1.4.29

14 September 2026

• New: a driver or operator can void an outstanding invoice from the trip page (the block icon next to it), with a reason. An invoice JollyDrivers raised in Xero is voided there on the spot; one raised by the operator's own system is refused with a note to void it there and refresh. The void is recorded on the booking, and once the only invoice is voided the "Request a new invoice" button comes back.

1.4.28

14 September 2026

• Changed: an invoice JollyDrivers raises in Xero now describes the trip the way your own invoices always did — flight banner, pickup time and zone, passenger and mobile, seats, extras, each stop, distance and ETA, the reference and the booking date — and carries the passenger-band item code (PAX-X / PAX-XL / PAX-MAX).

• Fixed: an invoice JollyDrivers raised in Xero after you confirmed the customer left no trace on the booking. The booking now shows when the invoice was held (and why), and once it is raised the operator's system is told about it and the booking records that, exactly as it does for an invoice raised straight from the trip.

1.4.27

14 September 2026

• Fixed: a customer waiting to be approved as a new Xero contact showed a greyed-out confirm button. The card now says no contact matched and offers "Approve as a new customer in Xero"; approving creates the contact and raises the waiting invoice.

1.4.26

14 September 2026

• Settings → Accounting → "Raise invoices from JollyDrivers" can now re-draft the invoices that were shadowed before JollyDrivers could draft the whole document. It builds the invoice JollyDrivers would have raised that day and checks it line by line against what is in Xero, so those early invoices count towards the switch-over bar — for it if they agree, against it if they do not.

1.4.25

14 September 2026

• My Trips: every booking in the list now shows the same invoice chip as the three cards at the top — "Invoice · Approved", "Invoice · Draft", "Invoice · Not issued" and so on — instead of the bare word "Invoice", so you can see whether an invoice has been raised without opening the trip.

1.4.24

14 September 2026

• Settings → Accounting gains the last switch for an operator whose own booking system is being turned off: once it is on, JollyDrivers sends that system nothing and takes over every invoice in Xero — refreshing, recording payments, voiding — including the ones the old system raised before the switch-over. It is offered only after "Raise invoices from JollyDrivers" is on, so invoicing can never fall between the two.

1.4.23

14 September 2026

• JollyDrivers can now text customers itself — pay links and receipts — from its own SMS number, instead of asking the operator's booking system to relay the text. Off until switched on. A new System Admin page, SMS opt-outs, holds every number that must not be texted: STOP replies land there automatically, START removes them, and the operator system's existing list can be pasted in.

• System Admin → Settings gains "Splash stays for at least", so how long the JollyDrivers mark shows while the app starts is yours to set. The splash itself has a new look: a sweeping ring around the mark, a soft halo, and the name settling in letter by letter.

1.4.22

14 September 2026

• Operators and admins can now accept or decline a booking on its trip page in JollyDrivers itself, and Settings → Booking Form gains a switch to confirm passenger bookings automatically the moment they are submitted. Auto-confirm holds back, and says so on the trip, when there is no price or the driver has an unacknowledged fatigue warning. Both are off until switched on; while your booking system still accepts bookings for you, leave them off.

1.4.21

14 September 2026

• When JollyDrivers raises one merged invoice for a booking group in Xero, the notice it sends the operator's system now names every trip on that invoice, so their records can show the invoice against each trip rather than only the first. Nothing changes until an operator is switched over.

1.4.20

14 September 2026

• Billing a booking group as one invoice now goes through the same door as a single booking: for an operator switched over to raising invoices in JollyDrivers, the merged invoice is raised in Xero by JollyDrivers itself, due on the day of the group's last trip, with each trip's share recorded against that trip. Nobody is switched over yet, so nothing changes today.

1.4.19

14 September 2026

• A JollyDrivers splash while the app starts up, in place of a blank page.

• The home menu, your trips list and the trip page now reveal their cards in sequence when you arrive.

1.4.18

14 September 2026

• On an invoice that JollyDrivers raised in Xero itself, changing the due date now changes it in Xero on the spot. Reclassifying a completed trip as cancelled now settles that invoice in Xero too: withdrawn when there is no fee, or credited for the difference when there is one. If the invoice was already paid, the credit sits on the customer's account and the refund is recorded in Xero by the operator. Invoices raised by the operator's system are unchanged. Nothing applies until an operator is switched over.

1.4.17

14 September 2026

• When a trip on an invoice that JollyDrivers raised in Xero itself is marked paid in cash, or its invoice is cleared so a group can be billed as one, JollyDrivers now voids that invoice in Xero on the spot instead of asking the operator's system to. A paid invoice is never voided. Invoices raised by the operator's system are unchanged. Nothing applies until an operator is switched over.

1.4.16

14 September 2026

• When a card payment is marked on an invoice that JollyDrivers raised in Xero itself, the payment is now recorded in Xero by JollyDrivers against your card terminal account, with the Square transaction as the reference. A part payment records the amount and leaves the invoice open. Invoices raised by the operator's system are unchanged. Nothing applies until an operator is switched over.

1.4.15

14 September 2026

• On an invoice that JollyDrivers raised in Xero itself, the trip page's Refresh button now reads the invoice's status straight from Xero and answers on the spot, instead of asking the operator's system and waiting. A payment made through Xero's online invoice, or keyed into Xero by hand, marks the trip paid the next time anyone refreshes — and every open one is checked overnight anyway. Invoices raised by the operator's system are unchanged. Nothing applies until an operator is switched over.

1.4.14

14 September 2026

• When a bank transfer is marked as paid on an invoice that JollyDrivers raised in Xero itself, the payment is now recorded in Xero by JollyDrivers, against your bank account, with the payer's reference. Invoices raised by the operator's system are unchanged. Nothing applies until an operator is switched over.

1.4.13

14 September 2026

• Settings → Accounting now has Raise invoices from JollyDrivers: it shows how many of your invoices JollyDrivers's comparison has agreed with, across everything you bill, and what is still short. Once the bar is met and the platform switch is on, you can switch over by typing the confirmation word it asks for. Switching back is one press. Nobody is switched over by this release.

• Confirming a customer on the review list now also raises any invoice that was waiting on that confirmation, once an operator is switched over.

1.4.12

14 September 2026

• When JollyDrivers raises an invoice in Xero itself, the operator's own system is now told about it straight away, so their records show the invoice and payments can still be recorded against it there. The pay link Xero provides is kept with the booking. Only applies once an operator is switched over, which none is yet.

1.4.11

14 September 2026

• JollyDrivers can now raise an invoice in an operator's own Xero organisation itself, instead of asking the operator's accounting system to. It is switched off for every operator and for the platform, and it stays off until the comparison evidence says it is safe. When it is on: the first invoice to each customer is held until you confirm the Xero customer, every invoice is authorised on creation and due on the day of the trip, and anything Xero refuses is shown to you in plain words rather than retried in silence.

1.4.10

14 September 2026

• Behind the scenes, JollyDrivers now works out for itself which Xero customer each invoice should go to — from a customer you have already confirmed, or by looking them up in Xero by email, ABN, phone or name — and records whether its answer matched the one the operator's system used. Nothing acts on it yet; it is the last piece of evidence before JollyDrivers raises invoices itself.

1.4.9

13 September 2026

• If a customer has been waiting more than a day to be confirmed, every portal page now says so at the top, with a link straight to Customers to confirm. Operators see their own; admins see every operator's. A customer left unconfirmed is an invoice JollyDrivers cannot raise, so it is not left to a screen you might not open.

1.4.8

13 September 2026

• Customers to confirm now catches up on invoices raised before the check existed: on first view it looks each one up in Xero once to find which customer it went to, so the cards for customers you have already invoiced appear without waiting for their next invoice.

1.4.7

13 September 2026

• Settings → Accounting has a new section, Customers to confirm. The first time a customer is invoiced, a card appears showing which Xero customer that invoice went to, and asks you once whether it is the right one. Confirm it and every later invoice for them resolves to that exact contact; mark it wrong and it will not be used again. Cards waiting more than a day are flagged. Admins see every operator's queue on Platform settings.

1.4.6

13 September 2026

• Groundwork for a one-time check per customer: JollyDrivers now keeps a review record for the first invoice raised to each customer of each operator, holding the Xero customer that invoice went to. Nothing is shown or held yet; the screen where you confirm or correct each one is the next step. Confirming will make that customer's invoices resolve to the same Xero contact every time without any matching.

1.4.5

13 September 2026

• When JollyDrivers reads an invoice back from Xero it now also records which Xero customer the invoice was raised for, and checks it against the customer JollyDrivers remembers for that bill-to. A mismatch is the one mistake nothing used to catch: a correct-looking invoice against the wrong customer. Groundwork for the review step that will let you confirm each new customer once.

1.4.4

13 September 2026

• After an operator's system raises an invoice, JollyDrivers now reads that invoice back from Xero and checks which of the operator's accounts each line actually posted to, against the account it would have chosen. This is a read only — JollyDrivers still creates nothing in Xero — and it is the last piece of evidence the shadow comparison was missing.

1.4.3

13 September 2026

• Behind the scenes, JollyDrivers now writes down the whole invoice it would have raised for a booking — every line, which of the operator's accounts each would post to, and the due date (the day of the trip) — at the moment it asks the operator's system to invoice. When that system's invoice comes back, the two are compared line by line and date by date. Nothing is sent to Xero and nothing about invoicing changes; this is the evidence that decides when JollyDrivers may raise invoices itself.

1.4.2

13 September 2026

• The Xero shadow comparison now records the invoice number (for example INV-0000) alongside each observation, so an admin reading the shadow log can see which invoice a row is about without looking it up by Xero's internal id. Rows recorded before this release keep a blank number.

1.4.1

13 September 2026

• When you press Connect to Xero and your organisation is greyed out on Xero's page, the Accounting tab now tells you why before you get there: Xero allows only two uncertified apps per organisation, and the fix is to disconnect one you no longer use under Xero's Settings → Connected apps. Nothing else about connecting has changed.

1.4.0

13 September 2026

• Operators can connect their own Xero organisation to JollyDrivers, and say which line of their own accounts each thing they bill should be recorded against — passenger fares, deliveries, tasks, a recovered passenger levy, purchases made for a customer, and the accounts payments land in. It is on Settings → Accounting. JollyDrivers never sees a Xero password: you approve it on Xero's own pages, and you can revoke it from your Xero account at any time.

• Nothing on that screen is ever filled in for you, and a missing account is never guessed — a code that is right for another business would put your income somewhere your accountant did not choose, and that is the kind of mistake found at BAS time rather than by an error message. The screen says plainly which gaps stop an invoice being raised and which do not.

• Groundwork for JollyDrivers to raise an operator's invoices itself, rather than asking their accounting system to. Before that happens for anybody, JollyDrivers now writes down what it would have put on each invoice and compares it against the one their system actually raised — on real bookings, until the differences stop. Nothing about how invoices are raised changes yet, and nobody sees anything different.

• All of the above is off for every operator until it is switched on deliberately.

1.3.1

12 September 2026

• A page left open no longer dies after a few minutes. If the connection drops — a tunnel, a locked phone, or just leaving a tab alone while you do something else — JollyDrivers now holds your place for 15 minutes instead of 3, and reconnects the moment you come back to the tab. Where it cannot be saved, the page refreshes itself instead of leaving you on a grey "could not reconnect" screen with your work behind it.

• The booking chat is the one exception, on purpose: it will not refresh itself out from under you, so a conversation you were part-way through stays on screen to read.

1.3.0

12 September 2026

• Operators can now set the name customers see on their emails and the address customer replies go to, on Settings → Branding. Each operator gets its own JollyDrivers sending address behind the scenes; nothing changes in what customers receive until it is switched on for that operator.

• Groundwork for JollyDrivers to send booking confirmations to customers directly, as the operator, instead of handing them to the operator's own system to forward. Off for every operator until it is switched on deliberately.

1.2.1

11 September 2026

• The calendar now shows every trip at the pickup's own local time, in the state it happens in. A Byron Bay pickup at 9:00 reads 9:00, not the Queensland 8:00 it also is, and the day view labels each entry with its state when the two clocks are in play.

• Calendar invitations — the ones emailed to drivers, and the download — now say which state's time they are in, and a cross-border trip ends in the other state's time. Google, Outlook and Apple file the event under Australia/Sydney or Australia/Brisbane instead of "UTC".

• Blockouts ask which state they are in, so a border driver's "Tuesday 9–5" is the right 9–5. It defaults to the state of your last blockout or last pickup, so the usual case is one tap.

• The passenger's Add to Google Calendar link now names the pickup's state, so a Queensland passenger booking a New South Wales pickup no longer gets an entry an hour out in summer.

• Behind the scenes: every release now has to carry a new version number and a description before it can go out, and the app reports the changelog's version rather than a fixed one.

1.2.0

10 September 2026

• You can tell us about a problem, or ask for something to work differently, from Report a problem on your home board. Add a screenshot, a booking number, and we'll come back to you — My reports shows what you've raised and where each one got to.

• When you're making a booking and it clashes with something already in the calendar, you can now stop. Before, the only choices were to carry on anyway or move the pickup time; leaving the page was the only way out of a clash you couldn't work around.

1.1.0

10 September 2026

• Portal pages now stop at a comfortable width on large monitors instead of stretching all the way across the screen. On a 32" display the content sits in a readable column with the JollyDrivers logo and your account menu lined up with it.

• There is now a changelog — this page. It shows which version you are on and what changed in each release.

• Behind the scenes: JollyDrivers can now tell you exactly which build it is running, which makes a bad deploy obvious in seconds instead of taking a morning to find.

1.0.0

8 September 2026

• JollyDrivers went live at jollydrivers.com.au.

• Booking, trips, invoicing, driver and vehicle records, compliance documents and the operator messaging protocol all running in production for the first time.