Scheduling that knows your rules
Service duration, breaks, staff availability and equipment differ from business to business. Before drawing a calendar, I document what happens when an appointment moves, who can change it and how double bookings are prevented.
- Staff and resource availability
- Different service durations and blocked periods
- Appointment status and change history
- Reminders only when explicitly included in scope
A work order from intake to completion
An enquiry becomes a task with an owner, an agreed time and a clear status. Photos, materials and reports are added where the process needs them. The example on this website shows a basic transition using fictional information.
- Intake, assignment and completion
- Access based on employee roles
- Change history and relevant search fields
- Export in an agreed format
Stock is movement, not just a number
Receipts, issues, reservations and returns have different meanings. A stock model separates those events first. Balances follow actual movements; required fields and warnings reflect how products enter and leave your business.
- Product code, variant and unit of measure
- Receipt and issue records
- Reserved and available quantities
- Import from existing spreadsheets with duplicate checks
Connecting the tools you already use
If an existing application handles part of the job well, I first check its API and export options. An integration needs a defined source of truth, transfer direction and failure behaviour. Access to a particular API is checked before it is included in a proposal.
When to keep the spreadsheet
A simple list maintained by one person may not need a custom application. A clearer sheet, validation and a small import can be enough. Software becomes useful when permissions, concurrent work, history or complex rules exceed the current record system.