UPLOAD THE DOCUMENT. LIA DOES THE READING.
Lia reads the prime contract, the spec book, the drawing set, the schedule, 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.
.svg)
Contract value, completion dates, milestones, liquidated damages, payment terms, retainage, and notice requirements, each pointing to the page it came from. Upload the signed contract and Lia checks it against the record and flags what doesn't match.
Generate an AIA-form contract from a mapped template, with the extracted fields filled in and the rest left as fillable fields for your team. 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 $1.25M AIA A101 for a site development package. Upload it. Lia proposes five fields, each tagged to the page it came from, and the PM confirms them. 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.
THE SUBMITTAL LOG, BUILT FROM THE SPEC BOOK
Lia reads the spec book cover to cover, tags every section with its CSI code, and builds the submittal log and the material list from it. Your team verifies it.
Lia proposes each submittal it finds in the spec: title, type, and the CSI section it came from. Approve, edit, or reject each line. Approved lines land in the log and go to the sub whose subcontract scope covers that section.
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 and the material list. Your team verifies both. 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 CSI section and routed to the sub that owns it. 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. One click raises a pre-filled RFI from the change, or links it to an open RFI.
Start an RFI from the sheet or ask Lia for one in the chat. Lia writes the subject and description. You review it, fix what needs fixing, and send.
Revision 3 lands Friday. Lia files 42 sheets by discipline and overlays S-201 against revision 2: a beam size changed at grid line C. The PM clicks the change, tightens the RFI Lia drafted, and sends it to the engineer.
Unusual title blocks can be misfiled, so check the index before you publish the set. Lia also reads the scale and proposes quantities, which you check first.
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.
THE SCHEDULE, READ AND WATCHED
Upload the schedule and Lia pulls the activities, dates, and milestones into Linarc. Once it’s in, Lia flags what’s holding the job up and tells the people watching an item when it moves.
Upload your project schedule in MPP, Primavera P6 (XER), or CSV format. Lia reads the activities, durations, dates, and milestones into a proposed schedule. You approve it before it becomes the baseline.
Lia flags the activity that is holding up the ones behind it, before the crew finds out on site.
Watch a submittal, an RFI, an activity, or a piece of equipment and Lia tells you when it changes, slips, or gets answered.
The PM uploads the owner’s updated schedule. Lia reads 180 activities and milestones into a proposed schedule. The PM checks the dates against the contract milestones and approves. From then on, anyone watching the elevator inspection gets told the moment its date moves.
ASK THE PROJECT A QUESTION
Lia answers questions from your own project data and keeps the thread across the project. Ask it to do something and it does it, with your sign-off before anything saves.
"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, as a table, a list, or a link back to the source. One search covers every module, document, and thread.
Draft the RFI, update the field, log the item. Lia takes the action from the chat and shows you what changed before it saves. 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 links to both. One search, not four modules, and no waiting on the PM.
WHAT LIA WILL AND WON’T DO
Plain terms. Here is where the line sits.
Every extraction arrives as a draft you read line by line before anything enters the job.
Nothing saves to the job on Lia’s output alone. You approve, or it does not land.
Every proposed field points to the page it came from, so you check the source.
If Lia cannot point at a page, it does not fill the field. You check the source, not the guess.
No prior project history needed. Lia reads the documents on the job in front of you.
No training window, no back catalog to load first. The job in front of you is enough.
Marked-up contracts and odd title blocks get a closer read. Lia builds the log. Your team verifies it.
A person signs off every time. A first pass is a first pass, never the last word.
BUILT FOR THE PEOPLE WHO DO THE READING
The ones who turn a stack of PDFs into a job.
.webp)
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
