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

Process Tracking for Ankara businesses

If you work inside a multi-unit institution in Ankara, a request starts by joining a queue: a unit fills in a form, the centre works through them in order, an answer returns days later. For a multi-unit institution weighing process tracking software in Ankara, the bottleneck is rarely how long that queue is. It is that every first answer has to leave through one door. Tahlil.com splits that door in two.

Get a quote Tell us about your project

Process Tracking — Ankara

In Ankara a request may pass through the centre before it reaches the unit that will answer it: one head office, several units beneath it, a request list behind each. The first thing process tracking brings to mind is a report; the harder question is where a request first lands. The closest thing in our portfolio to that way of working is Tahlil.com, a health technology platform: someone enters a value, a qualified physician writes and approves the reading, and the approval returns as a notification. Where it does not overlap is worth naming: Tahlil.com was written for health technology, and we have nothing to show for corporate approval chains or budget workflows. Beneath it Laravel runs the flow, MySQL holds the records and Redis the cache, with React Native (Expo) and OneSignal on the phone.

  • A request does not have to come through one door: the calculator opens its own entry point, and work that needs a human reading stays in the main flow.
  • Writing the reading happens in one panel; a model prepares the first pass, but the text that reaches the other side leaves the hand of the physician who approved it.
  • When a result is ready it calls its owner back, carried by an OneSignal notification, so nobody sits refreshing a list to find out.

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

Tahlil.com — the calculator opens a second way in, approval stays with the physician

A patient enters a test value and a physician writes the reading; website, physician panel and mobile app hang off one Laravel core. What this page leans on is the entry side: the tahlilmatik calculators open a second door into the platform. A user types one value and sees which reference range the result falls in, with no appointment in between. In the panel a model prepares the first pass and the physician approves the reading; responsibility stays with whoever signed it. An OneSignal notification then calls the person back. MySQL holds the records, Redis carries the cache.

Read the case study →

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

  • Requests already arrive through a form. Would a second entry point not add noise?

    It does not, because the two carry different questions. The calculator takes what can be answered on its own, while anything needing a human reading stays in the main flow. The noise comes from putting both kinds into one queue.

  • If a model does the first pass, who is answerable for the answer?

    Whoever approves it. In Tahlil.com the model prepares a reading and a physician writes and approves the final one in the panel. We never push a generated output straight out; what reaches the other side has passed a person's approval.

  • Is there an address in Ankara where we could meet your team?

    We keep no office and the team works entirely remotely — that is the working model itself, not a gap in it. Tahlil.com's two entry doors were separated in writing before the build: which questions a calculator answers, and which reach the physician panel.

  • How does the right person find out when a process finishes?

    A notification goes out when the record is ready; in Tahlil.com OneSignal carries it. Nobody refreshes a screen by hand, the result comes back to them. We draw no savings figure from that, because we have measured none.

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