A City of Medina residential deck application combines two questions that should remain visible in the project file: where the deck may be placed and how the proposed deck is documented for building review. A permit number without the submitted site and structural records cannot reconstruct either decision.
This guide applies to the City of Medina, not every property with a Medina postal address. Confirm the permitting authority first. The City’s application index is the current starting point for City forms.
The ten-record deck file
| Stage | Evidence to retain | What it protects against |
|---|---|---|
| 1. Property | Address, parcel ID, owner/applicant, and dated jurisdiction check | Sending the project to the wrong authority |
| 2. Base site record | Survey or parcel map used to prepare the plan | Losing the source behind the drawing |
| 3. Site plan | Deck location, house, lot lines, dimensions, and side/rear setback figures | Treating zoning review as an undocumented assumption |
| 4. Scope | New, replacement, enlargement, repair, attached/detached, materials, height, stairs, and guards | Comparing bids that describe different work |
| 5. Dimensions and connection | Overall geometry, elevation, ledger or freestanding condition, and openings | Leaving the structural concept unstated |
| 6. Structural plans | Required plan sets, worksheet, member layout, foundations, connections, stairs, and guards | Relying on a verbal design |
| 7. Submission | Signed combined application, attachments, receipt, and project number | Losing what the City actually received |
| 8. Decisions | Zoning and building comments, approvals, conditions, and approved plans | Collapsing separate reviews into “permit filed” |
| 9. Field record | Inspection requests, results, corrections, approved revisions, and reinspections | Concealing work before its required record exists |
| 10. Closeout | Final result and any certificate or status the City identifies | Mistaking physical completion for administrative closure |
The City’s deck application asks for two sets of plans and identifies the project scope, material, size, height, railings, stairs, footers, and attached-versus-detached condition. It also requests a site plan with side and rear setbacks. Those fields are the minimum shared vocabulary for the owner, designer, contractor, and reviewer; they are not an approval by themselves.
Begin with a parcel record, then make a project drawing
The application points applicants toward a county auditor map as a starting resource. Save the dated source record, but do not represent a parcel-map screenshot as a survey or approved site plan if it is not one.
The submitted site record should make it possible to answer:
- Which parcel and structure does the plan depict?
- Where are the lot lines shown, and what is their source?
- What are the proposed deck dimensions and distance to the side and rear lines?
- Are stairs, landings, and projections included in those measurements?
- Did the City request a survey or other location evidence?
If the plan changes, keep the original, the correction comment, the revision date, and the approved replacement. That sequence is more useful than a folder containing only the latest unlabeled PDF.
Keep site approval separate from structural documentation
A zoning certificate can address location without proving the framing is adequate. A building review can address submitted construction information without establishing that the deck was built as approved. Preserve both tracks.
The City’s residential wood-deck guide organizes technical subjects such as footings, posts, beams, joists, attachment, guards, and stairs. Use it to identify which plan details need to be explicit. Do not copy a generic span, footing, or connection detail into a project without confirming that it applies to the materials, loads, geometry, soil, and code review for that property.
Align proposals with the permit scope
Before selecting a proposal, place its scope next to the application description. Look for differences in:
- demolition and disposal of an existing deck;
- attached versus freestanding construction;
- deck area, height, and number of levels;
- stairs, landings, guards, gates, or privacy features;
- foundation and connection work;
- electrical or other trade work; and
- permit preparation, corrections, inspections, and closeout.
This is not a recommendation to choose a particular contractor. It is a method for detecting when two prices describe different records and responsibilities.
Define inspection responsibility before construction
The sources reviewed do not provide a project-specific inspection schedule. Ask the City which stages apply to the approved scope, who may request them, what must remain visible, and which final record closes the permit. Put those answers in the contract and project file.
A strong field log records the permit number, inspection type, requester, requested date, actual date, result, correction, reinspection, and supporting document. “Inspector came” is not a result.
Method and limitations
Local Service Ledger reviewed the City application index, combined deck permit and zoning certificate application, and residential wood-deck construction guide on August 10, 2026. We converted their fields into a ten-stage evidence chain and separated site, structural, inspection, and final records.
We did not inspect a property, prepare a site or structural plan, calculate a span or footing, determine a setback, verify a fee, or retrieve a private permit. Confirm current requirements and project-specific stages through the City application route.