Block Renovation operated as a two-sided marketplace connecting homeowners with vetted contractors. As Studio, our 0→1 renovation planning tool, moved into the core product experience, it changed the type of information Block collected from homeowners. Some clients now came through the marketplace with richer planning assets, including existing space photos, final renders, design intent, materials, and estimated costs. Others still came through the traditional flow with a simpler project brief. The contractor work order needed to support both paths clearly.

The initial ask was to add Studio assets into the existing work order, but I saw a larger opportunity. Contractor-facing teams had already heard recurring feedback that the work order was narrow, scroll-heavy, visually plain, and difficult to scan. Contractors were not reading the work order like a document. They were using it to make a fast qualification decision.

Through feedback from contractor operations and sales teams, I framed the redesign around three questions contractors needed to answer quickly:

1. Can I service this location?
2. Is the scope of work in my wheelhouse?
3. Is this job financially worth my time?

I redesigned the work order from a narrow modal into a more spacious, near full-page desktop experience, with the most important qualification details surfaced upfront. Location, scope, and estimated cost became the primary scan points.

On mobile, where contractors were more likely to be reviewing jobs on the go, I made sure those same details appeared above the fold.

On the jobs pipeline page, I added a Renovation Studio tag and onboarding tooltips so contractors could understand when a client had gone through the new planning experience and what had changed in the work order.

System Logic and Edge Cases → The work order had to flex across several project types: clients with Studio Touch, clients without Studio Touch, and mixed cases where a client used Studio for one space, like a bathroom, but added another non-Studio space, like a basement. I designed dynamic sections that could adapt based on available project data, including variable client names, spaces, maps, photo counts, existing space photos, ideal space imagery, materials, and project planner information. One important clarification was separating the Block project planner from the client, since contractors could not contact the client directly until they accepted the work order.

Because this change touched contractor operations, sales, support, and the contractor app experience, the work was highly visible across the company. I created a detailed handoff file with annotated dynamic components, content logic, and state variations so engineering could build efficiently and internal teams could understand what contractors would see. The final design turned a basic project summary into a more useful marketplace handoff: one that helped contractors qualify jobs faster, supported richer Studio-generated assets, and gave internal teams a clearer artifact to explain, troubleshoot, and operationalize.