Skip to content

Remarks

Review observations and notes that technicians captured during task execution. The Remarks page is a searchable log — not a CRUD for reusable remark templates.

Required role

Any role with task.view (Technician's own remarks; Supervisor, Manager, Admin, Viewer see all).

Overview

A remark is a free-text observation a technician adds during task execution — something they saw, a flag for follow-up, a piece of context that doesn't belong in the structured form fields.

The Remarks page consolidates every remark filed across the company into one searchable, date-filterable table. It's the place a Supervisor or Manager goes to answer "what did the team flag this week that I should know about?"

Open the page

Remarks in the top-level sidebar.

Layout

A search bar and date-range filter at the top; a table below.

Column Meaning
Date When the remark was captured (the task's execution time).
Task Point The task-point name the remark is attached to.
Location Breadcrumb showing where in the hierarchy (Site › Line › Section › Asset).
Type The task type — Electrical, Lubrication, Mechanical, Production, Repair request.
Assigned To The technician who filed the remark.
Status The task's status at the time the remark was attached.
Remarks The text of the remark itself.

An empty state shows "No remarks found." — which is what you'll see on a fresh installation until a technician files one.

Filter

  • Search — matches the remark text.
  • From / To dates — narrow to a window.

Filters persist across sessions.

Where remarks come from

Technicians file remarks from the mobile app during task execution:

  1. The technician opens a task.
  2. Fills in the form.
  3. Optionally taps Add remark and types a note.
  4. Submits the task.

The remark is attached to that task execution and appears on the Remarks page immediately (or on the next sync if offline).

Using the Remarks page

Weekly review

Open the Remarks page, set the date range to the past 7 days, scan for patterns:

  • Same task point coming up repeatedly → investigate asset condition.
  • Same technician flagging a lot → they may be catching issues others miss (good!) or inflating noise (review).
  • Recurring words or phrases ("leak", "vibration", "heat") → a systemic issue worth escalating.

Investigation

"Did anyone see X around time Y?" — narrow the date range, search for a keyword, scan results.

Audit

For compliance / maintenance review, filter to a specific time window and export (if your installation exposes export on this page; not all do). The Activity Log page may carry the same data for audit purposes.

What Remarks is NOT

  • Not a CRUD for predefined remark text. There's no "add remark" button on this page — remarks come from the field, not from config.
  • Not where you configure component-level hints. Advisory text on components lives in Components (as a remark field on the component type, shown to technicians when they open a related task).
  • Not a comment thread. Remarks are single observations, not conversations.

Things to watch for

Don't confuse field-filed remarks with component remarks

Two different things share the name "remark":

  • Field remarks (this page) — filed by technicians during execution; one per task.
  • Component remarks (on Components) — editorial hints attached to a component type by a Mapper, shown advisorily to technicians when they open any task on that component.

Both are called "remarks" in the platform. This page shows only the first kind.

Pair with the Activity Log for deeper investigation

If a remark raises a question, open the Activity Log to see what else happened around the same time.

Troubleshooting

Problem Fix
"No remarks found" Try a wider date range; confirm technicians are actually filing remarks
Remark text truncated Click the row for the full remark (if row-click is enabled on your installation)
Missing a remark you filed Confirm you submitted the task it was attached to — drafts don't surface here