One place to run a growing service business.

A maintenance contractor growing from one city to three and from 15 people to 50. The owner can no longer approve everything, subcontractors come and go, and clients want proof of every hour. Jobs, quotes, credit terms, compliance and SLA reports sit in one console, and every decision is recorded as the work happens. Pick a record, make a decision, then try to tamper with it.

Jump to the data model

Demo only. Tidewell Facilities is fictional and every record is synthetic. Contract and policy references are illustrative, and POPIA and safety references are simplified. This is not legal advice. Nothing you enter leaves your browser.

This demo needs JavaScript and a modern browser. Read how projects start instead.

Designed around the people

Technicians capture job cards on site, offline if they must. Clients log jobs, sign off and follow their SLA in a portal. Office staff approve, query and report in the console. Each gets a journey that fits how they work.

Decisions stay with people

Automation suggests, checks documents and flags risks. Quotes, credit terms, disputes and bank detail changes are decided by a named person, and the reason is kept.

Records built in

Every step is sealed with a SHA-256 hash that includes the one before it. SLA reports trace back to job cards, and any later edit shows up on verification.

the data model behind it

The schema is where the rules live.

Twelve tables hold the whole operation. The approval limits, the compliance checks and the audit trail are properties of the data, not habits people have to remember.

clientpk iduuidnametextcredit_statusenumcredit_limit_zarnumericCredit terms are set by a decision, never by the score alone.

contractpk iduuidfk client_iduuidp1_response_hoursintrate_cardjsonbThe SLA and rates the client signed, in one place.

sitepk iduuidfk client_iduuidregionenumaccess_notestextWhere the work happens, across every region.

jobpk iduuidfk site_iduuidpriorityenumsla_due_attimestamptzstatusenumThe SLA clock starts when the job is logged.

job_cardpk iduuidfk job_iduuidfk worker_iduuidarrived_attimestamptzcaptured_offlineboolCaptured on site, offline if needed; original times are kept.

workerpk iduuidkindstaff | subcertified_forenum[]bank_verified_attimestamptzStaff and subcontractors, assigned only to work they are certified for.

compliance_docpk iduuidfk worker_iduuidtypeenumexpires_ondateAn expired document blocks assignment and payment.

quotepk iduuidfk client_iduuidamount_zarnumericapprovals_requiredintstatusenumCannot be sent until the approvals match its value.

decisionpk iduuidrecord_refreffk decided_byuuidoutcomeenumreasontextWho decided what, why and when, for any record.

requirementpk iduuidsourceenumreftexttitletextContract clauses, company policies and POPIA sections.

record_eventpk iduuidrecord_refrefkindtextprev_hashchar(64)hashchar(64)Append-only. Each hash includes the one before it.

sla_reportpk iduuidfk contract_iduuidperioddaterangep1_on_time_pctnumericfk approved_byuuidBuilt from job cards, so every figure traces back.

pk primary keyfk foreign keyref: points at any record

contract, site, quotemany to oneclient
jobmany to onesite
job_cardmany to onejob, worker
compliance_docmany to oneworker
decision, record_eventmany to oneany record
any recordmany to many, via a link tablerequirement
sla_reportbuilt fromjob_card, record_event

Outgrowing spreadsheets and chat groups?

A Requirements & Gap Analysis maps what your business needs to track as it grows, where today’s tools fall short, and what to build first.

Book a discovery call How projects start