If you don’t see this in your navigation, your administrator can switch the module on under Administration → Modules, or it may not be included in your plan.


A report runs as whoever opens it
The screen states this in a box above the list, because it is the thing people most often assume the opposite of. A report does not run as the person who wrote it. Every row passes the same rules you meet everywhere else in the product — your site access, your asset scope and your permissions. Two people can open the same shared report and see different numbers, and neither is seeing anything they could not already open. A scheduled report is the one exception — see Schedules.Who can do what
Building a report and changing one are separate on purpose. A role that may create but not change
reports can put its own reports together and save them as drafts, without being able to rewrite the
shared reports everybody else reads. Publishing counts as changing, even straight after building, so
a create-only role sees Let a schedule send it greyed out with “Publishing is for whoever may
change saved reports.”
A role can also be limited to reports in certain categories — for example, a procurement role that
may run Purchasing reports only, or a planner who may change the Work reports and not Finance’s. The
limit can be set separately for viewing, creating, changing, exporting and sharing. Where it applies,
the actions on this page are offered only on reports filed under a category your role reaches. Roles
are edited under Administration → Access; see Roles.
The reports list
The header counts reports (in your list), shared (how many of those are shared beyond their author) and sources (how many lists of records a report can be built over). Three tabs sit underneath: Reports, Schedules and, if you may share reports, Who sees what. The Saved reports table is sorted by category, then name. Two controls sit above it:
Remove this report asks once more (Remove it / Cancel) and also removes its schedules.


The reports that come with the product
A new organisation starts with a pack of 96 reports, shared with everybody unless the table says otherwise, so the commonest questions are answered before anybody builds anything. They are grouped here by the category they are filed under. A list returns one line per record; a summary returns counts and totals by group, usually with a chart. Several open on a date range, or suggest narrowing to a site or a year when you run them.Assets
Bookings
These read the checklists your organisation sets for assets going out and coming back — see
booking settings.
Energy
Inventory
The three spare part reports cost each issue as the quantity issued at the unit cost recorded when it
was issued, so a month’s consumption is valued at what those parts were worth on the shelf at the time.
IT assets
Maintenance
People
Purchasing
The two provisions reports are shared with the Procurement User role rather than with everybody.
Reliability
Security
These read the audit trail, without the values before and after a change. They are
shared with the System Administrator and the roles that may read the audit trail rather than with
everybody, and anybody else who runs them gets no rows. The same goes for any report you build over
Audit events: the source is offered only to people who hold Audit · view.
Sensors
Tools
Vendors and contracts
Work
Dispatch group wise performance, Monthly ticket volume and SLA adherence and Problem
Code/Priority Wise Performance read as a sheet rather than a tree: every row repeats its project,
property and community, the grand totals sit above the table, and there are no subtotals. A group
with no value is named — Unassigned, No community, No priority — rather than left blank.
SLA Compliance % is green from 90% and amber from 75%, and SLA Breached % is red above zero.
The chart draws one level of the summary, such as one bar per dispatch group, instead of a bar for
every combination of every level.
Which of these you see depends on your organisation’s modules and on who each report is shared with.
Your administrator can take any of them out of a role’s list on the Who sees what
tab.
The work order explorer
The Work order explorer is the first row in the Work reports, marked built in, with Open where a saved report has Run. It is not a saved report, so it has no Edit, Schedule or Remove, and it is not counted in the header’s figures. It walks work orders from a site, team, priority or type down to the jobs themselves — see the work order explorer. It is offered to anybody who may read reports about work orders.Running a report
Run opens the answer over the whole page, with the report’s name, its category and source, and its one-line description across the top. Back to reports (or Esc) returns you to the list where you left it.

On a phone the header is one row: each button is drawn as its icon alone, and Back to reports is
the way out.
The PDF and the Excel workbook open with whose copy they are: your organisation’s print logo and
name, the report’s name, Printed on with the date and time, Printed by with your name, and —
where you narrowed the run — a Filter: line saying what by, with each record named as you picked
it. Those are the first questions a figure quoted in a meeting gets asked. The CSV has no heading,
because a line above its rows would be read as a row by whatever opens it.
Amounts and totals
Figures the report’s author marked as money are shown with the currency symbol, grouped and to the currency’s own number of decimal places — on the screen, on a dashboard tile, in the PDF and on the chart. They are in your organisation’s currency, except where a report groups its rows by currency: then each line is in the currency it sits under, and a line adding several currencies together gets no symbol. A list whose source records a currency for each row prints each row in its own currency. Averages are rounded to two decimal places. A list can end in total lines: a Total line adding up the columns its author chose, and, where the author asked for it, a total line for each value of another column — one per unit, say, so cubic metres and kilowatt hours are never added into one figure. A total line is in a currency only when every row it adds up is in that currency.How codes, headings and numbers are written
A run reads its rows the way the rest of the product does, rather than as they are stored:
A scheduled copy is written in the same words as the screen, so the file that arrives by email and the
answer you ran agree.
Narrowing a run
The Filters strip lets you narrow the run in front of you — this site, last week, this vendor — without editing the report. It works like the filters on any register:
Some reports open with filters of their own already on the strip, named the way their readers know
them — Project, Community and Property, for example. Where one filter’s choices depend on
another, it says Choose … first until the one above it is set, and changing the one above clears
anything below it that no longer belongs. A filter marked * must be chosen before the report runs:
until it is, the screen says Choose … to run this report in place of the answer, because the
report would otherwise add every year into one line.
A report can also let you choose what one level of its summary is grouped by — Data Based On
Priority or Problem Code, for example. The report opens on the first choice, and changing it
runs the report again grouped the other way.
The strip says “narrowed by 1 filter” (or n filters), and Back to the report removes every
filter and sort you added. The run waits until you stop typing before it asks again, and keeps the
previous answer on screen meanwhile.
“This narrows the run in front of you and nothing else — the report keeps the filter its author
saved, and a filter added here can only ever return fewer rows than it, never more.” Your filter is
always combined with the report’s own. The report itself, and whatever its schedule sends, are
unchanged, and your filter is forgotten when you leave — it does not come back the next time you run
the report. A download includes your filter, and says so.
What the count under the table means
Building a report
Build a report (top right) needs permission to create reports. The builder opens as a panel above the list, titled A new report, with a live Preview of the answer beside it. Edit in a report’s ⋯ menu opens the same panel on an existing report, titled Edit this report; it needs permission to change saved reports in that report’s category.

What it is about
Beside the boxes is the source’s field list, with each field’s kind (text, number, yes/no, date and
time). Find a field searches it. Drag a field into a box, or click it to add it. A source also
offers the fields of the records each row points at — a work order’s asset, assigned team, site,
contract and so on — folded under the record’s name with a count. Show n ID and audit
columns reveals identifiers and audit fields that are hidden by default.
Each box — Columns, Rows, Columns across, Values and Filters — has a header that
folds it to one line: its title, how many it holds, and the first three names with “+n more”. A
box that already holds something starts folded when you open a saved report, because you have
usually come to change one thing; an empty box starts open. A folded box still takes a drop and
still offers its picker.


A list of rows
Counts and totals
Filters
Filters says which rows the whole report is about. Drop a field there, or Add a condition, and build a clause from the field, a test (is, is not, is more than, is at least, is less than, is at most, is between, is one of, is none of, has a value, is empty, and windows of a number of days for dates) and a value. Where a field has a fixed set of values — a priority, a status, an origin — the value is offered as a choice rather than typed. Clauses can be gathered into a Group, combined with All of these must hold or Any one of these is enough, and reversed with Not. “No filter — the report is every row of this source that its reader can open.” Anyone running the report can narrow it further without changing it.Date range for readers
Under the filters, Date range for readers says which of the source’s dates a reader’s “last week” is about, so nobody running the report has to find out which date column means what. It is not a filter on the report.
“A reader can change the range or clear it for their own run. A schedule always sends every date the
report’s own filter allows.” The range does not narrow a dashboard tile either. The reports that come
with the product already name their dates.
Preview and chart
The Preview runs the report as you build it and shows the first few hundred rows; the saved report runs to its own limit. Above it, choose how the answer is drawn: Table only, Bars, Columns, Line, Pie or Donut. A donut is a pie with the total printed in its middle, for a summary whose total is the figure somebody came for. Both quote every slice’s figure and share in the legend beside them.Name, category and sharing
Sharing and delivery is folded shut, with a summary of its settings beside the heading — “Only me
· at most 1,000 rows · not scheduled”. It opens on its own if something in it stops the report
saving.
Save stays unavailable until the report has a name, a source, a sane row limit, no half-built
condition and, for a role or site audience, at least one role or site. The sentence beside it says
which is missing. The filter is checked when you save, so a column that is not there is refused at
once rather than when the report next runs.
A saved report can also be shown on a dashboard: a Table or Pivot table widget offers From
a saved report. See Dashboards.
Schedules
The Schedules tab lists the scheduled deliveries you set up — an administrator sees everybody’s, so a schedule left behind by somebody who has gone can still be stopped — and Schedule a report (top right on this tab, or Schedule in a report’s ⋯ menu) adds one. Scheduling needs permission to create reports.

Configured schedules
Schedule a report


Deliveries are queued on the hour. If the period you save into has already begun, the first copy goes
out within the hour rather than at the next boundary.
What went out
Below the schedules is the delivery log: Report, For (the period it covered), Answered with (“Priya Nair’s access”, or “nobody’s — refused”), Rows, As, Sent to (how many recipients were notified), Status and When, with The file to open or download what was sent. The file is written the way a run on the screen is — fixed values in words, your own codes as typed — see how codes, headings and numbers are written. Anything refused or failed is lifted into its own Not sent table at the top, with the reason — an author who has left, a recipient who is not a user here, a report still in draft, or a render that failed. A schedule that has quietly stopped sending has no other symptom: the email does not arrive, and nobody reports the absence of an email.Who sees what
The Who sees what tab, shown to people who may share reports, answers the question the other way round: not “who is this report for” but “what can this role see”. It is a grid of every report against every role, grouped by category. The grid is wider than any screen, so the report’s name stays in place while you scroll sideways through the roles. Roles held only by the accounts the product’s own integrations sign in with are not listed.

Each tick takes effect at once. Unticking a role takes the report out of that role’s Reports list and
stops it being run by them. What the report shows each reader does not change, and a schedule keeps
sending to the people it names.
Related
Dashboards
Boards of tiles and charts, which can show a saved report as a table.
Roles
Which roles may view, build, export and share reports.

