Request a trial

Quick look

From the developer's folder to a priced change request, in 5 steps.

These are real screens from Landsight, run on the sample package. Scroll through the 5 steps, then see what you get.

Drop the folder

Drop the developer's package as it came. Every file gets a verdict, and the bill that counts is named.

The upload screen: each bill, scan and photo in the package has a verdict, and the current bill is marked as the one that governs.

Choose what to check

The project is read off the title block. Then pick the checks: quantities and the bill, drawing logic, the local building code, with your own price list.

The choose screen: the project read from the title block, and the 4 groups of checks.

Analyze

Muse Spark 1.3 reads every sheet, SAM 3.1 measures colour plans, geometry counts. About 2 minutes.

The analysis in progress: Muse Spark reading 23 sheets, then geometry, SAM 3.1, versions and the building code.

Review

The findings come grouped: send back, fix before pricing, the code. Every item opens on the drawing, and nothing counts until you confirm.

The review screen: findings grouped under Send back, next to the drawing.

Send it back

A change request clouded and priced on the drawing, and a reply to the developer, ready to send.

The change request: the planting plan with clouded, numbered changes and their prices.The drafted reply to the developer, listing every change.

The result

What you get.

2weeks→10min

A package review: about 2 weeks by hand, about 10 minutes with Landsight.

$19,248

to query with the developer, found on the sample package.

28found·2flagged·0missed

On the sample package with 30 planted errors. Nothing counts until a person confirms.

Request a trial Follow @ericfangdotai for the latest