Document Controller

New

Yamas Al-Arabia Construction & Contracting

📍 Riyadh, Saudi Arabia 📅 Posted today 🔎 Ref: #34995
💼 Full Time
💼 Job TypeFull Time
📍 LocationSaudi Arabia
🏙 CityRiyadh
📄 Experience3 Years; Proven document control experience on construction projects; Experience managing correspondence, transmittals, submittals and drawing registers
📅 Posted DateToday

Document Controller Jobs in Riyadh – Job Overview

Yamas Al-Arabia Construction & Contracting is hiring for Document Controller Jobs in Riyadh, Saudi Arabia. For applicants exploring Document Controller Jobs in KSA, Yamas Al-Arabia Construction & Contracting lists a Document Controller vacancy in Riyadh, Saudi Arabia. The position joins the company's construction project teams in Riyadh. The notice lists this address: RAWA2938, Northern Ring Branch Cross Abu Bakr Al Siddiq Road, Al Wadi Dist., Riyadh. This advertised focus covers construction records, document logs, filing systems and written and spoken English.

Job description

In general construction practice, document control starts with identifying the purpose of each record. A drawing carries design information, while correspondence records requests, decisions or instructions. A submittal presents information for review, such as details of proposed materials. A transmittal lists the documents sent together and provides a delivery record. Before organising these records, the controller checks the project's document numbering and filing rules. These rules connect each file to a project, document type and revision. However, a revision number alone does not show whether someone approved the content. The controller therefore keeps document identity, review status and intended use separate. This helps users understand what they can safely rely on. The controller also checks which records belong together, so related submissions do not become isolated files.

When a submission arrives, the controller compares its attachments with the covering list. This check covers document numbers, titles, revisions and the number of files. Next, the controller opens the files to check that their contents remain readable. A matching file name does not prove that the attachment contains the right drawing. The controller also checks the sender and receipt date before entering the submission. If the package lacks information, the sender needs a clear request identifying the gap. Meanwhile, the record should show what actually arrived rather than imply a complete package. Technical reviewers assess the design or material; document receipt does not replace their decision.

Document Controller Jobs in Riyadh – General Occupational Context

After checking the package, the controller sends it through the agreed review route. The register links the submission to its reviewer and any assigned response date. Because several people may review related files, each transfer needs a clear record. The controller checks who currently holds the submission before following up on progress. A useful follow-up identifies the document reference and the response still needed. However, the controller should not change a technical decision to clear an overdue item. If responsibility remains unclear, the project lead can confirm the correct reviewer. Once a response arrives, its reference and status need to connect with the original submission. That link keeps later searches meaningful.

One practical uncertainty occurs when a contractor sends two packages under the same transmittal number. The second email includes an extra drawing but gives no explanation for the change. Instead of replacing the first package, the controller compares both lists and preserves both messages. Then the sender needs to confirm whether the later package replaces or supplements the first. The reviewer also needs to know that the contents differ before continuing the assessment. Until clarification arrives, the record should make the unresolved difference visible. After confirmation, the controller links the explanation to both packages and updates the review record. This preserves evidence of what each recipient received.

Coordination and completion

When reviewers return comments, the controller connects them to the exact document revision. Otherwise, a later response may appear to address a different version of the design. The outgoing record should identify the files, recipients and purpose of the issue. If a new revision replaces an earlier issue, users need a clear current version. Older files still support the project history, so the controller retains their traceable links. Superseded means that a newer issue has replaced an earlier one. The filing arrangement should distinguish these older records from current information. Meanwhile, reviewers decide whether comments need further action; the controller records that decision without interpreting technical acceptance.

Towards project handover, the controller compares the required document list with the available records. This check looks beyond file counts because a folder can contain several outdated copies. Each final record needs an identifiable reference, revision and location in the handover index. If an item remains missing, the responsible team needs its reference and required next action. The controller separates missing documents from files that still await a review response. Then the receiving team can see which gaps affect its own checks. Before closing the record set, the controller tests whether the index leads to readable files. A clear history also helps future users understand how the final issue developed. Where the receiving team reports a broken link, the controller corrects it and checks the same path again.

Typical Duties & Responsibilities (General Role Guidance)

  • Maintain a correspondence index linking letters to their replies, so staff can identify unanswered requests without checking every message.
  • Check document distribution lists against current project contacts, and flag outdated details before notices reach the wrong people.
  • File meeting records under the relevant project references, keeping agreed document actions easy to find alongside their supporting records.
  • Confirm access permissions with authorised staff before releasing restricted records, so the intended audience matches the information sharing limits.
  • Identify duplicate register entries and resolve them carefully, retaining links to earlier correspondence rather than deleting useful document history.
  • Prepare status summaries that separate overdue responses from items without agreed dates, helping project staff choose suitable follow-up actions.
  • Record requests for archived documents and their storage locations, so users can retrieve the correct record without unnecessary searches.
  • Check file location changes against saved links and indexes, then correct broken paths so users can still find records.

Candidate Profile

Applicants can prepare a truthful example of improving a document search or filing structure. For instance, explain how inconsistent reference formats made records difficult to find. Then describe your own changes, the checks you used and the result you can support. If you have a sample register, share only material you have permission to disclose. Remove confidential names and project details before using it as evidence. Also, describe which MS Office functions you used rather than listing software names alone. Ask which document platform the team uses and how it divides project record responsibilities. Before accepting an offer, clarify the reporting line, work arrangement and expected document workload. You can also ask how the team handles access permissions. Also clarify any expected site attendance.

Qualifications & Requirements

  • Experience: 3 Years; Proven document control experience on construction projects; Experience managing correspondence, transmittals, submittals and drawing registers.
  • Education or qualification: Bachelor's degree or diploma in a related field.
  • Proven document control experience on construction projects
  • Experience managing correspondence, transmittals, submittals and drawing registers
  • 3 years of experience.
  • Strong skills in maintaining document logs and filing systems.
  • Proficiency in MS Office; experience with Aconex or similar platforms is a plus.
  • Good written and spoken English.

Employer-stated Skills & Competencies

  • Strong skills in maintaining document logs and filing systems
  • Proficiency in MS Office; experience with Aconex or similar platforms is a plus
  • Good written and spoken English
  • Managing correspondence, transmittals, submittals and drawing registers.
  • Maintaining document logs and filing systems.
  • MS Office proficiency.
  • Aconex or similar platform experience is a plus.
  • Good written and spoken English.

How to Apply

Kindly send us your CVs at cv@yamas.com.sa mentioning the position you are interested with.

About Yamas Al-Arabia Construction & Contracting

Yamas Al Arabia Construction describes its work as providing integrated engineering solutions in the building sector. The company highlights its technical expertise and use of modern approaches. It states a commitment to quality and safety standards when turning building plans into completed work.

Browse more vacancies · General employment information

Candidate Requirements

💼 Experience3 Years; Proven document control experience on construction projects; Experience managing correspondence, transmittals, submittals and drawing registers
🎓 EducationBachelor's degree or diploma in a related field
📨
Interested in this job?Apply now and submit your profile for this opportunity.
✈ Apply by Email

Similar Jobs You May Be Interested In

View all jobs

No similar jobs are available at the moment.

Apply safely for Document Controller Do not pay for an application, interview or job offer. Verify unusual requests before sharing sensitive personal or financial information.
Contact Support