Reports & studio
Use the reports library
Understand included and unit-built reports, runtime scope, default overrides, duplication, reset, and deletion.
Guide at a glance
How to use this guide
Start with
Decide the audience, record scope, fields, and output format before arranging the design.
By the end
The output answers its intended question, uses current data, and exposes no unnecessary information.
A report is a live question about the roster
A report stores its layout, fields, filters, and starting scope—not a frozen export. Open it for a company, battalion, or selected Cadets and it renders against the current roster.
That lets one personnel roster design serve every company and remain correct as Cadets move.
Included reports
| Report | Purpose |
|---|---|
| Roster | A personnel roster built from selected Cadet fields. |
| Chain of command | A position- and assignment-aware view of unit leadership. |
| Memorandum | A reusable memorandum layout with unit-bound text. |
| Cadet information sheet | One person’s detailed record, suitable for per-Cadet output. |
| Blank portrait / landscape | Empty letter-size starting points for a custom report. |
Edit a default without creating a second copy
Editing an included report stores the unit’s override while the library still shows one logical report. Reset removes that override and restores the shipped version.
Duplicate creates a separate unit report. Use duplication when the new design has a different purpose, not merely a different company scope.
Report permission is intentionally sensitive
Can manage reports grants access to build, edit, print, and export roster-backed documents. Reports may expose phone numbers, addresses, grades, and other fields across the unit.
Treat the grant as close to broad roster read and export access, and review it at position turnover.
Reset versus delete
An included report is reset, not deleted. A unit-created report may be permanently deleted after confirmation.
The library labels included and unit-owned reports so the destructive action is unambiguous.
Key terms in this guide
- Position
- A named unit duty that can carry permissions, scope, an assigned Cadet, and continuing work.
- Scope
- The records or formations within which a permission, report, tool, or action applies.
Continue reading
Build reports in Studio and export PDF, Word, or Excel
Design roster-backed pages with live fields, conditional content, record tables, reusable scope, multi-page output, and office exports.
Read nextExport and print the roster
Prepare a clean roster for an inspection or spreadsheet workflow without changing the source record.
Read nextConfigure positions and permissions
Build a chain of command where responsibility and access survive annual turnover.
Read next