admin@kalkiweb.com.au
Home

Fieldline

The detail is easiest to record where the work happens. Fieldline explores a reporting flow for small screens with clear input, local saving and a clear indication of where each report is stored.

Studio concept / Interactive prototype

Illustration of open fieldwork terrain in warm daylight

Closer to
the work

Capture the observation while it is still in front of you

The scenario

An observation
with a clear place to go

  1. 01

    Record the detail

    Choose a sample condition and add an inspection note. The task stays short enough to complete on a small screen.

  2. 02

    Know where it is

    Save the report on this browser. The confirmation says exactly that, not that it has reached an office.

  3. 03

    Take it with you

    Refresh to inspect the saved report, export a text copy or clear the demo data. No report is uploaded.

Now try it

A report, ready when you are

Create a sample inspection, save it on this browser and export the text. Reports stay on your device and are not uploaded.

FieldlineMobile reporting preview

New sample report

Keep the detail
close to the work

This preview saves text locally after you press Save. Do not enter personal, customer or confidential information.

Up to 20 sample reports are kept on this browser. Saving another replaces the oldest.

Saved here

0 reports

Local only

Room for the next observation

Complete the form to see a saved report here. It will remain on this browser after a refresh, if browser storage is available.

No report is sent to a server. Use sample information only.

Behind the concept

Useful information
Beyond the desk

The brief follows a field team recording inspections on paper for the office to review later. The concept explores reporting on a device, with synchronisation and connection handling proposed for a full application.

Focus
Field reporting concept
Contribution
Concept, interface design and frontend prototype
Status
Studio concept

The approach

The decisions
behind the direction

Keep the task close at hand

The interface starts with the reports a person needs today. A short, staged form gives each inspection item enough space, with progress and draft status visible throughout.

Say exactly where the work is

Saved on this device, waiting to send and received by the office are different states. The concept makes those differences explicit instead of using one ambiguous success message.

Treat synchronisation as a product feature

A production build would need durable storage, conflict rules, retry behaviour and testing on the actual devices used in the field. The study makes those requirements visible rather than treating offline support as a label.

In focus

What this
concept explores

  • A report workflow designed for mobile
  • Draft and completion states
  • Evidence prompts beside the relevant task
  • Clear local and server status language
  • A proposed synchronisation and conflict handling model
Discuss a similar project

Next concept

Rivet

Architecture website

View all work