BuildEase

LProject lifecycle

Through the whole project, on one record

Choose a phase to see what BuildEase covers in it. Each phase uses the same project, people and history.

Phase 01 of 06

Set-up and mobilisation

The project is created through one controlled set-up and its organisations join in their capacity.

  • Create the projectProjects → Create new project, then a controlled set-up.
  • Organisations and capacitiesOwner, PMC, consultants and contractors registered on this project.
  • BreakdownPhases, packages, disciplines and locations down to room level.
  • SettingsNumbering, forms and workflows, review periods and calendars, published with four eyes.
  • MobilisationMobilisation and start-up requirements, tracked to completion.
Surveying and setting out on a new site

02A submittal, start to finish

Every step has an owner and a clock

Scroll through one shop drawing. The orange square is where the document is now: the party that holds it, and whose time is running.

  1. Main contractor

    Drafted and submitted

    The contractor prepares the submittal with its files. The project manager's approval can be required before it leaves the contractor; on submission it receives its reference from the project's numbering convention.

    Stage: Submitted. Time running for: Consultant. Recorded: Reference allocated, files fixed.
  2. Consultant document control

    Received and routed

    A valid submission is the consultant's receipt. It is routed to the disciplines that review it, and the review period starts from the project's own settings.

    Stage: Consultant receipt. Time running for: Consultant. Recorded: Receipt instant, review period started.
  3. Architectural and MEP reviewers

    Discipline review

    Reviewers open the PDF in the browser, mark it up and comment. Their marks stay internal until a code is issued.

    Stage: Discipline review. Time running for: Consultant. Recorded: Markups, comments, reviewer.
  4. Consultant project manager

    Approval and code

    The project manager approves the consolidated response and issues the code. Technical review and release authority stay separate.

    Stage: Manager approval. Time running for: Consultant. Recorded: Code, approver, consolidated comments.
  5. Main contractor

    Returned to the contractor

    The response is delivered electronically the moment the code is issued. If action is needed, the contractor's resubmission clock starts at that instant.

    Stage: Returned. Time running for: Contractor. Recorded: Delivery instant, released markups.
  6. Main contractor

    Resubmitted as Rev C

    The new revision opens a clean review. Earlier revisions, their marks and their codes stay in the document's history.

    Stage: Resubmitted. Time running for: Consultant. Recorded: New revision, history kept.
  7. No open step

    Closed

    A code that needs nothing more from the contractor closes the document. The time each party held it is on the record.

    Stage: Closed. Time running for: Nobody. Recorded: Time held by each party.

See it on a project of your own

A demo is a private workspace with three synthetic projects and data in every module, open for 15 days. You can act as each role: contractor, consultant, project manager or client.

Project lifecycle — BuildEase