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.
DocumentsDrawings, 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
DocumentsDoc AnalysisA 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 AnalysisFormsSite 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
FormsWork BoardDeliverables 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 BoardCalendarPermits, 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
CalendarSharing HubIssued 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 HubCustomer ManagementClients 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 ManagementBudgetsProject 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