Project management built for Indian AEC teams

Why a purpose-built tool

Generic project managers — Asana, ClickUp, Jira — don't know what an RFI is. They don't understand that a drawing changes state fifteen times before it's "approved for construction." They don't model the difference between an architect reviewing a design and an owner signing a sheet.

Blueprint's project module starts from the AEC practice's actual workflow and works backward to the UI.

The project lifecycle

Every project moves through an explicit state machine:

• Draft — the owner or PM is still shaping scope, BOQ, and team.
• Planning — PM assigned, designers being added, milestones defined.
• In progress — on-site work happening, drawings versioning, daily logs flowing.
• Review — PM has submitted for owner sign-off; findings come back here.
• Completed — owner-approved, files archived, final RA bill issued.

An on_hold detour is reachable from any active state for weather, client delay, or permit issues — and is reversible.

Access that matches org reality

Blueprint ships with a two-layer RBAC system:

1. Platform roles — superadmin, admin, owner, pm, designer.
2. Org-level custom roles — your organisation defines its own roles on top (e.g. "Principal Architect", "Site Supervisor", "Quantity Surveyor") from the full permission catalogue, scoped per project.

A designer assigned to Project A doesn't see Project B. A subcontractor's user doesn't see vendor margins. An owner sees the roll-up of everything.

Milestones and the progress layer

Milestones carry both planned and actual dates and a completionPercentage so the progress view is never a lie. Milestones feed the Gantt, trigger billing via RA bills, and show up in the AI review when their delta drifts past threshold.

Audit, timeline, and immutability

Every state change writes to an append-only project timeline. Every data write — including the seemingly boring ones — emits an audit event with user, IP, user-agent, and change diff. Soft deletes only. No silent mutations.

What we deliberately don't have

• Kanban cards with 80 statuses that don't mean anything in AEC.
• Gamification points for finishing a task.
• "Velocity" metrics borrowed from scrum-world.

Who this is for

• Construction firms moving off spreadsheets + WhatsApp groups.
• Architecture practices that want RFIs and submittals in the same place as fees.
• Real estate groups running five buildings across three cities.
• Infrastructure contractors with PWD-style deliverables.