Every document carries its number, revision and status.
Revisions are tracked on the document itself, and replaced documents carry a Superseded status instead of quietly disappearing, so a site team can see which sheet is current.
Engineering document control
Every drawing, revision and reply — under control.
ArcScale EDMS is one workspace for the documents, transmittals, correspondence and approvals that run a construction or engineering project. Numbering, review codes, deadlines and an audit trail are built in, so the right revision reaches the right people, on time, with proof.
- Application hosted in Germany (EU)
- English & Arabic interface
- Your data, exportable at any time
AApproved
Document no.MHT-B-STR-DWG-1001
RevC
TitleLevel 3 Slab — Reinforcement Layout
Disc.Structural
Numbering rule · {PROJECT}-{DISCIPLINE}-{TYPE}-{SEQ}
- Auto-numberingConfigurable rule per organization, sequenced per discipline and type
- A · B · C · DReview codes on transmittals, with linked responses
- 11 lifecycle statesFrom Draft and Under Review to Issued and Superseded
- 7 registersMaster, drawing, transmittal, correspondence, ITR/MIR, NCR/SOR, NOC: export to Excel or PDF
- Append-only logEvery action recorded; filter and export to CSV or Excel
Why teams switch
Document control rarely fails loudly. It fails one forwarded email at a time.
Reviews follow a route, with an owner and a deadline.
Approval workflows move a document stage by stage, each with a responsible role and SLA days. Overdue stages surface on the dashboard and in reminders.
Correspondence that expects an answer, and chases it.
RFIs, NCRs, technical queries and inspection requests get a reference number, a response-required flag and a due date, with reminders when a reply is missing.
An audit trail you can hand to an auditor.
Uploads, status changes, approvals, sign-ins and access to files are written to an append-only activity log that cannot be edited, then filtered and exported in minutes.
Inside ArcScale
The working screens, as your team will use them.
These are real screens from ArcScale, shown with fictional project data.
A document register that stays honest.
Each project keeps its documents numbered, revisioned and filterable by discipline and type, in a list or folder view.
- Numbers generated from your rule, e.g. MHT-B-STR-DWG-1001
- Revision history kept on every document
- Bulk upload, and an import wizard for your existing folders
DraftUnder reviewApproved w/ commentsFor revisionIssuedSuperseded
Approvals that know whose turn it is.
Reusable workflow templates route a document through ordered review stages, from technical check to final approval.
- A responsible role or person for every stage
- SLA and reminder days per stage, with overdue detection
- “Pending your action” so reviewers see their queue first
Project correspondence, out of personal inboxes.
Letters, RFIs, NCRs, notices, technical queries and inspection requests live with the project, with sender, recipients and history.
- Automatic reference numbers per project and year
- Response-required flags, due dates and threaded replies
- Reminders for unread, unanswered and overdue items
Registers your client actually asks for.
Live registers are built from the work itself, so nobody re-types a transmittal log at month end.
- Master, drawing, transmittal and correspondence registers
- ITR/MIR, NCR/SOR and NOC tracking
- Filter by project, status and date; export to Excel or PDF
A complete record of who did what, and when.
The activity log captures actions across documents, transmittals, correspondence, tasks and sign-ins. Entries can be added, never edited or deleted.
- Filter by project, entity, action, user and date
- Export to Excel for audits and dispute files
- Visible to admins, project managers and document controllers
How it works
How a submission moves through ArcScale.
The same path your document controllers already follow, with the bookkeeping done for them.
Upload & number
The document gets its number, discipline, type and revision on upload.
MHT-B-STR-DWG-1002 · Rev BInternal review
A workflow routes it through your checkers, each stage with an owner and an SLA.
Checker → Senior engineer → ApprovalTransmit
A transmittal sends it with a stated purpose and due date, and is logged.
For information · review · approval · constructionReview code returned
The reviewer answers with a code, and a linked response transmittal records it.
A · B · C · DIssue or resubmit
Approved documents are issued; the rest go back for revision. The registers update with every step.
Issued · For revision · Superseded
AApprovedProceed as submitted
BApproved with commentsProceed, incorporate comments
CRevise & resubmitUpdate and submit again
DRejectedNot accepted
Built for
For the people who answer for the documents.
Submit with confidence
Method statements, shop drawings and ITPs, numbered and tracked from first issue to approval, with RFIs and NCRs on the same project.
- Method statements
- Shop drawings
- ITPs
Review without the chase
Incoming submittals arrive with a purpose and a due date; review codes and comments go back on the record.
- Submittal reviews
- Review codes
- Comments
See the real status
Registers, dashboards and an activity log that show where every package stands, without waiting for a monthly report.
- Registers
- Dashboards
- Activity log
Control beyond projects
Policies, procedures and internal memos can live in the organization-wide area, under the same numbering and audit trail.
- Policies
- Procedures
- Internal memos
Bring partners into a project. Invite other organizations as observers who can read shared documents and transmittals, or as contributors who can also upload and send transmittals. Your internal correspondence stays yours.
- Submittals
- Multi-party submission chains: forward, review, return, resubmit, decide
- Meetings
- Agendas, minutes, attendees and action items
- Tasks & calendar
- Assigned actions with priorities and due dates, in one calendar view
- Deliverables
- A deliverables register from not started to closed
- Search
- One search across documents, correspondence, meetings and projects
- Delegations
- Hand over authority during leave, for a set period
- Role overrides
- Time-limited project roles on top of organization roles
- Team chat
- Project and department channels, in real time
Data & security
Your documents are evidence. We treat them that way.
Everything here describes how ArcScale runs today, not a roadmap.
- Application hosted in Nuremberg, Germany (EU)
- Append-only activity log
- Role-based access, per project
DataLocation
Application & databaseNuremberg, Germany (EU)
Uploaded filesCloudflare R2 object storage, or the application server
Encrypted backupsCloudflare R2 object storage, encrypted before upload
TrafficTLS end to end, HSTS enforced
Isolation enforced by the database
Each organization's records are separated with row-level security, and the application runs with least-privilege database access.
Access that matches the project
Roles from admin and project manager to document controller, reviewer and viewer, with project-level overrides and dated delegations.
Backups you can restore
Encrypted daily backups are kept off the server, and restores are tested from those backups, not assumed.
Leave with everything
On exit you receive a complete export: every record as structured data plus all files, with checksums. Deletion then follows the agreed terms.
A data processing agreement
Pilots run under a written DPA that names every sub-processor and where it operates.
No surprise AI
AI features are off by default for every organization. Your documents are not sent to AI providers unless you ask for it.
Managed pilot
Prove it on one live project before you commit.
We set ArcScale up with you and run it on a real project for 60 days, so the decision rests on your own documents rather than a sales demo.
Fit call 30 min
We walk through your projects, numbering rules, review routes and the registers your clients expect.
Set-up with you
We create your organization, import your existing folders, and configure numbering, document types and review workflows.
Live project 60 days
Your team runs real documents, transmittals and correspondence in ArcScale, with us on hand.
Decide
Continue, or leave with a complete export of everything you put in.
Pilot terms, including the data processing agreement, are agreed in writing before any of your data is loaded.
Transmittal
Request a demo or pilot
No.TRS-REQ-0001
Privacy
ArcScale is a personally operated project. We use the details you submit to respond to your demo or managed pilot request. Your request is stored on our server in Germany. We use Resend to email your request details to the ArcScale team. Technical checks help protect the form from abuse. Inquiries that do not become a managed trial or customer relationship are retained for up to 12 months after the last contact. For privacy questions or a deletion request, contact sales@arcscale.org. Please do not include confidential project documents or sensitive information.
Request sent
Thank you. Your request has been sent.
We'll reply to your work email to arrange a time that suits your team.
Questions
Straight answers.
Where is our data hosted?
The application and database run in Nuremberg, Germany (EU). Uploaded files are stored either on that server or in Cloudflare R2 object storage; encrypted backups are kept in Cloudflare R2 and are encrypted before they leave the server. R2 is set to prefer European data centres, but that is a placement preference, not a guarantee of EU residency. Data is not hosted in the UAE today, and the pilot agreement states this plainly so you can confirm it fits your requirements.
Can we bring our existing documents?
Yes. The import wizard takes your existing folder structure, reads document numbers and revisions from file names, lets you review each item, then creates the documents and revisions in a project. Set-up is part of the managed pilot.
Does it work in Arabic?
The interface switches between English and Arabic with a right-to-left layout. Arabic coverage is still being extended across every screen; tell us which areas matter most to your team.
Can our consultant or client work in the same project?
Yes. Partner organizations can join a project as observers (read shared documents and transmittals) or contributors (also upload documents and send transmittals). Correspondence stays inside your own organization.
What happens if we decide not to continue?
You receive a complete export: every record as structured data plus all uploaded files, with checksums so you can verify it. Your data is then deleted under the terms agreed for the pilot.
Does ArcScale use AI on our documents?
Not unless you ask. AI features are switched off by default for every organization, and documents are not sent to AI providers while they are off.
Do you offer single sign-on, e-signatures or an API?
Not today. Sign-in is by email and password with verified email addresses and managed sessions, and there is no public API or e-signature integration yet. If one of these is a requirement, say so in your request and we'll be specific about timing.
Managed pilot
See your own document flow in ArcScale.
Bring one live project. We set it up with you, and you decide on your own documents.
Pilot terms, including the data processing agreement, are agreed in writing before any of your data is loaded.