Skip to main content

Design custom report templates

Event reports — accident reports, intervention reports, inspection forms — are built from templates you design: their fields, their types, their layout. Agents then fill them from the duty log, and print them in your format.

Open the reports management

  1. Open Hamilton Security and click Administration in the left menu.

  2. In the Reports section, click "Reports management".

  3. The list shows the report templates; open one to edit it.

Design a report's fields

The report editor shows the template with its name and its data table, and the field grid — one row per field:

  1. For each field, define:

    • Field (the technical name) and Label (what agents see).

    • Field type: Text (50), Memo (long text), Date, Time, Date and time, or Automatic date.

    • Button type: how the field is filled (typed, picked...).

    • Source: where the field's values come from when applicable.

  2. Add, reorder or remove fields, then click Validate.

The "Data access without interface" action opens the structure view — the template's underlying table — for advanced maintenance with your Hamilton contact.

Link reports to events

A report template is triggered by the event types it is attached to: when an agent records such an event, the report form opens pre-linked to the event — see "Configure events, event families and system events" and, for the agent side, "Generate and print activity reports" in the user guides.

Verify a template

  1. Record a test event of the linked type: the report form opens with your fields.

  2. Check the mandatory-field and date/time validations behave as designed.

  3. Print the report and review the layout.

Good to know

  • Changing a template affects future reports; existing filled reports keep their data.

  • The printable layouts (headers, logos) are part of the template configuration — align them with your client's reporting requirements.

Related Articles
Did this answer your question?