DraftDraft

Use case

A refit, with the record kept aboard.

A boat goes into the yard once or twice a year and comes out with a bill nobody planned. Draft runs the refit as a project inside the boat's own workspace: the jobs are locked, the changes are decided with their cost in front of the person who signs, and the record stays with the boat.

The record that outlasts the owner

Owners change and the people aboard change; the boat's history should not. Every job, change and decision is logged against the boat, and the next owner, surveyor or yard reads the same record.

M/Y Auriga's spring refit, as the record has it.

The yard's jobs on one timeline

Hull coatings, the generator service, the tender garage: each a job with a planned span. When the osmosis treatment adds six days by an approved change, the bar shows it and the launch date moves with it.

Six days on the hull, by one approved change. Nothing else moved.

The position, for whoever signs

The boat's decision maker sees the baseline, what has been approved, what is pending and where the project now lands, in the currency the yard bills in.

One approved change so far; nothing pending. It carries the completion date six days out.

The rule

The loop is the same at any size.

A yard's change and an owner's request follow the same path: raise, see impact, decide, update. The mandate on the project says who signs for what.

Get started See the boat in the walkthrough