Parking lots / Site information / Commercial planning
What to Include in a Parking Lot Site Package
Assemble plans, photos, measurements, operating notes, and open questions for a more focused concrete parking-lot scope discussion.
By Great Lakes Bay Concrete & Stone ·
Loading article…
Build one shared picture of the property
A site package does not need to be a polished bid set. Its purpose is to let an owner, manager, and contractor look at the same place. Start with an aerial screenshot or plan, property address, approximate area, and a marked outline of the proposed parking space. Add photos from every approach and at each building connection.
Then add a one-page note: intended use, vehicle types, pedestrian routes, current surface, known removal areas, access constraints, and questions that are still open. Include existing surveys or drawings if you have permission to share them, but label their date and source. Old documents can be helpful context without being a final site representation.
Make unknowns useful
An honest “unknown” prevents an invented answer from becoming part of a scope. Examples include uncertain property responsibility, a possible utility issue, or an area that may need a public-agency answer. List the unknown with the person or agency who may need to clarify it.
The package is especially valuable when several people make decisions. It creates a record of what has been asked for and helps compare proposals on the same information. It does not establish an engineered design, permit status, price, or project schedule.
Great Lakes Bay Concrete & Stone offers concrete parking-lot installation. Send the information you have; a complete drawing is not required to begin. Read Parking-area access questions to add the operating details that plans often omit.
Put the material in a simple order
Send the site image first, then photographs, then the one-page operating note, then any existing documents. Label files with a plain location or view: “front entrance looking west” is easier to use than a camera filename. Add the date because a site can change quickly.
The useful distinction is between information that describes the property and information that decides the work. Photos and plans describe. A final scope, price, permit decision, or operating arrangement requires the appropriate review. Keeping that boundary clear lets a contractor ask focused questions without treating an old drawing as a current promise.
A sample one-page note
State the property address, intended parking area, usual vehicle types, primary pedestrian route, known access issue, and open question. Example: “Delivery van uses rear door weekdays; visitor entrance is at front; final extent of existing-surface removal is not yet decided.” This is more actionable than “commercial lot needed.”
Before sending, remove unrelated personal or confidential documents. The goal is enough detail for a productive first conversation, not every file the organization has ever created.
Use the package to compare conversations fairly
Send the same current package whenever you ask more than one contractor to discuss the project. If one receives a plan, a delivery schedule, and clear photos while another receives only a square-foot estimate request, their responses may appear different because the facts were different. A shared package makes it easier to compare whether each conversation addresses the same parking area, access needs, existing surface, and unresolved questions.
Example
A property manager may have an old plan showing a parking field but no indication that a rear door now handles morning deliveries. Adding a current marked photo and a one-sentence operating note changes the information from “old document” to “useful context.” The manager still has not decided the scope, price, permits, or work arrangement. They have simply made the current site legible.
Keep a short change log
At the bottom of the note, list the date and any change since the last version: new tenant route, closed gate, different vehicle type, or updated removal area. This avoids carrying an old assumption into a new discussion. It also shows which issues are known facts and which remain open for the property team, contractor, or relevant authority to clarify.
Label the decision owner for each open question
Not every blank on a site package belongs to the same person. Beside an open item, note whether the property manager, a tenant, a supplier, a designer, or a public authority is the person most likely to clarify it. For example, a manager may know delivery windows, while a tenant knows which entrance receives visitors. This prevents an early scope discussion from quietly turning an operational uncertainty into an assumed fact.
The package is still useful when some answers are pending. A line such as “rear-gate use to be confirmed with tenant” is clearer than omitting the gate altogether. It tells everyone which part of the site needs follow-up without inventing a requirement or a construction arrangement.
Explore concrete parking lots for the offered work and the decisions to discuss for your project.