Skip to main content
Time entries grouped by person, showing 8 hours total, a 30-minute unpaid break and 7 hours 30 minutes paid Time entries grouped by person, showing 8 hours total, a 30-minute unpaid break and 7 hours 30 minutes paid Build a report when a preset does not answer your question. It saves its source, columns, widths and date range for reuse.
Creating a report needs Create reports permission. Changing an existing one needs Edit reports and edit access to that report.

Create the report

1

Start a new report

Go to Reports and choose New report.
2

Choose its layout

In Create view, choose Table for one configurable table or Report for a dashboard of table and chart blocks.
3

Name and create it

Give the report a name, choose who can see it, then select Create view.
Each Report block has its own settings and source. For example, compare scheduled shifts in a chart with paid hours in a table. A table block scrolls inside its own box, so a long table never pushes the blocks below it down the page. A printed copy still holds every row, not only those in view.

Choose what to measure

Open the settings and choose Source. Shifts counts shifts only; availability, unavailability and time-off blocks are never counted. Approvals lists each time-off and timesheet request filed in the period, one row per request: who it is about, the Request, when it was Filed at, its status, who it was Decided by and when it was Decided at. Filed by is a column you can add, for a request someone filed for a colleague. A row says that a request was made and how it was decided, never what it asked for: no absence type, note, reason or hours. You see the requests your approvals access lets you open, about the people your access covers. A colleague’s time-off request shows only when you could see it in Absences. Approvals has no chart, and you can filter it by person and period. A request decided over several workflow steps is still one row: its status and Decided by are those of its latest step. The Approval steps group adds, for each of the first three steps, its name, status, who it was sent to, who decided it and when, and whether it was decided by the approver, a substitute or an admin override. A request decided in one step fills only step 1, and a step decided after the period ends still shows on its request. Work items lists each record people logged on their time entries, with its Work item, Item, Quantity and Unit, and the entry’s person, date, location and status. It appears once Work items are turned on for Timesheets. Summarise it by Work item, Item, Person or any other field to total the quantities: Quantity adds them up separately for each unit, so kilograms and metres are never added together. A chart counts records, or sums quantities when Unit is on an axis. Absences counts only the days of each request that fall inside the report period. Leave that started before the period appears in it with its days inside the period, and its start and end columns still show the whole request. Set Summarise by to None to inspect individual records. Choose Person for every calculated column, including norm, overtime and period balances, or choose another grouping to see hours by location, position, date or record field. A Location, Position or Date summary adds up its people’s calculated hours, and Group by splits each summary row by a second field, such as each person by location. Norm and overtime stay on person rows. Under Labels, Clients, Project or Status, the hour columns are calculated too, but the premium and work day columns stay empty. Under Shift type, the calculated hour columns stay empty. Group by takes any field except the one you summarise by. A record with several labels or clients counts under each of them, so those rows can add up to more than the row above them. Under a Person summary, Date lists the days each person worked, with norm and overtime on the person’s row. To add up the whole table, turn on Show grand total in the view settings of a summary. The last row, Total, adds up the summary rows, never the Group by rows under them. It is added from the exact figures and rounded once, so with decimal hours it can differ by a hundredth from the sum of the rounded rows you see. A cell on it stays empty where a column does not add up, such as an average or the People count. A person whose row shows no figure in a column, for example because their hours are not calculated, adds nothing to that column’s total; Info says how many people the total leaves out and in which columns. A summary by a field that can hold several values at once has no total row, because its rows add up to more than the report: Labels, Clients, a person’s Departments, Locations or Positions, and a multi-select custom field. With a person’s days open, the total is that person’s own row. A CSV or Excel download writes the same row last, except a generated file of one person’s days, which has no total row. A list of records has totals too. Show grand total closes the list with a Total row that counts every record once. Once the list has a Group by, Show subtotals closes each group with a Subtotal row. Both add up the exact values under the hour and number columns and are rounded once. Break columns, distances and percentages stay empty on them, and so does Quantity on a Work items list, because one figure could not say which unit it adds up. When the list is grouped by Labels or Clients, a record with two of them counts in both subtotals, so the subtotals add up to more than the total. They cover the whole list from the start, so on a long list a subtotal shows before all of its group’s rows have loaded. A downloaded CSV names each subtotal by its group, and an Excel file writes it under the group’s rows. A summary has no subtotal rows: the row each Group by row sits under already is that group’s total. Show grand total covers a summary and the records under it: with it on, the records you open from a summary row also end with a Total row. The loaded report that Begin shows in place of a live one too large to load at once shows no Subtotal or Total rows on a list of records. To split each person’s hours by where they worked, for example for payroll across several sites, summarise Shifts or Time entries by Person and set Group by to Location, Position or Location and position. Each person’s row stays their total. Under it, Location gives a row for each place they worked, Position a row for each position they worked, which can cover several locations, and Location and position a row for each pair. A row under a person shows the paid time calculated for the work done there (scheduled time on a Shifts report), plus its count and breaks. Overtime, norm and the other figures for the person as a whole stay on the person’s row. Hours that count towards this report’s figure but have no work record, such as qualifying leave, appear under Not set. Total rounding stays on the person’s row, so the rows below can differ by the rounding grid. A work day counts at every place worked that day, so those rows can add up to more days than the person’s. Without access to draft shifts, a Shifts report shows no scheduled time in the rows under a person whose drafts change their scheduled time, because the split counts draft shifts too. On such a report a Location or Position filter keeps the work done there, not the people assigned there. A download writes the location or position in its own column beside the person. When you group individual records, each section heading counts all matching records, including rows that have not loaded as you scroll. Clients groups or summarises a Shifts or Time entries report by the clients the work was for, and the Clients filter offers No client. A record with two clients counts under both, so client rows can add up to more than the report’s total (Seeing work by client). Project does the same for the project the work was for, and its filter offers No project. A record carries one project, so project rows add up to the report’s total. Choose the columns that answer your question. For example, put Total hours, Unpaid break and Paid time beside each other to check how breaks affect paid hours. The hour columns explains the differences. Identification number, Payroll export code, Birthday, Bank account (IBAN), Account holder and BIC/SWIFT columns need both people access and View private details for each person. If either permission covers only part of your team, the columns show values only for people covered by both. Contract number, Payroll contract ID, Probation end, Internal contract ID, Address and the three emergency contact columns need people access. Job title needs no extra access: anyone who may open the person’s profile sees their current title there. Without that, the cell is blank. With people access, it shows the title from the contract overlapping the period: the active one, otherwise the one that started last. A column heading wraps onto up to three lines, so every column shows its full name, and a column never gets narrower than its heading needs in your language. Drag a heading’s right edge to widen or narrow its column. A column’s menu opens from …, a right-click, or on a phone or tablet a tap on its heading. To move a column, drag its heading; on a phone or tablet, rest a finger on it, then slide. Move left and Move right in the column’s menu do the same without dragging. In a person summary the Person column stays first. Everyone reading the report gets the saved width, except that a 390px-wide phone caps the name column at 160px, or at its heading’s width where that is wider, so other columns remain reachable. Presets and reports shared with view access keep the author’s widths. Long names, notes and labels wrap inside their columns, including in print. A person summary’s Absences column names each policy with its days, such as “Annual leave: 2 days; Training: 1 day”, the same text a download carries. Report cells show names and labels in words, without avatars, icons or colour dots. If you can edit the report, widen a column when a long entry makes its row too tall. On a chart block, Break down by splits a bar, horizontal bar, line or area into one coloured series per value. A pie or radial chart has no second dimension to draw with, so it offers no breakdown and refuses a saved one. Every source can also show the person each record is about. In the column list, Person holds their Profile, Organization, Contract, Contact and bank and Custom fields, with profile and organisation values read as they are today and contract values as described below. Every person field works as a column and a sort. A field of answers also works as Summarise by, Group by, and a chart’s axis or Break down by: Status, Gender, Departments, Top-level department, Locations, Positions, Manager, Contract type, and a dropdown, checkbox or multi-select custom field. On a People report, Status, Positions and Contract type are the report’s own columns, which do not summarise or chart. Those fields filter too, and so do Age, Employee ID, Employment start and custom fields of text, numbers or dates. Job title, Contract number, Payroll contract ID, Probation end, Phone and Email never filter. A person in two departments, or with two answers to a multi-select field, counts under each. Gender and Age need access to personal data, and Custom fields, Employee ID, Contract type, Employment start, Phone and Email need people access; a reader without it is not offered them. Phone and Email show even for a person who hid their contact details, as their profile does with that access. A multi-select field sorts by its alphabetically first answer and cannot head a list’s sections. A CSV or Excel download writes custom fields as the screen shows them: a number as a number, a date as its day and a checkbox as Yes or No. If that access covers only some of your team, everyone else counts under Hidden by your permissions, never under Not set, which keeps meaning that no value is recorded. A filter on such a field leaves those people out, and Info says how many, or that the number could not be counted. A colour rule on such a field never colours those people, whatever the rule says. A saved report grouped, charted or filtered by such a field tells a reader who has that access for nobody which permission it needs instead of showing figures. On Shifts, Time entries, Absences, Absence balances and Approvals, the person’s Contract group also offers Job title, Contract number, Payroll contract ID and Probation end, all hidden by default and requiring people access. Contract fields, including Contract type and Employment start, use the contract in force on each record’s start day. An absence uses its request’s original start day, even when it began before the report period, and an approval uses the start day of its request. Balances use the contract at period end, or the last contract held during the period; if none covered the period, the cells stay blank. Employment start is the first day of the continuous employment that contract belongs to, so a record from before a rehire shows the first hire. A filter on Employment start judges the person, not each record. On a People report it uses the contract the row shows: the active contract overlapping the period, otherwise the one that started last. On other reports it uses the person’s contract at period end, or the last contract held during the period, and keeps or leaves out all of that person’s records. Probation end includes approved leave that extends probation. Existing reports keep their selected columns. Open Contract type and choose This record to keep matching shifts, time entries or absence requests. Choose Person during the period to keep people who held that type on any day of the period, with all their records. You can use both filters together. People, balance and approval reports offer only the person filter. The chips name the selected scope, and Info explains its rule. The report data source settings beside a table of hours The report data source settings beside a table of hours

Set the period and filters

Choose the period before comparing figures. On a table report, the date range sits at the top of the page, in the middle of the bar; people who cannot edit the report see it there but cannot change it. On a report built from blocks, each block has its own Range in its settings. For payroll and period balances, use a whole calendar month, such as This month or Last month. A rolling range such as Last 30 days is not the same period. Filter narrows the records. On a report grouped by person, a Position, Location or Department filter keeps the people who hold it, with all of their work, so the result matches the position each row shows. On any other report it keeps the shifts or time entries that carry it. Check the saved Status filter: on both Timesheets and Shifts reports every calculated figure follows the selected statuses, so Pending or Cancelled shows the norm, overtime and period balance those records would give. With no status filter, a Timesheets report lists every status but calculates approved work only, so clearing the filter can add records without adding their hours to a calculated total. Ticking every status is different: it calculates every record. If you cannot edit the report, your filters apply to you only and are not saved. Duplicate the report to keep them.
A filter that narrows a person’s work, such as a label, can make norm and overtime unavailable for the people whose work it narrows. On a Shifts report a status filter never does. People the filter leaves unchanged keep their figures. Open Info to see which rule applies.

Reuse the result

Open the report again to use its saved setup with current data. Each reader sees only the rows their permissions allow, and a row they can see may still hold back a column they cannot: on screen, a colleague’s absence lists without the reason behind it unless you have View others’ time-off details. A generated file asks the same question when someone opens it, so a reader whose access to the people or columns it covers has changed cannot download it; running the report again gives them a file with their current access. Click a person’s row to read the day breakdown, or share the report with someone who needs it. A person summary adds rows as you scroll through a large team or date range; the count above it covers the whole report. Name and position sorts order everyone before showing the first rows. An hours sort waits for every figure, so a very large report may ask you to shorten the range or filter. Sorting individual rows by person also needs every person first; on a team of several thousand, use another sort or filter. A list of records you have not sorted reads in date order: shifts and absences by when they start, time entries by date and then start time, and people by first name and then last name. An arrow beside each of those headings shows it. Sort by any column to replace it. Absence balances keep your team’s order.

Next

The hour columns

Choose the figure that matches the question.

Reading a day breakdown

Follow a person’s total down to the days and records.

Still need help?

Contact support

Email the Begin team and we’ll get back to you.

Ask Begin AI

Open the AI assistant and get instant answers based on these docs.