Generate Your First Project

A Project is the core container of knowledge in Darwin.
Every estimation, document, IFC model, QTO session, work request, approval, baseline, cost entry, and revision lives inside a project. Before estimation work becomes durable, it needs a project context.

This page walks you through:

• what a project represents
• when to create your first one
• how Darwin generates it from work-request information
• when to create one directly
• what each field means
• recommended practices for organizing real projects

---

1. What a Project Represents

In Darwin, a project is:

• the place where all cost information lives
• a timeline of decisions and revisions
• a container for documents, IFC imports, and correspondence
• the context for your estimations
• the workspace where teams collaborate
• the memory layer that connects requests, approvals, actual costs, and variance learning

Once a project is created, everything else — modules, IFC data, estimations, price reviews — connects back to it.

---

2. When to Create a Project

In normal operations, a project should be generated when a work request is clear enough to become real work.

The preferred path is:

1. A requester creates a Request For Work.
2. The estimator clarifies missing scope, files, or assumptions.
3. The request is accepted, approved, or moved into active work.
4. Darwin generates the project automatically from the work-request information.
5. The project preserves the request as the origin of the work.

When Darwin generates the project, the information already captured in the request becomes the starting point for the project record. This can include the title, scope context, client or project context, attached files, requester, assignee, comments, and activity history, depending on what was provided in the request.

You can still create a project directly when you are setting up a demo, migrating existing work, or building internal sample data. The important habit is to keep the reason for the project visible.

---

3. Generating a Project From a Request

To generate a project from a work request:

1. Open the accepted Request For Work.
2. Confirm the request has enough scope, files, assignee, and requested-outcome context.
3. Use the project generation action from the request detail page.
4. Review the generated project information.
5. Open the Project Summary page.

The generated project keeps the original request, files, comments, and activity tied to the project. This is what lets the project explain why it exists before estimation begins.

---

4. Creating a Project Directly

To create your first project directly, follow these steps:

1. Navigate to Projects in the sidebar.
2. Click Create Project.
3. Fill in the required fields (explained below).
4. Click Save to generate the project container.

After saving, you will land on the Project Summary page — the main dashboard for your work.

Screenshot placeholder:
Add here: Create Project form

---

5. Understanding Each Field

When reviewing a generated project or creating a project directly, you will see several fields. Here’s what each one means and how it affects your workflow.

Project Name

Give your project a clear and recognizable name.
Examples:

• “Office Building – Phase 1”
• “Residential Tower – Preconstruction”
• “Warehouse Renovation – Concept Estimate”

Client (optional)

Allows you to link the project to a specific client record.
Useful for grouping work and managing documents.

Location

The project’s physical location.
Used for:

• transportation calculations
• currency/exchange considerations
• future regional pricing features

BIM Settings (optional)

If you plan to import an IFC model or 2D drawing, you can predefine related preferences here.
These settings can always be adjusted later.

Tip:
You can create projects with or without BIM or 2D drawings. Darwin supports both workflows equally.

---

6. After Generating the Project

Once generated or saved, Darwin will display the Project Summary, which includes:

• total estimations
• applied price lists
• attached documents
• IFC files, 2D drawings, and import sessions
• linked work requests and request history
• approval decisions and active baseline context
• actual-cost and variance context when the project reaches cost control
• recent activity
• collaboration tasks

This summary acts as your launching point for the entire project workflow.

From here, you can:

• import an IFC or 2D drawing
• create your first estimation
• upload documents
• manage modules and price lists
• review linked requests and comments
• request price review or approval when ready
• invite collaborators (if enabled)

---

7. Best Practices

To keep your pilot projects clean and easy to navigate:

Use clear naming conventions

Avoid generic project names like “Test 1” or “Sample Project.”
Instead, use descriptive titles.

Create one project per estimate

Darwin is designed around project containers — not mixed folders. When a different approved direction needs to preserve a separate history, use revisions or request-driven follow-up rather than silent overwrite.

Attach relevant documents early

Plans, drawings, specs, and RFQs help contextualize your modules and inputs.

Prefer request-generated projects

When a project starts from a request, use Darwin’s project generation path so the request, comments, files, and activity stay visible. This makes later review, approval, and variance analysis easier to trust.

If working with IFC or 2D drawings, import them before estimating

This ensures quantities and classifications are ready when you start building your cost structure.

---

8. Next Step

Your project is now ready.

Continue to the next chapter:

➡️ Import an IFC Model or 2D Drawing