To manage shop drawings, technical data sheets and material certificates in monday.com, create a register where each submittal has a number, type, specification section, revision, current owner, required date and official response. Attach the controlled file or its link, automate reminders and keep technical approval with the authorized person.
Short answer: monday.com can carry the register, responsibilities, deadlines, working versions and reminders. It does not automatically become the contractual document repository. If Procore, Autodesk Construction Cloud, SharePoint or another CDE holds the official record, monday.com should point to that source instead of duplicating it.
This boundary prevents two common failures: a team building from an old revision and a register that says "Approved" without showing who approved which document.
Managing shop drawings, technical data sheets and material certificates in monday.com
The process begins with a distinct item for every required deliverable. Procore also recommends individual registry entries for submittal requirements so product data, shop drawings, certificates and other types remain distinguishable. One item holding a large mixed package becomes difficult to review and distribute.
The three document types prove different things.
| Type | What it describes | Primary control |
|---|---|---|
| Shop drawing | How a product or component will be fabricated and installed | Design conformance, interfaces, dimensions and revision |
| Technical data sheet | Properties, performance and conditions of use for the proposed product | Specification requirements, exact model and selected options |
| Material certificate | Evidence tied to a material, batch, test or declared compliance | Link to the delivered batch, applicable standard and document validity |
Autodesk defines shop drawings as detailed drawings showing how materials or products will be fabricated and installed. Its documentation also separates product data, samples, test reports and certifications. This taxonomy is a practical starting point, and the project can add its own types.
The minimum register to build
Each register item should let someone who missed the email chain understand the document's state.
- Identity: project, submittal number, title, specification section, discipline and type.
- Origin: subcontractor or supplier, submitter and received date.
- Version control: current revision, revision date and link to the previous version.
- Schedule: site-required date, fabrication lead time, approval deadline and days remaining.
- Responsibility: coordinator, current owner, technical reviewer and distribution list.
- Decision: workflow state, response code, required comment and response author.
- Evidence: file, CDE link, annotations and distribution record.
The submittal number should not change when a revision returns. The revision changes while the deliverable identity remains stable. This makes the history searchable without creating competing records.
A readable approval lifecycle
Labels must match the project's actual contractual process. A common sequence looks like this.
- Expected: the register identifies the deliverable, but it has not been received.
- Received for completeness check: the coordinator checks the number, type, specification section and required pieces.
- Under technical review: the authorized person reviews the content.
- Response issued: approved, approved as noted, revise and resubmit, or rejected, according to the project's codes.
- Distributed: the response and correct revision have reached the people buying, fabricating or installing.
- Closed: the register confirms that the relevant team is using the approved version.
The status should not replace the official response. Retain the code, date, author and marked document. For an "Approved as noted" response, the notes must be visible to the people responsible for procurement, fabrication and installation.
Where the files should live
monday.com provides several options. The Files Column accepts PDFs, images and Office documents, among other formats. Files uploaded directly to that column can use versions. monday.com's file versioning documentation says users can review versions in order, restore a previous version as current and add another version. It still describes the feature as a trial.
File annotations let users place comments on images, PDFs and videos, mention a colleague and resolve comments. They can support an internal review, but the contractual response still follows the project's procedure.
Store files directly in monday.com when volume, permissions and the document policy support it. Use a stable link when a specialized CDE controls transmittals, signatures, naming or official retention. In that model, the monday.com register coordinates the work and opens the correct source.
Automate reminders without automating approval
monday.com automations use a trigger, condition and action. In this register they can:
- notify the coordinator when an approval deadline approaches;
- assign the current owner when the workflow state changes;
- flag a required-on-site date that is earlier than the expected response;
- remind a supplier about an expected submittal;
- move a returned revision into the resubmission queue;
- notify distribution only after the official response is recorded.
An automation should never infer technical conformance because a date has passed or a file was uploaded. It prepares, assigns and signals. The authorized reviewer makes the decision.
Connect the document schedule to the job schedule
The register becomes operational when approval dates work backward from the real need. Start with installation or fabrication, then subtract delivery lead time, production lead time, review duration and a resubmission allowance.
A submittal can be "At risk" before it becomes overdue. A shop drawing still in preparation may be on time against its submission date but already threaten fabrication if there is no longer enough time for a correction cycle.
Connect each deliverable to its milestone or work package. The project manager can see why an activity is at risk, while the document coordinator can see which submittal deserves attention today.
Permissions and external partners
The register can include pricing, technical detail and restricted documents. Define access before suppliers and consultants are invited.
Docs created in a Files Column inherit board, item and column permissions according to monday.com's documentation. Board types, column restrictions and guest roles therefore need to be tested with a representative account. Files in a Files Column are not shown in a publicly shared view, but that behaviour does not replace an access policy.
Suppliers can also submit through a WorkForm. Official documentation says an Upload file question feeds a Files Column. Check upload permissions, login requirements and correction rules before making it a contractual channel.
The dashboard and weekly review
The dashboard does not need to count every document. It should surface exceptions that can change the job.
- deliverables expected in the coming weeks;
- approval dates that put fabrication at risk;
- returned revisions with no new submission date;
- decisions waiting by reviewer;
- distributed documents with no receipt confirmation;
- missing certificates for material already delivered.
During the review, every at-risk item receives a next action, one person and one date. Without those fields, the register describes the problem but does not manage it.
When Procore or Autodesk should remain the official system
Procore and Autodesk Construction Cloud provide specialized submittal, package, approval and distribution capabilities. Procore's Submittals documentation includes submitter and approver groups, revisions, distribution and closing.
If the contract, owner or design team requires that system, keep it as the official source. monday.com can receive a status, date and link to coordinate procurement, fabrication, schedule and internal follow-up. An integration or the API can reduce duplicate entry, but its owner and failure behaviour must be documented.
Frequently asked questions
Can monday.com manage shop drawing versions?
Yes, monday.com provides file versioning for files uploaded directly to a Files Column. For a complex contractual workflow, assess whether transmittal, signature, audit and retention requirements call for a specialized CDE.
Can a technical data sheet be approved automatically?
An automation can route the sheet, remind the reviewer and record a status change. The authorized person should make the technical decision according to the contract and design process.
How do you connect a certificate to the right material?
Keep the product, supplier, order, batch, delivery date and intended location in the same item or in connected items. The certificate should point to that specific batch, not only to a generic product name.
Sources and editorial method
Guillaume McGee is a monday.com and AI consultant and product developer at Horizon Nord. He previously owned construction businesses. monday.com capabilities were checked on August 7, 2026 against official documentation for the Files Column, file versioning, annotations and automations. The document taxonomy and controls were compared with official Autodesk and Procore guidance. The proposed model is a coordination method, not a contractual interpretation.
certified partner