The Current Approach

Most signage planning today follows this pattern:

  • Open floor plans in Illustrator
  • Annotate sign positions with markers or labels
  • Maintain a parallel Excel spreadsheet with sign codes, types, and quantities
  • Cross-reference between the two documents manually
  • Prepare the sign schedule and BOQ in separate spreadsheets

This works. It has worked for decades. But it creates structural problems that become visible at scale.

Where Illustrator Falls Short

Illustrator is a graphic design tool. It excels at visual work. But sign markers placed in Illustrator are just graphics — they carry no structured data. An annotation that says "D-01" on a floor plan is a text label, not a data point connected to a schedule.

When the architect issues a revised floor plan, every annotation must be manually repositioned. When a sign code changes, every Illustrator file must be updated individually.

Where Excel Falls Short

Excel is a spreadsheet. It tracks data effectively. But it has no spatial awareness. A row that says "D-01, Level 3, Lift Lobby" tells you the data but not the position. You cannot verify from Excel whether the sign is actually at the lift lobby on Level 3 — you need to cross-reference with the Illustrator file.

When multiple people edit the spreadsheet, version conflicts arise. When floors are added or removed, manual recounting is required.

The Core Problem

The fundamental issue is that placement (visual) and data (schedule) live in separate systems. Every change must be made in two places. Every review requires cross-referencing two documents.

A structured signage planning workflow connects placement and data in one system. Place a marker, and the schedule updates. Change a sign code, and every affected position reflects the change. No dual-entry. No cross-referencing.

When It Matters

For a project with 30 signs, the manual approach is manageable. For a hotel with 400 signs across 15 floors, the disconnection between Illustrator and Excel creates real operational risk — missed signs, incorrect BOQs, and fabrication delays.