Build an index before collecting more files
A large folder can still be missing the one document that matters. Make a short index of the records currently requested for your project: drawing revision, cabinet schedule, appliance information and any documents identified by the responsible applicant or authority. Write who supplies each item and which version is current.
Keep completeness and correctness separate. A file can be present but show an abandoned layout. A complete cabinet packet can also differ from the packet needed for a particular city review. Ask each recipient what they need instead of assuming that one PDF satisfies every purpose.
Recognize Lakeland's application and upload steps
The City of Lakeland Building Inspection FAQs describe online applications through iMS. When the selected permit type requires plan review, the city describes an ePlan ProjectDox email with a link for uploading plans and supporting documents.
Use the city's current instructions for the actual permit type and scope. A submitted application is not proof that every required document reached plan review. Confirm whether the property is in Lakeland's jurisdiction; these instructions do not establish a process for Winter Haven or every Polk County address.
Check consistency at the connections
Compare the appliance model on the selections sheet with the model shown in the current design. Ask the responsible designer to confirm which product information controls cabinet dimensions or other dependent details. Do the same for the sink and other selections that providers identify as relevant. Similar-looking products should not silently substitute for the specified item.
When a revision arrives, label the older file as superseded in your own project folder and keep it for the history. Ask providers to acknowledge the current revision through their usual process. Do not replace their authoritative records yourself or remove evidence of an earlier agreement.
Use two separate readiness questions
First ask the applicant whether the requested review documents are complete and what official status they have. Then ask the supplier and responsible designer whether the proposed product order is ready under their terms. One answer does not settle the other.
If a document is still missing, identify the specific order items it affects. Record whether those items stay provisional and who can close the question. Avoid converting an “all files uploaded” message into permission to start work or a promise that no product changes will follow. Keep the index with your Lakeland–Winter Haven kitchen planning notes.
| Record to check | Current version / owner | Readiness question |
|---|---|---|
| Kitchen drawing | Revision and responsible designer | Does it match the proposed order? |
| Appliance or fixture data | Exact selection and supplier | Which dimensions depend on it? |
| Requested review document | Applicant and request reference | Received, submitted or still missing? |
| Order release record | Listed units and supplier terms | Which unresolved documents affect it? |
Worked example: present files, inconsistent versions
Suppose the folder contains a revision-three kitchen drawing and an appliance sheet for an earlier hood choice. A requested attachment is also still with the contractor. The index flags two different problems: a conflicting product record and a missing review document. The homeowner asks the designer which cabinet items depend on the hood, and the applicant to complete the requested submission. The supplier then receives the coherent revision set for its order-release discussion. Uploading the missing file alone does not resolve the outdated selection.
Questions to settle before ordering
Does a complete folder mean city approval?
No. Completeness, submission, review and authorization are different states. Record the actual official status separately.
Should I delete earlier drawings to prevent confusion?
Keep prior versions as history and clearly identify the current one. Ask affected providers to confirm which revision they are using.
