Skip to main content
Construction program teams use Surfaice to stay ahead of jurisdictional risk, budget drift, and closeout delays — especially when data lives across Procore, Smartsheet, email, and shared drives. Hugo is the in-app agent. An AHJ is an authority having jurisdiction (the city or county that issues permits). An RFI is a request for information between the GC (general contractor) and the design/owner team. Sitefolio is a construction project tracker some retailers use. New here? Start with What is Surfaice?.

​
Permits and jurisdictional risk

Retail buildouts cross many AHJs. Surfaice helps:
  • Track permit submission and approval status by project
  • Surface projects stuck in review or missing submittals
  • Route permit-related email to the right PM or expeditor
Connect Procore, Smartsheet, or document folders so Hugo can answer “where is this permit?” without a manual status meeting.

​
Schedule and trade coordination

​
Change orders and budget

Before approving a change order:
  • Model budget impact against the current GMP or allowance
  • Compare pricing to similar line items on prior projects (when historical data is available)
  • Flag scope that should have been in base bid
Treat outputs as decision support — final approval stays with your PM and finance team.

​
Punch list and store opening

Closeout workflows:
  1. Generate punch items from site photos or walk notes (when the skill is enabled)
  2. Track open vs completed items by store
  3. Tie punch status to opening readiness checklists

​
Punch walk App (field use)

Where the punch walk App is enabled, field teams should:
  • Confirm store number and contacts on the start card against your system of record (for example Sitefolio, a construction project tracker) before the walk
  • Choose inspect all sections in order when you want Hugo to advance automatically — you should not have to say “open next section” after every category
  • Use checklist widgets for compliance questions (fire suppression, alarm, certificate of occupancy) instead of typing long answers — especially on iPad
  • Verify the active section before logging a deficiency — voice or freeform text can land items in the wrong trade (GC vs installer)
  • Expect 30 seconds to a few minutes for heavy voice or inventory steps; narrow scope if the site is large
Report the generated punch PDF to your program standards (trade grouping, contact blocks, page layout) before distribution.

​
Example prompts

Punch walk is an App — see Apps & automations. Full catalog: Store development skills · Estimating skills