Overview

Many of our customers find that they'd like to standardize their DADO projects so that admin and user experiences are more consistent between job sites. Applying this level of standardization can be laborsome and error-prone if each setting of every new project has to be configured. Some of our customers have opted instead to create a "base project" to import into new projects. This importing gives admins a head start, and removes some margin for error.

Importing Project Settings

While creating a new project, you have the option of importing settings from an existing project. When you import a project's settings, you'll bring over its:

  • Team members,

  • Templates,

  • Custom Document Types,

  • Disciplines, and

  • Forms.

Best Practices

Creating a Base Project is very similar to creating any other project, but these best practices can help you get the most of this tip.

Creating the Base Project

Base Projects are made in the same way that any normal project is - by clicking Create Project in the Projects page of your company. Once there...

  • Give the project a name that's easy to find. In the example above. you can see that my Base Project's name starts with "zz". This makes it easy to find the project both by typing the characters in the Select existing project box, or even by visually scanning.

  • Set the Project Status to Archive. If you don't want the Base Project to be visible in the Projects page by default, set the Project Status field to Archive. This helps keep the active project list tidy, and you will still be able to find the archived Base Project in the Import Project Settings field.

Add Standard Document Types

If your organization has standard document formats, like RFI's, add them to the Base Project as Custom Document Types (CDT's). A couple of best practices for CDT's in Base Projects are:

  • Add as many Custom Document Types as you can. If you're not sure that every project will need a specific CDT, add it anyway. This helps admins of new projects know that they have the option to import those documents if needed, or they can opt to quickly delete them from the project.

  • Add Templates for the CDT to the project. Since templates are supported for CDT's it's best to configure at least one template for them in order to give admins of new projects a head start. Read the Create Templates section to learn more about best practices for Templates.

Add Templates for Common Document Layouts

Templates is one of the most important features in DADO to automating admin work. To do this, import a single sample of the document you'd like to template, then create a new template for it. You will likely create multiple templates for each drawing type or CDT.

  • Add templates liberally. Customers who get the most out of the Base Project workflow add templates for almost everything to their Base Project. For example:

    • Add project drawing templates for each architect or designer that you work with on repeat projects.

    • Create templates for every CDT that you add to the Base Project.

  • At a Minimum, add templates for Shop Drawings. Most of our customers are self-performing trade contractors who create their own shop drawings. If this is true for you as well, create shop drawing templates for every kind of shop drawings that your drafters product. If it's install drawings, spool maps, spool drawings - anything - add those Shop Drawing templates to your Base Project.

Add Universal Forms

Add forms to your Base Project that most projects will need to use on a regular basis. Some examples of forms that work well for this are:

  • Daily Reports,

  • Time Sheets,

  • Observation Reports,

  • Time and Material (T&M) Forms, and

  • Job Hazard Awareness (JHA) forms.

Did this answer your question?