What questions are asked in a document controller interview?
A UK document controller interview usually covers five areas: your hands on experience with a common data environment such as Asite, Aconex or Viewpoint For Projects, your understanding of naming conventions and revision control under ISO 19650, how you handle compliance and confidentiality, how you chase and manage people who are late with information, and your attention to detail under pressure. Expect around 20 questions across a 45 to 60 minute conversation, plus a short practical test on many roles. The single most common opening question is “talk me through how you would set up document control on a new project from day one”.
Below are the 20 questions, grouped by what they are really testing, with guidance for candidates preparing and for hiring managers building an interview that actually predicts performance.
What are document controller interviews really testing?
Document control is one of the few support roles where a mistake has a compliance consequence rather than just an inconvenience. Issue the wrong revision of a drawing and something gets built to it. So the interview is less about personality fit and more about whether you can be trusted with a single source of truth.
Across the roles we place, interviewers are assessing five things.
| What they are testing | Why it matters | The question type that reveals it |
|---|---|---|
| Systems fluency | Every CDE behaves differently and retraining costs weeks | “Which platforms have you used and what did you do in them” |
| Standards knowledge | ISO 19650 and file naming underpin everything downstream | “How would you name and revise this drawing” |
| Compliance instinct | Building safety and data protection duties sit on this role | “What would you do if you found an uncontrolled document in circulation” |
| Influence without authority | You chase architects and engineers who do not report to you | “Tell me about a time someone missed a deadline you owned” |
| Accuracy under load | Peak issue weeks are relentless | Practical test, or “how do you prioritise a 200 document upload” |
If you are a hiring manager, that table is a useful scoring frame. If you are a candidate, it tells you which of your stories to prepare.
Experience and background questions
These open the interview and set the tone. Keep answers specific to project type, volume and platform, not general admin language.
- Talk me through your document control experience and the projects you supported. Name the sectors, the approximate project values, and the number of live projects you handled at once. “I ran document control on three live education projects, roughly £8m to £20m each” tells an interviewer far more than “I have five years of experience”.
- Why document control, and why the built environment? Interviewers ask this because turnover in the role is expensive. A genuine answer about liking order, process and being the person everyone relies on lands better than a generic one about career progression.
- What does a typical day look like in your current role? This is a quiet consistency check against your CV. Cover the morning inbox and transmittals, uploads and quality checks, chasing outstanding information, and the reporting you produce.
- How many documents do you typically handle in a week, and how do you keep on top of it? Volume gives context. Pair the number with your method, whether that is a daily register review, a chase log, or automated CDE workflows.
Systems and software questions
This is the section that most often decides the shortlist, because CDE fluency is the hardest thing to teach quickly.
- Which common data environments have you used, and at what level? Be honest about depth. There is a real difference between uploading into Asite and configuring workflows in it. Interviewers will probe, and overclaiming is the fastest way to lose an offer.
- Walk me through setting up a new project in a CDE. A strong answer covers folder structure, permissions and access matrices, the naming convention, workflow and approval routes, distribution matrices, and the register that keeps it all visible.
- How do you manage transmittals and distribution lists? They want to hear about controlled issue, acknowledgement tracking, and what you do when someone claims they never received a drawing.
- What would you do if the CDE went down during an issue deadline? A test of pragmatism. Good answers include a controlled offline fallback, a clear record of what was issued and when, and reconciling the register once the system is back.
- How comfortable are you with Excel, SharePoint and Bluebeam? Excel still runs a surprising amount of document control reporting. Pivot tables, lookups and conditional formatting are worth mentioning explicitly.
The platforms that come up most often in UK built environment interviews in 2026 are Asite, Oracle Aconex, Viewpoint For Projects, 4Projects, Autodesk Construction Cloud, Procore, Bentley ProjectWise and SharePoint. Every additional platform you can genuinely use widens the range of roles open to you, and as we cover in our guide to document controller salary in the UK, it moves your pay too.
Standards and compliance questions
This is where document control interviews have changed most in the last three years, and where candidates who prepare properly pull clearly ahead.
- What is ISO 19650 and how does it affect your day to day work? A plain, confident definition works best. ISO 19650 is the international standard series for managing information across the life cycle of a built asset, published by BSI in the UK. In practice it governs how information is named, classified, reviewed, approved and shared through a common data environment, and it defines the states a document moves through from work in progress to shared, published and archived.
It is worth knowing that the standard is currently being revised. BSI and nima released draft revisions of Parts 1 and 2 for public consultation on 10 March 2026, with comments closing on 3 May 2026 and final publication projected for 2027. The drafts move the language away from “BIM” and towards “information management”. The current editions remain in force until the revisions are formally published, so do not claim to be working to a standard that does not exist yet. Mentioning that you are tracking the revision, however, is a genuine differentiator.
- Explain a file naming convention you have worked to. Do not recite theory. Take a real example and break the fields down, typically project, originator, volume or system, level, type, role and number, then explain why each field exists and what breaks when someone skips one.
- How do you handle revisions and superseded documents? Interviewers want to hear that superseded material is removed from circulation, not just renamed, and that there is an audit trail showing who had what and when.
- What do you know about the golden thread under the Building Safety Act? This question is increasingly common on residential and higher risk work, and most candidates cannot answer it. The golden thread is the requirement introduced by the Building Safety Act 2022, in force since 1 October 2023, for accurate building and fire safety information to be kept digitally and kept current across the design, construction and occupation phases of a higher risk building. Higher risk buildings are generally those at least 18 metres tall or with at least seven storeys, containing at least two residential units. The information must be electronic, version controlled, access managed and auditable. Paper records alone do not comply, and failing to hand the golden thread over to a new accountable person can carry criminal liability.
If you can connect that to what a document controller actually does, which is maintaining exactly that kind of controlled, traceable record, you have made yourself a much easier person to hire.
- How do you handle confidential or commercially sensitive documents? Cover permission based access, restricted folders, redaction where relevant, and your obligations under UK GDPR and the Data Protection Act 2018. On construction projects, mention the health and safety file requirements under the CDM Regulations 2015 if the role touches handover.
Behavioural and pressure questions
Use the situation, task, action, result structure. Keep each answer under two minutes.
- Tell me about a time you found an error in a document that had already been issued. The point is not that you never make mistakes. It is whether you escalate quickly, notify everyone affected, and put a check in place so it does not recur.
- How do you chase a design team that keeps missing information deadlines? The strongest answers show escalation with a light touch. A visible outstanding information report, a standing five minute slot in the design team meeting, and a clear escalation path to the project lead beats sending increasingly firm emails.
- Describe a time you had to say no to a senior person. Common on architecture practice roles, where a director may want a drawing out before it has been through approval. Interviewers want to see that you hold the process while offering a workable alternative.
- It is 4pm on a Friday, an issue is due, and 40 drawings have just landed with inconsistent naming. What do you do? Prioritise by what is contractually due, flag the non compliant files immediately rather than silently fixing them, agree what can slip, and confirm the plan in writing.
Questions you should ask them
Candidates who ask nothing at the end look uninterested. Candidates who ask these two look like they have done the job before.
- Which CDE do you use, and who configured it? This tells you whether you are inheriting a well run system or being handed a mess to fix, which is a very different job at the same salary.
- How many live projects will I be supporting, and is there a second document controller? Volume and cover are the two things that most often make a document control role unmanageable. Ask early.
Worth adding: ask about ISO 19650 maturity, whether the practice works on higher risk buildings, what document control reporting the leadership actually reads, and what happened to the last person in the role.
How the interview differs by employer type
The job title is the same. The interview is not.
| Employer type | Interview emphasis | Likely format |
|---|---|---|
| Architecture or design practice | Naming conventions, working with creative teams, discretion, flexibility across studio support | One or two stages, often informal, sometimes with a studio tour |
| Main contractor | CDE depth, volume handling, site pressure, compliance and audit | Two stages, practical test likely, competency scored |
| Consultancy or engineering firm | Multi project coordination, reporting, standards knowledge | Two stages, technical questioning heavier |
| Infrastructure or rail programme | ISO 19650 detail, audit trail, security and access control | Two or three stages, formal competency framework |
Architecture practices in particular tend to interview for fit alongside capability, because the document controller often sits inside a small support team and touches bids, marketing and studio admin as well. Our guide to document controller jobs in architecture covers what that broader role usually includes.
For hiring managers: how to run a document control interview that predicts performance
Three things separate interviews that produce good hires from interviews that produce turnover.
First, test rather than ask. A 20 minute practical exercise, giving candidates a small batch of inconsistently named files and asking them to sort, name and log them, tells you more than an hour of questions. Score it on accuracy, on whether they flag problems rather than silently fixing them, and on how they explain their decisions.
Second, be honest about the state of your systems. If your CDE is under configured and your register has not been reconciled in six months, say so. Candidates who take the job expecting order and find chaos leave within the year, and you pay to hire twice.
Third, decide in advance what is trainable. Platform specific knowledge can be taught in weeks. Attention to detail, comfort chasing senior people and instinct for compliance cannot. Weight your scoring accordingly.
The red flags we watch for are vague platform claims that do not survive probing, candidates who describe fixing others’ naming errors without telling anyone, and anyone who cannot give a concrete example of an error they caught.
If you are also hiring on the bids side, the same structure applies, and our list of bid coordinator interview questions works as a companion set. If you are still deciding whether the role should be permanent or contract, our comparison of permanent, contract and freelance hiring covers the cost and speed trade offs.
Preparing for a document control interview, or hiring for one?
If you are a candidate with an interview coming up, we brief every person we put forward on the practice, the platform they use and the format of the interview, because a fair process beats a surprising one. Register your interest or browse our current positions to see what is live.
If you are hiring a document controller and want a shortlist of people who can actually demonstrate CDE fluency rather than list it on a CV, tell us about the role and we will build the interview structure with you.
Frequently asked questions
What questions are asked in a document controller interview?
Document controller interviews typically cover experience and project types, common data environment software such as Asite, Aconex and Viewpoint For Projects, file naming and revision control under ISO 19650, confidentiality and compliance including the Building Safety Act golden thread, and behavioural questions about chasing late information and handling errors. Most interviews run 45 to 60 minutes and include around 20 questions.
How do I prepare for a document controller interview?
Prepare three things. First, a specific list of the CDE platforms you have used and what you did in each. Second, a real file naming convention you can break down field by field. Third, two or three situation, task, action, result stories covering an error you caught, a deadline you protected and a senior person you had to hold to process. Then read the job advert for the platform they use and revise it.
What is ISO 19650 and why do interviewers ask about it?
ISO 19650 is the international standard series for managing information across the life cycle of a built asset. It governs how documents are named, classified, reviewed, approved and shared through a common data environment. Interviewers ask about it because it defines the process a document controller runs day to day. Note that BSI and nima opened public consultation on revised drafts of Parts 1 and 2 in March 2026, with publication projected for 2027, so the current editions still apply.
What should I ask at the end of a document controller interview?
Ask which CDE they use and who configured it, how many live projects you would support, whether there is a second document controller for cover, whether they work on higher risk buildings under the Building Safety Act, and what happened to the last person in the role. These questions tell you whether the job is well run or a rescue mission.
Do document controller interviews include a test?
Often, yes, particularly with main contractors and larger consultancies. The most common format is a short practical exercise using a batch of inconsistently named or filed documents, testing whether you can apply a naming convention accurately, spot non compliant files and explain your reasoning. Some employers also set a short Excel task.
What should employers ask a document controller candidate?
Ask candidates to walk through setting up document control on a new project from day one, to explain a naming convention they have worked to, to describe how they handle superseded documents, and to give an example of chasing a senior person for late information. Pair those with a 20 minute practical filing exercise, which predicts performance better than questions alone.
