
Guides
Part of Historic motel restoration: 8 planning mistakes to avoid before 2027
Historic motel restoration: a scope checklist before you plan for 2027
Historic motel planning mistakes checklist for 2027 helps teams confirm evidence, location, review roles, and scope before making property claims or plans.
This checklist catches planning errors before an observation becomes a project claim. It helps a writer or owner confirm what is actually documented and what still requires qualified review.
What to take away
- Start with the location and source, not an expected answer.
- Keep physical observation separate from a technical finding.
- Record an evidence gap openly.
- Do not describe a public checklist as a formal assessment.
Check before writing a conclusion
NPS guidance on accessibility says written documentation should be supplemented by physical investigation before anticipated changes, and it notes the value of appropriate consultation. Read Preservation Brief 32 on historic-property accessibility. The brief does not evaluate a motel or decide which change applies to it.
| Check | What to confirm |
|---|
Use a six-step check
- Name the exact feature and location.
- Preserve the dated source material.
- Describe what is visible or reported.
- State what the source does not prove.
- Identify the next review role.
- Add a correction later if evidence changes.
This structure prevents a photo, a broad preservation source, or a vendor statement from being treated as a property decision. It also makes a later handoff easier because the next reader can see the gap rather than guess why a conclusion was made.
Record access limits
Add a line when an area was not visible, a document was not available, or the reviewer did not have the authority to assess it. A partial checklist is useful when it is labeled as partial. It is misleading only when it is published as a complete property review.
That distinction protects both readers and the record.
Add a source-limit check
Before a checklist entry is reused in public copy, compare the sentence with the record beside it. The NPS documentation standards require accurate documentation from reliable sources with limitations stated so the information can be checked independently. A practical version for a motel file is simple: cite the dated source, state the location, and name the part that remains unknown.
| Record problem | Check to add | Result |
|---|---|---|
| Undated photo | Date and location field | Image remains context, not proof of current condition |
| Broad source | Scope note | Guidance is not mistaken for a site decision |
| Missing reviewer | Role field | The next action has an accountable handoff |
| New evidence | Correction line | Earlier wording remains traceable |
The National Archives guidance for digital photographic records explains the need for identifying and descriptive information around image files. Include a stable image ID, location, date, and short caption in the checklist. A phone-album label alone is too fragile for a record that will be reviewed later.
Use the checklist during a review meeting
Read every open line aloud. The group should be able to separate what was seen from what someone hopes will happen next. If the issue calls for a professional review, the entry should say that plainly rather than using a technical term as a substitute for evidence.
The NPS preservation planning overview describes documentation as information that supports planning and design work. That is the right role for a pre-project checklist. It helps decision makers arrive at a defined question, but it does not make a decision for them.
Keep a one-page review trail
Use one short entry for each decision point. Start with the existing record ID. Add the date of review, the person or role that checked it, the observation, and one next action. If no action is justified, write that result as well. It tells a future reader that the item was considered without pretending that nothing can ever change.
Avoid a checklist that tries to contain every source in one paragraph. A separate source register can hold titles and URLs. The checklist should point to the relevant IDs and say why they matter to the question at hand. That split keeps the field sheet readable during a visit.
Common questions
Does this checklist confirm code compliance?
No. It organizes records and questions. Local code conclusions require appropriate current review.
What if there is no document for a claim?
State that it is not found in the reviewed material. Do not replace missing evidence with a confident summary.
Should a checklist include a product choice?
Only as a documented proposal or decision with a clear source and status, not as a general recommendation.







