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

Process Tracking for Besiktas businesses

A group running several units ends up keeping every part of its work somewhere else: the timetable in a calendar, the roll in a spreadsheet, collections in another program, and the report stitched together by hand once a month. When you go looking for process tracking software in Besiktas, the trouble is rarely visibility. It is that one record now exists in more than one copy. Vipkurum was built from the other end.

Get a quote Tell us about your project

Process Tracking — Besiktas

Besiktas is thick with head offices and multi-brand corporate groups, and the stretch between Zincirlikuyu and Levent is the visible part of it. If management sits at the centre while the work happens at other addresses, the picture at the centre is assembled from files sent in and arrives a day late. The closest work in our portfolio to that sector profile is Vipkurum. It was written for education institutions; we have nothing to show in agency work, media planning or brand communications, and campaign reporting is something we have never built. What overlaps is the part about roles and rights: a teacher, a parent and an administrator reach the same record only as far as their permission goes. React runs the panels on a Laravel core, MySQL and MongoDB hold the records, Redis carries the cache. We have no physical address and the work runs remotely.

  • The timetable, the class, the section, the exam and the payment entry live in one data model, so no function needs a program of its own to be reconciled later.
  • A teacher, a parent and an administrator open the same record to the limit of their permission, so who sees what is answered by rights rather than by copies.
  • Announcements, messages and notifications move inside the same system, and invoices, payments and analysis reports are derived from those records instead of a sheet kept beside them.

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

Vipkurum — timetable, exam, payment and reporting in one data model

A platform built for education institutions. Timetable, class, section, exam, student, parent, payment and reporting entries sit in one data model, so no month-end pass lines separate programs up. A teacher, a parent and an administrator reach the same record to the limit of their permission. The content management layer lets an institution build its own lessons, tests, questions and exams, and because the institution defines the assessment type itself, a new marking scheme waits on no code change. React drives the panels, React Native (Expo) the mobile side, Laravel the core; MySQL and MongoDB hold records, Redis the cache.

Read the case study →

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

  • Each of our units runs its own program. What does one platform change?

    Not the number of screens — the number of copies a record has. Keep the timetable, the exam and the payment in three programs and month end means matching three lists by hand. In one data model that matching step never arises.

  • Our way of marking is not a standard one. Does the system take it?

    On Vipkurum the institution defines the assessment type itself. Lessons, tests, questions and exams are built on the institution's side through the content management layer, so a new marking scheme does not queue behind a code change.

  • Vipkurum is education work. Our head office is not a school. What carries?

    We wrote Vipkurum for education institutions and we say so plainly. What carries is not the sector but the way roles are cut: several parties reach the same record, each to the limit of their permission. Agency, media and brand communications work is not something we can show.

  • Sitting at the centre, how far do we trust a figure a unit sends up?

    The record opens where the work happens rather than travelling to the centre as a file. Reports are derived from those records, and with no second sheet maintained by hand alongside, two figures have nothing to disagree about.

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