Kindhearted Operations software
Log in Create account
Documentation ยท Timecards

Timecards Setup Overview

What this does

This overview explains what needs to be in place before Timecards works cleanly for your team.

Timecards is not set up as one isolated app. It depends on people, structure, wages, and pay grouping being configured properly across the Kindio Suite.

What must already be set up

  • the company must have an active Timecards subscription
  • the user must be assigned access to Timecards
  • the staff structure should already exist in the Admin App
  • staff wages should already be set up in the Admin App
  • pay periods should already be set up in the Admin App
  • if labor is expected to follow operational work automatically, the related booking and job structure should already be stable in Booking

Why the Admin App matters here

If you are in Timecards and wondering where to set wages, divisions, teams, services, or pay periods, those core setup items live in the Admin App, not inside Timecards.

That matters because Timecards depends on them for:

  • cleaner labor entry
  • more reliable reports
  • correct grouping and filtering around pay periods
  • better downstream payroll-style workflows

Why Booking can also matter here

If your team expects timecards to follow work that already exists in Booking, the timecard side only works well when the booking-side structure is already clean.

That matters because Booking can supply:

  • the job and schedule context staff are working under
  • the division, service, and team context labor should follow
  • a cleaner starting point for auto-created or repeated labor records

What you can set up inside Timecards

Once the Admin App setup is in place, Timecards gives you the app-specific workflow surfaces such as:

  • manual timecard entry
  • bulk create
  • auto-create
  • drafts
  • viewer
  • reports
  • export settings
  • draft settings
  • permissions and preferences

Recommended setup order

  1. Finish company and staff setup in the Admin App.
  2. Assign the user access to Timecards.
  3. Confirm wages and pay periods are already configured.
  4. If labor should follow jobs from Booking, confirm the booking-side structure is ready.
  5. Configure any Timecards-specific settings such as export, preferences, and drafts.
  6. Start using entry, auto-create, viewer, and reports.

What stays incomplete if skipped

If wages or pay periods are missing, users may still reach parts of Timecards, but the app will not behave as cleanly as expected for labor tracking, filtering, and reporting.

If app assignment is missing, the user may not be able to access Timecards at all.

Related guides