Skip to main content

How can we help you?

Search for guides on sheet markups, RFIs, cost settings, roles, and more.

Browse Categories

Select a category to explore detailed step-by-step documentation.

How a SIDABuild project is put together, what the tools along the top do, and how to find your way to the screen you want. Start here if the product is new to you.

Creating a project, filling in its details, and the screens that describe the project as a whole — the dashboard, the activity log, and the workspace the project belongs to.

Publishing drawings, keeping track of which revision is current, and marking up a sheet so a question on site points at the right detail.

Raising, assigning and closing the work that needs putting right — from a snag on a site walk to a defect found at handover — and the categories, types and root causes that make the list worth reporting on.

Asking the design team a formal question, tracking who owes an answer, and closing the loop once one arrives.

Getting products, shop drawings and samples approved against the specification, and following each one through its review cycle.

Loading the spec book into the project, reading a section on screen, and linking what is specified to what is being submitted and built.

Site photography that stays findable: albums, locations and tags, so a picture taken today can still be produced in evidence next year.

The project document store — folders, versions, and the recycle bin that gives you a second chance after a deletion.

Running a meeting series, writing the minutes as you go, and turning what was agreed into actions with a name and a date against them.

Checklists and permits built to your own template — daily site checks, pour records, permits to work — filled in on site and kept as a record.

Formal letters and notices in and out of the project, kept as threads so the reply sits with the letter it answers.

Importing the programme, reading it as a Gantt, comparing a revision against the baseline, and seeing what is coming in the next few weeks.

The register of what is being installed — plant, equipment and materials — from delivery through commissioning to handover.

The breakdown of the building into levels, rooms and zones, and how naming it once makes every other tool filterable by where the work is.

Turning what is in the project into a document somebody can be sent: what each report contains, how to run one, and how to have it arrive on a schedule.

The budget, the contracts against it, the changes that move money, and the forecast of what the job will finish at.

The read-across of the project: what the numbers in the other tools add up to, and which of them is worth worrying about this week.

Sharing a defined slice of your project with another company that has its own SIDABuild project, without giving them the run of yours.

Who is on the project, what each of them can do, and how permissions are assembled from roles rather than set person by person.

Deciding what the product tells you about, how often, and through which channel — at project level, per tool, and per person.

Your own profile and preferences, the workspace the projects sit in, the plan it is on, and the add-ons connected to it.

What to check when something is missing, refused or not behaving — most often a permission, a filter, or the wrong project being selected.

Popular Articles

Frequently read guides by construction teams.