Questions fabricators ask.

Earned tonnes divided by project tonnes. Each item's weight is shared across the stages that apply to it (equally by default), so finishing every stage earns the item's weight exactly once. The How it works page has a worked example.

No. An assembly's weight already contains its parts. Part preparation earns a share of the assembly weight through the parts' own stages (40% by default, adjustable per project), and the assembly stages earn the rest.

The Assembly List (Gross), the Assembly Part List (Gross) and the Plate Part List (Gross), as .xsr, .txt or the Word-wrapped .doc files many offices save. Any Excel or CSV list works too, with a column-mapping step.

It gets a route with only the stages it needs, usually procurement and cutting. Stages that don't apply are never shown as outstanding and never dilute the percentage.

Yes. Required, completed and remaining quantity are tracked for every mark at every stage, and the weight follows the quantity.

The activity is shown as overdue and asks for a reason and a revised forecast. The baseline date is kept permanently, and the change is recorded with who made it and when.

No. It is a fabrication schedule driven by production data: work packages, stages, baseline and forecast. It deliberately leaves out resource levelling and critical-path engines.

Only people in your workspace, according to their role. Every record is scoped to your organisation on every database read. Fabricata staff look at customer data only to resolve a problem you have reported.

On Vercel with a Neon Postgres database, in the European Union (Frankfurt), encrypted in transit and at rest. Details are in the Privacy Policy.

Not yet. The products are designed to connect: cutting progress from Cut could complete the Cut to Size stage, and a released assembly could raise an inspection request in Inspect.