Request for Information Preparation
Prepare a design clarification request with four clear parts: location and reference, observed ambiguity, options and impact, and the decision needed. A worked ceiling-services example shows field engineers and trade leads how to frame the question and hand it off through the authorized project route.
Every employee gets a seat — priced per employee in Communications & Intranet, quoted with this template ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
Built for: Commercial construction · Mixed-use development · Building services and MEP coordination · Property operations
Overview
Request for Information Preparation is a procedure page for field engineers and trade leads who need to turn an unclear design reference into a focused clarification request. It opens with scope guidance, distinguishes design clarification from IT support and broader project escalation, and sets out a four-part structure: location and reference, observed ambiguity, options and impact, and decision needed. The worked North Quay example applies that structure to a possible conflict between a ceiling zone, duct route, and service access panel. It is explicitly illustrative, not approved design direction or a project record.
Use the page when a drawing, specification, schedule, or detail is unclear or appears inconsistent and the authorized project team needs to confirm or select an arrangement. The examples ask requesters to identify the location and document revision, state what they observed without guessing at intent, describe plausible options and practical coordination effects, and ask one direct question. The embedded form is a handoff point, but its destination and workflow must be configured for the organization’s authorized process. The page names the project or property operations owner as the route for help when submission or routing is unclear.
Do not use this page as a substitute for approved project information, design or operational approval, IT support, or general escalation. It does not set response times, establish decision authority, or define regulatory requirements. Before publishing, confirm the form setup and help route, and keep sensitive, regulated, or safety-critical matters within their applicable approved processes.
Standards & compliance context
- Treat this page as a request-writing aid, not as design approval, code interpretation, construction instruction, or a replacement for approved project information.
- For regulated, safety-critical, or otherwise sensitive questions, follow the applicable approved local process and consult the responsible domain owner.
- Configure and verify the embedded form through the organization’s supported setup mechanism; the template does not specify a connected system, access model, or approval workflow.
- Keep headings descriptive and page content readable with assistive technology, and verify the published page against WCAG 2.1 AA accessibility expectations.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Prepare a clear design clarification request
Use this page to frame a design question for the authorized project team, not to request IT support or general escalation.
-
For this fictional example, North Quay is a mixed-use construction project. Use the four-part structure below to help the authorized project team understand where the question applies, what is unclear, what options affect the work, and what decision is needed. This page is for design clarification—not IT support or general project escalation.
Choose the right kind of request
Check that the issue is a design clarification before using this structure, and route other concerns through their established channels.
-
Start with the issue you need resolved. Clarify a design reference Use this structure when a drawing, specification, schedule, or detail is ambiguous or appears inconsistent. Name the exact location and reference. Describe what you observed without guessing at intent. Resolve a coordination choice Use it when more than one design interpretation appears possible and the project team needs to select or confirm an option. State the options you can identify. Describe the work-coordination impact of each. Route a different issue IT access problems belong with the organization’s IT support route. Broader project escalation belongs with the project’s designated escalation process. Do not use a design clarification request as a substitute for those routes. If unsure, ask the project or property operations owner which authorized route applies.
Build the request in four parts
Capture the location, observed ambiguity, options and impacts, and the specific decision needed.
-
Keep each part specific enough for someone who was not at the workface to understand. Location and reference Identify the building or area, level, grid or room where applicable, and the exact drawing, specification, schedule, or detail reference and revision available to you. Observed ambiguity Describe what the reference shows and what is unclear or appears inconsistent. Separate what you observed from your interpretation. Options and impact List the plausible options you can identify and the practical coordination impact of each, such as an interface, sequence, access, or rework consideration. Do not present an option as approved. Decision needed Ask one direct question. State what needs to be confirmed or selected so the authorized design or project role can respond.
Worked example: ceiling service route at North Quay
See how a fictional coordination issue can be described clearly without presenting a possible arrangement as approved.
-
Illustrative coordination example—not an approved design, instruction, or project record. Location and reference North Quay, Block B, Level 03, west corridor between grids 4–6. Architectural reflected ceiling plan A-231, revision C, and mechanical services plan M-118, revision B. Observed ambiguity At the west corridor crossing, the architectural plan shows a continuous ceiling zone. The mechanical plan appears to route a duct through the same zone as the ceiling service access panel. The references do not make the intended arrangement clear. Options and impact Option A: Keep the duct route shown and shift the access panel within the ceiling zone. This may require the relevant design roles to confirm the panel remains coordinated with the affected services. Option B: Review an adjusted duct route at the crossing. This may affect coordination with adjacent services and the planned installation sequence. Decision needed Please confirm whether Option A is acceptable, or provide a coordinated alternative for the duct and access-panel arrangement at this location. Which reference or revised detail should the trade team use for coordination? Keep the request focused on the ambiguity and coordination decision. Do not treat this example as project direction; follow the authorized project process and applicable approved information.
Send the request through the authorized process
Submit using the project’s configured route and verify the form destination before relying on it.
Handoff and help
Use the established project channel to ask the project or property operations owner about routing or sensitive matters.
-
Use the project’s authorized request route for submission. If the submission form is not available to you, or you are unsure which process applies, contact the project or property operations owner through the established project channel. That owner can clarify routing and the appropriate design or project role for the question. Keep sensitive project information in the system authorized for it. For regulated, safety-critical, or otherwise sensitive matters, use the applicable approved local process and consult the responsible domain owner; this page does not establish policy or provide operational approval.
Project and property operations contacts
The project or property operations owner can clarify the authorized route and help direct the question to the appropriate project role.
-
Clarifies the authorized request route and helps direct the question to the appropriate project role. Project or Property Operations Owner Project and Property Operations
How to use this template
- Confirm the project’s authorized request route, the appropriate project or property operations owner, and the form destination before publishing the page.
- Replace or retain the clearly fictional North Quay example as appropriate, ensuring any project-specific example is approved for publication and is not mistaken for direction.
- When preparing a request, record the exact work location and the drawing, specification, schedule, or detail reference and revision available to you.
- Describe the observed ambiguity, list plausible options with their coordination impacts, and ask one direct question without labeling an option as approved.
- Submit through the authorized project route and use the established project channel to ask the operations owner for routing help if the form or recipient is unclear.
- Use the response and any revised or confirmed reference provided through the authorized process, and raise unresolved or sensitive matters through the applicable project route.
Best practices
- Include the building or area, level, grid or room where applicable, and the exact reference revision so the issue can be located and checked.
- Separate what the drawing or site condition shows from your interpretation of what it means.
- Ask one decision question per request and identify what confirmation or coordinated alternative is needed.
- Describe each plausible option’s practical interface, access, sequence, or rework impact without recommending it as approved direction.
- Use the worked example to understand the structure, but do not copy its fictional project references into a live request.
- Keep sensitive project details in the system authorized to hold them and follow the applicable local process for regulated or safety-critical matters.
- If you cannot identify the authorized route, ask the project or property operations owner through the established project channel rather than inventing a recipient.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
When should I use this design clarification request structure?
Use it when a drawing, specification, schedule, or detail is ambiguous or appears inconsistent, and the project team needs to confirm the intended arrangement. It is designed for design clarification and work coordination questions. It is not for IT support or general project escalation.
What information should I include in the request?
Identify the building or area, level, grid or room where applicable, and the exact reference and revision available to you. Describe what you observed separately from your interpretation, list plausible options and their practical coordination impacts, then ask one direct question. The North Quay example demonstrates how those four parts work together.
Who submits the request and who decides the answer?
The field engineer or trade lead preparing the question should use the project’s authorized request route. The appropriate design or project role provides the response through the applicable project process; this page does not assign approval authority. If the route or recipient is unclear, ask the project or property operations owner through the established project channel.
How quickly should I submit a request, and how often should I check it?
This page does not set a submission deadline or response cadence. Follow the project’s established process and raise timing concerns through its designated route. Include relevant location, references, revisions, and coordination impacts so the question can be understood without relying on an informal site conversation.
Does this template establish regulatory or safety approval?
No. It is a communication aid, not a code interpretation, design approval, or operational instruction. For regulated, safety-critical, or sensitive matters, follow the approved local process and consult the responsible domain owner. Use only approved project information for work decisions.
What are common mistakes when preparing a design clarification?
Common pitfalls include citing a drawing without its revision, mixing observed facts with assumptions, asking several unrelated questions at once, and presenting a possible option as already approved. Another mistake is using this route for IT access or broader project escalation. The four-part structure and routing guidance help keep the question specific and directed appropriately.
Can we customize the page for our project?
Yes. Replace the fictional North Quay example with a clearly identified example suited to your project, and update the submission route and help ownership only after confirming them. Preserve the distinction between observed conditions, possible options, and authorized decisions. Do not imply that sample details are approved project direction.
Does the embedded form connect to a particular system or approval workflow?
The page includes a form embed, but the supplied template does not identify its system, data fields, integrations, or approval workflow. Configure the embed through your site’s supported form setup and connect it only to the authorized project request route. Verify access and handling requirements with the responsible owner before publishing.
How is this better than sending an informal message?
The structure prompts the requester to provide a precise location and reference, describe the ambiguity, explain coordination implications, and ask for a decision. That gives someone who was not at the workface enough context to understand the issue. Informal discussion may help identify a question, but the authorized project process remains the submission and decision route.
Related templates
Go deeper on the topic
-
A modern intranet is a specific surface — typically the home-base destination where employees get company news, find policies, and access key apps. A digital...
Ready to use this template?
Every employee gets a seat. Request pricing for Communications & Intranet and we quote into a workspace with Request for Information Preparation ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
