Identifying Survey Requests Made by Each Team
To avoid confusion and ensure efficient workflow, it's essential to maintain a clear record of survey requests made by each team involved in development transactions.

This article is sponsored by Aurum Title. Partner content policy
In this article
A Las Colinas development can produce several survey requests before anyone checks how they relate. The owner needs to understand the land in a transaction. An engineer needs reliable information for design. A title reviewer may want to connect a survey to particular recorded documents. Gather each question and intended use before asking a surveyor to confirm what work and deliverables are appropriate.
Give the request log a current property reference and working plan. Include the person asking the question, the responsible reviewer and the date an answer will be needed. When two groups appear to be requesting the same work, compare the deliverables each wants and how they will use them. A surveyor can then explain what the proposed scope will cover.
Find the land each request actually covers
Ask each team to identify the part of the property behind its question. Early site descriptions may use an overall project name for more than one tract. A title request may refer to one transaction, while a construction or access question could concern a wider area. Keep the relevant exhibits, descriptions and current plan associated with their proper requests.
If the team has already retrieved a survey or earlier site plan, record the source, date and purpose. A plan that shows the site broadly can help the owner explain what it hopes to build. An older survey may have specific observations or references worth discussing. Give the surveyor the full copies where appropriate and ask which matters it can evaluate from them.
For example, imagine an owner preparing to buy one part of a site with an existing shared entry. The design team also asks for information about a grade change across an adjoining area, and the title contact wants to locate information from an access instrument. Give both areas clear references and ask what work can be coordinated. The legal and survey reviewers should know which request concerns a particular document and which concerns existing physical conditions.
Record the question instead of copying a general request
Ask why the team needs the work. A designer may be checking how existing features relate to a proposed connection. An acquisitions team may need information for an upcoming review. A title or lender contact may have a written requirement. Keep those descriptions with the requests so that a person can respond to the intended task.
Aurum Title’s developer services describe its work on acquisitions, plats, easements and closing coordination. When sharing material with the title team, ask which documents it will use and whether a stated survey request comes from its own review, the lender or another party. Give it the details relevant to that transaction and preserve the source of any requested change.
The Texas Department of Insurance’s title FAQ discusses commitment and policy documents and comparing a legal description with a survey. Let the title team or counsel address a transaction question. Ask the surveyor what its work is able to show and which references it needs in order to prepare the appropriate materials.
Compare professional scopes before combining requests
The Texas Board of Professional Engineers and Land Surveyors’ rules handbook includes provisions covering survey drawings and their record references. Ask the responsible professional how to define the work for your site. Bring existing drawings and copies of relevant instruments. Some requests may draw on the same field work and still need different deliverables or approvals.
An engineer preparing a site layout may want information about surface features in a defined area. A title reviewer considering an instrument may want to see a relationship shown or explained in the survey. Let both groups state the use they expect. Ask whether the surveyor can describe their needs in a coordinated scope without assuming one package will automatically satisfy everyone.
If someone has already requested similar work, confirm what was actually commissioned and who is responsible for it. Compare the limits and dates on the two requests. Ask whether the other team will receive a copy and what its reviewer will need to confirm. Do not merge requests solely because they use the same street address or project name.
Give city submissions their own timetable and source
The City of Irving’s planning applications and forms page includes information on site plans and plats. The city’s pre-plat civil review page describes its process for reviewing civil engineering plans before platting. Ask the designated project lead to confirm which requirements apply to the site and what material it needs for each municipal stage.
When a city question refers to a certain plan or note, record the application reference and the date of the document. A survey task serving early design discussions may involve a different timetable from an item for a city submission. Identify the person who will receive the survey deliverable and confirm whether it addresses the actual review request.
If the proposed work changes after a city meeting, ask which features should be checked again before circulating the next plan. Ensure each team has the drawing version it needs and the context of the change. Give the surveyor the actual questions raised by the revision instead of relying on a general request for an update.
Keep title, design and construction questions traceable
For a title-related request, include the instrument or exhibit reference and state which reviewer identified it. Ask that person what information it wants the surveyor to consider. For design or construction, include the current drawing and name the feature involved. Give the field or design contact room to explain whether a different part of the site is involved than the transaction contact initially expected.
Check access before confirming work dates. A site manager or owner representative may need to approve a time or route. Record the areas the authorized team is expected to reach and any practical limitations. If more than one group is arranging entry, assign one contact to confirm the actual plan and tell each team when it can rely on that confirmation.
When a relevant document is incomplete, ask who will obtain the remaining pages or a copy from the intended source. Mark this fact in the request and indicate whether another task depends on it. When the missing source arrives, send it to the appropriate reviewer and identify which request prompted it. This helps the project avoid chasing another copy after the scope has already been updated.
Resolve changed requests before they reach the field team
Ask who can authorize additions once the professional has proposed a scope. A staff member may want another observation after seeing a design update. Give them a place to explain why the question arose, identify the drawing and say which date matters. The project lead can then obtain the appropriate review before the added work becomes an unplanned assumption in the schedule.
For a request involving adjoining land or public areas, give the surveyor the relevant limits and the person who can explain the project’s access arrangement. Ask whether the desired information requires another record, a different field visit or a change to the professional scope. Capture what was agreed rather than adding a brief instruction to a message the original field team may never receive.
If an early drawing already went to a title or lender contact, tell them which new question has been added and how it might affect the work they expect to receive. They may need to check a portion separately or wait for another file. The coordinator can record who has the latest proposed scope and when the next update should be sent.
Use the same process if a requested item is no longer needed. Ask the original requester to confirm what changed and whether any work has already been performed for that item. The person managing the order can determine how to record the change and who needs to revise the work schedule. Save an earlier copy if it explains why an expected deliverable has disappeared from the updated list.
For changes discovered during a visit, bring the reported condition to the relevant reviewer and ask what it means for the current request. Note who saw the condition and when. Update the requested deliverable after the surveyor and relevant team have confirmed the change. A clear record helps everyone distinguish a field observation from a decision about the work under review.
Review the proposed deliverables with each request owner
Ask the surveyor to identify the scope, expected dates and deliverables it proposes. Give each initiating team a chance to check what the proposed work will answer. If a recipient expects a different document or information for a later decision, ask it to explain the specific need and when it arises. Keep the agreed changes in the request log.
After delivery, have the requester locate the answer to their own task. For an issue still open, record what information is missing and who can provide it. If a revised drawing arrives, tell the people who relied on earlier copies what has changed and when they need to review it. Save the confirmed scope alongside the work received.
Our partner guides cover related North Texas development topics. Keep each request tied to the actual land, purpose and recipient. Ask whether the professional’s proposed work addresses those uses before the teams rely on a shared survey date or expect the same documents.
Visit Aurum Title.
Sources
- Aurum Title’s developer servicesaurumtitle.com
- Texas Department of Insurance’s title FAQtdi.texas.gov
- Texas Board of Professional Engineers and Land Surveyors’ rules handbookpels.texas.gov
- City of Irving’s planning applications and forms pageirvingtx.gov
- pre-plat civil review pageirvingtx.gov
