Protocol Detail
Here you can find all protocol data, from client information and performed work to the change timeline and the option to download the PDF.
Accessing the Detail
Open the protocol detail:
- By clicking a row in protocol history
- By clicking the protocol number in a list
- By opening a direct link (the URL contains the protocol ID)
Header
At the top of the page you will find:
- Protocol number - the unique protocol identifier
- Protocol status - a colored badge (see below)
- Revision badge - if the protocol was reopened, Rev. 1, Rev. 2, etc. is shown
- Lock badge - if someone is currently editing the protocol, you see Being edited (a colleague) or You’re editing (you)
- Client name - for quick orientation
- Back button - returns to protocol history
Note about locks: The application prevents multiple users from editing the same protocol at the same time. If you see Being edited, wait until the colleague finishes, or contact them.
Protocol Status
Each protocol has a status that tells you which phase it is in:
| Status | Color | Meaning |
|---|---|---|
| In progress | 🔵 blue | The protocol is being created or edited |
| In review | 🟣 purple | Submitted to a manager for review |
| Sent | 🟢 green | The protocol has been sent to the client (final) |
| Returned | 🟠 orange | An in-progress protocol that a manager returned for correction (special badge with an icon) |
| Canceled | ⚫ gray | The protocol was canceled |
Tip: The Returned status appears only when the protocol is in progress and the last action was a return from review. You can see it in the header and in the protocol list.
Lifecycle
The lifecycle depends on the protocol process settings in your organization. The administrator configures it in protocol settings.
Without a Process (Direct Send)
The simplest setup. The technician fills in the form and sends the protocol to the client with one click.
- The technician fills in the form
- Clicks Send -> the protocol is Sent (final)
- The PDF is generated and emailed to the client
There are no intermediate steps and no review. This is suitable if you work alone or do not need approvals.
With Optional Review
The technician can save the protocol, return to it later, and decide whether to send it directly or submit it for review.
- The technician fills in the form
- Clicks Save -> the protocol is In progress
- The technician can return to it at any time, edit it, and then:
- Click Send -> the protocol is Sent (final)
A manager can see in-progress protocols and review or send them.
With Mandatory Review
The technician must submit every protocol for review. Only a manager can send it to the client.
- The technician fills in the form
- Clicks Save -> the protocol is In progress
- When the form is complete, clicks Submit for review -> the protocol is In review
- The manager reviews the protocol:
- If it is correct -> clicks Send -> the protocol is Sent (final)
- If it needs corrections -> returns it to the technician -> the protocol is Returned
- The technician corrects it and submits it For review again
- After approval, the manager sends it -> Sent
Manager-Prepared Protocols
If this option is enabled, a manager can create the protocol base before the service visit:
- The manager creates a protocol and fills in known data (client, address, work type)
- Assigns the protocol to a technician
- The technician completes the missing data in the field (materials, photos, signatures)
- Continues according to the configured review mode (sends directly or submits for review)
Reopening a Sent Protocol
If this option is enabled, a manager can reopen an already sent protocol for correction:
- The manager opens the sent protocol
- Clicks Reopen - a confirmation dialog appears
- Optionally fills in Reason for reopening (for example “correct material amount” or “add signature”)
- Confirms the action - the protocol returns to In progress
- After correction, it goes through review and sending again
- The revision number increases automatically - after the next send, Rev. 1, Rev. 2, etc. is shown
Tip: The reopen reason is optional, but we recommend filling it in. It helps colleagues, and you later, understand why the protocol was changed.
Every reopening is recorded in the timeline and the original version remains in history. For revisions, mandatory signatures become warnings: they are not required to resend the protocol if signatures already existed on the first send.
Protocol Actions
View PDF
Click View PDF to open the protocol in the PDF viewer directly inside the application. The viewer supports:
- Zooming in and out
- Page navigation
- Downloading to the device
Download PDF
The Download PDF button saves the file directly to your device. The file name matches the protocol number.
Share
The Share button opens the system sharing menu on your device. You can share:
- By email
- Through messenger applications
- By saving to files
- Through another installed application
Note: Sharing depends on the capabilities of your device and browser.
Resend PDF
If you need to send the protocol by email again:
- Click Resend PDF
- In the dialog, select recipients:
- Email from the client address
- Client company email
- Administrator/manager email
- Custom email address
- Click Send
You can select multiple recipients at once.
Deleting a Protocol
If you have permission to delete protocols:
- Click Delete (trash icon)
- Confirm the action in the dialog
Warning: Deleting a protocol is irreversible. A deleted protocol cannot be restored.
Timeline
Below the protocol header you will find the timeline, a chronological overview of all events and changes since the protocol was created.
Event Types
| Event | Icon | Description |
|---|---|---|
| Created | ✅ green | The protocol was created |
| Updated | 📝 blue | Protocol data was changed |
| Signature | ✍️ purple | The client or technician signed |
| Invalid signature | ⚠️ yellow | Changes were made after signing, so signatures must be renewed |
| Submitted for review | 📤 blue | The technician submitted the protocol for review |
| Returned for rework | 🔄 orange | A manager returned the protocol for correction |
| Sent | 📨 green | The protocol was sent to the client |
| Canceled | ❌ red | The protocol was canceled |
| Reopened for correction | 🔄 yellow | A sent protocol was reopened for revision |
What You See in Event Details
For each event you see:
- Date and time - when the event happened
- Who - the name of the user who performed the action
- Changed sections - colored badges showing which sections changed (for example Materials, Pests, Photos)
Click Change details to expand a detailed overview of changes:
- For text fields, you see the original and new value
- For lists (materials, pests), you see added, removed, or changed items
- For photos, you see previews of added or removed photos
Invalid Signature Warning
If protocol data changed after signing, the application warns you in two ways:
1. Yellow Banner at the Top of the Detail
A prominent banner appears above the protocol: “The signature no longer matches the current state of the protocol”. The banner shows:
- Which signatures lost validity - client, technician, or both
- Changed sections - colored badges with field names where a change occurred (for example Materials, Pests, Notes)
- View change history button - scrolls directly to the timeline
2. Event in the Timeline
The timeline gets an Invalid signature event with details of which fields invalidated the signature.
What now? Open the protocol for editing (if you have permission) and sign again. The signatures will be renewed and the banner will disappear. This confirms that the signatures match the current data.
Detail Sections
The protocol detail is divided into several sections. Visibility of individual sections depends on your organization’s settings.
Client Data
- Name / company name
- Billing address (registered office)
- Contact email and phone
- Company ID, Tax ID, VAT ID (if filled in)
Work Site
Information about the site where the work was performed:
- Site name (if different from the registered office)
- Work address
- Contact person on site
- Phone and email for the work site
Work Details
- Start date and time of work
- End date and time of work
- Work type (for example deratization or disinsection)
- Work subtype (for example preventive inspection)
- Protocol creation date
Tags
Colored labels (tags) assigned to the protocol. If you have permission:
- You can add tags by clicking +
- You can remove tags by clicking x next to the tag
Note: Tag availability depends on your permissions set by the administrator.
Technicians
- Lead technician - responsible for performing the work
- Additional technicians - collaborating technicians (if entered)
Locations (GPS)
If the protocol contains GPS data:
- Start of work - location when the form was opened
- End of work - location when the protocol was saved
- Synchronization - location when the offline protocol was synchronized
Click the coordinates to open the location in Google Maps.
Pests
List of found pests with details:
- Pest species
- Detailed specification (if entered)
- Count/intensity
Used Materials
List of materials used during the work:
- Material name
- Quantity
- Concentration (if entered)
Installations
List of installed devices:
- Device type
- Quantity
Photo Documentation
Photo gallery from the work site. Click a photo to enlarge it. In the enlarged view you can:
- Move between photos by swiping
- Zoom into details
- Close by clicking outside the image
Deficiencies
Shows found deficiencies by category:
- Organizational deficiencies - issues with work organization
- Construction deficiencies - building defects
- Hygienic deficiencies - hygiene issues
For each category, you see:
- Status (yes/no/no deficiencies)
- Description of the deficiency
- Photos (if attached)
Additional Information
- Temporary system storage
- Insurance event
- Number of concession holders
- Next intervention date
- Next inspection date
Recommendations
List of recommendations for the client. Each recommendation contains:
- Title/heading
- Recommendation text
- Illustrative image (if assigned)
Notes
Text notes about the protocol entered by the technician.
Offline Mode
In offline mode:
- ✅ You can view protocols that were loaded before disconnection
- ❌ PDF is not available for download
- ❌ Sharing and sending by email are not available
Tips
Tip: If you need to find a specific protocol quickly, use the protocol number search in history.
Tip: When sharing on mobile, you can send the protocol directly through WhatsApp or another messenger application.
Tip: Tags help you categorize protocols for later filtering, for example “urgent”, “complaint”, or “VIP client”.
Tip: The timeline lets you trace exactly who changed the protocol and when.