How Does Scaftra Manage Selections?

How do you stop a room from being built before the owner has actually chosen the finishes?

Scaftra tracks each owner choice as a first-class selection record with its own review and approval, and blocks a room from releasing until a required selection is approved.

The problem it solves

Selections are the owner and builder choices that define a finish-trade job: the faucet, the door style, the tile, the appliance package. Each one carries a cost impact, a schedule impact, and an allowance it draws against. When selections live in a spreadsheet or an email chain, nobody knows which choices are final, which are blocking the room, and which were never made.

Why it matters

A required selection that has not been approved is a room that cannot safely release to order or install. Building ahead of an unmade selection means re-cuts, reorders, and a client who says they picked something different. Tracking each choice as a record with a real approval is how the field knows a room is actually ready.

Common mistakes

How it works

1. Create the selection

   Each owner choice is recorded against its room, trade, work package, budget line, and allowance, with its cost and schedule impact.
2. Submit for review

   The selection moves into review so the client can act on it through their portal.
3. Client decides

   The client approves, approves as noted, requests a revision, or rejects the selection from their own login.
4. Room releases when required choices clear

   A required selection blocks the room until it is approved, approved as noted, or cancelled; a rejection does not clear it.

How Scaftra does it

Scaftra models the Selection as the first-class source of truth for an owner choice. It anchors to room, trade, work package, budget line, and allowance, carries cost and schedule impact and a required-for-release flag, and runs its own review lifecycle. The client acts on it through curated client actions (approve, request revision, reject) gated to the client role on a project they belong to. A selection marked required-for-release blocks its room until the choice reaches approved, approved as noted, or cancelled. A rejected selection does not resolve the block, because the owner picked nothing, so the room stays gated until a real choice lands. This is built and live.

Key capabilities

• Required-for-release gating: A required selection holds the room until the choice is approved, so the field never builds ahead of an unmade decision.
• Cost and allowance impact: Each selection carries its cost and the allowance it draws against, so an over-allowance choice surfaces as a change.
• Client review actions: The client approves, approves as noted, requests a revision, or rejects, each as a recorded decision.
• Anchored to the work: Every selection is validated to belong to the same project, room, and trade, so it cannot attach to a stranger's room.

Benefits

• Rooms only release when the choices that gate them are genuinely approved.
• Over-allowance choices surface as cost changes instead of getting lost in the decision.
• A recorded approval per choice ends 'I picked the other one' disputes.

Who it's for

• Designer-led remodelers.Shops where the homeowner makes many finish choices that each gate the room.
• Project managers on finish work.PMs who need to see which rooms are blocked on an unmade selection before scheduling install.

Related on Scaftra

Go deeper