Attain OS for engineering firms

One workspace per project for the drawings, the inspections, the permit dates and what you sent.

Electrical, civil, mechanical and industrial work runs on documents that change: a drawing set that reaches Rev D, a specification that gets amended, a permit that expires, an inspection that turns into an action. Attain OS keeps each project's files, site checklists, compliance dates and deliverables in one workspace. It is not CAD and it is not a document-control system with version history: you keep each issued revision as its own labelled document.

14 days free · No card needed · Cancel anytime

Project Management Software for Engineering Consulting Firms

Who this is for

What this looks like today

Electrical, civil, structural, mechanical and industrial engineering consultancies producing drawings, calculations, reports and stamped deliverables for clients, contractors and permitting authorities.

The set is in a folder full of names like EL-102_rev_C_final_ok. The site visit is a notebook and a phone gallery. The permit renewal is a date the office manager happens to remember. The structural engineer emailed a revised detail straight to the contractor, so the set you issued and the set being built from stopped being the same document sometime last month. When the client asks where their project stands, someone opens four folders, a mail thread and a WhatsApp chat and starts assembling. The engineering is sound. The record around the engineering is not, and the record is what you will be asked for.

  • A contractor is building from Rev B while your office has already issued Rev D
  • Site observations come back as a notebook and forty photos on a phone, then get retyped into a report at 9pm
  • Permit and inspection deadlines live in one person's head and one person's calendar
  • Electrical, structural and mechanical each keep their own list of open items, and nobody sees the whole project
  • Nobody in the office can say which deliverables are due this month without asking each engineer

What changes

The project is the container. Drawings, specifications and calculation notes are documents on the project, each with labels for discipline and revision, an owner, a due date and a link to the client. Pin the current set and archive the one it replaced, so the file someone opens first is the one you issued. Attain OS has no version history: replacing a file overwrites it, so upload each issued revision as its own document.

The site visit gets structure. Build the inspection checklist as a form, with checkboxes, readings in number fields, dropdowns and notes, and open its link on a phone at the site. Forms have no photo field, so each finding that needs action becomes a Work Board ticket with its photos, an owner, a priority and a due date. Or describe the findings to Atty in the web chat, or by voice note on WhatsApp where your organization has it enabled, and it drafts the note and the tickets for you to approve.

Deliverables and dates stop living in one head. Each deliverable is a ticket moving through the statuses you define, with a discipline label and an owner, and permit submissions, renewals and authority inspections are calendar events with reminders. When you issue, share the document by a public link that counts views and can be turned off, or email it from the client's record, where the email is logged. It is a record of what you did, not a transmittal system with read receipts.

Findings captured once, at the site

Checklist answers are saved as form submissions, and findings become tickets with photos and an owner. Atty can draft the inspection note from what you tell it, for you to approve, so the evening retyping gets shorter. Atty cannot read form answers, so the report is still yours to finish.

Fewer mistakes from opening the wrong file

When the current set is pinned and superseded revisions are archived and labelled, the file your team shares is far less likely to be the old one. Documents, forms, a calendar, client records and team chat come in one workspace instead of separate subscriptions. Attain OS does not track fees or hours.

Every open item has an owner and a date

Findings and deliverables carry an assignee, a priority and a due date instead of sitting in a report nobody actioned. Documents show who uploaded them, and the project feed, your share links and the emails sent from a client's record leave a trail of what happened and when.

Carry more projects per project engineer

A consultancy usually caps out on senior attention, not on technical capacity. When each project keeps its files, checklists, dates and deliverables in one place, and Atty drafts the tasks, tickets and notes for your approval, a principal can follow more projects without being the only person who knows where each one stands.

The apps that carry the work

Every one of these is built in and already connected to the others. Nothing here is an integration you have to buy or wire up.

Documents

Drawings, specs and calculations on the project

Upload drawings, specifications and calculation notes of any file type to the project, label them by discipline and revision, assign an owner and link them to the client. Pin the current set and archive what it replaced. Images, PDFs and audio preview in the app. There are no folders and no version history, so each revision is its own document.

  • Discipline and revision labels on every drawing and spec
  • Current set pinned, superseded revisions archived
  • Search and filters by label, assignee or uploader
Documents
Doc Analysis

A first read of the long specification

On a document, run an analysis: a summary, text extraction, a translation or your own instruction, such as listing the inspections a specification requires. It runs in the background and the result is saved with the document, where you can copy it or turn it into a note. Check it against the source before you rely on it.

  • A summary of a tender or scope document before the fee conversation
  • A custom instruction that lists the obligations in a specification
  • Text extracted from a scanned permit or letter
Doc Analysis
Forms

Site inspection checklists on a phone

Build a checklist with checkboxes, number fields for readings, dates, dropdowns, ratings and text, and open its public link on a phone with no login. Answers are saved as submissions in a table you can filter. Forms have no photo, file or signature field, so the photos go on the ticket for the finding.

  • A standard checklist per discipline or project phase
  • Readings and measurements in number fields
  • Submissions filtered and reviewed back at the office
Forms
Work Board

Deliverables and findings on one board

Each deliverable or site finding is a ticket with an owner, a priority from P0 to P5, labels such as the discipline, a due date and images. Set your own statuses, such as in design, internal check, issued and superseded. The board has no dependency links or Gantt chart, so sequencing between disciplines is still a conversation, but everyone sees the same open items.

  • Deliverables moving from design through internal check to issue
  • Non-conformities logged as tickets with photos and an owner
  • Discipline labels so electrical, structural and mechanical items share one board
Work Board
Calendar

Permits, inspections and statutory dates

Put permit submissions, renewals, authority inspections and site visits on the project calendar as events or milestones, with attendees from your team, RSVPs and a reminder at the lead time you choose. Task and ticket due dates appear in the same view. You can download a date range as an .ics file; the calendar does not sync with Google or Outlook.

  • Permit and approval milestones with a reminder ahead of the date
  • Renewal and expiry dates that repeat every year
  • Site visits and authority inspections with the team who must attend
Calendar
Sharing Hub

Issued documents shared by link

Create a public link to a document, such as an issued drawing set or a report, and send it to a client, contractor or authority. The Sharing Hub lists your links with a total view count and a QR code, and you can turn a link off when a revision is superseded. It does not record who opened a link.

  • An issued set shared by link instead of an email attachment
  • Old links turned off when a revision is replaced
  • A QR code for a document someone needs on site
Sharing Hub
Customer Management

Clients and their details in one record

Keep a record for each client with contacts, address, preferred contact method, labels and custom fields for things like permit numbers or site access. Tasks, tickets and documents can link to the client, and a one-off email sent from the client's page is logged in its Communications tab. Inbound email is not captured, so it is not a full correspondence history.

  • Permit numbers and site access notes in custom fields
  • Documents and tickets linked to the client
  • One-off emails to a client logged on their record
Customer Management
Budgets

Project expenses against a budget

Track what a project spends on outside costs, such as subconsultants, lab testing and permit fees, as budget items with an estimate, the amount actually paid, the vendor and a receipt. An item turns red when the amount paid passes the estimate. Budgets do not track hours, billed fees or profitability, and Attain OS does not send invoices.

  • Subconsultant and testing costs per project
  • Estimate against amount paid on each line
  • A receipt kept on the item it paid for
Budgets
Working guide

Engineering project management for a consultancy means keeping each project's current drawings, site findings, permit dates and deliverables in one place, with an owner and a date on every open item. Label each issued revision as its own document, because the workspace keeps no version history and a replaced file is overwritten. The test is simple: anyone in the office should be able to say which set was issued last and who must act next.

In practice

A week from the site visit to the issued set

  1. Monday · open items by discipline

    The project lead reviews open items by discipline: electrical, structural, mechanical and civil. Every item has a named owner, a priority and a due date, so the review ends with names rather than a list of problems. Items waiting on the client sit in a status you create for that purpose.

    Work Board
  2. Tuesday · the site visit

    The engineer on site opens the inspection checklist on a phone. Readings go into number fields, and each answer is saved as a submission in the form's table. Forms take no photos, so every finding that needs action becomes its own ticket with photos, an owner and a due date.

    Forms
  3. Wednesday · a revision is issued

    The office uploads the issued drawing set as a new document, labelled with its discipline and revision. The current set is pinned, and the one it replaced is archived. The workspace does not compare the two files, so the revision label and the archive carry that job.

    Documents
  4. Thursday · permit and inspection dates

    The permit submission, the renewal and the authority's inspection go on the project calendar as events, with the people who must attend invited. Due dates for tasks and tickets show alongside them. Dates leave the calendar as .ics files only.

    Calendar
  5. Friday · the issued set goes out

    Share the issued set by a public link, and turn the link off when that revision is replaced. Client contacts, addresses and permit numbers stay on the client's record, with site access notes in custom fields. The Sharing Hub shows view counts but does not record who opened a link.

    Sharing Hub
Workflow map

Which app holds each part of the record

JobAppWhat it does here
Drawings and specificationsDocumentsUpload drawings, specifications and calculation notes of any file type, label each one with its discipline and revision, and assign an owner. Pin the current set and archive what it replaced. Images, PDFs and audio preview in the app, but there are no folders and no version history.
Reading a long documentDoc AnalysisRun a summary, a text extraction or a translation on a long specification or a scanned permit letter. The result is saved with the document, where you can copy it or turn it into a note. Check it against the source before anyone relies on it.
Site inspection checklistsFormsCombine checkboxes, number fields, dates, dropdowns and text into one checklist, and open its public link on a phone with no account. Responses are saved as submissions you can filter. Forms have no photo, file or signature field, so photos belong on the finding's ticket.
Findings and deliverablesWork BoardEach deliverable or finding is a ticket with an owner, a P0 to P5 priority, labels such as the discipline, a due date and images. Set your own statuses, such as in design, internal check and issued. The board has no dependency links or Gantt charts, so sequencing between disciplines stays a conversation.
Permits and statutory datesCalendarPermit submissions, renewals and authority inspections sit on the project calendar as events. Only workspace members can RSVP. Use the .ics export to give a date range to someone outside the workspace.
Client and contractor recordsCustomer ManagementEach client has a record with contacts, an address, a preferred contact method and custom fields such as permit numbers. Tasks, tickets and documents can link to it. A one-off email sent from the record is kept on it, but inbound email is not captured.
Start here

Records to adapt for your consultancy

Technical specification page

State goals, non-goals, interfaces and failure cases before a design is built, so reviewers can object to specific decisions.

Meeting minutes page

Put design and site meeting decisions and actions near the top, with the open questions for the next review.

Contract approval form

Give reviewers the contract type, value and template departures up front, since the form records the request but does not approve it.

Workplace incident report

Capture what happened, where and what was done while the facts are clear, without replacing an emergency call or a formal injury log.

Invoice submission form

Record supplier invoices with the purchase order and budget line, so your accounts team can check them through its own process.

Mistakes to avoid

Three record gaps that cost the most

Replacing a file and calling it a revision

The workspace overwrites a file when you replace it and keeps no copy of the earlier one. If a contractor is building from the old set, nothing in the file will say so. Upload each issued revision as its own labelled document, and archive the one it replaced.

Leaving an old share link live

A public link stays on until you turn it off, so a superseded drawing can keep reaching a contractor after the new one is issued. Turn off the link when the revision changes, and send the new link with the transmittal you already use. The Sharing Hub shows views but not who opened the link.

Treating a checklist as the report

A form holds the answers from the site visit, but it cannot hold the photos, the sketch or the judgement behind a finding. Write the findings into the report yourself, and use tickets to track each action. A saved submission shows that something was recorded, not that it was checked.

Working checklist

Before a set is issued, and before a site visit

Before a set is issued

  • Label every drawing with its discipline and revision.
  • Upload the issued set as a new document rather than replacing the old one.
  • Pin the current set and archive the superseded one.
  • Turn off the share link for the superseded revision.

Before a site visit

  • Open the inspection checklist link on the phone before leaving the office.
  • Confirm the client's site access notes on the client record.
  • Agree who owns the follow-up for each expected finding before the visit ends.
What this agreement means

What the workspace keeps and what it does not

  • Drawings, specifications and calculation notes are kept as documents, labelled by discipline and revision, with an owner and a link to the client.
  • Checklists, findings, permit dates, client records and outside project costs sit beside the files they relate to.
  • There is no CAD or BIM authoring, no version history, no fee or hours tracking and no invoicing.
  • Professional sign-off, stamping and issue decisions stay with your engineers and their licensing process.

Permit, inspection and stamping rules differ by jurisdiction. Confirm them with your licensing body or with the authority that will receive the work.

Frequently asked questions

Is this a CAD or BIM tool?

No. It does not author, open or coordinate geometry, so your team keeps working in the modelling software it already uses. The workspace holds what surrounds those files: the documents themselves, their labels, inspection checklists, deliverable tickets and dates.

Does it control revisions or keep version history?

No. There is no version history or formal document control, and replacing a file overwrites it. Upload each issued revision as its own document, label it with the revision, pin the current one and archive the rest.

Can I see every project's status on one dashboard?

Not across projects. A project's Home dashboard shows only that project's apps, and there is no portfolio screen. Switch between projects to check each one.

Can I use it to track project costs?

Only outside costs. The Budgets app compares items such as subconsultant fees, lab testing and permit fees against an estimate, with the amount paid and a receipt. It works in US dollars only and does not track hours, billed fees or profitability.

Can a contractor or client see only their part of the project?

Not by item or scope. A public link shows one document to anyone who holds it, and a project member sees all of that project's records. Share the document itself, not the project, when someone outside the team needs one file.

Who Attain OS Is For — One Operating System for the Team You Actually Run

Attain OS BETA