Build a custom report

Custom reports on PC.o: your checks, your thresholds, your logo, on paper. The Guide notes that this is where opinions become documents.

Custom Reports holds the definitions you own; the runs live in Reports. Create a report. Name it, keep Analysis-shaped for one schedule; Comparison-shaped takes a pair. One section to start. Modest beginnings.

Cover: title, subtitle, prepared by and for, a footer line, a note. Done when it reads like yours. Add analytics opens the library: search, filter by area, tick. More than a hundred, built in.

Click a check to set its judgement: none, pass or fail, a traffic light, or bands. Set the threshold and the review point. The card above shows the line as readers see it.

Commentary takes placeholders: value, count, threshold, schedule. The Preview line fills in what it knows. The detail table is ticked, with the rows behind the number. Word shows your columns; Excel shows all.

Logos: PNG or JPG under a megabyte; one is the default. PC.o's mark stays small, at the foot. Choose a schedule and press Preview: the whole dashboard, with nothing saved and no row created.

The preview reads exactly as a run will: which checks pass and which fail, section by section. Save, and the version counts up. Run on… takes the template to the Files list.

Pick the schedule, then Run. A moment later it is ready, and waits under Reports. The report: overview, a tab per section, details. Word and Excel each come as Summary or Full.

Every run waits under Report Collections, Cus. Analysis: view it, re-run it, download it, or delete it.

That was building a custom report. Next in the Guide: subscribing, and what the thirty-day trial leaves out until you do.

Taken from the video’s English captions.