Preconstruction spec capture for every Vistaza job. Sign in with your Vistaza Google account.
PM Success
Owner
Projects
Pipedrive deals at the 30 for 30 stage appear here. Click a project to capture its spec.
—
—DRAFT v1
jobsite rendering
GapsCatalogDesign pressurePerformance classThermal U-factorWater test countSill pan flashing
Types summary
Requirements
Tests
Sections & flashings
Accessories
Sources
Engineering
Logistics
Shops
0 types
Project requirements — defaults the catalog inherits.
Design pressure · water test pressure · performance class · thermal · acoustic · air leakage. Phase 1 wave 2.
Tests — water · air · structural · mockup · other rows.
Each row references the standard, count, basis, pressures, location rule, and which catalog types it applies to. Phase 1 wave 3.
Sections & flashings — head, sill, jamb conditions; sill pan, head flashing, end dams, drip cap.
Each entry cross-references which catalog types it applies to. Phase 1 wave 4.
Accessories & finishes — screens, opening-control devices, special hardware, color matching, fall protection.
Per-type or project-wide. Phase 1 wave 5.
Sources — contract, spec sections (CSI 08 80 00), window schedule, schedule notes, building & wall sections, elevations, floor plans, detail sheets, design plans, finish schedule, RFIs, emails, verbal.
Each spec line links to ≥1 source for provenance. Phase 1 wave 6.
Running engineering
Wind load · structural · anchor design · thermal · condensation · AAMA test reports. Each item tracks status, owner, and the linked deliverable in 06-Engineering/.
No engineering items yet.
Click + Add engineering item to start. Each item links to the Google Sheet / PDF in {project}/06-Engineering/ and tracks who's doing it + where it is in the review cycle.
Logistics
Three phases. Quoting → Ordering → Scheduling. PM Success owns each one end-to-end.
1Quoting
No container quotes yet.
Get freight quotes from carriers / forwarders before booking. Each captures: carrier · origin port · destination port · # of containers · rate · transit time · valid-until date · terms.
2Ordering
No containers booked yet.
Once a quote is accepted, log each container: booking # · container # · sequence · units · ETD factory · ETA destination port · shipping line · POL/POD · BOL link.
3Scheduling
No deliveries scheduled.
Two scheduling legs per container — trucking (port → jobsite: carrier · pickup window · ETA jobsite · driver/cell · POD) and customer delivery window (GC/owner sign-off · date · time window · receiving contact · forklift/lift instructions).
Shops
A project has multiple shop sets (Main windows · Mockup · Install details · Storefronts · etc.) with varying rush levels. Each submission cycles internal (Natasha ↔ Israel) → external (Vistaza ↔ customer architect) → architect approves → close.
Shop setsMultiple per project · each tracks submission count · rush priority · target ship date · status
No shop sets yet.
Click + New shop set to create one. Typical sets for a Vistaza job:
Main windows — production shop drawings, Sub #1 → ~#4 to approved Mockup — usually 🔥 rushed (contract-driven mockup ship date weeks ahead of production) Install details — head / sill / jamb / flashing detail sheets Storefronts — separate fabricator, separate cadence
Each set carries its own rush level (🔥 rush · normal · slow), target date, and submission iteration history. Sets run in parallel — Mockup can be on Sub #3 while Main is still on Sub #1.
Submission iterationsClick a shop set above to view its submissions · ~5 subs max · ~5-10 iterations per cycle
Select a shop set to see its submissions.
Each submission has two iteration streams:
Internal cycle (Natasha ↔ Israel) — every draft + Israel's redline + Natasha's revision, dated and authored. Final internal version graduates to external.
External cycle (Vistaza ↔ Customer architect) — sent date · reviewer · returned date · markup PDF · comments · revision-required flag. Architect approval closes the submission.
Active action itemsOpen items across all shop sets · grouped by owner (Natasha / Israel / architect)
No open action items.
Each callout (from Israel's internal redline or the architect's external markup) becomes an action item: shop set · owner · category (swing · sizing · wall align · visual · spec) · which submission it surfaced on · status (open / addressed in next iteration / resolved). Items unfixed by submission close carry forward into the next sub's internal cycle for that shop set.
Newer build available.
Add type
Latest estimate
Type detail
Handles set project-wide on the Requirements tab — not per type.
Link resource
Paste a Drive share link, Pipedrive attachment URL, or Firebase Storage URL. Stored on the shared project doc — Install reads the same field.
