DIGITAL FORMS AND PROCEDURES

From a paper form to a request you can track online.

We build digital forms and procedures that capture information in a structured way. Users fill in the request, attach documents and follow its status, while the team works on the same information.

Work equipment requestIllustrative concept
  1. 1Details
  2. 2Documents
  3. 3Confirm

supplier-quote.pdf

Reference number

REQ-2026-0214

Request status

In review

The request is with the department manager.

Owner

E. Prifti · Sales

  • Step-by-step forms
  • Visible status
  • Ready for mobile

THE PROBLEM

Collect the information you need from the start.

When a request arrives incomplete, the work starts with phone calls and follow-up questions. A structured form collects the right information at the first step.

This page covers capturing information and the experience of the person who fills in and follows the request. Routing, approving and coordinating the request are covered under process automation.

What happens with manual forms

  • Incomplete forms
  • Hard-to-read handwriting
  • Missing documents
  • Scattered messages
  • Information retyped into the system
  • No reference number or status
Service requestIllustrative concept
  • CustomerDemo Client LtdPicked from a list
  • Date05/03/2026Format checked
  • Service typeMaintenanceRequired field
  • Documentequipment-photo.jpgAttached
  • ReferenceSR-2026-0091Created automatically
  • StatusSubmittedVisible to the customer

Compare the same fields on paper and in a digital form.

EXAMPLES

Which procedures can move online?

Procedures that repeat every week or every month are the first candidates.

  • Leave and absence requests

    The employee picks the dates, the system shows the remaining days and the request goes to the manager.

  • Purchase requests

    Description, estimated value and attached quotes in one request with a reference number.

  • Expense claims

    Expenses with date, category and a photo of the receipt, ready for finance to check.

  • Customer registrations

    Customer details and the required documents collected in a single form.

  • Service requests

    The customer describes the issue, picks a category and follows the status without calling.

  • Check and inspection reports

    The same questions for every check, with photos and notes for each item.

  • Equipment handover and return

    Who took what, when and in what condition, confirmed by both sides.

  • Field work reports

    Hours, materials and work done, recorded where the work happens.

  • Maintenance requests

    Location, problem and urgency, with photos, so the technical team is prepared before going on site.

FEATURES

Forms that follow the procedure.

The form follows the rules of the procedure: it asks only for what is needed, checks completeness and shows clearly what happens next.

Purchase requestIllustrative concept
  1. 1. Details
  2. 2. Documents
  3. 3. Submit
Purchase type *

Try the form. Nothing is sent: the reference number and status are examples shown only on this page.

  • Multi-step forms
  • Required and optional fields
  • Fields that change based on answers
  • Format and completeness checks
  • Save as draft
  • Document upload
  • Corrections
  • Reference number
  • Status
  • Comments
  • Return for completion
  • Notifications
  • Mobile-friendly layout

USERS

For employees, customers and partners.

The same procedure can have different users. The way they access it is chosen around them.

Public form

For requests anyone can submit without an account. Suitable when the information is not sensitive.

  • No account
  • Reference number

Portal with sign-in

For customers and partners who submit several requests, follow their status and see their history.

  • User account
  • Request history

Internal role-based app

For employees: each person sees and acts according to their role, from submission to review.

  • Roles and permissions
  • Work lists

The level of sign-in and access depends on how sensitive the information is and on the nature of the procedure.

STATUS

From submission to completion.

An illustrative example of a request's states. Each state tells the requester clearly what has happened and what to expect.

SubmittedIllustrative concept

What it means

The system has received the request and given it a reference number. It has not been reviewed yet.

What the requester sees

Request REQ-2026-0214 was received by the system. You will be notified when it is reviewed.

“The request was received by the system” does not mean “the request was approved”. Success messages do not imply automatic approval.

FIELD WORK

Suitable for field work too.

For inspections, checks and services outside the office, the form needs to work well on a phone and show clearly what has been saved and what has been sent.

  • Use on a phone
  • Photos and documents
  • Location recorded only when needed and authorised
  • Offline saving when required
  • Clear sync status
  • Handling of conflicts and repeated submissions

Working offline requires dedicated development and testing. It is included only when the solution is designed for that need.

Inspection report

Site 3 · Entrance B

  • Equipment condition
  • Safety labels
  • Cleanliness of the area
2 photosLocation: with permission

Sync status

  • No reports waiting.
  • IR-2026-0029: also changed by the officeNeeds resolving

Offline saving works only when the solution is built for it.

Save the report while offline, then turn the connection on. Everything happens only on this page.

THE PROCESS

How we build it.

  1. 01

    Review of current forms

    What information is requested, who fills it in and how it is used.

  2. 02

    Data structure

    Fields, validation rules and the reference number.

  3. 03

    Prototype

    A clickable version to try before development.

  4. 04

    Development

    Forms, statuses, notifications and views for each role.

  5. 05

    Integration

    Connections to the systems the information needs to reach.

  6. 06

    User testing

    Real users fill in the forms on phone and computer.

  7. 07

    Go-live

    Moving from the old form and guidance for users.

FAQ

Questions about digital forms and procedures

Tell us about the form you use today.

We review what information it asks for and how it is used, to turn it into a clear digital procedure.


Describe the procedure in words. Please do not send confidential documents or data at this stage.

What happens after you write to us

  1. 1We read your descriptionWe look at the process, the systems you mention and where it gets difficult.
  2. 2We contact youWe clarify the questions we need to understand the process.
  3. 3We propose the first stepAn analysis, a limited trial or an estimate, depending on the case.

Please do not send confidential documents or data at this stage.