> ## Documentation Index
> Fetch the complete documentation index at: https://docs.yrka.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Go-live checklist for launching Yrka

> Run through every pre-launch check — access, data, billing, integrations, and permissions — before your team starts production work in Yrka.

Before your team starts real operational work in Yrka, run through this checklist to confirm that access, data, billing, integrations, and permissions are all in order. The goal is to catch gaps before they affect your employees — not after timecards are submitted or schedules are published. Work through the checklist with your launch owner, and record any accepted gaps along with who owns the follow-up.

<Warning>
  Complete the setup readiness pass at `/admin/onboarding` before using this checklist. Use non-production test data for any destructive or provider-facing verification steps.
</Warning>

## Owner and admin access

<Steps>
  <Step title="Confirm the owner can sign in and reach Billing Account">
    The owner needs access to `/admin/billing` to manage the plan, handle payment issues, and request exports or account changes. Verify this works before go-live, not during a payment crisis.
  </Step>

  <Step title="Verify email and password sign-in works">
    Confirm email/password authentication is working for at least one admin account before enabling Google or Microsoft sign-in. If external provider sign-in fails after launch, you need a fallback path.
  </Step>

  <Step title="Review allowed domains and pending access behavior">
    Confirm which email domains are allowed for self-serve access and what happens when someone from an unrecognized domain tries to sign in. Pending access requests should route to an admin who can approve or deny them promptly.
  </Step>

  <Step title="Review admin role assignments">
    Check that every admin has the right permission scope for their role. Admins with broad permissions can affect billing, payroll exports, employee records, and sensitive writes. Remove access that is broader than needed before inviting your team.
  </Step>
</Steps>

## Company data and configuration

<Steps>
  <Step title="Confirm company profile is complete">
    Business name and timezone must be correct before employees start submitting time. Schedules, payroll periods, and reports all depend on these settings.
  </Step>

  <Step title="Confirm employees are added and ready">
    All active employees should be in the system with correct job assignments, department memberships, and team affiliations. Verify that no placeholder or demo employees remain in the active roster.
  </Step>

  <Step title="Confirm jobs, payroll settings, and timekeeping settings">
    Company job types, payroll period anchor, overtime rules, break settings, and rounding should all be set before the first timecard is submitted. These settings are difficult to correct retroactively.
  </Step>

  <Step title="Confirm departments, teams, and job roles exist">
    Resources, training, reports, schedule filters, and access reviews all depend on organizational structure. Confirm that at least the foundational structure is in place so these areas do not look empty on day one.
  </Step>

  <Step title="Confirm schedule defaults are configured">
    Review schedule templates and default shift settings so the first publish cycle does not require starting from scratch.
  </Step>

  <Step title="Confirm resources and training are published and targeted correctly">
    Any resources or training content that employees should see on day one should be published and targeted to the right teams, roles, or departments. Verify acknowledgement tracking is enabled for required content.
  </Step>
</Steps>

## Sample data separation

<Steps>
  <Step title="Confirm no sample data is mixed with production records">
    Demo or sample records left in a workspace that also has real data corrupt reports, payroll exports, and employee-visible content. If any sample data remains, contact support before going live — do not try to clean it up manually while real records exist alongside it.
  </Step>
</Steps>

<Warning>
  This is one of the most common causes of launch problems. If you ran starter actions or imported demo data during evaluation, verify that every one of those records has been removed or is clearly separated before real employees start using the workspace.
</Warning>

## Employee access and permissions

<Steps>
  <Step title="Confirm employee app access is enabled for the right profiles">
    Employee app access is enabled per-profile. Confirm that every employee who should be able to use the employee app has it enabled, and that employees who should not have access do not.
  </Step>

  <Step title="Confirm document and payroll visibility settings">
    Check that paystub visibility, document access, and any sensitive record settings are configured correctly. Employees should only see what their role and your policies allow.
  </Step>

  <Step title="Confirm timecard write grants and correction permissions">
    Employees with timecard write access can submit entries and corrections. Verify these grants match your operational policy — some organizations allow self-correction; others route all corrections through a manager.
  </Step>
</Steps>

## Integration and provider readiness

<Steps>
  <Step title="Confirm your launch integration path is truthful">
    Review what each provider connection actually does at launch: file handoff, reviewed import, provider-gated setup, or live sync into review surfaces. Do not describe a provider as active until credentials, authorization, and a verified adapter are all in place.

    <Note>
      Provider readiness in the setup checklist means the connection has no visible issues. It is not proof of live automation until end-to-end verification is complete.
    </Note>
  </Step>

  <Step title="Confirm payroll export behavior">
    Payroll-prep exports are handoff files or reviewed packages — they are not a direct payroll submission. Confirm that your payroll provider or processor has received and can work with the export format Yrka produces.
  </Step>
</Steps>

## Scheduling and timekeeping edge cases (if applicable)

If you are launching scheduling and timekeeping, confirm your setup handles the following scenarios before real shifts begin:

<AccordionGroup>
  <Accordion title="Early and late clock-in">
    How does the system handle someone who clocks in significantly before or after their scheduled start? Confirm rounding, grace period settings, and supervisor notification behavior.
  </Accordion>

  <Accordion title="No-show and missed clock-out">
    What happens when an employee never clocks in for a scheduled shift, or clocks in but never clocks out? Confirm missed-clock-out handling and no-show alerts are configured.
  </Accordion>

  <Accordion title="Break tracking">
    If your operation requires tracked breaks, confirm break rules are configured and that employees and managers understand the process.
  </Accordion>

  <Accordion title="Location and geofence">
    If clock-in requires a location check, confirm geofence boundaries are set correctly and that employees understand what happens when they are outside the fence.
  </Accordion>

  <Accordion title="Kiosk and offline clock-in">
    If you use a shared kiosk device, confirm kiosk credentials are working. Confirm what happens when an employee tries to clock in without a network connection.
  </Accordion>

  <Accordion title="Timecard corrections and payroll readiness">
    Walk through a timecard correction from the employee side and the admin side to confirm the workflow works as expected before the first payroll period closes.
  </Accordion>
</AccordionGroup>

## Billing and account state

<Steps>
  <Step title="Confirm billing is active and the plan covers your roster">
    Verify that your account is in an active or trialing state, your employee count is within plan limits, and you understand the renewal or upgrade path. See [Billing and account lifecycle](/setup/billing).
  </Step>

  <Step title="Confirm the support tier and support path">
    Know who to contact and through which channel when something goes wrong. Confirm support contact details are documented and accessible to your admin team.
  </Step>
</Steps>

## Final review and handoff

<Steps>
  <Step title="Record accepted gaps and their owners">
    Any checklist item you intentionally skipped or deferred should have a named owner and a next-action target date. Do not hand off the workspace to your team with unresolved gaps and no plan to close them.
  </Step>

  <Step title="Complete the go-live review step in the onboarding checklist">
    Return to `/admin/onboarding` and confirm the go-live review step. This signals that the workspace has been reviewed and is ready for production use.
  </Step>
</Steps>

<Note>
  This checklist supports launch readiness. It is not a formal compliance attestation, SOC 2 report, uptime guarantee, or legal approval. Yrka's payroll-prep exports prepare data for your payroll provider — Yrka does not process payroll or file taxes.
</Note>