Skip to main content

Access the Request Portal

Updated yesterday

The Tractian Request Portal allows anyone to submit a maintenance request quickly and intuitively, without needing to be logged into the platform. Submissions can be made via mobile or computer, as long as you have access to the link or QR Code provided by the company.

Important note: To access the Request Portal, please contact the person responsible for your company at Tractian directly.


Access to the Portal

You can access the Request Portal in the following ways:

  1. By scanning a QR Code installed at the workplace.

  2. By clicking on the web version link provided by the responsible team.

No login, corporate email, or mobile number is required to access.


Filling out a request

When accessing the portal, a form will be displayed with the following fields:

  1. What needs to be done?
    Required field. Clearly describe what task needs to be performed.

  2. Attachments (optional)
    You can attach images and files in formats .pdf, .xlsx, .txt, .doc, among others, to illustrate or detail the problem.

  3. Description (optional)
    Use this field to provide more information about the situation. The more details, the better for maintenance planning.

  4. Active or Local
    Selection field of the asset tree registered on the platform. Choose where the problem is occurring.

  5. Requester Name
    Required field. Indicate who is making the request.

  6. Contact Information
    Provide a phone number so that the maintenance person can contact you if necessary.

Important note: The fields in the Request Portal are standardized and cannot be customized. After submission, the information contained in the request cannot be edited or modified.


After submitting the request

After filling out and submitting the request:

  1. The request is saved and sent automatically;

  2. It appears in the Requests > Pending tab, awaiting approval or cancellation by the responsible team;

  3. Before being approved, the request can be edited for adjustments, such as:

    • Adding priority (low, medium, or high)

    • Inserting categories, tags, and associating with service orders

  4. If approved, the approver can set:

    • The due date and time

    • The persons responsible for execution

  5. After that, a Service Order is generated automatically.

  6. The responsible person is notified by email whenever the status of the service order is updated.


Best practices

  • Use clear and objective language in the field "What needs to be done?".

  • Attach images whenever possible to facilitate understanding of the problem.

  • Fill in the contact information correctly, as this can speed up the response and execution of the service order.

Did this answer your question?