Construction Document Control System

Construction document control, made simple

Autodocs manages every construction document from day one to handover: RFA, RFI, instructions, variation orders, drawings and daily reports. Every document is numbered, routed to the right person, and signed.

Request a demoExplore the system
Document NumberAuto-generated
RFAType
·
PRJ02Project
·
CONFrom
·
CSCTo
·
FACSubject
·
0421Running
·
R01Rev
In reviewRev 01
CONCSC
A configurable, frozen code — never re-sequenced, never overwritten. Reads the same on screen, on paper, and in the audit log.
OBS ROUTED
CON → CSC
Traffic Map — every document on its routeFrom a real project
Autodocs Traffic Map — documents moving through Create, Review, Other Parties Review and Published, with live counts at every station
OWASP audit closedRestore drill: 1.8M rows in 11 minRTO 4 hr · point-in-time 7 daysYour data never trains AI modelsRead the 21 answers →
Day to day

Spend less time chasing documents

Same project, same team. A different working day.

The familiar way
A simpler way
The site group chat asks for the latest drawing. Three versions get attached.
Nobody asks. The approved revision is the only one in the system.
Hours preparing binders for the weekly meeting.
Open the dashboard. The summary is ready.
A VO surfaces in a meeting. No one can say who ordered or signed it.
Every VO references its site instruction, with signatures and values.
Dozens of binders searched page-by-page for evidence.
Print the report. The full signature chain is in it.
Live from our database

Real projects, counted right now.

These numbers come straight from the Autodocs production database, updated continuously. Counts only — project details stay private.

0
Documents issued
0
Companies on board
0
Questions answered (RFI)
Documents on the platform — cumulative by monthNov 2026 · 10,969
+359docs/month
average, last 3 full months
▲ 1.3× vs last year
By document type
RFA5,096Approval requestsRI1,972Inspection requestsDR1,471Daily reportsRW1,141Work requestsRFI810Information requestsEI200Engineer's instructionsSI128Site instructionsVO116Variation ordersPMI27PM instructionsDEF4CONTRACT2ContractsSAFETY1SafetyMCV1
Why Autodocs

From day one to handover

Five things Autodocs does that a shared drive can’t.

Keep every document in order.
Every record is structured, numbered and searchable, from day one to handover.
See budget and contracts.
Contract and VO values sit beside the documents and update as work is approved.
Coordinate without chasing.
Requests route to the right person automatically.
Keep every party aligned.
Employer, Engineer and Contractor see the same live record.
Lose nothing. Miss nothing.
Due dates, overdue flags, and a history nobody can rewrite.
The FIDIC parties

Three parties. One source of truth

The three FIDIC parties — Employer, Engineer and Contractor — work on the same live documents. Each sees what their role needs.

OWNEmployer (Owner)
See the whole project without waiting for reports.
  • Approvals arrive in order, ready to sign.
  • Real-time view of progress, budget and overdue items.
  • PM Instructions carry contract weight and a full trail.
ENGEngineer (Consultant / CM)
Run every review from one queue.
  • Every document line flows through you, in a clear review queue.
  • Technical answers and design reviews are recorded, signed and citable.
  • VO price evaluation is a formal signed step in the workflow.
CONContractor
Submit from site. Track every request.
  • Create RFA, RFI, work requests and daily reports from site.
  • Know the status of every request.
  • Finish a drawing and submit it for approval in the same system.
Every document flows through the Engineer (CM). Nothing slips past.
Document Modules

Twelve document types. One control system

Each type has its own form, numbering and approval path. Pick one to see it.

RFARequest for Approval
RFA·PRJ02·0421
In review
Modules
Curtain wall mock-up sample
Routed · OBS
CONCSC
Feature cinema

Watch it work, not a slideshow

Demo clips cut straight from the product, pulled live from the changelog — the day a feature ships with a clip, it shows up here.

การลงนามเอกสารดิจิทัลบนไฟล์ PDF2.0.2-ADD-01 ↗
ผู้ตรวจสอบสามารถบันทึกหมายเหตุและทำเครื่องหมายบนไฟล์เอกสารที่ผู้รับเหมาจัดส่ง ลงลายมือชื่อของตน และจัดเก็บเป็นเอกสารฉบับลงนามเพื่อส่งต่อไปยังขั้นตอนถัดไป เอกสารที่ลงนามแล้วจะมีตราประทับดิจิทัลและรหัส QR สำหรับตรวจสอบความถูกต้องและยืนยันว่าเอกสารมิได้ถูกแก้ไขภายหลัง ทั้งนี้ระบบรองรับการจัดเก็บลายมือชื่อได้หลายรูปแบบและเลือกใช้ได้ในขณะลงนาม
Workflow

Flexible workflows, built for Thai construction

Each document type carries its own path, and every path can be customised to how your project actually works — steps, parties and SLAs included.

Workflow builder — an RFA template as configuredFrom a real project
The Autodocs workflow builder — an RFA template running Create, review stages with signing and due dates, fan-out to other parties, revise loops and Published
Every step carries an SLA you define in days — e.g. CM review within 3 days, other parties reply within 5 — with overdue flags and alerts when time runs short.
Cost & Contract

Follow every contract and every baht

Contracts and variation orders live beside the documents that created them, with values that update as work is approved.

Contract & money path
Illustrative values — real contract figures stay private to the project.
Variation Orders — live totalsVAT excluded
Total addition
139,000.00
Total omission
0.00
VO·PRJ02·0001
Increase glass panel thickness
+75,000.00
VO·PRJ02·0006
Upgrade to HVAC system
+64,000.00
Total+139,000.00 THB
Tax & currency built in
Project tax rate and currency are set once — every contract and VO computes consistently.
SI → VO, linked
A variation order references the site instruction that caused it — the money trail starts at the source.
Values hidden by role
Parties not involved in a VO cannot see its monetary value — commercial detail stays contained.
Autodocs Intelligent

Let the system follow up for you

AI reads the document register and flags what threatens the handover date. Alerts reach your team on LINE and email.

AI risk summary
SI·0017 — schedule-critical: delay impacts the handover date.
SI·0010 — fire-safety inspection: delay affects visitor safety.
VO·0024 — high-cost change on a critical system; review first.
LLINE Connect
What’s overdue?
6 RFIs pending. Longest: “Floor load capacity” — 118 days (due 25 Nov).
Which ones relate to glass work?
2 items: glass panel dimensions (due 9 Dec) and revised panel design.
Email digest
HELLO,
URGENT DOCUMENTS ARE WAITING
SI·0022
Structural material change
01 Apr
VO·0008
Scope adjustment — west wing
01 Jan
RFA·0007
Protective coating material
09 Dec
Off by default, and enabled per project. Contracts, pricing and user data are stripped before anything is sent for analysis.
Trust & Control

Accountable at every step

Construction documents are legal documents. Every step is signed, logged and permissioned.

FIDIC applied
Instruction and variation workflows follow FIDIC contract practice — SI, EI and VO carry the authority the contract defines.
Digital signature
Every review step is signed on screen with name and timestamp — approvals carry real accountability and resist forgery.
Three-level permissions
Confidential, role-based and assigned documents — contracts stay private to their parties; VO values hide from outsiders.
ISO 19650-aligned drawings
Structured drawing numbers, floor-by-floor location dashboards, and revision-controlled sets from tender to as-built.
Full audit trail
Every action, party and timestamp is logged. Printable reports carry the whole signature chain — defensible to handover.
Security

Answers your IT reviewer can check

Enterprise procurement sends a security checklist before it sends a contract. Ours is already answered, item by item, from the system as it is built — not as we would like to describe it.

21
assessment items answered
1,808,737
rows restored in a drill
11 min
to restore the database
4 hr
recovery time objective
OWASP audit closed
A full internal audit against OWASP Top 10:2021, API Security Top 10:2023 and ASVS 5.0 Level 2 — every finding documented, every fix carrying a regression test. External penetration testing can be arranged on request.
A restore that was actually run
On 27 August 2026 a copy held outside the database provider was restored into an empty database in another region: 183 tables and 1,808,737 rows came back with no missing rows and no foreign-key violations, in 11 minutes. The drill repeats at least once a year.
Recovery you can plan around
Point-in-time restore to any moment within 7 days, daily snapshots kept 30 days, and a 4-hour recovery time objective for the service as a whole. Hosting, database and file storage each run on an independent provider, so no single one can take the service down.
Access proven at every request
Role-based permissions from an administrator-editable matrix, enforced on the server rather than hidden in the interface, with an optional email one-time-password step-up at sign-in that each user can turn on from their own account.
Logged, including the refusals
Authentication events, workflow transitions, outbound email, defect history and authorization denials are each recorded — a denied attempt leaves a trace, not silence. Authentication events are kept for a year.
Six sub-processors, named and under notice
Every provider that touches your data is named with its purpose. Five of the six are risk-assessed and under a data processing agreement; the assessment and agreement for LINE are not yet in place. We give 30 days written notice before any of them changes.
Published disclosure · last reviewed 27 August 2026
Where Autodocs fits

Every tool has its place. We fill the gap

Drives keep files moving and chat keeps people talking. Autodocs adds the part construction documents still need.

In product

One console for the whole project

A document register where every row carries its number, party and stage.

RFA/Receive
5
PT
DAILY REPORT
RFA12
Document
Receive4
Sent
REQUEST INFO
SITE INSTRUCTION
RFA · Receive
4 awaiting your review · Project PRJ02 — Phase 2
+ New RFA
No.SubjectPartyStage
RFA·PRJ02·0421Curtain wall mock-up sampleCON → CSCIn review
RFA·PRJ02·0418Waterproofing method statementCON → CSCApproved
RFA·PRJ02·0415Rebar coupler submittalCON → CSCChange req.
RFA·PRJ02·0410Facade anchor detailCON → CSCPublished
RFA·PRJ02·0405Lift shaft layoutCON → CSCFinal review
Live from the changelog

Getting better every single week.

Autodocs is under active development. This list is read live from our release notes — the moment something ships, it shows up here.

v2.0.7Latest releaseAUTODOCS 2.0.7Live23 Oct 2026
  • Security
    Responding to PHP2Shell: Autodocs now runs on TypeScript, and the legacy version has been patched
    To all Autodocs users and customers: there has been recent news of two flaws in the PHP language known as PHP2Shell (CVE-2026-109618 and CVE-2026-109619). They allow an attacker to run commands on a server that uses PHP without signing in. The PHP project released fixed versions on 21 October 2026, so the Autodocs team would like to tell you where both versions of the system stand. The current Autodocs is not directly affected by these flaws, because the team has moved its main platform from PHP to TypeScript and the system no longer runs on PHP. The legacy Autodocs still runs on PHP, so the team moved it to PHP 8.4.27, a version that fixes these flaws, on 22 October 2026, Thailand time. As for how the team handles security patches, with every major release, and at least every quarter, the team tests and applies the system's security patches. For a serious vulnerability in a package the system uses, the team starts testing the patch within 48 hours of the package's maintainer releasing the update, and releases the update as soon as testing is complete, without waiting for the regular update round. You do not need to do anything.
    2.0.7-SEC-01

See it on your own project

Tell us about your project and we’ll walk through how Autodocs handles your real documents.

We reply within one business day.or call 02-118-6324 ext. 4