Skip to main content

Project info fields

Every firm and every country prints a slightly different project board: the building permit number here, the investment amount there, the works duration somewhere else. Info fields let you add whatever yours needs without waiting for Builddar to add a field for it.

Required role: Project Manager (or Organization Admin) to add or edit. Any project member can see them.

What they're for

An info field is a label and a value that gets printed in the headers of generated documents alongside the project name and address.

Typical uses:

LabelValue
Building permitPC 075 112 24 A0031
Works duration18 months
Investment amount€ 4,200,000
FinancingBank X — file 4471
caution

Info fields are for printing only. Nothing in Builddar reads them, validates them, or acts on them — a date here won't drive a deadline, and a number here won't gate anything. If you need a value the system reasons about, use the real field for it: due dates on issues, phases for stages, external codes on zones.

Add an info field

  1. Open the project's Settings and find Info fields.
  2. Select Add field.
  3. Enter:
    • Label — what it's called on the document, for example "Building permit".
    • Value — the content, for example the permit number.
  4. Save.

Result: the field appears in the list and is printed in the headers of documents generated from this project.

Reorder fields

The order you set is the order they print in.

  1. Open Info fields.
  2. Drag the fields into the order you want, or use the reorder action.
  3. Save.

Result: generated documents print them in your order.

tip

Put the fields a reader looks for first — permit number, then dates, then financial detail. The header is skimmed, not read.

Edit or remove a field

  1. Open the field and change its label or value, or choose Delete.
  2. Save or confirm.

Result: documents generated from now on reflect the change. Reports already generated keep what they were printed with.

note

Info fields are per project. A permit number belongs to one project, so there's no organization-level version of this list, and they aren't copied when you create a project from another.

Next steps