Award to Project¶
| Stage | Building |
|---|---|
| Status | Partial |
| Design status | In progress |
| Estimate | M |
| Confidence | Medium |
| Linear | PIN-274 ↗ PIN-1078 ↗ |
| Linear status | Done · +1 planned |
| Cycle | C15 |
| Design | Design ↗ |
| Linear epic | Bid Intake & Pipeline |
| Module | Bids ↗ |
Priority: High
Scope¶
Backend + UI for the single "Award" action that converts a bid into a Project: locks the bid, checks for duplicate projects, generates the project number, creates the Project record from bid data, carries over the allowed document folders, seeds cost codes, and initializes the Submittals/RFIs/COs/Daily Logs modules — all in one atomic transaction behind a 4-step confirmation stepper. (Source: PIN-274.)
Acceptance criteria¶
- "Award" click opens a 4-step stepper — confirm project info, documents to transfer, budget/cost codes, handoff scope — before anything is created; cancel at any step aborts
- Verbal, LOI, and Contract award stages all trigger the same conversion
- Duplicate-project check warns ("A similar project exists...") and lets the user create anyway or open the existing one
- Sequential project number generated per year (PYY-###)
- Documents are copied (not moved) from only the allowed bid folders; sub-folder structure preserved
- Cost codes seeded from the estimate; Submittals/RFIs/COs/Daily Logs start empty
- Multi-GC bids: only the winning GC's entry becomes Awarded; others prompted to mark Lost
- Re-clicking Award on an already-awarded bid returns the existing project, never creates a duplicate
Conor's comments¶
Have no seen this yet. Needs testing & signoff after 8/19. The workflow needs to be fully verified with the cost codes, budget, creating new project number/name, transfering the relevant documents and creating correct proejct handoff. This workflow will be tested by Pinley team post 8/19.
Notes¶
4 financial bugs in 2 weeks; 100x budget fixed; needs seeded data to retest
Open question for Conor¶
-