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 · Istanbul

Process Tracking for Istanbul businesses

If your crew does not stay at one address in Istanbul, whoever starts the morning on one job is across the city by afternoon, and a record not taken where the work happens gets written from memory that evening. Process tracking software for Istanbul starts at that first link: entry and exit are scanned from the worker's own phone, and the hours come from that matched pair.

Get a quote Tell us about your project

Process Tracking — Istanbul

Istanbul is where the distance between a field crew and the office stretches furthest: one worker turns up at several addresses inside a month, and the signal differs at each. The work closest to this market's sector profile is a construction workforce attendance system: temporary sites, several subcontractors on one of them, entitlement derived from the records. A row there carries the person and the site together, so hours never pool across addresses. AlgoKlima is the second piece: a record taken outside coverage queues on the device and goes through in creation order when the connection returns. We have no office and work entirely remotely — the model itself, not a gap.

  • The record is created on site: QR scans open and close the day, and a location check names the site rather than a dropdown.
  • A row belongs to a person and a site at once, so different addresses total separately and an entry with no exit stays open.
  • The chain holds where the signal stops, because records queue in creation order and edits from site and desk merge into one version.

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

Construction workforce attendance: QR and location where a turnstile would have gone

A construction site is temporary: a turnstile put up has to come down when the project ends, and the crew moves between sites anyway, several subcontractors to a site. Nothing was installed in its place. Entry and exit are scanned from the worker's own phone, and a location check names the site. Entitlement is derived from the matched pairs with no second sheet alongside, and one worker's records stay separate per site. React Native (Expo) runs on the phone; Laravel takes the scans and MySQL holds them.

Read the case study →

Working with Istanbul 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

  • You work remotely — does anything get installed on the site?

    We have no office and the whole team works remotely. Nothing goes onto the site itself, so setup is not an installation visit: the app downloads to the worker's phone and sites are defined from the panel.

  • What replaces the paper timesheet and the turnstile?

    A matched pair of records replaces the paper; nothing replaces the turnstile. A scan opening the day is closed by a scan ending it, and if the two never meet the row stays open. Under a disputed figure sits a time- and location-stamped record. We quote no savings figure, because we have measured none.

  • Coverage differs address to address. What happens where there is no signal?

    The record is still taken. In AlgoKlima's field flow it lands in a queue on the device, and that queue goes through in creation order once the connection returns. If the desk touched the same record, the two edits merge through conflict resolution.

  • Can it connect to the payroll and accounting systems we already run?

    It can, though we will not call integration standard. Two things get settled first: where a record is entered, and which side wins when both change it. A connection built before those answers leaves two lists that disagree at month end.

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