From registers to real systems: what digitisation actually requires
Replacing a paper register is not a data entry problem. It is an operational design problem — and most projects underestimate that.
Institutions come to us with a register — hostel occupancy, school attendance, member contributions. The instinct is to digitise the register as-is. That rarely works.
Paper processes hide ambiguity. Who is responsible when a room shows occupied but the resident checked out? What happens when a fee is paid in two instalments across different terms? Software forces those decisions into explicit rules.
Our discovery process maps how staff actually work: partial payments, room transfers, term rollovers, refund approvals. Only then do we design data models and workflows.
Digitisation succeeds when the system models real operations — not when it mirrors a spreadsheet with a login screen.