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

Process Tracking for Tuzla businesses

Work in Tuzla does not stop when the light goes. A shift hands over and a different crew takes the same job, often working for a different firm on the same site. Keep the timesheet by calendar day and the night shift breaks in two — one person, two rows, neither of them the hours actually worked. Workforce tracking software for Tuzla starts at that break: a matched scan pair sets the span, and midnight does not cut it.

Get a quote Tell us about your project

Process Tracking — Tuzla

Tuzla's working landscape is shipyards, an organised industrial zone, and heavy manufacturing. None of those sites are permanent addresses: the work finishes, the site closes, the crew moves to the next one. Production carries on through the night, and at any hour several subcontractors have people on the same ground. The closest thing in our portfolio to that sector profile is a construction workforce attendance build: temporary sites, shifts that hand over, entitlement derived from closed records. Where attendance is kept on paper or in separate spreadsheets, month end arrives the same way every time: there is a number, and nothing underneath it. On our side there is no office, no site visit, and nobody dispatched — the team works remotely.

  • A shift running past midnight stays one span: the hours come from the gap between the two ends of a matched scan pair, not the calendar.
  • Each subcontractor on the site keeps a separate column: a scan carries the job it belongs to, no shared gate device decides whose hour it was.
  • The month-end total is built from closed rows, not a spreadsheet kept alongside, and a row with no exit scan is never filled with an average.

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: a scan pair sets the shift, closed rows the entitlement

Shifts hand over around the clock, and more than one subcontractor keeps a crew on the same ground. Duration comes from a matched scan pair — the gap between its two ends — so a night shift crossing midnight stays one span. Each row carries the person and the site together, which keeps hours in separate columns per subcontractor. Entitlement is derived from the closed rows themselves, with no second sheet beside them, so a disputed hour is settled against its own stamp. The phone side is React Native (Expo); Laravel receives the scans and MySQL stores them.

Read the case study →

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

  • A night shift crosses midnight. Which day do the hours land on?

    The hours are the gap between the two ends of the pair, so the calendar boundary does not split them. A shift opening before midnight and closing after stays one span.

  • Several subcontractors work the same site. Whose column gets the hours?

    A scan row carries both the person and the site, and it holds the job it belongs to. Columns total separately; no shared gate device at the entrance makes that call.

  • Someone forgets to scan out. What happens at month end?

    The row stays open, never enters the total, and nothing fills it with an average. The gap stays visible; closing it is a person's decision, not a guess the software writes.

  • What if someone scans for another worker? How far does location go?

    Location ties a scan to the site and rules out one taken from the wrong address. It cannot say who held the phone; we claim no biometric check and do not publish what we have not measured.

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