How to Use Notion for a Land Surveying Company: Jobs and Reports

{/ synced-from-notion — do not edit manually /}

A land surveying job is a long chain of small, dependent steps.

Someone researches the deeds and the prior surveys. A crew needs access to the property, a utility locate that hasn’t expired, and weather that cooperates. Field data comes back to the office, where it’s processed, drafted, checked, reviewed, and signed by the licensed surveyor.

Then it’s delivered, sometimes recorded, and invoiced. A delay at any link, such as a locate that lapsed, an instrument that’s due for calibration, or a plat waiting on a reviewer who’s in the field, can stall the job and the client.

Most small firms hold this in a whiteboard, an email inbox, and the memory of whoever is running the job, and the cost shows up as late deliveries, rework, and invoices that go out weeks after the work.

Notion can hold the management layer in one place.

This guide is for owner-surveyors, party chiefs, drafters, and small land surveying firms. It follows a job from the first inquiry to the final invoice. It shows how to set up clients, jobs, fieldwork, deliverables, resources, and invoices, how to track each job through its stages, how to run a review checklist before anything leaves the office, and how to turn records into PDFs such as job sheets, transmittals, and status reports. It also covers safety and confidentiality.

It is general information about organizing a business, not to be considered any legal, professional, or regulatory advice.

Land surveying is a licensed profession in most places, with rules on who may sign and seal work, standards for the work itself, record retention, insurance, and liability, so check what applies to you.

An important boundary comes first.

Notion is not survey software, a CAD program, or a records archive. It doesn’t compute closures, draw plats, or hold raw data, and it can’t sign or seal anything.

The professional work, and the signature and seal of the licensed surveyor, happen in your survey and CAD tools and in your approved process. Notion tracks the jobs, the dates, the people, the checklists, and the links to the files.

Short answer on how to use Notion for land surveying:

To use Notion for a land surveying company, create linked databases for Clients, Jobs, Fieldwork, Deliverables, Resources, and Invoices.

Give every job a stage, from research to delivery, and use formulas to show how long it has been in that stage and when it’s stuck. Schedule fieldwork with its access, utility locate, and weather status, and track instruments and licenses so nothing lapses.

Run every deliverable through a review checklist, record the date it was sealed and delivered in your approved process, and link to the files in secure storage. Put the key facts in report-ready fields, so a job sheet or a transmittal PDF takes minutes.

Notion works well for surveying firms because the work is a pipeline with clear stages and dates.

A job has fieldwork visits and deliverables, each deliverable has a reviewer and a due date, and each job has a fee estimate and a budget of hours. A formula counts days in the current stage and flags jobs that are stuck, another compares the estimated fee with the hours used, and another turns a calibration date and an interval into the next due date.

Notion isn’t survey or CAD software, a document archive, a time tracking tool, or an accounting system. It doesn’t send reminders by itself, so it works best beside your survey software, your file storage, your calendar, and your accounting tool. For documents that leave the office, such as transmittals and status reports, you can export a page as a PDF or generate one from a template.

Table of Contents

What Notion Can and Can’t Do for a Land Surveying Company

Professional Responsibility, Confidentiality, and Safety

The Six Databases

Clients and Inquiries

Jobs: Stages From Authorization to Delivery

Fee Estimates and Budgets

Fieldwork: Access, Locates, and Weather

Deliverables and the Review Checklist

Resources: People, Instruments, and Vehicles

Invoices and Payments

Your Business Numbers

A Tuesday for a Small Surveying Company

The Documents That Leave Notion

Generating PDFs with PDFOutput

Who Can See What

Common Mistakes

Frequently Asked Questions

Related Reading

Conclusion

What Notion Can and Can’t Do for a Land Surveying Company

Notion is good for:

• Tracking inquiries, proposals, and authorized jobs.
• Moving each job through stages, with dates and owners.
• Scheduling fieldwork, and recording access, locate, and weather status.
• Tracking deliverables, reviews, and delivery dates.
• Tracking instruments, calibration dates, licenses, and training.
• Tracking fee estimates, hours used, and invoices.
• Creating consistent job sheets, transmittals, and status reports.

Notion is not made for:

• Survey computations, CAD drafting, or point cloud and raw data storage.
• Signing or sealing survey products.
• Time tracking and payroll.
• Taking payments or full accounting.
• Acting as the official record archive.

If you already use survey software, CAD, a file server or cloud storage, and accounting software, treat Notion as the coordination layer beside them. Link to the files and records by path, and don’t copy survey data into Notion.

Professional Responsibility, Confidentiality, and Safety

A surveying firm’s work has legal weight, and its crews work outdoors on other people’s land. A few habits protect the firm, the clients, and the people.

• Keep the licensed surveyor in charge of the work. Rules usually require that a licensed surveyor is responsible for, and signs and seals, survey products. Notion can show who is assigned and whether review is complete, but it can’t replace the professional’s judgment or signature. Record the date the product was signed and sealed in your approved process, and don’t treat a status in Notion as the seal.
• Know your record rules. Many places require firms to keep field notes, calculations, and drawings for a set number of years, and sometimes to file or record certain surveys. Find out what applies to you, and keep the originals in a system that meets the rules. Notion should point to them.
• Keep files out of Notion. Raw data, CAD files, point clouds, photos, title documents, and sealed PDFs belong in secure file storage with proper backup and access control. Link to them from the job.
• Protect client confidentiality. A client’s plans for a site, financing details, and ownership matters are often sensitive, even though deeds are public. Restrict who can see each job, and don’t discuss one client’s work in a shared view with another’s.
• Respect property access rules. Rules on entering private land, notifying owners, and working near boundaries vary. Record that permission or notice has been given, and follow the law.
• Follow utility locate rules. Many places require contacting a locate service before digging or driving stakes, and locate tickets expire. Record the ticket and its expiry date in Notion, and follow the rules and the locate service’s instructions.
• Plan for field safety. Crews face traffic, terrain, heat, cold, wildlife, and lone working. Record the hazards, the check-in plan, and who knows where the crew is, and follow your safety policy and any required job hazard analysis.
• Never store access codes or keys. If a site needs a gate code or a key arrangement, share it by phone or a secure method, and keep only a note such as “Access arranged with owner” in Notion.
• Think about liability. Scope, standard of care, limits of liability, and who may rely on a survey are handled in your contract and insurance. Have your agreement reviewed by an attorney, and tell your insurer what you need to.

Rules differ by country, state, and profession, so check what applies to you. While you are testing, use made-up clients and made-up jobs.

Use These 6 Databases

Start with these six. You can add more later, such as Equipment Checkouts, Monuments, or Subcontractors.

• Clients stores who you work for. Add these properties: Name, Company, Type (Homeowner, Developer, Builder, Lender, Attorney, Government, or Other), Contact Person, Phone, Email, Source, Notes, and a Jobs relation.
• Jobs is the main database. Add: Job Number, Job Name, Client (relation), Type (Boundary, Topographic, Construction Staking, Subdivision, As-Built, Elevation, or Other), Site Address or Parcel Reference, Status (Inquiry, Proposal Sent, Authorized, Research, Fieldwork, Drafting, QC Review, Surveyor Review, Delivered, Recorded, or Closed), Stage Entered (a date), Days in Stage (a formula), Stuck Flag (a formula), Authorized On, Delivered On, Turnaround (a formula), Surveyor in Charge (relation), Party Chief (relation), Fee Estimate (a formula), Research Hours, Field Hours, Drafting Hours, Review Hours, Office Rate, Crew Rate, Principal Rate, Expenses, Budget Hours (a formula), Hours Logged (a formula), Budget Flag (a formula), Billed Total (a rollup), Paid Total (a rollup), and Notes.
• Fieldwork stores each visit. Add: Job (relation), Date, Crew (relation to Resources), Instruments (relation to Resources), Status (Scheduled, Completed, Weather Delay, Access Problem, or Needs Return Visit), Hours, Access Permission (a checkbox), Locate Ticket Reference, Locate Expires, Locate Flag (a formula), Hazards and Check-In Plan, Field Notes Link, Data Link, and Return Visit Needed (a checkbox).
• Deliverables stores each product. Add: Job (relation), Type (Boundary Plat, Topographic Map, Legal Description, Elevation Certificate, Staking Report, CAD Files, or Technical Report), Stage (Drafting, QC Review, Surveyor Review, Ready for Seal, Delivered, or Recorded), Drafted By, Reviewer, Due Date, Revision Number, Sealed On (a date, recorded from your approved process), Delivered On, Recording Reference, File Link, Overdue Flag (a formula), and the review checklist boxes.
• Resources stores your people, instruments, and vehicles. Add: Name, Type (Surveyor, Crew Member, Drafter, Instrument, or Vehicle), License or Serial Number, Status (Available, In Field, In Repair, or Out for Calibration), License or Insurance Expiry, Last Calibration, Calibration Interval (months), Next Calibration Due (a formula), and Renewal Flag (a formula).
• Invoices stores billing. Add: Job (relation), Type (Retainer, Progress, Final, or Change Order), Amount, Issued On, Due Date, Paid On, Status (Draft, Sent, Paid, or Late), Paid Amount (a formula), and Late Flag (a formula).

A relation connects a record in one database to a record in another. Link Jobs to Clients, link Fieldwork, Deliverables, and Invoices to Jobs, and link Fieldwork to the crew and instruments in Resources. Now a job’s page shows its client, its stage, its field visits, its deliverables, and its invoices together.

Clients and Inquiries

Most jobs begin with a call or an email asking for a price. A consistent first step makes the proposal faster and the scope clearer.

When an inquiry arrives, create a Job with the status Inquiry, and a Client if they’re new. Collect the same details each time: the site address or parcel reference, what the client needs the survey for (a purchase, a fence, a permit, a subdivision), any deadline, who the contact is, and what documents they have, such as a deed, a previous survey, or a title commitment. The purpose matters, because it sets the type of survey and the standards to follow, and the licensed surveyor decides what’s appropriate.

Before you quote, check the research that affects the fee: whether prior surveys exist, how complicated the title is, how hard the site is to reach, and whether utilities or easements are likely to matter. Keep notes short, and link to documents in storage.

Make these views of Jobs:

• Pipeline: a board grouped by Status, from Inquiry to Closed.
• Proposals to follow up: jobs with the status Proposal Sent, sorted by how long ago they were sent.
• By client: all jobs for one client, for repeat work and relationships.

A short, prompt proposal, with a clear scope and what’s excluded, is often what wins the job.

Jobs: Stages From Authorization to Delivery

The most useful thing a job record does is answer “where is this, and who’s waiting on whom?” in a few seconds.

Use one Status property for the stages, and a date for when the job entered the current stage:

• Inquiry and Proposal Sent: before the client agrees
• Authorized: a signed agreement and any retainer received, in your approved process
• Research: deeds, prior surveys, title documents, and records gathered
• Fieldwork: access, locates, and the visits themselves
• Drafting: processing, calculations, and drawing
• QC Review: a second person checks the work against a checklist
• Surveyor Review: the licensed surveyor in charge reviews, and signs and seals in your approved process
• Delivered: the product has gone to the client
• Recorded: filed or recorded, if required
• Closed: invoiced, paid, and archived

When a job moves to a new stage, update the status and set Stage Entered to today. A Notion database automation can do this for you, so the date is always right. Then add:

`` Days in Stage: dateBetween(now(), prop("Stage Entered"), "days")

Stuck Flag: if(or(prop("Status") == "Delivered", prop("Status") == "Recorded", prop("Status") == "Closed", prop("Status") == "Inquiry", prop("Status") == "Proposal Sent"), "", ifs( prop("Status") == "Authorized" and prop("Days in Stage") > 3, "Stuck: start research", prop("Status") == "Research" and prop("Days in Stage") > 7, "Stuck: research", prop("Status") == "Fieldwork" and prop("Days in Stage") > 14, "Stuck: fieldwork", prop("Status") == "Drafting" and prop("Days in Stage") > 10, "Stuck: drafting", prop("Status") == "QC Review" and prop("Days in Stage") > 3, "Stuck: QC review", prop("Status") == "Surveyor Review" and prop("Days in Stage") > 3, "Stuck: surveyor review", "" )) `

The numbers are examples. Use limits that match your firm’s real pace, and your commitments to clients. The flag tells you where jobs wait, and it’s often the queue at one person, or at one step such as access or review, that needs attention.

For turnaround, record the date a job is authorized and the date it’s delivered, then add:

` Turnaround: dateBetween(prop("Delivered On"), prop("Authorized On"), "days") `

Make these views of Jobs:

• Stuck: jobs with the flag, grouped by stage.
• By person: jobs grouped by party chief or drafter, to balance workload.
• Needs review: jobs in QC Review or Surveyor Review, sorted by days in stage.
• Ready to invoice: jobs with the status Delivered and no final invoice.

> 💡 Pro Tip: Add a “waiting on” property to each job, with options such as Client, Title Company, Utility Locate, Weather, Crew, Drafter, and Reviewer. Grouping the Stuck view by it shows at a glance whether delays are on your side or someone else’s.

Fee Estimates and Budgets

A clear estimate protects the firm’s margin and the client’s expectations. Build it from the same inputs each time, so two people give the same price for the same job.

Break the work into research, field, drafting, and review hours, and apply your rates to each. On Jobs, add:

` Fee Estimate: prop("Research Hours") prop("Office Rate") + prop("Field Hours") prop("Crew Rate") + prop("Drafting Hours") prop("Office Rate") + prop("Review Hours") prop("Principal Rate") + prop("Expenses")

Budget Hours: prop("Research Hours") + prop("Field Hours") + prop("Drafting Hours") + prop("Review Hours") `

Here is a made-up boundary survey of a residential lot. Amounts are in your own currency, and the hours and rates are examples.

Item	Value
Research	3 hours at 95 = 285
Fieldwork (two-person crew)	4 hours at 160 = 640
Drafting	6 hours at 95 = 570
Review and seal	1.5 hours at 140 = 210
Expenses (monuments, records, mileage)	75
Fee estimate	1,780
Retainer at 50%	890
Budget hours	14.5

Many firms quote a fixed fee based on an estimate like this, and others bill hourly with a cap. Whichever you use, state the scope, the assumptions, and what’s excluded, and what happens if conditions differ, such as heavy vegetation, missing records, or extra monuments to find. A change order, recorded as an Invoice of the type Change Order, keeps extra work from becoming a dispute.

To watch the budget, roll up the crew hours from Fieldwork, add the office hours logged in your time tracking tool, and add:

` Hours Logged: prop("Field Hours Logged") + prop("Office Hours Logged")

Budget Flag: if(prop("Hours Logged") > prop("Budget Hours"), "Over budget", if(prop("Hours Logged") > prop("Budget Hours") * 0.9, "Near budget", "")) `

The flag shows jobs approaching or over their hours. Talk to the client early about changes, and learn from the overruns, because they tell you where your estimates are too low.

Fieldwork: Access, Locates, and Weather

Fieldwork is the most expensive hour in the business and the most exposed to delays. A good record makes sure the crew arrives ready, and that a wasted trip is rare.

Create a Fieldwork record for every visit, with the job, the date, the crew, and the instruments. Before the visit, check three things: you have permission to enter, any utility locate is valid, and the weather and the site conditions suit the work.

Record the locate ticket reference and its expiry date, as your rules require, then add:

` Locate Flag: if(and(prop("Status") == "Scheduled", dateBetween(prop("Locate Expires"), prop("Date"), "days") < 1), "Locate expires before visit", "") `

The flag shows scheduled visits where the locate runs out on or before the visit day. Locate rules and validity periods vary, so use the ones that apply to you. Don’t set stakes or dig unless your rules say you may.

Use a Fieldwork template as a checklist:

• [ ] Job number, site, and purpose confirmed
• [ ] Owner permission or notice recorded, as required
• [ ] Locate ticket valid for the visit date
• [ ] Hazards noted, and a check-in plan agreed
• [ ] Instruments checked and charged, with calibration in date
• [ ] Records and control information loaded in the field software
• [ ] Weather and daylight reviewed
• [ ] Vehicle ready, with safety equipment and first aid
• [ ] After the visit: data backed up, field notes scanned or linked, status updated
• [ ] Return visit needed, and why

Use the statuses Weather Delay, Access Problem, and Needs Return Visit, with a short reason, so you can see why visits slip, and so you can tell the client honestly. When a visit is complete, link to the field notes and the data in secure storage, and set the job to the next stage.

Make these views of Fieldwork:

• This week: a calendar view, grouped by crew.
• Needs attention: visits with the locate flag, or the status Weather Delay or Access Problem.
• Return visits: visits that needed a return, grouped by job, to see why.

Deliverables and the Review Checklist

The product leaves the office only after it’s been checked. A consistent review catches errors before the client, the title company, or a neighbor’s surveyor does.

Create a Deliverable record for each product on a job, with the type, the person drafting, the person reviewing, and the due date. Move it through the stages: Drafting, QC Review, Surveyor Review, Ready for Seal, Delivered, and Recorded.

Build a QC Review checklist with your own standards, such as:

• [ ] Field data and notes match the drawing
• [ ] Closure and computations reviewed
• [ ] Bearings and distances compared with the record calls, and differences explained
• [ ] Monuments found and set are shown correctly
• [ ] Easements, rights-of-way, and encroachments plotted and noted
• [ ] Items from the title documents addressed
• [ ] Legal description checked against the drawing
• [ ] Names, parcel numbers, dates, scale, and north arrow correct
• [ ] Required notes, certifications, and standards statements present
• [ ] Spelling, formatting, and file naming checked

The second person ticks the boxes and signs off in the record, and the licensed surveyor does their own review. The licensed surveyor signs and seals in your approved process, and you record the date in Sealed On. Never mark a deliverable as sealed in Notion unless it has been done in your official process.

Add an overdue flag:

` Overdue Flag: if(and(prop("Stage") != "Delivered", prop("Stage") != "Recorded", dateBetween(now(), prop("Due Date"), "days") > 0), "Overdue", "") `

Track revisions with a number, and note what changed and why. If a client asks for changes after delivery, check whether they’re corrections or new scope, and use a change order for new scope.

For deliverables that must be filed or recorded, record the recording reference and date once it’s done, as the authority requires. Keep the final sealed files in your records system, and link to them.

Make these views of Deliverables:

• Review queue: deliverables in QC Review or Surveyor Review, by due date.
• Overdue: deliverables with the flag.
• Awaiting recording: deliverables that must be filed and haven’t been.
• By reviewer: deliverables grouped by reviewer, so the queue is fair.

Resources: People, Instruments, and Vehicles

Surveying depends on calibrated instruments, valid licenses, and reliable vehicles. A lapse in any of them can invalidate work or stop a crew.

In Resources, record each licensed surveyor’s license and its expiry, and each person’s insurance, safety training, and continuing education dates, as your rules require. For each instrument, such as a total station, a GNSS receiver, or a level, record the serial number, the date of the last calibration or check, and the interval. Then add:

` Next Calibration Due: dateAdd(prop("Last Calibration"), prop("Calibration Interval"), "months")

Renewal Flag: if(dateBetween(prop("Next Calibration Due"), now(), "days") <= 30, "Calibration due", if(dateBetween(prop("License or Insurance Expiry"), now(), "days") <= 60, "Renewal due", "")) `

The flag shows instruments due for calibration within 30 days, and licenses or insurance expiring within 60. The intervals and the checks required depend on the instrument, the manufacturer, your standards, and your rules, so use the ones that apply to you. Keep the calibration certificates and check records in your records system, and link to them. A documented calibration history is also useful evidence if a survey is ever questioned.

Set an instrument’s status to In Field, In Repair, or Out for Calibration, so you know what’s available when you schedule a crew. If a job needs a particular instrument, such as a GNSS rover, check it’s available before you commit to a date.

Make these views of Resources:

• Needs attention: anything with a flag.
• Instruments: all instruments with status and next calibration.
• Licenses and training: people with their expiry dates.

Invoices and Payments

Surveying firms often bill in stages: a retainer when the job is authorized, and the balance on delivery. Write the terms in your agreement, and use Notion to track them.

For each job, create Invoice records for each billing, with a type, an amount, and a due date. Notion can’t sum only the paid invoices with a plain rollup, so use a helper formula on Invoices:

` Paid Amount: if(prop("Status") == "Paid", prop("Amount"), 0) `

Roll up Paid Amount on Jobs as Paid Total, and the invoice amounts as Billed Total. Add a late flag on Invoices:

` Late Flag: if(and(prop("Status") == "Sent", dateBetween(now(), prop("Due Date"), "days") > 0), "Late", "") `

A view called Invoices due shows what’s coming and what’s late. Payments and the formal accounts happen in your accounting tool, and you update the status in Notion when the money arrives. Check your agreement before you withhold a deliverable for non-payment, and be careful, because rules and contracts differ. Be clear and polite in reminders. A Ready to invoice view, with delivered jobs and no final invoice, catches the most common leak in a small firm: work finished and not billed. Tax rules differ by country, so check what applies to you. Notion Receipt Template shows how to structure a receipt.

Your Business Numbers

A surveying firm has a few numbers worth watching. Here is a made-up quarter.

Item	Value
Jobs delivered	30
Average fee	1,780
Billed	53,400
Collected	50,730
Collection rate	95%
Average turnaround	18 days
Delivered on or before the due date	24 of 30
On-time rate	80%
Estimated hours	300
Actual hours	330
Hours vs estimate	110%
Field visits	40
Return visits	5
Return visit rate	12.5%

To count these, make grouped views with a count or a sum in each group: jobs by delivery month, deliverables by whether they were on time, and fieldwork by whether a return was needed.

Divide collected by billed for the collection rate, on-time deliveries by total for the on-time rate, and actual hours by estimated hours to see how your estimates perform.

A high return visit rate often points to access, locate, or research problems you can fix before the crew goes out. Consistent overruns point to estimates that are too low for certain job types.

Also watch the time jobs spend in each stage, the number of jobs per person, proposal conversion, and where clients come from. A small sample can mislead, so treat these as guides. They leave out wages, equipment, insurance, vehicles, software, and tax, so check the full figures with an accountant. Test every formula with made-up numbers and check it with a calculator.

A Tuesday for a Small Surveying Company

To see how the pieces fit, here is one made-up Tuesday for a firm with a principal surveyor, a party chief, a crew member, and a drafter.

7:30 am. The principal opens the Stuck view. One job has been in Drafting for 12 days, flagged as stuck. The “waiting on” note says the drafter is waiting for a record from the county. She calls the county.

8:00 am. The party chief opens Fieldwork for the week. A visit on Thursday shows the locate flag, because the ticket expires Wednesday. He requests a new one.

9:00 am. The Needs attention view shows a Weather Delay on today’s job. He reschedules the visit and tells the client why, in a short message.

10:30 am. The Resources view shows a GNSS receiver due for calibration in three weeks. The principal books it, and sets the instrument to Out for Calibration after the planned dates.

1:00 pm. The drafter finishes a plat and moves it to QC Review. The reviewer works through the checklist, finds a bearing that doesn’t match the record call, and sends it back with a note.

3:00 pm. The Ready to invoice view shows a job delivered on Friday with no final invoice. The principal sends it.

4:00 pm. She follows up on three proposals, each with a short message, and updates their status.

5:00 pm. She sets a job’s transmittal to Ready to Generate. The PDF goes to the client with the delivery link.

Nothing depended on anyone’s memory.

The Documents That Leave Notion

Clients and partners don’t use your workspace, so some records need to become files. Survey products themselves, such as sealed plats, come from your survey and CAD tools and your approved process, and not from Notion. From Notion, generate the management documents around them:

• Proposals and fee estimates: scope, assumptions, exclusions, the fee, and the retainer
• Service agreements: terms, scope, liability, and responsibilities, with wording checked by an attorney
• Job sheets for the crew: the site, the purpose, the access arrangements (without codes), the hazards, the instruments, and the checklist
• Transmittal letters: what’s being delivered, the date, the revision, and a link to the files
• Status updates for clients, lenders, and title companies: the stage, what’s next, and the expected date
• Invoices and receipts. Notion Receipt Template shows how to structure a receipt.
• Equipment calibration and license registers
• QC review records: the checklist, the reviewer, and the date
• Annual or quarterly summaries for the owner

For a single page, you can use Notion’s export option. How to Export Notion to PDF shows the settings. Clients judge a surveying firm partly by the clarity of its communication, and Notion’s own export gives you limited control over layout. How to Add Your Logo and Brand Colors to Notion PDFs explains how a template solves that.

Generating PDFs with PDFOutput

PDFOutput creates documents from your Notion data using a template. A template can be a Google document, a Word file, a PDF file, or a Notion page. If you already have a proposal or transmittal layout in Word or Google Docs, you can reuse it.

Here is how it works:

• Create your template with your firm’s name, your license details, your logo, and your layout.
• Add placeholders in double curly braces where the data should go, such as {{Job_Name}} or {{Fee_Estimate}}`.
• Make sure each placeholder matches the name of a Notion property.
• Start the document with a Notion database button or a status property.

These are some of the status options:

• Ready to Generate creates a PDF from the database record.
• Generate Page converts the Notion page into a PDF.
• Generate PDF and Doc creates a PDF and a Google document.
• Preview creates a Google document so you can check it before making the final PDF.
• Generate E-Signed Doc creates an e-signed PDF in the database workflow.

The e-signed option may help with proposals and service agreements. Whether an electronic signature is valid for a given agreement depends on your location and the type of document, so check before you rely on it. It isn’t a way to sign or seal a survey product, which has its own rules. You can save the finished file to a property in your database, so a transmittal stays on the deliverable record. You can also save it to a Google Drive folder and store the link in a property.

Three kinds of document work well.

A proposal uses the fields on one job record: the client, the site, the job type, the hours, the rates, the expenses, and the fee estimate.

A job sheet uses the fields on the same job and a fieldwork record: the date, the crew, the instruments, the hazards, and the checklist as text.

A transmittal uses the fields on one deliverable record: the type, the revision, the delivery date, and the file link. If you’d like a transmittal that lists every deliverable on a job, test a template with a sample job that has several, and check that each appears. If it doesn’t, write a short list as text on the job, and use that in the template.

Before using any document tool with information about your clients, ask the provider how data is handled, where it’s stored, and what agreements are available, and keep the answers with your records. The safest approach is to generate documents from records that hold only what the recipient should see. Don’t put access codes, other clients’ details, or confidential project plans on a document sent to someone else. Check the name, the job number, and the revision on every document before you send it.

Start with the transmittal, since you’ll send it on every job.

Use Preview first and check for empty fields, the right revision, and a link that opens for the recipient.

> 📌 Key Takeaway: Give every job a stage and a date, let formulas show where jobs are stuck, check access, locates, and calibration before the crew goes out, and run every deliverable through a review checklist. Then proposals, job sheets, and transmittals come from records you already have, and the licensed surveyor’s work stays in the tools where it belongs.

Who Can See What

Your workspace will hold client information, project details, and staff credentials, so control access tightly.

• Give crews access to their own job sheets and fieldwork, or send them a job sheet PDF instead.
• Give drafters and reviewers access to the jobs and deliverables they work on.
• Keep fees, rates, invoices, and margins in views that only the principals and the office manager can open.
• Keep licenses, insurance, and personal details visible only to those who need them.
• Never give clients access to the workspace. Send each client only their own documents.
• Keep survey files, title documents, raw data, and sealed products in secure file storage, with links in Notion.
• Keep access codes, keys, and card details out of Notion entirely.
• Remove access on the day someone leaves.
• Review who has access every few months.

Common Mistakes

Treating Notion as the official record. Keep field notes, calculations, and sealed products in the systems your rules require, and link to them.

Marking something sealed in Notion. A status is not a seal. Record the date from your approved process.

Scheduling fieldwork without checking access and locates. A wasted trip is the most expensive kind of delay.

Letting calibration lapse. Instruments drive the accuracy of the work. Use the flag, and keep the records.

Skipping the second-person review. The checklist is cheapest at your desk, not after delivery.

Quoting from memory. Two people give two prices for the same job. Use the same inputs and the same formulas.

Not tracking scope changes. Extra work without a change order becomes unpaid work.

Forgetting to invoice. Delivered and not billed is lost revenue. Use the Ready to invoice view.

Storing files in Notion. Large data, CAD, and title documents belong in secure storage.

Ignoring field safety. Record hazards and a check-in plan for every visit.

Too many properties. If a job record takes twenty minutes to update, it won’t get done. Keep the stages and the templates short.

No owner for the structure. If more than one person edits the workspace, pick one person responsible for the setup. Properties get renamed and formulas break, so tell that person not to rename properties used in PDF templates, because the placeholders must match exactly.

Skipping a test. Run a month with made-up jobs first, and fix what annoys you before you use real records.

Frequently Asked Questions

Can Notion be used to run a land surveying company?

For the management side, yes. It can organize clients, jobs, fieldwork, deliverables, instruments, and invoices. It isn’t survey or CAD software, a records archive, or a way to sign and seal work, so keep the professional work and the official records in the tools and systems your rules require.

How do I track survey jobs through their stages in Notion?

Give each job a Status property with your stages, and a Stage Entered date. Use a formula to count the days in the current stage, and add a flag for jobs that have been in a stage longer than your limit. Make a board view by stage and a view of stuck jobs.

How do I estimate a survey fee in Notion?

Record the research, field, drafting, and review hours, multiply each by its rate, and add expenses, using a formula. Use the same inputs every time so quotes are consistent, state the scope and assumptions clearly, and use change orders for extra work.

How do I track instrument calibration and licenses in Notion?

Create a Resources database with the serial number, last calibration date, and interval for each instrument, and the expiry dates for licenses and insurance. Use formulas to calculate the next due date and to flag items due within 30 or 60 days. Keep the certificates in your records system, and link to them.

How do I manage utility locates and fieldwork scheduling in Notion?

Record the locate ticket reference and expiry date on each field visit, and use a formula to flag scheduled visits where the locate runs out before the visit. Track access permission, weather delays, and return visits with statuses and short reasons, and follow the locate and entry rules that apply where you work.

Is it safe to store client and project information in Notion?

Notion lets you control who sees each page, but your duties depend on the rules where you work and on your contracts. Collect only what you need, keep survey files, title documents, and access codes out, use restricted pages for sensitive jobs, and limit access to the people who need it.

Can I create job sheets and transmittals from Notion?

You can export a page as a PDF, or use a template-based tool such as PDFOutput to fill a job sheet or transmittal template with data from each record. Sealed survey products come from your survey and CAD tools and your approved process. Put the key facts in clearly named properties on one record, test it on a few sample records first, and check each document before you send it.

Related Reading

• How to Use Notion for a Physiotherapy Clinic
• How to Use Notion for a Music School
• How to Use Notion for a Homeowners Association

Conclusion

A good land surveying setup in Notion keeps every job moving: a stage and a date for each job, a clear view of what’s stuck and why, fieldwork that starts with access, locates, and calibrated instruments, a review checklist before anything leaves the office, and invoices that go out when the work is done. Keep files and the official records in the systems your rules require, leave the signing and sealing where it belongs, and run a month with made-up jobs first. When your proposals, job sheets, and transmittals need to leave Notion, PDFOutput can fill your template from each record and save the PDF to your chosen storage.

Want proposals, job sheets, and transmittals as clean PDFs? Try PDFOutput.