Glossary

The words Structra uses, as the app uses them. Each entry links to the page that covers it.

People and companies

Organization: An engineering firm that runs its projects in Structra. Its staff are Organization Admins, Engineers and Designers. See the guide for the engineering team.
Client: A company that sends projects to an organization, such as a foundation repair contractor. See Clients, branches and groups.
Branch: One office of a client company. Each branch is set up as its own client, with its own users, projects and billing email.
Client group: Ties the branches of one company together, so a field inspector can be assigned to more than one of them. See Group branches together.
Client Admin: The person at a client company who runs its account: projects, people and field inspectors. See the guide for client admins.
CFI (certified field inspector): A member of a client’s field staff who records an inspection on site and submits it from the inspector portal. On a project, the app shows this person as Project Manager (CFI). See the guide for field inspectors.
Company code: The code a field inspector types to register under their company. See Get access.
Foreman: The crew lead a client names on a project’s inspection information. A foreman does not need to sign in.
EOR (engineer of record): The engineer whose name, credentials and signature image go on a project’s documents. A project has one. See Engineer of record.

Projects and statuses

Status: The stage a project is in: Intake, Triage, Design, Inspection, Finished or Canceled. Each is a tab on Projects.
Sub-status: The step within a status, shown as the colored label on a project’s row, such as In Drawing Queue. It says exactly where the project stands and who acts next. The full list is in Statuses and sub-statuses.
Job #: The number Structra gives a project.
Ref (Internal Reference #): The client’s own reference for the job.
Intake: Collecting a project’s details and documents, in the intake wizard or in the inspector portal’s form. See Submit a new project.
Triage: The engineering firm’s review of a submitted intake. It ends in an approval or a push-back. See Intake and triage.
Pre-check: An automatic comparison of the uploaded documents with the intake, shown to the firm in triage. It is advisory: it never approves or rejects a project. See The pre-check.
Push-back: The firm returning an intake to the client with a written reason. The project shows Project Issue Waiting On Client until the client fixes it and submits again. See Answer a push-back.
Comment: A message on a project that the firm and the client can both read.
Internal note: A comment marked internal. Only the author’s own organization or company can read it. A client never sees the engineering firm’s internal notes. See Internal notes.
Draft: An intake that has been started and not yet submitted. Nobody reviews a draft. See Drafts and weak signal.

Design and reports

Spool (design setup): Structra assembling a project’s starting document set from the firm’s template files for the scopes and brands on the project. It runs by itself when a project is approved in triage. See Design setup.
Scope: A kind of repair on a project, such as push piers or wall braces, with its quantity.
Brand: The product line used for a scope. The firm sets which brands each client can choose.
Checklist: The firm’s quality list for a drawing or for the engineering. One person works it and a reviewer judges it. See Review a drawing.
Build docs: Structra joining the report parts into one PDF, with the cover letter and title page. See Build the report.
Sealed report: The report after the engineer of record has signed and sealed it in Bluebeam. It is the file the client receives. See Sign and seal the report.
Deliverable: A file pinned at a specific version as the one handed to the client for a revision. See Deliverables.
Revision (R0, R1…): A numbered issue of a project’s report. R0 is the original. Each change order creates the next one.
Change order: A change to the work after the project was approved. It reopens the project and creates a revision. Some menus call it Change Request. See Reopen a project for a change order.
Modification / Correction: An Organization Admin’s edit to a project’s details that does not create a revision.

Inspections

Inspection information: The construction dates, foreman and related details a client supplies for a project that needs an engineer’s inspection. See Inspection details.
Inspection verification: The firm’s acceptance or rejection of the inspection information. See Inspections.
Inspection report: The report Structra produces once an inspection is accepted.

Leads and billing

Lead: A request for work from someone who is not yet a client. See Leads and engagement letters.
Engagement letter: The agreement a customer signs online before work starts, built from one of the firm’s agreement templates.
Ad Hoc: The project type for one-off work, with the scope and fee quoted per job. See The Ad Hoc project type.
Feature: A billable part of a project type, priced separately.
Client override: A price that replaces the default for one client. See Client pricing.
Finalize: Closing an open invoice and creating it in QuickBooks. See Billing and QuickBooks.

Stuck on something? Email support@structra.tech and tell us what you were trying to do.