Is There a Basketweave Layout Where the Straight-Lay Grout Number Still Works?

Total grout linear footage for a fully tiled field depends on tile size, tile shape, and joint width — not on which way the tiles are rotated. Every internal grout line in a tessellated floor is shared by exactly two tiles, whether those two tiles sit in a straight row or get flipped 90 degrees into a basketweave pair. That equivalence only survives when the basketweave module is built from a true 2:1 rectangle, because two of those units close into a perfect square with no sliver or offset seam left over.

Run it through the numbers: a 12x12 tile laid straight at a 3/16 in (0.1875 in) joint works out to 200 linear ft of grout per 100 sq ft. Model the same footprint as basketweave using 6x12 planks at the same 3/16 in joint, pairing them into 12x12 modules, and the output comes back at 206 linear ft per 100 sq ft — a 3% difference, driven by border cuts and module alignment rather than the pattern itself. That's inside the calculator's 5% reuse tolerance, so the straight-lay figure is fine to carry over without rerunning the tool.

The failure case is square tile forced into a basketweave or pinwheel look — a layout covered in more detail on the /patterns page and in the square-tile basketweave guide. Model that same field with square units instead of a 2:1 rectangle and grout footage comes back at 340 linear ft per 100 sq ft, about 70% more than the 200-linear-ft straight-lay baseline. A module built from square tile carries far more internal edge per unit of floor area, and there's no shared long edge to cancel any of it out the way a 2:1 rectangle does.

Joint width is a second, quieter variable. Rectangular plank tile with any dimensional variance often gets held to at least 0.1875 in per TCNA guidance so lippage stays manageable once the tile is rotated into a basketweave module. If the straight-lay number was calculated at a narrower joint and the installer bumps the joint width for the rotated pattern — which is common — the reused figure undercounts even when the tile ratio is correct.

Border condition is the third variable, and it shows up in waste allowance rather than grout footage per se. A basketweave module can't be trimmed down piecemeal at a wall the way a single straight-lay row can; a partial module at the edge usually forces a full extra cut. That's why the calculator defaults to a 15% waste allowance for basketweave layouts versus 10% for straight lay. That 5-point gap is real material — extra tile and extra grout, not rounding error.

The most common failure is running out of grout mid-pour on a square-tile basketweave job that was priced off a straight-lay number. Mixing in a second bag from a different production lot mid-floor is how installers end up with a visible color break across an otherwise clean pattern — a callback that costs more than the five minutes it takes to rerun the calculation up front.

The second failure is on the material side, not the grout side: a waste allowance carried over from straight lay (10%) instead of the basketweave default (15%) leaves the tile order short once border cuts start eating into the pattern. That shortfall surfaces late, usually after the first row or two is set and the installer realizes the module count at the wall doesn't line up with what was ordered.

Confirm the tile ratio first — measure the actual printed dimensions, not the nominal size, since a tile sold as "6x12" that's slightly off true 2:1 breaks the module math this whole exception depends on. Run the layout through the /tile-spacing-calculator with the basketweave pattern selected and the real joint width entered, then compare its grout output against the straight-lay number already in hand. If the two numbers land within the same 5% band the app treats as acceptable, keep the original figure; if they don't, use the fresh basketweave output and adjust the material order to the pattern's 15% waste allowance rather than the straight-lay 10%.