For technicians

If you are the person who actually goes to the building, most of Properate is not aimed at you. This is the part that is.

Start from your tasks

Open tasks.properate.com on your phone. It is a mobile-friendly view of task management: see the tasks assigned to you, update status as you go, and create new tasks for colleagues while you are still standing in front of the problem. That last part matters — a task created on site gets created; one you mean to write up later often does not.

Before you go out: open the system

In the FDV building overview, find the system you are going to work on. Each system shows its supplier, year, delivery date, capacity and whether it is end of life — plus the files that belong to it and any open tasks against it, in the same place.

So before setting off you can see whether the unit is already past its service life, what was done last time, and which manual you will need. The point of FDV is to stop the searching.

A ventilation schema with live values, setpoints and the governing calendar on the drawing itself.

Finding things

• Components — search by component or filter by brand. Put * around your search text for exact matches.
  

• Floor plan — see which room is which, and what its sensors currently read. Useful when a complaint names a room rather than a system.
  

• Technical schema — the installation drawn out with live values in position: supply and return, fan and coil. Faster than reading a list of sensor names when you are trying to work out what is actually wrong.
  

Reading meters

Where a building is not fully digitalised, register meter values from your phone by scanning the QR code on the meter and entering the reading on the spot. This avoids the paper-then-retype step where most reading errors come from.

A floor plan with room temperatures in place. Switch the rooms view to show CO₂ or humidity instead.

Log what you found

Use annotations to record what happened, where it happened. An annotation can sit on the whole building, a floor, a single room, or directly on a technical system or sensor, and gets a date and a level (info, warning or error).

This is the highest-value habit in the whole system. An email about a fault is gone in a week; an annotation on the component is still there when someone else opens that system in two years, or when you have moved on.

Your deviations

In Incident handling you can filter to the incidents assigned to you, and see severity. Anything unassigned is nobody's yet — worth a look if you have capacity, because unassigned items are the ones that get quietly forgotten.

When you take an alarm, add your practical read of what is happening in the building rather than only acknowledging it. You are the one person who can say whether a value looks wrong because the plant is faulty or because a door stood open all afternoon. An acknowledged alarm with no assessment tells the next person nothing.

Step by step: the jobs you do most

Work through the tasks assigned to you

• Open tasks.properate.com on your phone and sign in with your Properate account.
  

• Set the status filter to In progress to see what is actually live, rather than everything ever created.
  

• Open a task. Work down the checklist, ticking each item as you finish it — the progress bar above it shows how far through the job you are.
  

• Use the comment icon beside a checklist item rather than the task description to record what you found. It keeps the finding attached to the step it belongs to, which is what the next person needs.
  

• Select Add item if the job turned out to need a step nobody had written down.
  

• Update Status when you are done.
  

Create a task while you are still in front of the problem

• From Tasks, select New task.
  

• Give it a title, an Assignee and a Priority.
  

• Set Component to the equipment it concerns. This is the step people skip, and it is the one that makes the task findable later by whoever opens that component.
  

• Use Make recurring for anything that needs doing again on a schedule, or Set reminder for a one-off follow-up.
  

A task created on site gets created. One you mean to write up this evening often does not.

Look at a system before you drive out

• Open Technical schema and pick the system from the selector at the top.
  

• Read the live values in position on the drawing — supply and extract temperatures, fan output, valve and damper positions.
  

• Select any value to open its recent history in a pop-up, without leaving the drawing. A value that is correct right now but was wrong all night tells you something a snapshot cannot.
  

• Check the Calendar block on the drawing to see which schedule is governing the system. A unit that appears to be misbehaving is often simply following a schedule nobody has looked at in two years.
  

Find the manual, supplier and history for a component

• Go to FDV → Components.
  

• Search for the component. Put * around your search text for an exact match.
  

• The record shows contractor, supplier, manufacturer, serial number, delivery date and end of life — so you can see before setting off whether the unit is already past its service life.
  

• Files attached to that component are on the same screen, as is Add task.
  

Take a deviation and close it out

• Open Incidents → Incident handling. Filter by severity, or to what is assigned to you.
  

• Open the incident. The graph shows the base value over time, so you can see whether this is a one-off or something that has been flapping for weeks.
  

• Select Assign to me so nobody else duplicates your work.
  

• Open the Alarm configuration section to see exactly what condition triggered it — that is usually faster than guessing from the name.
  

• Select Acknowledge if the alarm requires it. Some do not, and say so.
  

• Set Status to Resolved once it is actually fixed — not when the value happens to come back on its own.
  

Change a setpoint

• Open Setpoints and search for the one you need. Large buildings do not show the full list, so search rather than scroll.
  

• Enter the new Value.
  

• Use the history icon to see who changed it before, and to what. Worth doing before you change anything, in case someone set it deliberately.
  

If the field is greyed out, either the value is a measurement rather than a command, or your role is Read-only.

Log what you found so it is not lost

• Go to Notes and select Add note. You can also start from a graph, where you select the item the note belongs to.
  

• Set the Level — Info for a record, Warning for something the next person needs to know.
  

• Set Date/time, or tick All day if it was not a precise moment.
  

• Under Assets, attach it to the system, room or sensor it concerns rather than to the building as a whole.
  

• Select Save.
  

An email about a fault is gone in a week. A note on the component is still there in two years.

Access you need

Most technicians work with the Technician app role, or with User access — standard access to assigned buildings, able to work with dashboards and modules but not to manage other users or organisation settings. If files or systems appear empty, that is usually a building access question rather than missing data; ask whoever administers users.

What good use looks like

• Every task is handled in Properate — including the small things that would otherwise stay verbal.
  

• Checklists are completed in the system, not on paper or from memory.
  

• Tasks are closed with clear documentation: what was done, what was found, and where it stands now.
  

• Alarms are not acknowledged passively — they are assessed and commented on.
  

• Service visits and input from suppliers are captured in the history.
  

What to avoid

• Carrying out work without registering it.
  

• Closing a task with too little information to be useful later.
  

• Letting observations stay verbal, and therefore invisible to everyone else.
  

• Treating Properate as extra admin rather than as the tool you work in.
  

Your first two weeks

• Open Tasks and prioritise the day's cases before anything else.
  

• Complete one planned checklist fully, in the system.
  

• Register at least one annotation every time you notice something unusual.
  

• Close every finished case with a short cause, the work done, and a photo where it helps.