BidCraft now adapts your Project Template to each project instead of starting from scratch
Project Templates have been a little underused — you'd build out a beautiful template for Shower Remodels, then BidCraft would generate scope from your synthesis without really consulting it. As of today, that flips around. When you have a Project Template AND your photos / voice notes give BidCraft enough to work with, the AI uses your template as the strong starting shape and only adapts what the specific project demands.
What that looks like in Scope Review
Each line on the Scope Review screen now shows a small origin badge:
- Template — Carried over from your template line unchanged. Most lines should land here. The whole point of the template is that you've already decided what work belongs.
- Template · adapted — Came from your template, but BidCraft adjusted the scope or quantity based on this project. The reason for the change shows next to the badge — "Scaled qty for 24 sqft floor", "Added accent tile band per synthesis", etc.
- Added from synthesis — Not in your template. BidCraft added it because your photos or notes called for work the template didn't cover.
- ⚠ AI inferred — BidCraft added it without a direct template or synthesis basis. Rare. Review carefully — if it doesn't fit, remove it.
What happens to lines BidCraft drops
If BidCraft removes any of your template lines — say "Demo existing shower" on a new-construction job — you'll see a small disclosure above the list:
AI removed 1 template line — review reason ▾
Expand it and you'll see the dropped line plus the AI's brief reason. To put it back, hit + Add line at the bottom of the list and pick the service. The drops are auditable, not permanent.
Why this matters
A template is the contractor's playbook — the shape you want every project of this type to take. Before today, BidCraft would generate scope from scratch every time and you'd have to manually verify it matched your usual approach. Now the playbook IS the starting point. The AI's job is just to handle the per-job exceptions — drop what doesn't apply, scale what's different, add what's genuinely new.
If you've tagged your template lines with Bundle a sub-scope chips (the change that shipped this morning), the adaptive draft honors those too — it won't split out waterproofing into its own line when your Tile Install line already bundles it.
When you don't see badges
If you don't have a Project Template yet for the project type — or your project is in a custom category — BidCraft falls back to the original behavior (generates scope from synthesis without a template anchor). Lines from that path render without origin badges. Build out a template for that project type and the next scope draft picks up the adaptive flow automatically.