Skip to content
About ForgeLot

We got tired of tracking lots on marked-up PDFs

ForgeLot started as a way to solve our own problem: turning a design alignment into a construction lot register without losing an afternoon to spreadsheets.

Illustrative road-construction corridor with pavement preparation, a grader and compactors
Origin story

Where ForgeLot came from

We've run civil earthworks jobs, the kind where the alignment lives in a DXF, the chainage lives in someone's head, and the lot register lives in whichever spreadsheet was last emailed around. It worked, in the sense that the job got built. But every handover, every site meeting, every "where are we up to on layer two" question meant reconciling three different versions of the truth.

We built the first version of ForgeLot to fix that for ourselves: import the alignment, generate chainage markers, draw lots by chainage range and offset, and let the software work out the area instead of a calculator. It stuck, so we kept building it.

ForgeLot is built around civil engineering workflows, with a practical focus on chainage, construction layers and QA records that are useful on the next job.

How we build

What that looks like day to day

We build in small, testable steps, and we test workflows against real alignment files and real chainage ranges before we ship them.

  • Every feature starts from a step someone does on site, not a feature list
  • We validate new workflows against real DXF alignments, not sample data
  • CSV registers, printable reports and original test results are included in QA exports
  • We'd rather say no to a feature than ship something that quietly gets a chainage wrong
What we believe

Four things we won't compromise on

These shape every decision we make about what ForgeLot does and doesn't do.

The map is the source of truth

A lot register is only useful if it matches the ground. We start from the alignment and the chainage, not from a table someone typed up after the fact.

Engineers shouldn't fight software

If a workflow needs a training day before it's useful, it's not finished. ForgeLot should feel like the tool you already had in your head.

Your data is yours

Your DXF files, your alignment, your lot register, they belong to your project and your organisation, not to us.

Built from the site up

Start from a reference drawn on the map or an imported survey design. Lock the line, map the lots and keep construction and QA records together, whether you run a small contracting crew or a project team.

Where we're headed

Themes we're working on

Not a dated roadmap, the areas we keep coming back to as we talk to teams using ForgeLot.

  • Deeper support for more alignment and survey file formats
  • Richer offline behaviour for teams working with patchy site connectivity
  • More flexible reporting so registers match how your organisation already reports progress
  • Better ways for supervisors and engineers to hand work back and forth on the same lot

Want to work with us?

If you're running earthworks jobs and want to talk about how ForgeLot could fit your workflow, or you'd just like to tell us what's missing, we'd like to hear from you.

Get in touch

Put your next project on the map.

No DXF needed. Draw your control line on the map, create work lots and keep every layer, test and report together.

Card required · Cancel before day 14 to avoid charges · Plans in AUD