WORKFORCE INTELLIGENCE
SyncAI summaries and explainable scores

Understand the signals behind the score.

A single number needs an explanation. Sync combines activity signals and available screen context into AI summaries, then exposes the factors behind its productivity estimate.

Windows · macOSAndroidBuilt for human review
THE WORKING PICTUREIllustrative example
Device signalsApps · time · activity
Context changes the story.

Quiet keyboard. Active conversation.

INPUT SIGNALLow typing
AVAILABLE CONTEXTMeeting in progress
AI INTERPRETATION

A meeting can be work, even when the keyboard is quiet. Inspect the evidence. Keep the human context.

Follow the signals
Interactive product walkthroughSynthetic data
FROM SIGNALS TO A USEFUL CONVERSATION

Context changes the story.

AI interpretation
Low typingMeeting in progress

A meeting can be work, even when the keyboard is quiet. Inspect the evidence. Keep the human context.

  1. 01Device signals
  2. 02Available context
  3. 03AI interpretation

Illustrative product experience · example data · no live actions

FROM SIGNALS TO A USEFUL CONVERSATION

The picture. The pattern. The why.

Change the team and period. Explore the activity behind an AI interpretation and the factors behind its score. Every number here is illustrative.

Interactive product walkthroughSynthetic data
WORKFORCE OVERVIEW

Engineering

Illustrative score81/ 100

Seven weighted factors

Average focus time / day3hr 29min

Within available activity

Activity coverage94%

An example coverage indicator

Patterns to review5

People decide what they mean

Activity score trend

Last 7 days
Period startPeriod end

Application mix

65%Role-relevant app time
  • Productive tiers65%
  • Neutral25%
  • Unproductive tiers10%
Five role-aware tiers, grouped for this view.
AI review brief

Longer focus blocks appear around development tools. Collaboration rises later in the day. Review switching patterns with the team before deciding whether they interrupt useful work.

A seven-day review of available activity. An interpretation to review, not a verdict.

Synthetic walkthrough, not employee data. Scores estimate digital activity; they do not establish work quality or make employment decisions.

THE CONNECTED WORKING PICTURE

AI summaries and explainable scores

Use explainable estimates to guide review, then bring in the context only your people know.

AI summaries and explainable scores

Understand the signals behind the score.

Use explainable estimates to guide review, then bring in the context only your people know.

01

Minute, hour and day narratives

Read what the analysis suggests happened, then inspect the underlying activity. AI summaries can be incomplete or mistaken.

02

Seven visible score factors

Explore active time, app productivity, engagement, focus, availability, consistency and context switching. Review the policy used for your rollout.

03

Role-aware app classification

Use five classification tiers and organization overrides. A design tool, a browser or a social platform can mean different things in different jobs.

04

Evidence before conclusions

Open the activity behind a summary, compare periods and ask the employee for context. A score is an estimate, not a measure of personal worth or work quality.

VISIBILITY WITH A PURPOSE

One working picture. Different responsibilities.

Shape access and review around the people who need it. Confirm the exact role permissions and employee-facing experience in your pilot.

Understand the organization, without losing the detail.

Compare branches and departments, inspect changes over time and agree where a closer review will help. Use the activity picture alongside business outcomes.

START WITH YOUR WORK

Your industry. Your working context.

Start with a question your team needs to answer. These example opportunities are a guide to scoping a pilot, not customer results.

Technology teams

Where is focused work being interrupted?

Explore development, design and collaboration patterns. Interpret app changes in the context of the role, not as automatic distraction.

Explore this with our team
CONTEXT IS PART OF THE PRODUCT

Clarity for leaders. Transparency for people.

The strongest rollout starts with a shared understanding of what is collected, why it is useful and who can review it.

Define capture boundaries

Agree device scope, working schedules and screenshot settings. Screens and window titles may include visible work content; configure them with care.

Make access intentional

Confirm roles, retention and evidence-review controls. Give administrators and employees a clear explanation of the policy in force.

Keep judgment human

Use flags to open a conversation about workload or changed patterns. Check the data and ask for context before taking action.

Explore the governance approach
GO DEEPER

Explore the whole working picture.

START WITH A FOCUSED PILOT

Make the first rollout meaningful.

Bring a team, a device mix and the questions you want to answer. We will help scope the setup, policies and review criteria before you expand.

  1. 01Agree the questions and collection boundaries
  2. 02Configure devices, roles and schedules
  3. 03Review the evidence with your team

Shape your conversation

Plan my Sync pilot

Your selections prepare an editable inquiry. Our team confirms current pricing, device scope and the right next step.

What to bring to the first conversation

Map job roles to relevant applications.

Review score factors, weights and exceptions with your team.

Agree how managers validate AI interpretations.

GOOD QUESTIONS. CLEAR ANSWERS.

Before you bring Sync to your team.

Speak with our team
What is Block Gemini Sync?

Sync is workforce activity intelligence software. It brings device activity, application use, AI summaries and explainable productivity estimates into a reviewable view of the working day. It helps people understand patterns and decide what to investigate.

Is the score a measure of work quality?

No. The score is an estimate based on the available digital activity and configured policy. It cannot capture every kind of work or judge someone’s value. Review it alongside output, role context, data coverage and a conversation with the employee.

Does Sync only count keyboard and mouse activity?

No. Activity counts are one input. The analysis can also use application and window context, operating-system activity and configured screenshots. Reading and call participation need context; a quiet keyboard alone does not mean no work is happening.

What should employees know about capture?

Your organization should explain the purpose, schedules, signals, access and retention before rollout. Input telemetry uses counts rather than typed text. Screenshots and window titles can expose visible work content, so their settings and review permissions need deliberate configuration.

Which devices can we include?

Plan your pilot around supported Windows and macOS desktops and approved company Android devices. Our team will confirm operating-system versions, deployment requirements and the signals available for your device mix.

Can one app have different meanings for different roles?

Yes. Application relevance depends on the job. Sync supports role-aware classification and organization overrides, so the review can distinguish a work tool from a distraction in its proper context.

How do we start, and what does it cost?

Start with a conversation about your devices, team structure and the questions you want to answer. We will confirm current pricing, rollout scope, setup support and the pilot criteria before you commit.

Are these examples real employee records?

No. Everything shown in this website walkthrough is synthetic and illustrative. It demonstrates how a review could work without publishing private employee activity, screenshots or customer results.

Better visibility starts with a better question.

Let us explore what your team needs to understand.

Existing customer login