Real Operational Problems, Rebuilt as Business Applications

The challenge. A workshop group ran vehicle intake, inspection findings, estimates, and final invoices on carbon-copy job cards and a shared spreadsheet. Approvals for extra parts happened over phone calls, parts consumption was reconciled at month-end, and each branch reported differently.

What was configured. Job card, inspection, estimate, and invoice screens with their own fields and line-item tables; an approval workflow so a customer confirms extra parts (with a price) before work continues; automatic service numbering; GST-correct invoice totals; branch-scoped access so a service advisor only sees their own branch.

Outcome. Every vehicle has one live record from check-in to delivery. Extra-work approvals are logged with who approved and when. Parts issued to a job are deducted from stock as the job is closed, and management sees the same numbers across every branch in one dashboard.

The challenge. Bookings, no-shows, and completed jobs were all one list. Detailers picked up whatever they wanted, customers had no way to confirm mid-job add-ons, and a booking that never turned up still cluttered the work queue.

What was configured. A customer-facing appointment record and a separate job-card record created only at check-in; an unclaimed job pool visible to all detailers until someone assigns it to themselves; a customer portal to review and approve extra items; per-branch capacity limits so a slot can't be overbooked; a self-service booking form with only the fields a customer should fill.

Outcome. The work queue only contains real work. Each job has one owner. Add-ons are approved by the customer in writing before they are billed, and front desk can still record a phone approval on the customer's behalf.

The challenge. Staff raised IT issues by email and chat. There was no queue, no priority, no record of what changed, and recurring problems were re-diagnosed every time.

What was configured. Incident, problem, change, and knowledge-base records sharing one submission form; status workflows with the right role gating each step; notifications to the assigned team on creation and on each transition; a knowledge base staff can search before raising a ticket.

Outcome. Every request is a tracked ticket with an owner and a priority. Changes carry an audit trail. Repeat issues are linked to a single problem record and its documented fix.

The challenge. Each branch kept its own spreadsheets for enrolment, staff records, fee collection, and leave. Head office had no consolidated view and no way to stop one branch seeing another's data.

What was configured. Student and staff directories, a fee ledger, and a leave-approval workflow on one platform; organization- and branch-level access control; role-based menus so a branch coordinator, a mentor, and a parent each see only what applies to them; a parent portal for fee status and approvals.

Outcome. Branch staff work only within their branch. Head office sees the whole group live. Fee dues and leave requests move through defined steps instead of informal follow-up.

The challenge. Counter staff billed from a basic tool that didn't split tax correctly, didn't tie a bill to the operator who raised it, and couldn't produce a clean day-end summary.

What was configured. A counter-bill screen with a fast line-item table, automatic bill numbering, tax computed per line and rolled into the correct CGST/SGST or IGST split, and each bill stamped with its operator and counter; day-end and per-operator reporting.

Outcome. Bills are quick to raise and arithmetically correct. Every bill is attributable. The day closes with a report instead of a manual tally.

The challenge. Visitors signed a paper register. Hosts weren't told their guest had arrived, parcels piled up unlogged, and there was no fast way to raise an alarm from the gate.

What was configured. A visitor pass record with a QR code, a host notification on arrival, a parcel log with a "collect from gate" alert, and an SOS record that notifies the security team immediately; a status workflow from expected to checked-in to checked-out.

Outcome. The site knows exactly who is inside and who they are visiting. Hosts are notified automatically. Parcels and emergencies are tracked, not shouted across a lobby.