Skip to main content
GullySystem
Automotive

Contract Management for Chauffeur-driven car rentals

Keep agreements, obligations and renewal decisions on a controlled record.

Documents

Does this function belong in your operation?

Use when signed agreements create dates, obligations or renewal decisions that need follow-up.

An agreement is drafted, signed, amended or nearing renewal.

Use contract records for corporate rate agreements and written partner-fleet arrangements where these exist. Keep the client’s billable terms separate from the supplier’s payable terms. Record effective dates, permitted service scope, required duty evidence and the authorised change contact. An expired tariff needs a commercial decision before reuse. A signed account agreement neither allocates a car nor proves that subcontracting is permitted; dispatch must confirm supply under the actual terms.

Bring the records the workflow depends on.

  • Signed corporate or hotel account agreement and effective rate version
  • Partner-fleet agreement where supply is subcontracted
  • Required duty evidence, billing terms and authorised change contacts
  • Notice, renewal and amendment decisions

Outputs to check

  • Customer agreement and partner agreement registers kept distinct
  • Effective tariff and amendment history
  • Notice and evidence obligations with named owners

Follow the contract management workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Register the agreement

    Identify parties, scope, dates and the document status.

  2. 2. Confirm the operative version

    Keep the executed agreement distinct from drafts and proposed amendments.

  3. 3. Assign obligations

    Record owners, notice dates and evidence required for completion.

  4. 4. Review changes

    Approve amendments and pass altered terms to affected operating processes.

  5. 5. Renew or close

    Retain the authorised decision and evidence of any notice or termination action.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Account owner

Maintains the customer’s operative agreement and approved amendments.

Partner coordinator

Checks the separate supplier arrangement and any restriction on onward supply.

Accounts reviewer

Applies the correct customer and partner terms to their respective settlements.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Tariff changes during an ongoing assignment

Keep the effective date and accepted transition decision; do not apply it retrospectively without authority.

A partner is proposed for a contracted customer

Check the actual supply terms before accepting the partner arrangement.

Missing duty evidence delays a bill

Retain the obligation and responsible follow-up rather than marking the contract fulfilled from the driver’s completion alone.

Can this work independently?

Agreement tracking can operate with entered parties, files and effective dates. Dispatch uses accepted terms but still confirms actual cars and drivers. Billing and supplier settlement consume different rate references. A stored clause or expiry date does not itself authorise subcontracting, send notice or end a service.

Systems and records it connects with

  • Duty register for the specific work governed by the agreement
  • Controlled agreement files and amendment evidence
  • Customer and supplier accounting records through separately agreed references

Configure, test and introduce the workflow.

  • Separate corporate customer agreements from partner-fleet arrangements before importing records.
  • Test an effective-dated rate change and a proposed subcontracted duty against the operative documents.
  • Agree notice owners, evidence access and the handoff to dispatch and accounts before using the register.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Customer and supplier rates remain separate for the same duty.
  • A later rate version does not silently alter earlier accepted work.
  • An agreement identifies who may authorise a changed duty or commercial term.
Chauffeur-driven car rentals

How the business operates.

A chauffeur-driven rental supplies a car and driver for a defined duty. The person booking, the passenger and the account paying the bill can be different. An owner driving a single car and a dispatcher coordinating partner fleets need the same clear handoffs: accepted requirement, confirmed allocation, actual duty and supported bill. Plan software around those records. This scope covers pre-booked passenger transport managed by the operator; it does not describe self-drive hire or a marketplace that merely introduces drivers.

Booking desk and account terms

Record who requested the car, who will travel and where the invoice belongs. Keep pickup instructions, luggage needs and the accepted vehicle specification with the duty. A corporate rate agreement supplies terms, not confirmation that a car is allocated.

Dispatch and partner coordination

Match the reporting time to an available car and driver. Include positioning and the expected release before accepting another duty. For partner supply, distinguish a request sent, supplier acceptance and the actual driver assignment.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Booking reference, booker, passenger and billing account
  • Accepted car specification, reporting point, reporting time and release plan
  • Applicable quote or account rate version and authorised change contact
  • Owned or partner vehicle, driver assignment and supplier acceptance

Operational bottlenecks to check

The passenger asks for more than the booker bought

A new stop or extended duty affects the next assignment and the bill. Keep the request and authorised decision together instead of leaving the chauffeur to negotiate alone.

A partner request looks like an allotted car

Until the supplier accepts and identifies the car and driver, dispatch still has an uncovered duty. Preserve that distinction in the operating list.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Agree the duty

    Capture the passenger journey and distinguish a local package, transfer or continuing assignment. Record the counting basis, inclusions and change authority before confirmation.

  2. 2. Confirm actual supply

    Allocate the vehicle and driver or obtain partner acceptance. Retain the difference between an unassigned booking and a confirmed duty; review the driver’s earlier release and vehicle restrictions.

  3. 3. Report at the pickup point

    Check that the driver has the latest location and passenger contact. Record actual arrival separately from passenger pickup so waiting has an identifiable start and reason.

  4. 4. Manage the passenger’s changes

    Record an added stop, extended wait or changed destination. Dispatch assesses the effect on the next duty and obtains the appropriate commercial decision from the booker or account owner.

  5. 5. Close the duty record

    Capture release time, meter readings and supporting extras. Retain the passenger’s acknowledgement or dispute. A missing acknowledgement stays visible rather than being invented by office staff.

  6. 6. Bill and settle the participants

    Apply the accepted rate version to the supported duty. Allocate customer receipts and reconcile driver or partner amounts through separate records. Retain corrections to a billed duty without erasing the original evidence.

Industry reports to connect with

  • Unassigned duties, partner requests awaiting acceptance and conflicting allocations
  • Reported, picked-up and released times with unresolved waiting explanations
  • Completed duties awaiting acknowledgement, expense evidence or billing review
  • Customer balances separate from driver advances and partner payables

Questions before implementation.

When should chauffeur-driven car rentals consider contract management?

Use when signed agreements create dates, obligations or renewal decisions that need follow-up. An agreement is drafted, signed, amended or nearing renewal.

What should we bring to the requirements discussion?

Bring anonymised examples of Signed corporate or hotel account agreement and effective rate version; Partner-fleet agreement where supply is subcontracted; Required duty evidence, billing terms and authorised change contacts; Notice, renewal and amendment decisions. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Keep agreements, obligations and renewal decisions on a controlled record. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

The system tracks agreements and does not provide legal interpretation, drafting advice or enforceability assurance.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Customer and supplier rates remain separate for the same duty. Use this check when reviewing the first working version.

Talk to us

Discuss contract management for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements