IMPLEMENTATION GUIDE

Clear rules for working with CrewTango

Data scope depends on the app, features, role and company settings. Before starting, define what is recorded, why and who can see it.

Roles and permissionsOptional locationOptional screenshots
CrewTango desktop app and computer work settings
RULES

Work recording should be transparent and proportionate

A good rollout starts with a clear explanation of the data used, its purpose and who can access it.

Clear data scope

Your company decides whether to use time tracking alone or add optional location, screenshots, photos or computer work details.

Role-based visibility

Employees, managers and administrators can have different visibility scopes.

Data needed for work

Collect information that supports pay calculations, planning, safety or work documentation.

Settings aligned with rules

Recording scope should follow documented company rules and system settings.

DATA SCOPE

The scope depends on the features used

AreaExample informationWhen it may be needed
Working timestarts, finishes, breaks and projectsattendance, pay calculations and planned-versus-actual comparisons
Mobile apptasks, photos, comments and optional locationfield work and site documentation
Desktop appapps, websites, optional screenshots and keyboard and mouse usage datacomputer work and productivity categories
Shared attendance deviceclock-ins, clock-outs, breaks and the selected identification methodshared attendance terminal for multiple employees
Reportstime summaries, overtime, allowances and costsapproval and pay calculations
Care homesresident records, contacts, care plans, action history and NFC identifiersstaff viewing information and recording care with defined access
Documents and signaturestask details, signers, statuses and the final PDFpreparing and confirming a document within an agreed process
Cleaning and warehouselocations, feedback, photos and material movement historyservice quality checks and operational work records
GOOD PRACTICE

What should you agree with the team before starting?

When the app runs

Explain how employees start and stop time tracking and when the app records information.

Who sees reports

Define what employees, managers, administrators and business owners can see.

Whether you use location

Enable it where it supports field work or attendance confirmation.

Whether you use screenshots

Define the purpose, frequency and rules for desktop app screenshots.

Whether you use additional data

Keyboard and mouse data is an optional setting.

How review works

Define who reviews exceptions, approves entries and answers employee questions.

LEGAL DOCUMENTS

Keep this guide separate from binding documents

This page describes good implementation practices. Current legal documents are published separately and should be read in their full wording.

Frequently asked questions

No. The scope depends on the app, enabled features, role and company settings.

No. It is an optional field work feature that should follow clear rules.

No. Screenshots are an optional desktop app feature controlled by company settings.

The scope depends on settings, but employees can be given access to their time and summaries.

No. It is an implementation guide. Links to the current privacy policy and terms are above.

Roll out the app with clear rules

Start with five people, explain the data scope and check settings before expanding the rollout.