01
Describe the project
Explain the current condition of the space and the result you need.
Use the project formTell us what the space needs now, what should change, and what information you already have.
This project form demonstrates the information needed for a clear request. Direct contact details are handled through the approved project conversation.
Quote-request details are used to review the project conversation and support a later response. This is project wording, not a claim of legal completeness.
Before using the project form
Describe the space as it exists today, including its current condition, the areas under review, and whether the property is occupied or vacant.
Explain the intended result and identify the primary need: commercial painting, a tenant improvement, or a white-box build-out. Separate required outcomes from options still under discussion.
Add available plans or photographs, plus practical constraints such as access requirements, property rules, work-area limits, and timing considerations. List open questions that should be resolved in a project-specific proposal.
If adjacent work categories are part of the conversation, keep them named as separate questions until the proposal confirms responsibility. A shared project discussion does not automatically make every related trade part of the same included scope.
Use plain descriptions of current conditions, visible damage, finish expectations, turnover goals, and staging limits. Specific field information is more useful in review than broad service shorthand on its own.
Project details to include
Use these prompts to keep the request specific to the space under review before any proposal turns it into included work.
A short request is fine when it still says what is known, what is changing, and what remains unresolved. The goal is not to overwhelm the page with filler but to make sure the next reviewer can understand the project without inventing the missing pieces.
Good prompts also make later proposal review easier. If the request already separates conditions, materials, access limits, and open questions, the written scope can track those same categories instead of rebuilding the conversation from memory.
Project contact details
Keep the request focused on the current condition, intended result, occupancy, access limits, and available project materials.
The page avoids publishing a phone number, address, hours, or response promise that has not been provided as a source-backed fact.
Those details belong in the project conversation when they are relevant to the individual request.
The same project prompts continue to support a clear written proposal when the contact workflow is activated in a later phase.
How the review packet should read
Start with the space and the requested result. The first reader should understand what area is under review and what change is being discussed before they have to interpret photos, plans, or supporting notes.
Then add the operating conditions that can shape the work, such as occupancy, access restrictions, sequencing concerns, work-hour limits, or property rules. These conditions often define the proposal more than the service label itself.
Finally, separate the supporting materials and the remaining questions. That structure helps the project conversation stay readable when the request moves from owner or tenant notes into a written proposal under formal review.
01
Explain the current condition of the space and the result you need.
Use the project form02
Plans, photos, site access details, and known property requirements can support review.
Review what to provide03
Share current conditions, intended results, and available project information.
Share project detailsProject questions
Share the current condition, intended result, occupied or vacant status, and any available plans or photographs.