Replace “the permit is handled” with a stage
When an installer asks whether a kitchen is ready to schedule, “we applied” leaves important questions unanswered. Record what has actually happened: application started, plans submitted, corrections requested, or permit issued. Add a reference and a named person to the latest completed step.
The purpose is to spot a dropped handoff. A homeowner might hold the requested appliance information while a contractor holds the application number. Neither person can assume the other has completed the next task simply because the project appears in an online account.
Follow Salt Lake City's separate entry points
Salt Lake City Building Services identifies a permit application through Citizen Access Portal and construction-plan submission through ProjectDox. Its instructions describe an email for plan-upload steps after applying. The city also distinguishes permit issuance from the earlier stages and says inspections can be scheduled after issuance.
Confirm the jurisdiction for the actual property; this guidance is for Salt Lake City, not every community in the broader Salt Lake market. Ask the city and your responsible professionals which application and supporting material fit your scope. An application confirmation alone is not an issued permit.
Give the next action to one person
For each pending item, write the action, its owner and what will prove completion. “Applicant uploads revision two and records its submission” is actionable. “Waiting on permit” is not. Include who will answer a correction and who will tell the designer if the response changes dimensions or the proposed layout.
Use the provider's approved method to share relevant files and status evidence. Keep login credentials private. If the invitation or request reached a different person, have the applicant resolve access through the official process instead of passing around passwords.
Translate the record into purchasing decisions
Ask the designer which product decisions depend on an outstanding response. Link that dependency to the cabinet drawing rather than putting a vague hold on every selection. A finish discussion can progress while an unresolved opening or equipment location receives the appropriate review.
Before treating an installation date as firm, ask the responsible contractor what authorization, readiness and inspection milestones must be met. Record supplier lead-time statements separately from city status and contractor readiness. None of those dates proves the others. Keep this handoff sheet beside your Salt Lake City kitchen planning notes.
| Stage to verify | Who holds the next action? | Evidence / dependent decision |
|---|---|---|
| Application recorded | Named applicant; reference | Application confirmation only |
| Requested plans submitted | Uploader; current drawing revision | Submission record / open requests |
| Corrections answered | Responsible professional or applicant | Response linked to affected units |
| Permit issued, if required | Person checking official status | Issued record / contractor readiness |
Worked example: an upload invitation stalls the plan
In a hypothetical remodel, the contractor begins the application and the homeowner receives an email about plan submission. Each assumes the other uploaded the revised kitchen drawing. The tracker shows an application reference but no plan-submission evidence. They assign the upload to the appropriate applicant, supply the current documents through the agreed process and record completion. They keep “submitted” separate from “issued,” and ask the installer what remains before confirming a start date.
Questions to settle before ordering
Does a plan upload mean the permit is issued?
No. Record the submission as its own completed step and verify the issued status through the official process when required.
Should I use a supplier delivery estimate as my installation date?
Discuss delivery, review status and site readiness separately with the responsible providers. The handoff tracker helps show which dependencies remain open.
