EN TR
Get a quote
View all services
Web software

One app carries the brochure pages and the request queue.

System architecture

The pieces and their boundaries are settled before code.

Enterprise & commercial software

Several institutions, one system, records kept apart.

Mobile app

One codebase, both stores: iOS and Android.

Software consulting

We take a running system over and improve it.

AI consulting

AI only where the problem actually calls for it.

Get a quote
EN TR

Process Tracking · Atasehir

Process Tracking for Atasehir businesses

Two lists are laid side by side at month close and they disagree. If you run a head office out of an office block around Icerenkoy in Atasehir, the picture is familiar: what was billed is kept in one place, what was reported in another, and somebody hunts the gap by hand. Process tracking software for Atasehir, Istanbul starts at that gap. In the dental clinic CRM the invoice keeps no ledger of its own — with no second ledger, nothing is left to reconcile.

Get a quote Tell us about your project

Process Tracking — Atasehir

Atasehir is a finance district, thick with multi-branch corporate management and head-office reporting. If a head office totals figures coming from several branches, a transfer step slips in between the work done at a branch and the report arriving at the centre. Wherever that step exists, so does the month-end argument. The work closest to this district's management texture was written for a single dental clinic, and we state its scale as it is. Where it does not overlap should be just as clear: we have nothing to show for consolidated reporting across many branches, nor for the processes of financial institutions. What carries across is not a management layer but the habit of standing on one data model. Laravel runs the process while MySQL keeps patient, plan and invoice records in the same schema.

  • The invoice keeps no ledger of its own: what was billed and what was performed are read off the same record, so no second list turns up to be reconciled at month end.
  • A report produces no new dataset, it reads the same record from another angle, so a changed figure does not leave the report waiting for an update.
  • The scope goes on the page too: the system was built for how one clinic runs, and consolidation across many branches falls outside that line.

Why Algoriel

  • Keeps working offline

    The field app keeps recording with no connection, and the queue reaches the server in order once signal returns. That is how AlgoKlima runs.

  • Entry from QR and location

    Where no fixed terminal can be installed, entry and exit are logged from a QR code and a location reading, and entitlement is worked out from those readings.

  • Records land the same hour

    Jobs close in the field, so the office sees where each one stands without waiting for end of day.

  • Office and field read one source

    The office panel and the field app read the same information, so nobody keeps a spreadsheet alongside it.

What we build

Process Tracking

  • What the record attaches to

    Rather than mapping a process in the abstract, we decide what a record hangs on. On the construction system a row belongs to a person and a site at once, and the two are never separated. In AlgoRandevu we are building a structure where a booking can attach to a person, a room or a piece of equipment.

  • The entry that stays open

    Instead of a live dashboard, one rule: a matched check-in and check-out produce the hours, and a check-in with no scan out stays open. Whatever is stuck shows up as that gap.

  • Who was where, on the record

    Because a single row carries both the person and the site, totals separate by site. When one worker spends the month across two sites, those hours never fall into the same bucket.

  • What is left when the figure is disputed

    Because payroll is derived from matched pairs, the number argued over at month end has a time- and location-stamped record behind it. There is no parallel calculation sheet to reconcile against; the dispute happens over the record itself.

  • Records taken beyond coverage

    In AlgoKlima's service flow the chain does not break where the network does. Once the connection returns the waiting entries are processed in the order they were created, and an edit made in the field and one made in the office merge into a single record through conflict resolution.

  • Process rules kept out of the code

    Rules like the length of a step and the gap between consecutive ones belong in a product setting, not in the code. The aim is that changing one does not mean shipping a release, and that is what we are building into AlgoRandevu right now.

Work like this

Process Tracking · Case study

Dental clinic CRM — invoice and report read off one record, no second ledger

A system we wrote for a single dental clinic, and we name that scale plainly. What this page leans on is the singleness of the record: the invoice is not kept in a separate ledger, and because the work performed sits on the patient record, billed and performed are read from the same place. Reports build no new table either; they read that record from another angle, so a figure and a report never wait on each other. A manager sees where a patient stands from one screen. Laravel runs the process and MySQL keeps patient, plan and invoice records in one schema. Multi-branch consolidation sits outside this scope.

Read the case study →

Working with Atasehir teams, remotely

We have no office, so work for this city runs remotely and we do not offer on-site support. What was done, and why it was done that way, stays in writing. The project pages mark which builds came out of a partnership.

  • The first release ships as a working piece; extras follow later.
  • Every client we know of is in Turkey.
  • Decisions stay in writing; progress shows in working screens.

Frequently asked

  • Why do the head-office report and the branch figure disagree?

    Usually because the two are produced in different places. In the dental clinic CRM the invoice has no ledger of its own; the work performed is on the record, so billed and performed are read from the same place. Remove the transfer step and the mismatch has nowhere to start.

  • We are not a clinic. What does this example tell us?

    It is a clinic and we say so. What carries across is not the treatment screens but the singleness of the record: the work sits in one place, and the invoice and the report both look at it. Rename the record from patient to job or customer and the rule holds.

  • Does the scope cover consolidated reporting and budget approval?

    It does not. We are describing a system written for how one clinic runs. Multi-branch consolidation, corporate approval chains and the processes of financial institutions fall outside it, and we do not promise what we cannot show.

  • Do you have people working on site in Atasehir?

    We keep no office and the team works entirely remotely. Setup needs no visit either: at the start we settle one thing, which figure comes from which record. Once that is clear, the rest is defined from the panel.

Process Tracking in other cities

The other cities where we publish this service are below, grouped by province.

Other services for this location

What stands behind your month-end figure today?

Get a quote or open the service