Interview proof plan | Three minutes
A concise, permission-based demonstration that shows readiness to support established project procedures without turning the interview into a presentation or implying prior authority.
“I prepared a short, fictional, and nonconfidential project-coordination example to show how I think about status, changes, invoice support, and handoffs. Would it be useful if I showed you three screens for about three minutes?”
If the interviewer says no or time is short, continue the conversation normally. The preparation still helps you answer questions with greater specificity.
Timed sequence
Use the exact sequence below. Do not open every artifact. Keep the emphasis on your working approach and respect for established procedures.
Open the Weekly Coordination Dashboard.
“This is a reconstructed academic case using synthetic data. It is not meant to copy or replace your process. It shows the coordination discipline I would bring after learning your systems, procedures, and approval structure.”
Point to the three items requiring attention: concealed corrosion, the incomplete pay application, and the quotation needing clarification.
“My job as a coordinator is not to make these decisions. It is to make the decision need, owner, impact, support, and deadline visible so the right person can act.”
What this proves: You understand status reporting, ownership, escalation, and role boundaries.
Open the Change Package Completeness Control and point to technical scope plus safety and access effects.
“Before routing a potential change, I would confirm that the source, quotation, cost, time, references, routing, and required supporting records are complete. Here the package stays open because two items still require authorized review.”
What this proves: You understand change coordination without claiming technical, contractual, or approval authority.
Open the Invoice Routing Completeness Control and point to certified payroll and the conditional lien release.
“The values reconcile to the revised commitment, but the package should not enter the approval queue because two required documents are missing. I would record the exact hold reason, owner, and due date, then route it only when complete.”
What this proves: You can support invoice processing, pay applications, and financial control while respecting approval authority.
“The formats would change to match your project platforms and procedures. The consistent part is how I work: accurate records, clear ownership, complete routing, early exception visibility, and dependable follow-through.”
Stop sharing and return the conversation to the interviewer.
Likely follow-up
Answer from the role boundary and the evidence shown. Do not claim use of a named platform or process that you have not actually used.
“The case is a portfolio reconstruction based on construction administration coursework and my current document-control and workflow experience. All project data is synthetic. I built it to demonstrate how I now connect the processes.”
“No. My first step would be learning your approved procedure, system, terminology, and approval matrix. I would use these same control principles within that environment.”
“I would document the missing item, current owner, due date, impact, and routing gate, notify the appropriate parties, and keep the item visible until the requirement is satisfied or an authorized exception is documented.”
“I separate preparation and completeness checks from technical interpretation, commercial decisions, payment approval, and owner authorization. I document who has authority for each step.”
“Small controls: one identifier, one owner, one due date, explicit status definitions, missing-document flags, linked records, and clear escalation. Those improve reliability without replacing the established workflow.”
“I would map the required fields and statuses to your existing platform, then follow your naming, permission, routing, and reporting standards. The examples are platform-neutral on purpose.”
Presentation discipline
The strongest impression comes from judgment and restraint, not from showing the largest number of documents.
Use this when there is not enough time to share screens:
“I built a synthetic project-coordination case study to sharpen how I connect commitments, meetings, changes, invoices, and closeout. The central principle is that I prepare and verify complete records, make owners and deadlines visible, and escalate exceptions, while authorized staff retain technical, contractual, and payment decisions. I would apply that discipline within your established procedures and systems.”