Producing the site report

At the end of a call-out the engineer leaves something behind: what was on the network, what it is, what is wrong with it and what to do. Site Report, its own page under Overview, runs the tools for you and builds that document as the results land — or assembles one from what the tools already found this session.

Running the survey

Each section of the report is backed by one tool, and the checklist says which. Tick the sections you want and press Run survey; the steps run one after another, on purpose, because they share the link and would skew each other in parallel:

• Adapters and addressing — read from this machine.
• Wireless survey — what the wireless adapter hears.
• Connectivity tests — the six checks on Diagnose, with the download speed test.
• Subnets and device inventory — an IP sweep of every subnet this machine is on (/22 or longer).
• Services and exposure — a scan of the Common port set, over TCP, on every host found, up to 256.
• Switch port — a 60-second listen for LLDP or CDP on the wired adapters.
• Throughput — only when you give an iperf3 endpoint; a 10-second TCP test against it.

Each row shows its step running, then what it found. A step that cannot run says why — no Npcap for the switch port, no endpoint for throughput, no wireless adapter — and is left out. Stop halts the running tool and marks the rest skipped. A section with no data is left out of the document rather than printed empty — an empty table would say “we checked and found nothing”, which would be a lie.

Filling in the header

Customer or site name, location, your name as the technician (remembered on this machine), a ticket or job reference, notes — what was done, what was left for the customer, what to check next visit — and an iperf3 endpoint if throughput should be measured. The reference is derived from the site and the time if you leave it blank, and earlier customers are offered as you type.

What it says

An executive summary; how this was measured — who ran the survey, when, from which machine and adapter, and each step with its target, duration and outcome, skipped and failed steps included; findings and recommendations, highest priority first, each citing the evidence it rests on; the device inventory grouped by role — routers and firewalls, switches, access points, printers, cameras, phones, servers, and the rest — with the basis and a confidence for each classification; then the sections above; and a method-and-limitations section that states what one machine at one position can and cannot establish.

Keeping and exporting it

Save report files the document in the app under the customer’s name, with the technician, the date and what it contains. Every report you have saved is listed beside the survey; open one to see it exactly as saved, then Export HTML writes one self-contained file — no scripts, no external assets — that opens in any browser, Print / PDF opens the print dialog, where Save as PDF makes the PDF, and Delete removes it. The file is named for the customer and the date so it sorts. Reports live in the app’s own data folder on this machine, not in the encrypted vault: they hold names and addresses, not secrets.