Domestic Cleaner's Scheduling & Management App

via Freelancer ·

Budget / Salary£250–750
TypeFreelance project
LocationRemote
Posted2 hours ago
# Freelance Cleaning Management Software

I am looking for a developer to build a professional management application for a self-employed/freelance domestic cleaner.

The cleaner may work directly for private clients while also carrying out work for several cleaning companies. The system therefore needs to manage all jobs in one place while clearly identifying which clients, jobs, income and records belong to each company or work source.

Most cleans are recurring, but frequencies vary, including weekly, fortnightly, every 3–4 weeks, monthly and one-off jobs.

The application should work well on desktop and mobile and be simple enough for a sole cleaner to use every day.

## Core Requirements

### Dashboard

Provide a clear overview of:

* Today's cleans
* Upcoming jobs
* Completed jobs
* Hours worked
* Expected earnings
* Outstanding payments
* Jobs by company/work source
* Missed, overdue or rescheduled cleans
* Daily workload/capacity

### Companies / Work Sources

The cleaner must be able to manage multiple work sources such as:

* Cleaning Company A
* Cleaning Company B
* Agency work
* Private clients

Each company/work source should store contact details, payment arrangements, standard rate if applicable, notes and active/inactive status.

The system should allow filtering and reporting by work source.

### Client / Household Records

Each household should support:

* Client name
* Address
* Phone/email
* Associated company/work source
* Normal cleaning duration
* Hourly rate or fixed price
* Preferred day/time
* Parking information
* Access instructions
* Pet information
* Cleaning product/equipment preferences
* General household notes
* Active/inactive status

Clients should be searchable and filterable.

### Recurring Scheduling

Recurring scheduling is a key requirement.

The system should support:

* Weekly
* Fortnightly
* Every 3 weeks
* Every 4 weeks
* Monthly
* Custom intervals
* One-off cleans

A recurring cleaning agreement must be stored separately from each actual visit.

Example:

**Mrs Smith – Fortnightly – Tuesday 10:30 – 2 hours**

The system should automatically calculate future visits.

### Calendar / Schedule

Include daily, weekly and monthly schedule views.

Jobs should show:

* Client
* Address
* Company/work source
* Time
* Expected duration
* Status
* Notes/instructions

It should be possible to filter the schedule by company and status.

### Today's Work Screen

Provide a mobile-friendly screen designed for use while working.

Example:

* 09:00 – Mrs Jones
* 11:30 – Mr Davies
* 14:00 – Mrs Williams

Each job should support actions such as:

* Start clean
* Finish clean
* Complete
* Cancel
* Reschedule
* Add notes
* View household instructions
* View checklist

### Time Tracking

The cleaner should be able to start and stop a timer.

Record:

* Scheduled duration
* Actual duration
* Start time
* Finish time

Reports should be able to compare expected and actual cleaning time.

### Cleaning Checklists

Each client should be able to have an individual checklist, for example:

* Bathroom
* Kitchen
* Vacuum bedrooms
* Mop floors
* Dust living room
* Change bedding
* Empty bins

Reusable checklist templates should also be supported.

### Visit History

Each actual visit must create a permanent historical record.

Possible statuses:

* Scheduled
* Completed
* Cancelled by client
* Cancelled by cleaner
* Missed
* Rescheduled

Historical visits must not be changed when the client's future recurring schedule is edited.

### Rescheduling

The application must distinguish between:

* **Move this visit only**
* **Change the recurring schedule**

For example, moving one Tuesday clean to Wednesday must not automatically move all future visits.

This behaviour is particularly important.

### Client Transfers Between Companies

A client may move from one company to another or become a private client.

The system should allow this while preserving the correct company/work-source information against historical visits, invoices and payments.

### Travel and Mileage

Support:

* Estimated travel time between jobs
* Business mileage
* Mileage linked to jobs
* Daily/monthly mileage totals
* Configurable mileage rate

Manual mileage entry is acceptable. Live Google Maps integration is not essential for version one.

### Workload Planning

The system should calculate expected workload.

Example:

**Monday**

* 4 clients
* 6.5 cleaning hours
* 1 hour travel

The software should warn when the planned workload exceeds a configurable daily capacity.

### Holidays / Unavailable Dates

The cleaner should be able to block dates or periods when unavailable.

The application should identify recurring cleans affected by these dates so they can be rescheduled.

### Payments

Support different payment arrangements, including:

* Paid directly by client
* Paid by cleaning company
* Hourly rate
* Fixed price
* Cash
* Bank transfer
* Other methods

Track:

* Amount expected
* Amount received
* Outstanding amount
* Payment date
* Payment method
* Who is responsible for payment
* Paid/partial/unpaid status

### Invoicing

Include basic invoicing with:

* Invoice number
* Client/company
* Date
* Work completed
* Amount
* Due date
* Payment status
* Printable invoice view

Automatic invoice creation following completion of a clean would be desirable.

### Expenses

Allow recording of business expenses such as:

* Cleaning products
* Equipment
* Parking
* Fuel
* Vehicle costs
* Insurance
* Telephone
* Software
* Advertising
* Other expenses

### Reports

Reports should include:

* Monthly income
* Income by company
* Private-client income
* Hours worked
* Jobs completed
* Average clean duration
* Average job value
* Expenses
* Mileage
* Outstanding payments
* Estimated profit
* Workload by day/week/month

CSV export would be useful.

### Search and Filtering

Allow searching/filtering by:

* Client
* Address
* Company
* Date
* Job status
* Payment status
* Cleaning frequency

### Backup / Restore

The user should be able to:

* Export a complete backup
* Restore a backup
* Export useful records to CSV

## User Interface

The design is important.

I do not want a basic spreadsheet-style interface or generic admin template.

The application should have:

* Modern professional design
* Responsive desktop layout
* Good tablet/mobile support
* Clear navigation
* Clean typography
* Easy-to-read cards and status indicators
* Simple forms
* Good visual hierarchy

The software is primarily for a sole operator, so usability is more important than complex multi-user administration.

## Technical Requirements

I am open to the technology used, provided the result is reliable and maintainable.

A lightweight web application/PWA would be suitable.

Ideally the application should:

* Work on Windows and macOS
* Work well on smartphones
* Be installable as a PWA where practical
* Work without complicated server installation
* Retain data between sessions
* Support backup/restore
* Use clean, maintainable code

A cloud backend and login system are not essential for the first version. Local/offline storage is acceptable.

## Demo Data

The project should include realistic fictional demonstration data so all main workflows can be tested immediately.

No real personal data should be included.

## Deliverables

Required deliverables:

* Complete working application
* Full source code
* All project/configuration files
* Installation/startup instructions
* README/documentation
* Demo data
* Backup/export functionality
* Responsive desktop and mobile layouts

All source code must be supplied at completion.

## Completion Criteria

The project will be considered complete when:

* Multiple companies/work sources can be managed
* Clients can be created and edited
* Recurring cleans generate correctly
* Individual visits can be moved without altering future recurrence
* Permanent schedules can also be changed
* Jobs can be started/completed
* Cleaning time can be recorded
* Checklists work correctly
* Historical visits remain intact
* Payments/invoices can be recorded
* Expenses and mileage can be entered
* Clients can move between companies without corrupting historical records
* Reports show meaningful totals
* Backup and restore work correctly
* The interface works on desktop and mobile
* No major runtime errors remain
* Full source code and documentation are supplied

## Preferred Developer Skills

Experience with:

* JavaScript/web applications
* Responsive UI development
* Data modelling
* Recurring scheduling/calendar logic
* Local databases/browser storage
* PWA development
* Business-management systems
* Reporting and financial calculations

Experience with CRM, field-service, appointment or workforce-management software would be useful.

When bidding, please include examples of similar work and briefly explain how you would structure the recurring-job system so that changing one visit does not unintentionally change the client's permanent schedule.
javascript mobile app development user interface / ia software architecture html5 database development web development css3
Apply on Freelancer →

Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.