← Interactive prototype

Floorwise — identity and UX reference

Version 0.2 · 24 October 2026

Direction

A working tool for flooring businesses: measured, compact and specific to the trade. Retain the Floorwise name. Use a staggered-plank symbol, neon green primary actions, charcoal navigation and plain white work surfaces. Measurements, item descriptions, ownership and review state carry the interface.

The identity is original. Jobber is a workflow reference for quote records, task lists, line-item editing, client previews and activity history. Its logo, illustrations and proprietary screen assets are not part of this kit. The custom PM review loop and technical Administrator boundary come from this project's requirements.

Reference mapping

Reference pattern Floorwise treatment Board
Work lists with actionable quote states Needs-action table with separate internal review and client response columns 01
Quote line items with quantity, cost and price Flooring material and labour rows, waste and installed-area context, private costing summary 02
Quote detail and activity Project record with owner, reviewer, property, files and revision activity 08
Client preview before sending Contractor-branded proposal with scope, total and terms 06
Requested changes and approval A separate internal PM review loop returning proposed edits to the original proposal manager 03–04

Sources reviewed 24 October 2026: Jobber Quote Basics and Jobber Quote Approvals. These inform the patterns above; Floorwise's internal PM routing is our proposed adaptation, not a claim about Jobber's internal approval features.

Brand foundations

Token Value Use
Volt #B6FF3B Primary action, active navigation in gallery, compact brand mark
Carbon #161B18 Navigation background, headings, all text on neon
Chalk #FFFFFF Tables, forms and documents
Subfloor #F2F4F0 Workspace background
Border #D9DFD6 Table rules and panel boundaries
Secondary text #626D65 Labels and supporting information on light backgrounds
Review #365D98 on #E7EDF9 Internal review status
Changes #82550A on #FFF0D5 Changes requested or review required
Approved #3D651A on #E9F7D8 Completed internal sign-off
Rejected #9C2D37 on #F9E7E8 Rejection decisions

Neon is an accent rather than a text colour on white. Neon actions use Carbon text. Status is always written out; colour alone cannot communicate approval. Disabled actions use neutral fill, muted text and a nearby explanation.

Logo: three vertical planks with staggered joints. Use one board-width clear space and avoid detail below 24px overall mark height. Do not distort, glow, outline or place the mark inside unrelated decoration. Source assets: assets/floorwise-logo.svg, assets/plank-mark.svg and tokens.json.

Typography: Arial/Helvetica/sans-serif for broadly available editable text; Consolas/monospace for amounts, IDs and measurement annotations. Product title 29px; panel title 17px; body 12–14px; small operational labels 10–11px. These are desktop design coordinates; implementation must respect text zoom and reflow. Do not reduce production text to fit a fixed mockup.

Geometry: 8px spacing base, 4–7px corners, 1px panel rules. Desktop sidebar 220px and toolbar 64px in 1440×1000 boards. Use purposeful density: actions align with the record they affect. Avoid unnecessary rounded cards, gradients, glow, oversized promotional copy, decorative metrics and floating shapes.

UX and copy rules

Journey and scope

Overview → Project record → Proposal editor → PM review → Owner reconciliation → New draft → PM sign-off → Client preview → Issue. The gallery links navigate concept boards, not a working approval system. Forms, status changes and permission controls are illustrations.

Nine boards: brand kit, work overview, proposal editor, PM review, owner reconciliation, technical Administrator configuration, client proposal, mobile review and project record. SVG output contains vector shapes and editable text sources. Native Figma components, variables and prototype wiring remain pending plugin tool availability.

The existing 150-point backlog remains the provisional baseline. The new project record is a presentation of existing project/file/review stories, not a new integration or scheduling module. Re-estimate the design acceptance story during sprint planning if the revised scope affects delivery.