The Book of GetSkipa Timekeeper

Timekeeper was created to solve a plain business problem. People begin work, stop work, move through a day, and eventually someone has to decide whether the recorded time is complete enough to review and export.

That work sounds simple until the record is spread across paper sheets, text messages, spreadsheets, memory, and software that tries to solve more problems than the business asked it to solve. Timekeeper stays close to the original problem. It records work time, preserves the history, helps workers and managers review it, and gives the business reports that support payroll review.

This book explains how the application works and why it was built this way. It is not a sales document. It is not a legal opinion. It is the operating reference for GetSkipa Timekeeper.

Timekeeper is not payroll software. It does not calculate taxes, deductions, benefits, insurance, wages, or direct deposits. It does not replace a payroll provider, accountant, bookkeeper, or labor law responsibility. Timekeeper is a timekeeping system that produces organized, payroll ready time records.

Every chapter is written for the same purpose. The reader should understand what Timekeeper does, why it behaves that way, and what the business remains responsible for deciding.

GetSkipa built Timekeeper around a simple promise. Time records should be accurate, understandable, and consistent.

A worker should be able to see the time that belongs to them. A manager should be able to review that time without guessing where the numbers came from. An owner should be able to export a report and see the same story that appeared in the application. When something changes, the change should be visible in the audit history.

This commitment shaped the application. Clock events are preserved. Manager edits are recorded. Worker approvals and manager approvals are stored as workflow events. Reports are generated from the same accounting engine that supports the dashboards. Timekeeper does not maintain one set of numbers for the screen and another set for exports.

There is also a shared responsibility. GetSkipa provides the system used to capture, store, calculate, review, and export work time. Each business controls how workers use PINs, who is allowed to manage the business, how exported records are retained, and whether the exported data satisfies the requirements that apply to the business in its jurisdiction.

This book is part of that commitment. It explains the product in plain language so businesses can make informed decisions about how they use it.

Small businesses rarely begin by looking for employee time tracking software. They begin with a simpler need. They want to know who worked, when they worked, and what hours should be reviewed before payroll.

The difficulty usually begins long before a business starts looking for timekeeping software. Hours are written on paper, exchanged through text messages, entered into spreadsheets, or simply remembered until the end of the week. Those methods often work when there are only a few people, but they become harder to manage as the business grows. Records get lost. Details are forgotten. Managers spend valuable time trying to reconstruct what actually happened instead of reviewing accurate records.

Even businesses that already use a time tracking system eventually encounter situations that test its reliability. A worker forgets to clock out. A manager corrects a missed punch. Someone works past midnight. A pay period ends during an overnight shift. A worker approves a timecard, then later clocks in again. A business changes a job assignment or moves a team between locations. Each of those events creates a record that should remain understandable weeks, months, or even years later.

Timekeeper exists to handle those situations without becoming payroll software, a human resources system, or a scheduling platform. It records time, applies the business rules configured by the business, and presents the result consistently through dashboards, reports, approval workflows, and exports.

Timekeeper was developed for small and medium sized businesses such as contractors, cleaning companies, landscaping crews, volunteer organizations, and other teams that need dependable employee time tracking without paying for features they will never use. It runs in a web browser on the computers, tablets, and phones a business already owns. Workers can clock in, clock out, review their own hours, and download their personal records from their worker dashboard. Managers and owners review business activity from the management workspace, while crews can share a kiosk on any supported device. Regardless of how time is collected, every record is stored, related, and calculated from the same business data in Cloudflare D1.

The design is narrow on purpose. Timekeeper should be easy to understand on the first day and still trustworthy after months of use. Features that support accurate timekeeping belong in the product. Features that move the product into payroll processing, benefits, taxes, or broad human resources management do not.

A business should begin setup in the same order it intends to operate. Timekeeper allows flexibility, but the cleanest workflow is to create the business, define the worker jobs or work types, define the locations, then add workers and assign them to the correct job and place in the business.

The business record establishes the name of the business, the reporting timezone, the pay cycle used for time review, the cycle start when required, and the weekly overtime threshold configured by the business. These settings influence how time is displayed, how reporting periods are grouped, and how overtime is identified.

Jobs and Work Types should be created before workers when possible. A job or work type identifies the kind of work being performed. A cleaning company might use Cleaner, Manager, Owner, Medical Office, or Apartment Complex. A landscaping company might use Crew Lead, Irrigation, Maintenance, or Shop Work. These names become available when adding workers, assigning kiosks, and filtering reports.

Locations and Sites should also be created before workers. Locations identify where work happens. A business may use customer locations, job sites, buildings, departments, offices, or mobile work areas. Location names appear in worker assignments, time logs, reports, and schedule adherence review.

Workers are added after jobs and locations are in place. The display name is required because it is the name shown throughout the operational experience. First name, last name, and Unique ID are optional metadata fields used mainly for exports and record keeping. A business can also assign a job, assign a location, choose whether the worker is overtime eligible, grant manager access, mark the worker as kiosk only, set an optional schedule, and assign a PIN.

GetSkipa recommends that every worker have a PIN. The business controls its own PIN policy, but assigning PINs during setup creates a clearer operating model and helps prevent accidental use of the wrong worker record. The Owner Dashboard always requires PIN protection because it controls the business.

If the business uses kiosks, kiosk records can be created after jobs and locations exist. Each kiosk has its own URL. That URL can be opened on a laptop, tablet, phone, or another device with a supported browser and camera. Workers authenticate at the kiosk by scanning their worker QR code.

Timekeeper uses a small set of roles so the business can understand who is allowed to do what. The main roles are owner, manager access worker, standard worker, and kiosk only worker.

The owner controls the business. The Owner Dashboard provides access to business settings, workers, time logs, reports, jobs, locations, kiosks, approvals, and account level information. The owner link must be protected because it is the administrative entry point for the business. Timekeeper requires PIN protection for the Owner Dashboard as a built in protection for the customer.

A manager access worker is a worker who has been granted management authority by the business. Managers can review time, approve timecards, edit time records when allowed, reset worker PINs, manage workers, and perform the business functions needed for daily administration. The main practical difference between owner and manager is subscription control. Subscription changes remain with the owner account flow.

A standard worker can clock in, clock out, review personal time, approve personal timecards, view the worker profile, change the worker PIN when available, download personal hours, and download the worker edit log. Workers cannot see other workers, change business settings, manage business reports, or edit their own historical time.

A kiosk only worker is required to clock in from a business kiosk. This setting is useful when the business wants workers to start work from a shared clock station instead of personal worker links. A kiosk only worker who is already clocked in may still clock out from the personal worker dashboard. This prevents a worker from being trapped in an open time entry if a kiosk is unavailable.

The business controls how PINs are assigned and used for workers and managers. Managers may reset PINs for workers inside the business. If no manager is assigned and the owner PIN is forgotten, GetSkipa can assist with owner PIN recovery after appropriate verification.

The business configuration determines how Timekeeper interprets time. The most important settings are business name, reporting timezone, pay cycle, cycle start, and weekly overtime threshold.

The reporting timezone is the timezone used for business reporting. Timekeeper uses IANA timezone identifiers such as America Chicago, America New York, America Phoenix, Pacific Honolulu, and other supported zones. The label shown to the user may include helpful offset text, but the value stored and used by the application is the IANA timezone value. This matters because IANA timezone rules handle daylight saving behavior where applicable.

The pay cycle controls how Timekeeper groups time for review. The supported cycles are weekly, biweekly, and monthly. Weekly and biweekly businesses use a configured cycle start. Monthly businesses use calendar month boundaries. These settings help the application determine current and previous reporting periods.

The weekly overtime threshold is the number of hours after which eligible worker time should be treated as overtime. Timekeeper applies this rule to the business configuration and the worker overtime eligibility setting. IMPORTANT: The business remains responsible for ensuring that the configured threshold matches the labor rules and business practices that apply to it.

Changing business settings can affect how time is displayed and grouped, especially reporting timezone and pay cycle. Timekeeper does not rewrite historical clock events when settings change. It recalculates views and reports from the stored clock records using the current business configuration.

The Time Accounting Engine converts clock events into reviewed time records. It is the reason the owner dashboard, worker dashboard, payroll workbook, payroll transfer CSV, worker hours report, and time log ledger can agree with each other.

The design is simple. Store facts. Apply business rules. Produce consistent results.

When a worker clocks in or out, Timekeeper stores the event as a timestamp in Cloudflare D1. The timestamp represents the moment the event occurred. Timekeeper stores clock events as UTC based instants so the original event does not change because of daylight saving time, travel, browser timezone, or a future change to the business reporting timezone.

When the application needs to display time or calculate a reporting period, it uses the business reporting timezone. That timezone is an IANA timezone value. UTC storage preserves the historical event. IANA based display places that event into the business context.

Cloudflare D1 is the source of truth for time records. Dashboards and reports do not maintain independent totals. They request data through the application and receive results derived from the same stored records and calculation rules.

The engine handles ordinary shifts, overnight shifts, shifts crossing midnight, shifts crossing reporting period boundaries, weekly overtime allocation, worker overtime eligibility, edited records, and approval state. When a shift crosses a reporting period boundary, the original entry remains one historical clock event, but the counted hours are allocated to the correct reporting periods.

Timekeeper was tested with weekly, biweekly, and monthly style reporting logic, timezone changes, Arizona reporting where daylight saving time is not observed, overtime scenarios, cross midnight work, and cross period work. The goal was not simply to see whether a number appeared. The goal was to confirm that the same records produced the same results across worker views, manager views, dashboards, workbooks, CSV exports, and audit logs.

The Dashboard is the administrative workspace for the business.

The dashboards give the business a quick view of current operations. It shows active workers, current hours, approval status, and other indicators that help the owner understand the day without opening every report. Refresh controls are available where live state matters. A refresh updates the visible information without changing the records themselves.

The Workers area is where the business creates and manages worker records. Each worker has a display name, optional first name, optional last name, optional Unique ID, job assignment, location assignment, overtime eligibility, manager access, kiosk only setting, schedule settings, PIN status, and QR code.

The Time Logs area is where the business reviews recorded entries. This is the detailed view. It shows individual clock events, status, edits, job and location context, kiosk context when applicable, and the total time for each visible record. The ledger is also the starting point for exports because exported reports are based on the filtered dataset being reviewed.

The Jobs and Locations areas allow the business to maintain its own vocabulary. A job can represent a work type, customer, department, or project. A location can represent a site, building, customer address, or other place where work happens. The best names are the ones the business will still understand when reviewing records months later.

The Kiosks area is available to subscribed businesses. A kiosk is a shared clock station opened from its own URL. Kiosks may be assigned to a job and location, and the business can choose a camera preference when the device supports it.

The owner workspace is protected because it controls the business. The owner link should be saved carefully. The owner PIN should be kept in a safe place. If a business accidentally removes the worker profile associated with the owner, creating a new worker for that owner can restore owner worker dashboard behavior without changing existing business records.

The Time Logs area is centered on one filtered dataset. That dataset drives the ledger, the KPI cards, and the exports generated from the page. Understanding this model makes the filters easier to trust.

The date range defines the first layer of records. Worker, Job or Work Type, and Location filters then refine the records already visible inside that date range. They do not create a separate reporting period by themselves. A worker filter applied to one day means the selected worker for that day. The same worker filter applied to the complete available history means that worker across the complete available history.

Clear returns the ledger to the complete available dataset stored for the business within Timekeeper retention. When enough historical records exist, the Period label may show the earliest and latest visible log dates rather than a single pay period. That behavior reflects the records currently displayed. The label may be refined in future interface work, but the underlying filter model is stable.

The exports follow the visible dataset. If the ledger is filtered to one worker, the workbook and transfer CSV reflect that filtered view. If the ledger is filtered to a date range and location, the export reflects that same date range and location. A business should be able to review the records on screen before exporting them.

One known limitation exists in the business edit log export. Worker specific edit logs function correctly, and business edit logs function by date range. Job and Work Type filtering for business audit exports may not always return profile edit history because worker profile changes are not inherently tied to historical clock entry job context. This does not affect time calculations, worker specific edit logs, or payroll exports.

Before time can be recorded, a worker must exist in the business. The worker record is the identity that connects clock events, approvals, reports, exports, audit history, and profile information.

The display name is required. It is the name used in the live application. It appears on dashboards, worker cards, time logs, approvals, and daily operations. Timekeeper also supports optional first name, last name, and Unique ID fields. These fields support exports, payroll review, reconciliation, and business record keeping.

The Unique ID is customer managed. Timekeeper does not automatically generate it. Some businesses use employee numbers or payroll identifiers. Other small businesses do not use them at all. The field is optional, but when used it is limited to 10 alphanumeric characters. That limit was chosen to improve compatibility with common payroll systems and spreadsheet imports.

First name and last name are also optional, but they are useful. Some payroll systems rely on employee names when no employee ID is present. Using explicit first and last names gives the business a clean fallback for payroll review and reduces ambiguity in exported files.

Workers may be assigned to a job or work type and a location or site. They may be marked as overtime eligible or not overtime eligible. They may be given manager access. They may be marked as kiosk only. They may have expected work days and expected start and stop times for schedule adherence review.

Workers can be deactivated when they leave the business or should no longer appear in active views. Deactivation removes the worker from the active roster without erasing historical time records. This preserves the ability to review prior activity and export records that belong to earlier periods.

Managers and owners can reset worker PINs, refresh worker QR codes, and update worker metadata. Timekeeper records meaningful worker changes in the audit history so the business can see what changed, who changed it, and when it changed.

The worker dashboard gives a worker access to the information that belongs to that worker. A worker can clock in, clock out, review time, approve a timecard, view profile information, change PIN when available, download hours for current or previous periods, and download the worker edit log.  Note: GetSkipa recommends the owner set the initial PIN when creating the workers profile then advise the worker to change their PIN on their worker dashboard. 

A worker does not see other workers. The dashboard is personal to the worker record. This keeps the worker experience simple and reduces the chance of one worker viewing another worker activity or private data.

Workers may use a personal worker link. They may also use a QR code at a kiosk. These are different credentials for different purposes. The worker dashboard is for personal review and direct clock activity when the business allows it. The worker QR code is used for kiosk authentication only.

The worker timecard approval process gives the worker a chance to review recorded time before manager approval. If a manager edits time after approval, Timekeeper marks the timecard as needing reapproval. If new time is recorded after approval, the approval state updates so the business does not rely on an old approval for new work.

Workers can download their own hours and their own edit log regardless of whether the business is on the free plan or a subscription plan. This gives workers access to their own records without giving them access to business wide exports.

My Profile displays the current worker metadata assigned by the business. It may include display name, first name, last name, Unique ID, job, location, overtime eligibility, kiosk only status, schedule, and QR code access. Empty metadata fields remain blank or visibly unset rather than being hidden.

Approvals are part of the review process. They do not change recorded time. They describe the status of review.

A worker approval means the worker has reviewed the timecard and accepted the recorded time. A manager approval means the manager or owner has completed management review. A bypass is a manager action that allows the manager to accept responsibility for approval when the worker has not approved the timecard.

Timekeeper prevents manager approval while a worker is still clocked in during the selected reporting period. This matters because the time is not complete yet. The worker must be clocked out before the manager can approve that timecard.

If a worker approves a timecard and then clocks in again, Timekeeper recognizes that new time has been added. The previous approval no longer describes the full set of records. The worker receives a notification that the timecard needs review. If the manager later uses a bypass and the worker approves afterward, that worker acknowledgment does not create another manager approval requirement. The manager already accepted responsibility for review through the bypass.

Approval actions are recorded in the audit history. The audit trail can show worker approval, manager approval, bypass approval, approval reset, and the reason a reset occurred when applicable.

A kiosk is a shared clock station. It allows workers to scan a QR code instead of opening their personal worker dashboard. Kiosks are available to subscribed businesses.

Every kiosk has its own unique URL that can be opened on a fixed or mobile device such as a laptop, desktop computer, tablet, or phone. This allows a business to dedicate a permanent kiosk or create a temporary one wherever work is being performed.

A mounted tablet at an entrance can serve as a permanent employee time clock. A supervisor carrying a phone can serve as a mobile time clock for a traveling crew. A team lead at a customer site can open the kiosk URL and allow workers to scan without returning to a central office. Anyone authorized with the kiosk link can temporarily operate that kiosk.

Each worker has a unique QR code used exclusively for kiosk authentication. Scanning the worker QR code identifies the worker and performs the appropriate clock action based on current status. Worker QR codes do not contain the worker dashboard link. If a QR code is lost, copied, or suspected of being shared improperly, a manager can refresh it and issue a new code. The previous code becomes invalid.

Timekeeper intentionally does not require PIN entry at a kiosk. The worker QR code is the kiosk credential. This decision gives businesses more ways to configure kiosk use. A permanent kiosk, a manager phone, a shared laptop, and a tablet carried by a crew lead can all serve the same basic purpose without slowing down the clock process.

Kiosk behavior is simple. If the worker is not clocked in, a scan clocks the worker in. If the worker is already clocked in, scanning any authorized kiosk clocks the worker out. Timekeeper does not currently transfer a worker between kiosks during an active shift. The kiosk shown on the ledger represents the kiosk used to start the clock entry.

Camera support depends on the device, browser, operating system, and available power for external cameras. Timekeeper supports cameras recognized by the browser. Front cameras, rear cameras, laptop cameras, phone cameras, tablet cameras, and external USB webcams were successfully used during validation where the device recognized and powered the camera.

Reports exist so the business can review, preserve, and export time records. They are not separate calculators. They are views of the same underlying records used by the dashboards and ledger.

The Payroll Workbook is the most complete owner report. It includes a summary and detailed time log information for the selected dataset. It is intended for review before payroll data is transferred elsewhere. It helps the business see worker hours, approval state, counted hours, regular hours, overtime hours, worker metadata, and detailed entries.

The Payroll Transfer CSV is designed for movement into another system or spreadsheet. It presents time in a simpler tabular format. The business remains responsible for confirming that any outside payroll system accepts the file format and that imported values are mapped correctly.

Worker Hours is a worker level download. It allows an individual worker to retain records for the current or previous reporting period. Worker Hours remains available regardless of the business plan because the worker is downloading personal records rather than business wide exports.

The Worker Edit Log provides the worker with a history of changes related to that worker profile and time records. It is available to workers on all plans. The Business Edit Log is broader. It helps owners and managers review business level activity such as worker metadata changes, PIN changes, QR refreshes, clock edits, approval events, and manager actions.

The Configuration Report captures the current setup of the business. It is useful when reviewing workers, jobs, locations, kiosks, schedules, and active configuration. It can also help a business document how the system was configured at the time of review.

The Schedule Adherence Report compares expected schedule information against actual recorded time. It is only as useful as the schedule data the business enters. Workers without expected schedules may still appear, but there may be no variance to evaluate.

Owner business exports are a paid plan feature. Worker personal downloads remain available to workers on all plans. Export filenames include the business name and the relevant date range where applicable. Businesses are responsible for their own long term archival needs.

Timekeeper is hosted using Cloudflare infrastructure. The application interface is served through Cloudflare Pages. Application requests are handled through Cloudflare Workers. Business data is stored in Cloudflare D1.

The browser does not connect directly to the database. Requests flow through the application. This allows Timekeeper to apply business isolation, authorization checks, PIN requirements, subscription rules, and validation before data is read or changed.

Timekeeper is a browser based application and requires an active internet connection to record clock activity, save changes, approve timecards, and generate reports. If a device loses connectivity, the requested action cannot be completed until communication with the service is restored. Timekeeper is designed to clearly notify the user when an operation cannot be completed because the device is offline rather than silently accepting or guessing at the requested action.

Each business is logically separated by business identifiers and access context. A business should not be able to access another business records. Worker dashboards are tied to their worker identity. Kiosk scans use worker QR credentials. Owner dashboard access is protected by the owner link and mandatory PIN authorization.

Authentication is shared between Timekeeper and the business. GetSkipa enforces owner PIN use because the owner dashboard controls the business. The business controls how workers and managers use PINs. GetSkipa strongly recommends PIN use for all workers and managers.

Worker QR codes are not worker dashboard links. They are kiosk credentials. This allows the business to replace a QR code without changing the worker dashboard link. Kiosk links should be treated as operational access points. A person with the kiosk link can operate that kiosk device if they also have worker QR codes to scan.

GetSkipa stores business data for fourteen months before purge. Customers are responsible for exporting and retaining records needed for labor, payroll, accounting, or business requirements beyond that period. Free plan businesses with no activity for thirty days may be purged. This policy helps control administrative and storage costs so GetSkipa can keep subscription pricing low.

Exported files leave Timekeeper hosted environment. Once a business downloads a workbook, CSV, edit log, or configuration report, the business is responsible for storing, protecting, and retaining that file.

Timekeeper has a free plan and a subscription plan.

The free plan allows a business to use Timekeeper with up to ten active workers. The owner worker profile counts toward that limit, so a free business can have the owner worker and up to nine additional active workers. The free plan is intended for very small teams, evaluation, and basic timekeeping without business wide exports or kiosks.

The subscription plan unlocks business wide reports, exports, kiosk use, and expanded worker capacity. A subscribed business can use kiosks, download owner reports, export workbooks and CSV files, and manage a larger active worker base.

The trial begins when a subscription is created through Stripe. The customer is not charged during the thirty day trial period. If the subscription is cancelled before the trial ends, the customer is not charged. If the subscription remains active after the trial, Stripe bills according to the selected plan. If the customer cancels after billing, access continues through the paid period.

Subscription status controls paid features. Worker personal downloads remain available independently from the business export subscription model.

Good setup makes Timekeeper easier to trust later. The business should use names that will still make sense when reviewing records months from now. Worker display names should be clear. Jobs should reflect the business real work categories. Locations should describe where work is performed in a way managers and owners can understand.

Create jobs and locations before adding workers when possible. This allows each worker to be assigned correctly during setup. It also improves reports immediately because time records will already include useful context.

Assign PINs to workers and managers. Keep the owner PIN somewhere safe. If the business uses kiosks, print worker QR codes clearly and replace any QR code that is lost, damaged, or suspected of being shared improperly.

Test kiosks before placing them in daily use. The camera should scan worker QR codes reliably under the lighting conditions where the kiosk will be used. External cameras can be useful for fixed stations if the device recognizes the camera and supplies enough power.

Review time before exporting. A good workflow is to let workers approve their own time, let managers review exceptions, correct records when necessary, then perform final approval before downloading business reports. Export reports regularly if the business needs records beyond Timekeeper retention period.

Deactivate workers instead of trying to erase history. Historical records are important for time review and business continuity. Deactivation keeps old records available while removing the worker from active operations.

Timekeeper is intentionally focused on timekeeping. It does not process payroll, calculate taxes, manage benefits, track labor law compliance, replace an HR system, or determine legal obligations for the business.

Manual edits during the repeated hour of a daylight saving time fallback event may be ambiguous because the same local clock time can occur twice. Actual clock events remain stored as UTC based instants. The audit history provides traceability for manual changes.

The business edit log currently works reliably by date range and worker context. Job and Work Type filtering for profile edit history may not behave like clock entry filtering because profile edits are not always tied to the historical job context of a time log.

If the owner worker profile gets deleted or is missing, creating a worker with the owner identity can restore the owner worker dashboard. This is a recovery path for an unusual situation, not a normal setup step.

If no manager is available and the owner PIN is forgotten, the business may contact admin@getskipa.com for assistance with owner PIN recovery after verification. Businesses should keep owner access information in a safe place or assign a manager to avoid relying on recovery.

Cell phones can be used for many Timekeeper functions, especially worker clocking and mobile kiosk use. The fullest management experience is best on desktop or tablet because owner review, filtering, reports, and configuration screens contain more information than a small phone screen can comfortably display.

Timekeeper was validated through real operating scenarios using multiple test businesses. Testing included clean businesses, businesses with existing configuration, free plan behavior, subscribed plan behavior, owner workflows, manager workflows, worker workflows, kiosk workflows, exports, audit logs, filtering, approvals, metadata changes, QR replacement, PIN changes, and camera selection.

Does Timekeeper replace payroll software? No. Timekeeper records work time, organizes it, and exports reports that support payroll review. Payroll processing remains outside Timekeeper.

Do workers need an app? No. Workers use browser based access through their worker dashboard or scan a worker QR code at a kiosk.

Can workers see other workers? No. The worker dashboard is personal to the worker record.

Can workers download their own records? Yes. Workers can download personal hours and personal edit logs regardless of the business plan.

What happens if a worker scans at a kiosk while already clocked in? The scan clocks the worker out. Timekeeper does not transfer the worker to another kiosk during the same open shift.

Why do some short entries show less than one minute? The entry lasted less than sixty seconds. Timekeeper preserves the entry but records zero counted minutes until a full minute has elapsed.

How long is data retained? Business data is stored for fourteen months before purge. Free businesses with no activity for thirty days may be purged. Customers are responsible for exporting and retaining records required for their own long term obligations.

Can GetSkipa reset an owner PIN? GetSkipa can assist if no manager is available and ownership can be verified. Managers within the business can reset worker PINs.

Timekeeper was built around the belief that a business should be able to understand the software it depends on.

The application records work time, preserves the history, applies the configured business rules, and presents the results consistently. That is the core of the product.

Timekeeper was designed around the idea that trust comes from transparency. Workers can review their own time records, approvals, and changes. Managers can review the same business records, including edits and corrections made throughout the payroll period. When time is corrected, the application preserves an audit trail instead of silently replacing the original information. Everyone responsible for reviewing time can understand what changed, when it changed, and who made the change.

Future versions may change the interface, add reports, improve mobile views, or refine workflows. Those changes should remain faithful to the same principles described throughout this book. Records should be accurate. Decisions should be understandable. Data should remain available to the business through clear exports. Software should explain itself instead of hiding behind complexity.

Thank you for trusting Timekeeper with your business.

GetSkipa LLC