FIELDLOG PRO ULTRA

fieldlogpro.app
A
00 00 00

How to Use This Manual

FieldLog Pro Ultra is a construction bidding and field operations platform. It runs entirely in your web browser — nothing to install, on a desk or in a truck.

This manual is organized the way a specification book is organized: numbered divisions, each one covering a single part of the product. You do not need to read it front to back. Use the contents list to jump to what you need.

Reading conventions

Save EstimateText shown in a fixed-width box is something you see on screen — a button, a tab, a field label.
Dashboard → SettingsAn arrow shows a path you click through, in order.
Tab 5Numbered tabs refer to the numbered navigation across the top of the screen and down the sidebar.
Three kinds of callout

Blue notes explain how something behaves. Orange tips are shortcuts and habits worth building. Amber warnings mark places where a mistake costs money, time, or safety — read those ones.

Who this is written for

Estimators, project managers, superintendents, and safety personnel at general and specialty contractors. It assumes you know construction. It does not assume you know software.

▲ Top
01 00 00

Getting Started

Open a browser, sign in, and you are working. There is no download and no installer.

01 10 00 — What you need

ItemRequirement
BrowserGoogle Chrome or Microsoft Edge, current version. Safari on iPhone and iPad is supported. Chrome is recommended, particularly for voice input.
ConnectionInternet access is required. Anything that uses AI — estimating, Plan Reader, Problem Solver — needs a live connection.
ScreenAny size. The layout adapts to phones, tablets, and desktops.
AccountA username and password issued by your FieldLog administrator.

01 20 00 — Signing in

  1. Go to fieldlogpro.app.
  2. Enter the username and password you were issued. Usernames are lowercase with no spaces.
  3. Choose your language when prompted — English or Spanish. Your choice sets the interface language and the language of the guided tour.
  4. You land on the Dashboard.
Your account is yours alone

Each account keeps its own separate set of projects, estimates, and field records. Sharing one login across a crew means everyone edits the same records with no way to tell who did what. Ask your administrator for additional accounts instead.

01 30 00 — Putting it on your phone's home screen

FieldLog Pro Ultra installs as an app icon without going through an app store.

  • iPhone / iPad: open fieldlogpro.app in Safari, tap the Share button, then Add to Home Screen.
  • Android: open the site in Chrome, tap the three-dot menu, then Install app or Add to Home screen.

The orange FLP tile appears with your other apps and opens full-screen, without the browser address bar.

01 40 00 — Your first fifteen minutes

If you have never opened the product before, do these four things in order. Everything else builds on them.

  1. Take the guided tour. On a desktop or laptop it runs automatically the first time, with narration. See 18 00 00.
  2. Fill in Company Settings — your company name, license numbers, default crew, and default markup percentages. See 03 00 00. Every estimate you produce inherits these, so getting them right once saves correcting them forever.
  3. Run one throwaway estimate on a job you already know the price of. Compare what the product returns against what you know to be true. This is how you calibrate your trust in it.
  4. Open the Jobsite Problem Solver from the orange wrench and ask it something real. See 16 00 00.
▲ Top
02 00 00

Finding Your Way Around

One numbered spine runs the length of the product. Learn the numbers and you can find anything.

02 10 00 — The three ways to navigate

ControlWhat it does
Top navigation barNumbered tabs running left to right across the top of the window. This is the primary spine of the product, and it follows the order of a real bid: estimate first, closeout last.
SidebarThe same numbered destinations stacked vertically down the left edge, plus Dashboard, Company Settings, Quick Presets, and the built-in intelligence tools. Sidebar items are color-coded by category.
DashboardThe home screen. Quick Action cards jump straight to the work you do most, and live cards surface what needs attention.

The top bar and the sidebar stay in sync. Clicking a tab in one highlights it in the other, so you never lose your place.

02 20 00 — The shape of the workflow

The numbered tabs are laid out as a lifecycle, not a menu. Reading left to right, they move through:

  1. Estimating — describe the scope, let the AI build the takeoff, review and correct the line items.
  2. Pricing — apply the markup stack and land on a final bid number (Tab 5, Bid Summary).
  3. Delivery — export and send the bid package (Tab 6).
  4. Execution — project management, daily field reports, submittals and RFIs, change orders, scheduling, and document storage.
  5. Analysis — the Plan Reader (Tab 13) and the AI tools that read your drawings and your bid history.

02 30 00 — Smart Search

The search bar at the top finds any feature in the product by name or by what it does. Search results give you two choices rather than dragging you somewhere:

  • Read Explanation — a written description of the feature, what it is for, and where it lives.
  • Audio Explanation — the same explanation spoken aloud, for when your hands are busy.

The search window stays open and stays put. It answers your question without moving you off the screen you were working on.

02 40 00 — The orange wrench

A floating orange wrench button sits on every screen in the product. It opens the Jobsite Problem Solver. You can drag it out of the way if it covers something, and it stays where you put it. Full instructions are in 16 00 00.

▲ Top
03 00 00

Company Setup

Settings is the least interesting screen in the product and the most consequential. Everything downstream inherits from it.

Reach it from the sidebar (Company Settings, in orange) or from the Dashboard. The screen scrolls independently — use the scroll bar inside the panel, and the Back and Home buttons at the top to leave.

03 10 00 — Company identity

Your legal company name, address, phone, license numbers, and logo. These print on every proposal, bid package, RFI, and change order the product generates. Enter them exactly as they should appear on a document going to an owner.

03 20 00 — Default personnel

The crew composition and labor rates you normally carry. The estimator uses these as its starting assumption for any scope where you have not said otherwise, which is what keeps AI-generated labor pricing anchored to your actual payroll instead of a national average.

03 30 00 — Default markup structure

Your standing percentages for field overhead, company overhead, contingency, profit, bond, and insurance. Every new estimate opens with these values loaded. You can override any of them on any individual bid without changing the defaults. See 05 00 00 for how they compound.

Set these before your first real bid

Changing a default markup does not retroactively reprice a bid you already saved. Saved estimates keep the numbers they were saved with, on purpose — so your history stays honest. Get the defaults right early.

03 40 00 — The Knowledge Base

Your own historical unit costs. Anything you record here is injected into every AI estimate as ground truth, ahead of the model's general knowledge. If you know what you actually pay for a cubic yard of 4,000 psi placed and finished, put it here — it will outrank anything the AI would otherwise assume.

The Knowledge Base is the single highest-leverage thing you can maintain. Estimating accuracy improves in direct proportion to how much of your real cost history lives in it.

03 50 00 — Delete authorization

Deleting a project requires a security code. The code is stored hashed, never in readable form, and is set on this screen. Your administrator issues the code separately from your login credentials.

Deletion is permanent

There is no recycle bin. A deleted project and its estimates, field reports, RFIs, and change orders are gone. Export a backup first — see 19 00 00.

▲ Top
04 00 00

Building an Estimate

You describe the job in plain language. The product builds a line-item takeoff, checks it against the code, checks it against your history, and tells you how confident it is.

04 10 00 — Two modes

ModeUse it when
Quick EstimateSomebody needs a ballpark on the phone. Minimal input, fast answer, order-of-magnitude accuracy. Any Quick Estimate can be promoted into a full estimate later without re-entering anything.
Full EstimateYou are bidding the job. Full scope entry, line-item takeoff, gap checking, complete markup stack, exportable proposal.

04 20 00 — Describing the scope

On the first tab, enter the project information and describe the work. Write it the way you would describe it to a foreman: what is being built, how much of it, what conditions apply. Detail improves the result more than any other single factor.

Things worth including every time:

  • Project location, down to the locality — this drives prevailing wage detection, permit assumptions, and regional cost multipliers.
  • Owner type — federal, state, municipal, or private.
  • Quantities you already know. Given numbers always beat inferred ones.
  • Site conditions that will cost money: access, existing conditions, phasing, occupied buildings, night work, hazardous materials.
  • Anything explicitly excluded from your scope.

04 30 00 — Prevailing wage detection

The product carries a fifty-state prevailing wage law database and screens your project description against eighteen federal trigger conditions. When it detects that Davis-Bacon or a state equivalent applies, it says so and prices labor accordingly.

Verify it, always

Automatic detection is a prompt, not a determination. Wage decisions, thresholds, and coverage change. Confirm the applicable wage determination against the solicitation and the governing authority before you submit a number that depends on it.

04 40 00 — Reviewing the takeoff (Tab 2)

The Review tab is where the estimate becomes yours. Every line item is editable — quantity, unit, unit cost, and vendor. This is the tab where estimating actually happens; everything before it is data entry and everything after it is arithmetic.

Work through it deliberately:

  1. Read every quantity against your own read of the scope. The AI infers quantities it was not given, and inference is where error enters.
  2. Check unit costs against what you actually pay. Correct them in place.
  3. Delete anything that is not in your scope. Add anything the AI missed.
  4. Watch the Est. Total Bid field at the top. It recalculates live and always matches the figure on the Bid Summary.
One number, everywhere

The total shown on Review, the total on the Bid Summary, and the total on your exported proposal are the same computed figure. They cannot drift apart. If you change a quantity on Review, the proposal changes too.

04 50 00 — The gap checker

The product screens your estimate against a ninety-item checklist spanning eighteen CSI MasterFormat divisions and flags what is conspicuously missing. Temporary facilities, dumpsters, final clean, testing and inspection, permits, mobilization — the scope items that get left out and eaten.

Each flagged item can be added back to the estimate with one click. Dismissing an item is a decision; make it on purpose rather than by scrolling past.

04 60 00 — Confidence scoring

Every estimate carries a confidence score built from several dimensions, including how completely the scope was described, how much of it your Knowledge Base covers, and whether prevailing wage compliance was resolved. A low score is not a failure — it is the product telling you which parts of the estimate you should personally verify before it goes out.

04 65 00 — Vendor pricing (Tab 3)

Before you build the priced estimate, Tab 3 surfaces real local suppliers near the job site with their current unit pricing, instead of relying on regional averages. This is the AVPIA™ engine — Automated Vendor Price Injection Algorithm — matching every supplier quote to the correct line item before a price ever reaches your cost breakdown.

Matching runs on two fields together: unit of measure (LF, CY, SY, EA, TON, and so on) and trade category. A vendor quoted per linear foot can only fill a per-linear-foot line item; a per-acre price cannot be applied to a per-linear-foot pipe item, even if both are technically "site work." The engine also understands construction shorthand — a line item written as "DI Water Main" matches vendors listed as "Ductile Iron Pipe Supply" without you having to reconcile the wording yourself.

Lump sum (LS) line items are the one exception: they accept any vendor price regardless of the vendor's unit label, since an LS item is priced as a whole rather than per unit.

Select All Best Value applies the lowest verified price across every trade category at once — one click prices the whole estimate at best-value market rates. Vendor cards carry a Best Value, Premium, or Local badge plus a rating, so you can see at a glance why one supplier outranks another. Use Selected Vendors → Build Costs commits your choices and sends you to the Cost Builder (Tab 4) with every price already injected.

A starting point, not a certified price

Vendor prices shown here are current at the time they were pulled, not locked in. Get a local quote before committing to a number that depends on one, the same as any other AI-assisted figure in this product.

04 70 00 — Cost basis and the reconciliation check

All AI-generated line item pricing in FieldLog Pro Ultra is bare cost — labor, material, and equipment only, with no overhead and no profit embedded. Overhead and profit are added once, by you, in the markup stack. This is what keeps the product from charging you twice for the same margin.

After every estimate, an automatic reconciliation check compares the sum of the line items against the AI's own independent bid range. If the two diverge by more than 25 percent, you get an on-screen warning. Treat that warning as a stop sign: something in the takeoff is wrong, and it is worth finding before you price it.

▲ Top
05 00 00

Pricing and the Markup Stack

Tab 5, the Bid Summary, turns cost into price. This is the MSBPA™ markup stack, and the order it applies in is not arbitrary.

05 10 00 — How the stack compounds

Each stage applies to the running total produced by the stage above it, not to the original direct cost. Profit is earned on overhead; bond is paid on the profit-inclusive figure; insurance is calculated last. That is how the money actually moves, and the product models it that way.

Direct Costbase
Field Overhead — project-specific+ %
Company Overhead+ %
Contingency+ %
Profit+ %
Bond+ %
Insurance+ %
Total Bid Amount=

Every percentage in the stack is editable on this screen. The total recalculates as you type, and the recalculated figure is written back to the Review tab and to every export at the same instant.

05 20 00 — Reading the matrix

The markup matrix shows each stage, the percentage applied, the dollars that stage adds, and the running subtotal. Read down the dollar column when you are deciding where to cut — it shows you what each point of markup is actually worth on this job, which is rarely what you assume.

05 30 00 — Recipient templates

The same estimate presents differently depending on who is receiving it. Choose the recipient and the product reformats accordingly:

RecipientWhat is shown
Owner / ClientScope, inclusions, exclusions, and the total bid. No internal cost structure, no margin.
SubcontractorThe scope-of-work portions relevant to that trade, formatted for a sub-bid solicitation.
InternalThe full picture — direct cost, every markup stage, margin analysis, and confidence scoring.
Check the template before you send

The Internal template shows your margin. Confirm which template is selected before exporting anything that leaves your office.

▲ Top
06 00 00

Bid Intelligence

Five tools that answer the questions estimating software normally leaves to your gut: should we bid this, where are we exposed, and what is this number going to do in the market.

All five live with the Bid Summary and on the Dashboard.

06 10 00 — Deep Analysis™

A go/no-go screen. Deep Analysis evaluates the project across twelve risk categories — scope, schedule, site, contractual, financial, regulatory, and others — and returns one of three recommendations:

BIDRisk profile is within normal tolerance. Proceed.
CAUTIONSpecific identified risks require mitigation, a qualification, or a contingency adjustment before submitting.
PASSThe risk concentration warrants declining, or the job needs terms you are unlikely to get.

The recommendation is always accompanied by the reasoning behind it, category by category. Read the reasoning — the value is in which categories drove the call, not in the single word at the top.

This is analysis, not authority

Deep Analysis has not read your contract documents, walked the site, or spoken to the owner. A PASS is a prompt to look harder. A BID is not permission to skip your own review.

06 20 00 — Bid DNA™

A live fingerprint of the estimate as you build it, shown in the sidebar of the Bid Summary. It profiles how this bid is composed — labor versus material weighting, division concentration, markup posture — and shows how that composition compares to your own bidding pattern. It answers the question: does this look like a job we normally win?

06 30 00 — Win Zone

The range within which your number is competitive without leaving money behind. Shown against your current bid figure so you can see immediately whether you are above, below, or inside it.

06 40 00 — BidPulse™

Pipeline tracking with urgency built in. Every bid you have in flight, ordered by what is about to expire — due dates, follow-up windows, and the bids that have gone quiet and need a phone call. BidPulse is the screen to open on Monday morning.

06 50 00 — How to Lower My Bid & Keep Value

Value-engineering advice specific to the estimate in front of you. It identifies where cost is concentrated and proposes reductions ranked by how much value they cost you, so you can distinguish a genuine efficiency from a cut the owner will notice on day one.

Suggestions are applied deterministically — you review each one and choose whether to accept it. Nothing changes your estimate without you agreeing to it.

▲ Top
07 00 00

Sending the Bid

Tab 6 assembles the outgoing package.

07 10 00 — Export formats

Choose your output format, then print, save as PDF, or send directly from the browser. The proposal carries your company identity from Settings, the scope as you finalized it on Review, and the total bid from the markup stack.

07 20 00 — Before you send

  1. Confirm the recipient template is correct — Owner, Subcontractor, or Internal.
  2. Confirm the total on the exported document matches the Bid Summary. It should always; check anyway.
  3. Read your exclusions. Exclusions are what protect the number you just spent an afternoon building.
  4. Confirm bid bond and insurance requirements against the solicitation.
  5. Save the estimate to the library before it goes out, so the version you submitted is preserved exactly. See 08 00 00.
▲ Top
08 00 00

The Estimate Library

Every estimate you save is filed under its project, numbered in sequence, and preserved as it stood at the moment you saved it.

08 10 00 — How estimates are filed

Estimates are stored in per-project folders and numbered sequentially, so revision three of the gymnasium job is always identifiable as revision three. Saving an estimate links it to its project in both directions — open the project and you see its estimates; open an estimate and you can jump to its project.

08 20 00 — Snapshots are frozen

A saved estimate keeps the numbers it had when saved. Later changes to your default markups, your Knowledge Base, or your labor rates do not reach backward and rewrite history. This is deliberate: your bid history is only useful if it reflects what you actually submitted.

08 30 00 — Reopening and revising

Open any saved estimate to review it, or load it back into the estimator to build a revision. Revisions save as new sequential entries rather than overwriting the original.

▲ Top
09 00 00

Project Manager

Where a bid becomes a job.

09 10 00 — Creating a project

Open the Project Manager tab and use the + control to create a new project. Enter the project name, number, location, owner, contract type, and key dates. Location matters here for the same reason it matters in estimating — it drives jurisdiction handling downstream.

09 20 00 — The project record

Once created, the project becomes the anchor for everything else. Daily field reports, RFIs, submittals, change orders, schedule activities, documents, and Problem Solver entries all attach to a project. Selecting the active project at the top of the screen filters the rest of the product to that job.

Set the active project first

Most field modules write to whichever project is currently selected. Make selecting the right job the first thing you do when you open the product, the same way you would check which set of drawings you picked up.

09 30 00 — Project detail tabs

Inside a project, sub-tabs organize the record — general information, contacts, contract details, and the linked estimates. Move between them without leaving the project.

▲ Top
10 00 00

Daily Field Report

The DFR is the record that matters when there is a dispute two years from now. Fill it out the same day, every day.

10 10 00 — What a report captures

The DFR is divided into sections you move between using the tabs across the top of the module:

  • Conditions — date, weather, temperature, and anything that affected the ability to work.
  • Manpower — crews on site by trade, headcount, and hours.
  • Equipment — what was on site, what ran, what sat idle.
  • Work performed — what was actually accomplished, by location and scope.
  • Delays and disruptions — what stopped work, for how long, and why.
  • Visitors and inspections — who came, who inspected, what they found.
  • Safety — briefings held, incidents, near-misses, and observations.
  • Notes and photographs — everything else.
Delays are the section people skip

A delay you did not document is a delay you cannot claim. Record the cause, the start and stop time, the trades affected, and who was notified — on the day it happened, not reconstructed later from memory.

10 20 00 — Dates

Every date field in the product uses the same two-panel picker: choose the month and year from the grid, then the day from the calendar. It behaves identically on a phone and a desktop.

10 30 00 — Reports from the Problem Solver

A jobsite problem worked through in the Problem Solver can be pushed straight into the day's DFR as a documented event, carrying the description and the option you chose. See 16 00 00.

▲ Top
11 00 00

Submittals & RFIs

Two logs, one module, tabbed at the top.

11 10 00 — The submittal log

Track each submittal by spec section, description, date submitted, reviewer, date returned, and disposition. The log gives you the answer to where it is without a phone call.

11 20 00 — The RFI log

Create an RFI with its number, subject, the question, the drawing or spec reference, the date issued, and the response required date. When a response comes back, record it against the RFI — responses are viewable directly in the log alongside the original question, so the full exchange reads as one record.

Write the RFI so the answer is usable

State the condition, cite the document and sheet, ask one question, and propose your recommended resolution. An RFI that proposes an answer gets a faster response than one that only reports a problem.

11 30 00 — Impact tracking

Where an RFI or submittal carries cost or schedule impact, note it on the record. That note is the thread that leads to a change order later.

▲ Top
12 00 00

Change Orders

Pricing a change uses the same engine as pricing the original bid, which is the point.

Create a change order against the active project, describe the changed work, and price it through the same estimating and markup path used for the base bid. Your markup stack, your Knowledge Base, and your labor rates all apply, so a change order is priced on the same basis as the contract it modifies.

Each change order tracks its number, description, originating cause, the referenced RFI or field condition, cost impact, schedule impact in days, status, and approval date. The contract value adjusts as change orders are approved.

Time is part of the price

Record schedule impact in days on every change order, even when the answer is zero. An unrecorded zero is indistinguishable from a day you forgot to claim.

▲ Top
13 00 00

Project Schedule

Activity tracking and timeline view for the active project.

Build the activity list with durations, start and finish dates, responsible party, and predecessor relationships. The timeline view renders the sequence so you can see float, overlap, and where the critical path runs.

Schedule activities can be generated directly from a Problem Solver option when the chosen solution adds work, so a recovery plan lands on the schedule instead of living only in someone's head.

▲ Top
14 00 00

Document Vault

Project documents, drawings, and photographs, filed against the job they belong to.

Upload contract documents, specifications, drawings, submittal packages, correspondence, and site photographs. Documents are stored per project and are available to the modules that need them — including the Plan Reader, which reads from the plan vault.

14 10 00 — Extract & Merge for Estimator

Select the documents that define a scope of work and merge them into a single estimating pass. The product reads them together, with an estimator-specific instruction set, and returns a takeoff built from the documents rather than from a typed description. Use it when you have a real bid set and want the estimate to come off the documents.

▲ Top
15 00 00

PIRCE™ Plan Reader — Tab 13

Upload a drawing set. The product reads all of it, cross-references it against regulatory requirements, and then lets you ask it questions.

15 10 00 — How it reads a set

A full bid set is far larger than any single AI request can handle. The Plan Reader splits the document into chunks and reads them in parallel, then assembles the findings into one coherent analysis. A large set takes time — the progress indicator is telling the truth, not stalling.

15 20 00 — What it returns

  • A structured summary of the drawing set — scope, systems, and what the documents actually call for.
  • Regulatory cross-referencing, flagging where the drawings touch code and standards requirements.
  • Identified gaps, conflicts, and ambiguities worth an RFI.

15 30 00 — Ask the Plans

Once a set is read, ask questions against it in plain language. What is the specified slab thickness at the loading dock? Which walls are two-hour rated? Where does the spec address dewatering? You get an answer with the reasoning behind it, drawn from the documents you uploaded.

The Plan Reader does not replace reading the plans

It is a fast, thorough first pass that finds things a person skims past. It is not a certification of completeness, and it does not carry professional liability. Verify anything you are going to price, build, or sign against the actual sheet.

15 40 00 — Practical notes

  • Text-based PDFs read far better than scanned images of drawings.
  • Upload the set as a set. Reading related sheets together produces better cross-referencing than reading them one at a time.
  • Very large sets are slow on a phone connection. Do the initial read on a desktop, then ask questions from anywhere.
▲ Top
16 00 00

Jobsite Problem Solver

Something has gone wrong on site and you need three defensible options in the next four minutes. That is what this is for.

16 10 00 — Opening it

Four ways in, from any screen in the product:

  • The floating orange wrench button — draggable, always visible.
  • The Problem Solver item in the sidebar.
  • The Problem Solver item in the top navigation bar.
  • The Problem Solver item in the mobile menu.

16 20 00 — Describing the problem

  1. Pick a category chip that fits the problem — this focuses the analysis.
  2. Describe what happened in the description box. Type it, or use the microphone.
  3. Attach photographs or documents if you have them. Photographs of an actual field condition materially improve the options you get back.
  4. Press Get 3 Solutions.

Describe the problem the way you would describe it to a superintendent who just walked up: what you found, where, what it is blocking, and what the constraint is. Say what you have already ruled out.

Using the microphone

Tap the microphone and speak. Your words appear in the description box as you talk. Tap again to stop.

Find a quiet spot

Voice recognition degrades badly around running equipment. Step into a truck cab or around a corner. Thirty seconds of quiet gets a far better result than shouting over a generator.

The Clear button empties the description box, deselects the category chips, and removes attached files, so the next problem starts genuinely clean.

16 30 00 — The disclaimer and waiver

Before the analysis runs, a disclaimer and waiver of liability appears. You must read it and check the acknowledgment box before Proceed — Get 3 Solutions becomes available.

In substance, it says this: the tool generates plausible planning suggestions from the description you gave it. It does not provide engineering, architectural, legal, or safety-certification advice. Anything touching structural integrity, life safety, means of egress, fire protection, electrical or mechanical systems, permitted work, or code compliance must be reviewed and approved by the appropriate licensed professional and by the authority having jurisdiction before you act on it. By checking the box, you accept responsibility for what you do with the output.

This is not a formality

The waiver is there because the failure mode of this feature is a superintendent acting on a suggestion that looked reasonable and was not. Read the options with the same skepticism you would apply to advice from a stranger who has never seen the job.

16 40 00 — Reading the three options

Your problem description stays visible at the top of the results so you can see what was actually asked. Below it, under the heading Read This Before Acting, come three distinct options. Each one carries:

ElementWhat it tells you
ApproachWhat the option actually is.
Cost impactThe order of magnitude, not a quotation.
Schedule impactDays gained or lost.
RequirementsWhat has to be true for this to work — approvals, licensed review, permits, materials, crew.
TradeoffWhat you give up by choosing it. Read this line first.

Three options exist so you have something to compare. The right answer is often a combination, or a fourth thing one of the three made you think of.

16 50 00 — Turning an option into a record

An option you act on should leave a paper trail. From the results screen you can hand the problem and the chosen option off directly into:

  • An RFI, when it needs a decision from the design team.
  • A change order, when it costs money.
  • A schedule activity, when it adds work.
  • The daily field report, to document what happened and what was done about it.

16 60 00 — The problem log

The Log button opens the running log of problems solved on this project — what came up, what was chosen, and when. Over a job it becomes a genuinely useful record of what went wrong and how it was handled.

▲ Top
17 00 00

Working on a Phone

The full product runs on a phone. A few things behave differently by design.

On a phoneBehavior
NavigationA bottom navigation bar and a full-width slide-out drawer replace the desktop sidebar.
IntroductionNew users get a mobile welcome card with narrated orientation rather than the full desktop tour. See 18 00 00.
Voice inputWorks in the Problem Solver. Your phone will ask for microphone permission the first time — grant it, or the button does nothing.
Back buttonYour phone's back button moves back through the product, and closes any open panel first.
LayoutsMulti-column screens, including the Bid Summary, stack vertically. The markup matrix takes the full width and the Bid DNA panel moves below it.

17 10 00 — What to do where

Field work — daily reports, photographs, RFIs, the Problem Solver — is comfortable on a phone. Estimating and the initial Plan Reader pass are genuinely better on a laptop, where you can see the whole line-item table and the whole markup stack at once.

▲ Top
18 00 00

Guided Tour and Training

A narrated walkthrough of the entire product, in English or Spanish.

18 10 00 — The desktop tour

On a laptop or desktop, the tour runs automatically on first sign-in and can be restarted at any time. It is professionally narrated and moves through the product tab by tab, in workflow order, highlighting each control as the narrator names it.

Controls: Next and Back to move a step at a time, the dots to jump to a specific step, and the audio controls to pause or seek within the narration. The description card can be dragged out of the way if it covers something you want to see.

You can also jump into the tour at a specific feature by clicking that feature's tab while the tour is running — the tour follows you there.

18 20 00 — The mobile welcome

Phones get a narrated welcome card instead of the full spotlight tour, covering orientation and the major capabilities. Take the full tour on a desktop when you have twenty minutes.

18 30 00 — Language

English and Spanish are both fully narrated. Your language selection at sign-in sets both the interface and the tour.

▲ Top
19 00 00

Your Data — Storage, Sync, and Backup

Your work is stored on your device and synchronized to a cloud database tied to your account.

19 10 00 — How storage works

FieldLog Pro Ultra writes your projects, estimates, field reports, RFIs, submittals, change orders, schedules, documents, Knowledge Base, and settings to your browser's local storage, then syncs them to a per-account cloud database. This is why the product stays responsive on a bad site connection — the local copy answers immediately and the sync catches up.

Data is separated by account. Nobody else's records appear in yours.

19 20 00 — Backup and restore

Use the floating backup bar to export every dataset in your account to a single dated JSON file. Credentials are deliberately excluded from the export. Restore reads that file back in.

Export before anything irreversible

Export a backup before deleting a project, before clearing browser data, before handing a device to somebody else, and at the close of every bid. It costs ten seconds.

19 30 00 — What breaks your local copy

Clearing browser data clears local storage

Clearing site data, clearing cookies with site data included, or using a private browsing window will remove the local copy of your work. The cloud sync exists to protect you here, but a current exported backup is what actually guarantees you lose nothing.

19 40 00 — Switching devices

Sign in on the new device and your account's data syncs down. Give it a moment on first sign-in — a full account with document uploads takes longer than a small one.

▲ Top
20 00 00

Troubleshooting

Start with a hard refresh. It resolves a genuinely surprising proportion of problems.

20 10 00 — Hard refresh

Press Ctrl + Shift + R on Windows, or Cmd + Shift + R on a Mac. On a phone, close the app completely and reopen it. This forces the browser to load the current version instead of a cached one, which is the cause of most reports that a fix did not work.

20 20 00 — Common situations

What you seeWhat to do
A screen looks wrong or a new feature is missingHard refresh. You are on a cached copy.
An AI feature returns nothing or an errorCheck your connection, then retry. If it persists, sign out and back in — your session may have expired.
The microphone button does nothingYour browser is blocking microphone access. Allow it in the site permissions, then reload. On iPhone, check Settings, then Safari, then Microphone.
Voice input transcribes badlyBackground noise. Move somewhere quieter and speak at a normal conversational pace.
A file will not uploadCheck the file size and format. Very large drawing sets take time — let the progress indicator finish rather than retrying.
A screen will not scrollScroll inside the panel rather than the page. Settings in particular has its own internal scroll.
The estimate total seems highCheck the markup stack on Tab 5 — the percentages compound. Then check the reconciliation warning and the line-item quantities on Tab 2.
Work is missing after switching devicesWait for sync to complete, then reload. If it is still missing, restore from your most recent exported backup.
Buttons stop responding after closing a panelNavigate to any tab, or reload. An invisible overlay may still be open.

20 30 00 — Reporting a problem

When something is genuinely broken, the report that gets fixed fastest includes: what you were doing, what you expected, what happened instead, whether you were on a phone or a desktop, which browser, and a screenshot. Send it to your FieldLog administrator.

▲ Top
21 00 00

Limits, Disclaimers, and Legal Notices

Read this section once, completely. It defines what the product is and is not.

21 10 00 — What the AI features are

The estimating engine, Deep Analysis, the Plan Reader, and the Jobsite Problem Solver generate plausible planning suggestions from the information you provide and the data stored in your account. They are decision support. They are not determinations.

21 20 00 — What they are not

FieldLog Technologies, Inc., its officers, employees, affiliates, and licensors do not warrant, guarantee, or certify the accuracy, completeness, safety, code compliance, or fitness for any particular purpose of any output generated by this product.

The AI has not visited your jobsite, reviewed your drawings, specifications, geotechnical reports, or existing conditions, and does not verify compliance with any federal, state, or local building code, safety regulation, or professional standard.

This product does not provide engineering, architectural, legal, or safety-certification advice.

21 30 00 — Where licensed review is required

Any decision affecting structural integrity, life safety, means of egress, fire protection, electrical or mechanical systems, permitted work, or code compliance must be reviewed and approved by the appropriate licensed professional — a professional engineer, licensed architect, licensed contractor or trade, or a qualified or competent person — and by the authority having jurisdiction, before it is acted upon.

21 40 00 — Jurisdiction and regulatory data

Prevailing wage law, permit requirements, code adoptions, and regulatory references built into this product reflect the state of the data at the time of the build. Laws and adoptions change. Confirm anything jurisdictional against the current governing authority before relying on it commercially.

21 50 00 — Estimates are estimates

Costs generated by this product are estimates produced from incomplete information. They do not constitute a quotation, a guarantee of price, or a representation that work can be performed for the amount shown. You are responsible for the number you submit.

21 60 00 — Your responsibility

You retain full professional responsibility for every decision you make using this product, and for the accuracy of anything you send to an owner, a subcontractor, or a regulatory authority under your company's name.

21 70 00 — Proprietary rights

FieldLog Pro Ultra, and the proprietary systems identified in 22 00 00, are the property of FieldLog Technologies, Inc. This manual and the software it describes are provided to authorized pilot participants for evaluation. Do not redistribute either without written permission.

▲ Top
22 00 00

Glossary and Support

22 10 00 — Proprietary systems

MarkWhat it does
MSBPA™The compounding markup stack that converts direct cost into a final bid price — field overhead, company overhead, contingency, profit, bond, and insurance, applied in sequence. See 05 00 00.
PIRCE™The Plan Reader engine — parallel chunked reading of drawing sets with regulatory cross-referencing and natural-language querying. See 15 00 00.
BidPulse™Urgency-ordered bid pipeline tracking. See 06 40 00.
Bid DNA™Live compositional fingerprint of an estimate, compared against your bidding history. See 06 20 00.
Deep Analysis™Twelve-category project risk screen returning Bid, Caution, or Pass. See 06 10 00.

22 20 00 — Terms used in this manual

Bare costLabor, material, and equipment only, with no overhead or profit included. All AI-generated line pricing in this product is bare cost.
CSI MasterFormatThe standard numbering system for construction specifications. The gap checker screens against eighteen of its divisions.
DFRDaily Field Report.
Knowledge BaseYour own historical unit costs, injected into every AI estimate as ground truth.
Prevailing wageStatutorily required wage rates on covered public work, under Davis-Bacon or a state equivalent.
Recipient templateThe output format that controls how much of your cost structure appears on an exported document.
SnapshotA saved estimate, frozen with the figures it carried at the moment of saving.

22 30 00 — Support

Contact your FieldLog administrator for account issues, additional user accounts, delete authorization codes, and bug reports.

▲ Top