UPLOAD THE DOCUMENT. LIA DOES THE READING.
Lia reads the prime contract, the spec book, the drawing set, the invoice, and the PO, and proposes the Linarc record each one calls for. You approve every line before it saves. No project history required. It works from the documents on your next job.
UPLOAD THE DOCUMENT. LIA DOES THE READING.
Lia reads the prime contract, the spec book, the drawing set, the invoice, and the PO, and proposes the Linarc record each one calls for. You approve every line before it saves. No project history required. It works from the documents on your next job.
THE JOB IS IN THE DOCUMENTS. THE DATA IS NOT.
Every project starts as a stack of PDFs. Someone reads the contract and retypes the terms. Someone reads 250 pages of spec book and builds the submittal log row by row. Someone tags every sheet in the drawing set. That is days of work before the first thing gets built, and it is where the first mistakes get in.
Retainage, liquidated damages, and notice periods keyed in by hand from the contract, or never entered at all.
A submittal missed because the requirement sat in a Division 01 table nobody got to.
Drawing sheets filed by hand, civil mixed in with structural, and the field hunting for the right one.
What is the retainage on this job? Which spec section covers the door hardware? The answer lives in a module, a folder, or a colleague.
LIA READS. YOU APPROVE.
Lia is built into Linarc. It reads the documents you upload and proposes what belongs in the project record. Every proposal shows where it came from. Nothing saves until you say so.
THE PRIME CONTRACT, READ ONCE
Lia reads the signed prime contract and proposes the job record from it: parties, values, dates, and terms. You approve each field before it saves.
Contract value, completion dates, milestones, liquidated damages, payment terms, retainage, and notice requirements, each pointing to the page it came from.
Generate a completed AIA-form contract from a mapped template with the extracted fields filled in. It is a draft for your review and signature, not a final legal document.
Approved terms become the prime contract on the job. Owner-funded change orders update it. Billing and WIP read from it.
A GC signs a $4.2M AIA A101 for a tenant improvement. Upload it. Lia proposes 10% retainage, $1,500 per day in liquidated damages, net 30 payment terms, and a 14-day notice window, each tagged to its page. The PM confirms the fields. The notice window is on the record before the first delay, not found in the contract after it.
Prime contracts at launch. Heavily marked-up or non-standard contracts still need a close human read.
See Lia on the Financials page →THE SUBMITTAL LOG, BUILT FROM THE SPEC BOOK
Lia reads the spec book cover to cover and builds the submittal log from it. Your team verifies it.
Lia proposes each submittal it finds in the spec: title, type, and the section it came from. Approve, edit, or reject each line. Approved lines land in the log, ready to assign and route.
When a submittal comes in, Lia checks it against what the spec section requires and flags what doesn't line up. The stamped review stays with your reviewer.
Lia builds the log. Your team verifies it. Requirements hide in Division 01 prose and tables, so walk the list before it goes out.
A 260-page spec book lands for a two-story medical office build-out. Upload it. Lia proposes the log: Division 08 door hardware schedule, Division 09 finish samples, Division 23 equipment data, each tagged to its section. The project engineer walks the list, rejects two duplicates, adds one from a Division 01 table Lia didn’t catch, and approves the rest. The log is built from the spec, not from memory.
THE SET, SORTED AND READ ON UPLOAD
Upload the drawing set. Lia sorts every sheet into its discipline, indexes it from the title block, and compares a new revision to the last one. You approve the index before the field sees it.
Architectural, structural, mechanical, electrical, civil. Lia files each sheet where it belongs when the set lands.
Sheet numbers, titles, and scale pulled into a proposed index. Sheets carrying more than one drawing are flagged.
Upload the new set and Lia overlays it on the last one, listing what was added, removed, and changed, each located on the sheet. Link the change to an open RFI or raise one from the sheet.
Start an RFI and Lia writes the subject and description for you. You review it, fix what needs fixing, and send.
Revision 3 of the structural set lands on a Friday. The PM uploads it. Lia files 42 sheets by discipline and overlays S-201 against revision 2: a beam size changed at grid line C. The PM raises an RFI from the sheet, Lia drafts the question, the PM tightens the wording and sends it to the engineer. The change and the question travel together.
Unusual title blocks can be misfiled. Check the index before you publish the set.
See Lia on the drawings →INVOICES AND POs, READ, NOT RETYPED
Lia reads the invoice or purchase order you upload and pulls the fields into Linarc. You check them before they post.
Upload the vendor invoice. Lia reads it and brings the fields into the record, so nobody keys the totals by hand. Used in fabrication shops as well as on the job.
Upload the PO. Lia pulls the fields into Linarc, ready for the PM or contract admin to confirm.
A steel fabricator takes in 30 supplier invoices in a week. Each one is uploaded to the job. Lia reads it and brings the fields into Linarc. The project engineer checks the numbers against the delivery ticket and confirms. The invoice is in the record the day it arrives, read once, not typed twice.
ASK THE PROJECT A QUESTION
Lia answers questions from your own project data and keeps the thread across the project. It reads the record. It doesn’t write to it.
"What is the retainage on this job?" "Which spec section covers the door hardware?" "What did the last RFI to the structural engineer ask?" Lia answers from the project record.
Lia answers. It doesn’t create or edit a record. The better the project data, the better the answer.
Upload a file, or point at one in the project drive, and Lia summarizes what’s in it. A summary, not an extraction. Long or badly scanned files summarize less reliably.
Ask how to do something in Linarc and get the answer where you are. Product help only; it doesn’t read your project data.
The controller is prepping a draw and asks Lia what the retainage terms are and when the last pay app went in. Lia answers from the contract and the billing record and points to the source. No module hunting and no waiting on the PM.
WHAT LIA WILL AND WON’T DO
Plain terms, because you have heard the pitch before.
Nothing saves to the job on Lia’s output alone. Every extraction is reviewed line by line.
Every proposed field points to the page it came from, so you check the source, not the guess.
No prior project history needed. Lia reads the documents on the job in front of you.
Lia proposes, you verify. Marked-up contracts and odd title blocks get a closer read, and the log goes out after your team walks it.
BUILT FOR THE PEOPLE WHO DO THE READING
The ones who turn a stack of PDFs into a job.
The spec book becomes a log to verify, not build. RFIs drafted. Sets sorted on upload.
Contract terms on the record, pointing to the page they came from. Invoices and POs read in, checked, and posted.
The current set sorted by discipline, revisions compared, and the question raised from the sheet.
SEE LIA ON YOUR DOCUMENTS
Watch Lia read a prime contract and a spec book and propose the record. Then decide.
Linarc is always evolving, enhancing, and refining our tools to help you build better. There's more on the way. We'll share more when it's ready.
%201.svg){kind=icon}
Our website uses cookies
