A report is a PDF built from your project: the observations you recorded, their images and details, and optionally the section views you captured. Every observation in the project goes in by default, so shape it before generating if you want a narrower one.
To generate one, see Creating and generating a report.
| Field | Required | Default |
| Title | ✓ | Your project name, followed by "Inspection Report" |
| Author | ✓ | You |
| Inspection company | ✓ | Your organization's name |
| Inspection dates | ✓ | None; you enter a date range |
| Report date | ✓ | Today |
| Language | ✓ | Your app language |
| Measurement system | ✓ | Your setting (metric or imperial) |
| Executive summary | — | Free text, optional |
| Company logo | — | Optional |
The defaults are usually right, so in practice you fill in the inspection dates and, if you want one, the summary.
Author is always you, never carried over from a previous report. A report generated from a colleague's project still shows who actually produced it.
The report language is independent of your interface language, so you can work in one language and issue the report in another. Your team's own field names come from the Observation Profile and appear in the languages it defines.
You do not choose these. They come from what you recorded:
Observations follow the order in your list, which you arrange by dragging. Reorder the list and the report follows. See Organising observations into groups.
Groups themselves do not filter a report. They organise the list, and a report covers the whole project regardless of how you have grouped it. To report on one part of an asset only, either hide the observations you do not want, or keep that part in its own project.
| Option | What it does |
| Include hidden observations | Includes observations whose visibility you switched off |
| Include section plans | Adds your captured section views |
| Include platform links | Adds links back into Twinsity, so a reader can open an observation |
| Show sensitive data | Includes data marked sensitive |
Think about include platform links before sending a report outside your organization: the links only work for people who can sign in.
Each observation row has an eye toggle. Switching it off hides that observation from the 3D view, and keeps it out of reports too. That makes the eye toggle the simplest way to shape a report: hide what does not belong, generate, then switch them back on.
To include them after all, turn on include hidden observations when you generate.
Sections appear only if you turn on include section plans when generating. That includes every saved section, and there is no way to pick a subset. If you want fewer, delete the ones you do not need before generating. See Capturing a section view.
Report screenshots are captured automatically and are often fine, but not always. A defect on the far side of a column may be hidden in its own screenshot.
Where that matters, position the 3D camera on the observation and use Update perspective in its details panel before generating. See Filling in an observation's details.