ScreenJournal

What reports can ScreenJournal generate?

Updated on 6 July 2026

ScreenJournal generates team reports from the work itself. A weekly digest opens with the biggest change of the week and who needs a check-in, and a template gallery covers productivity, attendance and billing. Because every report derives from AI-written work timelines, the numbers describe real output, not screenshots or activity percentages.

Most team reporting is assembly work: a manager stitches together dashboards, ticket queues, memory and a few pings, then writes the summary by hand. ScreenJournal removes the assembly. It already writes a work timeline for each person as work happens, so a report is simply that record, organised around a question a manager actually has.

What is the weekly digest?

The weekly digest is a prepared report that opens with the biggest change of the week, then shows who is thriving and who needs a check-in. It reads like a briefing rather than a dashboard: the point is what changed and where attention should go, not another grid of charts to interpret.

Because the digest derives from timelines, its statements are about what was actually produced. A week that looks quiet in app-usage terms but shipped something substantial reads as what it was: a good week. That is the difference between reporting on the work and reporting on the tools.

Proof: the rendered Weekly Digest view. Screenshot alt text: "A rendered ScreenJournal weekly digest opening with the week's biggest change, followed by team highlights and check-in suggestions."

A rendered ScreenJournal weekly digest opening with the week's biggest change, followed by team highlights and check-in suggestions.

How does ScreenJournal generate reports?

Reports are generated in three steps, and none of them involves anyone filling in a form. First, ScreenJournal reads on-screen work as it happens and writes a timeline for each person: apps, durations, plain-English summaries and scores. Second, the raw screen data is deleted immediately during processing, so every report reads from the derived record, never from footage. Third, you pick the report: open the weekly digest, choose a template from the gallery, or reopen a saved report, and it renders from the same record.

Proof: the template gallery and saved reports in the Reports area. Screenshot alt text: "The ScreenJournal Reports area showing the report template gallery and a list of saved reports."

The ScreenJournal Reports area showing the report template gallery and a list of saved reports.

What report templates are available?

The template gallery covers the questions managers ask most, and a saved report keeps any configured version one click away. In one sentence: each template answers a specific management question from the same underlying record of real work.

ReportThe question it answers
Weekly digestWhat changed this week, and who needs attention?
ProductivityWhat did each person and team actually produce?
AttendanceWho worked, when, and for how long?
BillingWhere did billable time go, by client and project?

Billing reports draw on the same mapping as AI timesheets, so the hours a client sees and the report a manager reads come from one record rather than two competing spreadsheets.

How is this different from an employee activity report?

An activity report scores how busy the tools looked: which apps were open, which sites were visited, how often the mouse moved. A ScreenJournal report describes what was produced, because it is generated from the work itself. The distinction matters because activity is a proxy that fails in both directions: time in the right apps counts as productive even when nothing is produced, and focused, low-click work looks idle. Reports built on output do not inherit those errors, and they give a manager something an activity chart never can: a plain-English account of the week. For the fuller picture of how the approaches differ, see ScreenJournal vs the alternatives.

Ask the question directly. Ask AI sits on every page of ScreenJournal and answers in plain English from the derived record, not footage: who is stuck, what is about to slip, where the billable hours went last month. And because timelines accumulate into a searchable chronicle, past work is as answerable as this week's; questions can also be asked from your own AI tools through the ScreenJournal MCP, permission-scoped by role. The digest and templates handle the recurring cadence; Ask AI handles everything in between.

Who are these reports for?

Managers of remote, hybrid, offshore and BPO teams get the Monday picture without building it, in time for the day's first conversation. Team leads get a digest that replaces the status-collection round, so meetings start from what happened rather than establishing it. Operations and finance get attendance and billing rollups from the same record the timesheets come from.

Employees are not on the outside of any of this. They see the same activity view managers do, scores are contestable through "Change my score", and personal entries are auto-hidden with redaction available before a manager sees anything. A report generated from real work is also the report that finally makes quiet, productive weeks visible.

Reports and weekly digest FAQs

What is in the ScreenJournal weekly digest?

The weekly digest opens with the biggest change of the week, then shows who is thriving and who needs a check-in, all derived from the week's work timelines. It is a briefing to act on rather than a dashboard to interpret.

Do I have to build the weekly digest myself?

No. ScreenJournal prepares the digest from the week's timelines; you open it and read it. Templates and saved reports work the same way, so a report is something you pick, not something you assemble.

Do reports include screenshots?

No. ScreenJournal deletes raw screen data immediately during processing, so there is no footage for a report to include. Every report is built from the derived timelines.

Can employees see the data behind the reports?

Yes. Employees see the same activity view managers do, and productivity scores are contestable through "Change my score". Personal entries are auto-hidden, and employees can redact entries before a manager sees anything.

What is ScreenJournal?

ScreenJournal is an AI work visibility tool that reads on-screen work as it happens, turns it into a detailed timeline of what each person actually did, and then deletes the raw screen data. Timelines accumulate into a searchable chronicle of everyone's work history, and from them ScreenJournal generates timesheets and reports automatically and drafts standup summaries on request, answering questions about any of it in plain English.

See the work itself, not screenshots of it

Timesheets, reports and answers from the work your team actually did. Available for Windows and macOS, with Linux and mobile support coming soon.