To trial a construction app, start with one defined reporting task and a small group of users. Test the full journey from a site observation to a report someone else can review. A successful pilot shows whether the app fits the work, the site's conditions and the information your team needs to deliver.
Choose a task with a clear output
Select a task the team already performs, such as documenting a site walk or recording observations before a work package is handed over. Define the output before choosing the tool. For example, the report might need a project reference, locations, photographs, comments and a list of follow-up actions.
Keep the scope small enough to review properly. Do not begin by asking the team to move every document and every process into a new system. One completed reporting task provides more useful evidence than a long list of features nobody has tested.
Agree how the trial will be judged
Write down a few practical questions. Can the person on site find the correct task? Is it clear how to record an observation? Can the reviewer understand the result without calling the author? Can the issued report be retained with the project's documentation?
Record how the task is handled today, including the effort required after the site visit. Compare the pilot with that baseline without promising a fixed time saving. Account for the extra time spent learning the tool during the first attempt.
Test the actual site conditions
Use the devices and connection conditions the team will face, rather than relying only on an office demonstration. Check camera permissions, account access and the process for getting a new colleague started. Agree what happens if a device cannot connect.
The Assurement app needs a connection today to register tasks and upload photos. Offline mode is on our roadmap, but it is not part of the product yet. Test the connection where the work will take place, for example in basements and stairwells, and agree a separate contingency for essential records. Do not assume that a planned feature is already part of the pilot.
Teach the record structure as well as the app
A short demonstration should cover which project to use, how locations are named and what a complete observation contains. Show an example of a useful description, including the subject, location and next action. Explain who reviews the records before a report is issued.
Use a practice observation to check understanding. Ask another team member to find it and explain what needs to happen next. If the record is confusing, fix the instructions or the structure before adding more users.
Review one finished report together
Include a site user, a project coordinator and the intended reviewer. Look for missing context, unclear photographs, inconsistent location names and observations with no owner. Separate problems with the tool from problems with the team's recording habits. Our guide to photo documentation on site covers what makes a photo usable as evidence.
Measure the pilot with practical results: records needing clarification, time spent preparing the output, missing fields and whether the recipient can use the report. A visually attractive report is useful only if its content answers the recipient's questions.
Decide whether to extend the pilot
Write down what worked, what needs to change and who owns the changes. Expand to another work package only when the basic recording and review process is reliable. Keep an agreed way to retain issued reports and project references when team members change.
Running the pilot with Lite Report
Lite Report is available today and fits a pilot like this. The project manager creates the report on the web, gives it a title and a description of the task, and sets up the tasks, either from the control plans for your trade or as custom control points. Drawings and procedures go in the project's shared documents, where every report on the site can use them. Field users carry out the tasks from their phone with photos, comments and markups. Photos are taken with the in-app camera and stamped with the date, time, GPS position and place name, and the registrations are compiled into one PDF report.
Add everyone in the pilot to the report. Tasks are not handed to one named person: once the project manager assigns them, they are open to everyone on the report with the Register permission. An invitation to a new user expires after 24 hours, so send it when the person is ready to install the app and accept. The app has no separate review step, so agree who checks the registrations, and use the report preview to see the result before you pay for it.
The pilot costs nothing until you generate a report. Creating the account, setting up the project and documenting on site are free, with no extra charge for users or photos. Each generated report costs 149 DKK excl. VAT (186.25 DKK incl. 25% VAT), with no subscription or commitment. See pricing for the details.
Lite Report is the module available today. The DS1140 module is launching soon and the quality assurance module is in development, so assess them separately when they are available rather than treating this pilot as proof of every planned workflow.
Frequently asked questions
Do all site workers need to join the first pilot?
No. Include enough people to test recording, coordination and review. Expand after the team has resolved the practical issues found in the first task.
How long should a pilot run?
Run it long enough to complete and review the chosen task. The right duration depends on the work, rather than a fixed number of days.
What if the site has poor connectivity?
The Assurement app needs a connection today to register tasks and upload photos; offline mode is on our roadmap. Test the affected areas and agree a contingency before relying on the app for time-sensitive records.
What does a pilot with Lite Report cost?
Nothing until you generate a report. Creating the account, setting up the project and documenting on site are free, with no charge for users or photos. Each generated report costs 149 DKK excl. VAT (186.25 DKK incl. 25% VAT), with no subscription or commitment.