Template Builder
AI guided as-built packet builder
Follow the assistant-led checklist from client branding through device documents, workbook setup, marked plans, packet layout, and final handoff.
AI Setup Guide
Complete each step in order. The next best action stays at the top.
0/7 Ready
Current Packet Preview
This updates as the guide gathers data.
Executive Closeout
What This Template Stores
Template records publish through the authenticated Vercel and Supabase backend.
The guide will tell the user exactly what to do next.
Brand
Client logo, colors, and portal URL
Each client gets a reusable template with their own look. The URL pattern stays consistent: theirchoice.asbuilt.thnikers.com.
Brand Settings
Upload a logo and choose the color set used in the portal and packet.
Use letters, numbers, and hyphens. Example: client-name -> client-name.asbuilt.thnikers.com.
Optional. Images are resized for reliable publishing.
Higher values keep text easier to read. The publish check prevents unsafe contrast.
Live Brand Preview
Updates apply immediately across the workspace.
Equipment
Low-voltage device catalog and symbol library
Tell the app what equipment the client marks. Default symbols are provided, and custom PNG/SVG symbols can be imported per device type.
Known Equipment Types
Check what this team will mark. Uncheck or use X to remove it from this template.
The automatic map feature depends on this catalog. Every client label should be linked to one of these known equipment types so the app can pick the right symbol and packet section.
Replace a Device Symbol
Choose an existing device, then upload the correct digital symbol for that device type.
Choose a transparent PNG or SVG. Uploaded artwork is used by itself—without a circle, square, or diamond—and marker numbers are centered on it.
Add a New Device Type
Create equipment that is not already in the catalog and optionally use the selected custom symbol.
| Client Label | Linked Type | Symbol | Action |
|---|
Device Documents
Find and attach device PDFs
Find the device warranty, manual, and cut sheet. The app downloads and attaches the actual PDFs—search-result links are never added.
Find Warranty, Manual & Cut Sheet
Use exact model and part numbers. All three PDFs are attached automatically when found.
The warranty, manual, and cut sheet will be stored as attached PDFs.
Upload Device PDF Manually
Choose a PDF from your computer and attach it directly.
PDF only, up to 20 MB. The file is stored securely with the published workspace.
Choose a PDF from your device.
Attached Device PDFs
Only stored PDF files appear here and are included in the manifest.
Workbook
Excel header builder with semantic mapping
Users can choose standard columns and add custom labels. Custom labels must be linked to known meanings so imports, map labels, and packet generation work correctly.
Standard Columns
Choose what appears in the generated workbook.
Do not let arbitrary labels float without a meaning. Example: if a client says "Jack ID", link it to "Port / Jack Number" so the map and packet know how to use it.
Generated Sheet Preview
This is the worksheet structure the app will give the client.
Plans
Interactive map with sharp PDF zoom and automatic symbol workflow
Upload a building plan, choose a device type, mark every icon you want, then number only those selected locations.
Plan Workspace
Markers stay compact so locations remain precise at high zoom.
Upload a plan, choose Camera (or another icon type), click Mark Icons, then click every existing plan icon that should be numbered.
Upload a building plan. PDF, image, CAD, BIM, and other plan files are accepted; preview is available for browser-readable PDFs and images.
Icon Selection
You choose the exact plan icons; numbering will not scan or guess based on color.
Upload a legend to turn the known low-voltage symbols into placeable digital map icons.
Automatic Feature Scope
What the production app should do before final packet generation.
A
Read legend and labels
Use the uploaded legend and three user-picked examples to learn which plan symbols belong to each device type.
B
Match to workbook
Map rows to known types, device numbers, closet, port, IP, MAC, and cable test results.
C
Suggest locations
Place compact markers with confidence and evidence; require approval before publish.
Packet Layouts
Four closeout packet layouts
Each client can choose a default document style. The selected layout changes cover page emphasis and packet ordering.
Packet Section Defaults
Sections included in the generated AS BUILT packet.
Publish
Deployment and client handoff settings
The URL convention is fixed. The client chooses the first segment; the app creates or requests DNS for theirchoice.asbuilt.thnikers.com.
URL Plan
Publishing activates the customer hostname through the production deployment API.
Publishing validates and saves one tenant configuration for . It reuses the tested application; it does not regenerate the code.
Run the preflight, then publish when every required item is ready.
Authentication + Permissions
Modern customer login for Telcom staff and outside users.
Leave blank to require an invitation. Outside users can still be invited by email.
Clerk provides the branded sign-in screen for Telcom staff and approved outside users. Vercel serves the application and Supabase stores private project data and PDF documents.
A
Admin
Manage members, configuration, maps, approvals, and publishing.
P
Project Manager
Edit maps, verify work, and advance project workflow.
F
Field / Viewer
Field users update assigned items; viewers have read-only access.