placement and first role

Arrive prepared. Learn safely. Become useful without pretending to know more than you do.

A practical preparation system for placements, cadetships, internships and graduate roles in Australian commercial construction.

YOUR PREPARATION MAP

Complete the essentials before the environment becomes busy

This checklist records practical preparation, not job readiness or competence. Some items will depend on your employer and project. Confirm local requirements with the person responsible for your placement.

18 preparation checks10 practical guides30, 60 and 90 day planPrivate browser record

Access, safety and logistics

Project and team context

Personal work system

Communication and boundaries

Project rules take precedence: use this as a preparation guide only. Follow the company’s induction, safety system, document controls, confidentiality rules, delegations and instructions.
01Before Day OneRemove avoidable uncertainty before you arrive.Practical guide

Confirm the practical details

  • Start time, arrival point and site or office contact
  • Travel, parking, security and site access
  • PPE, White Card and induction requirements
  • What to bring, what software is used and whether a laptop is supplied

Build basic project context

  • Project name, client, location and delivery stage
  • Builder, key consultants and major work packages
  • Publicly available project purpose and constraints
  • Your likely team, role family and placement objectives

Set the right expectation

You are not expected to know the project on arrival. You are expected to be punctual, prepared, safe, curious, organised and honest about what you have not yet encountered.

Avoid the first day scramble: do not leave access, clothing, travel, contact details or required documents until the morning you start.
02Your First Site VisitRead the physical environment without stepping outside safe supervision.Practical guide

Stay within the site system

  • Complete induction and follow the site rules
  • Stay with the person responsible for your visit
  • Respect exclusion zones, plant movements and edge protection
  • Never enter an area because somebody else appears comfortable doing so

Learn to observe

  • Project access and material movement
  • Sequence between structure, services, envelope and finishes
  • Temporary works and changing risk conditions
  • How drawings, set out and installed work connect

Capture context, not random photos

Only take photographs when permitted. Record location, orientation, date, drawing reference and why the condition matters. A photograph without context can create confusion rather than evidence.

Safety overrides curiosity: stop and ask whenever access, PPE, plant, temporary works or site behaviour is unclear.
03Your First Project OfficeUnderstand the team, systems and information routes before trying to move work.Practical guide

Map the people

  • Your supervisor and reviewer
  • Project manager, construction manager and site leadership
  • Commercial, engineering, design, planning, HSEQ and administration teams
  • Who owns common decisions and who needs to be informed

Map the information

  • Document management system and folder structure
  • Current drawings, specifications and registers
  • Email conventions, meeting minutes and action logs
  • Where templates, procedures and project controls sit

Map the rhythm

Learn the daily prestart, coordination meetings, design reviews, commercial cycles, programme updates, reporting deadlines and approval pathways that determine how work actually moves.

04Ask Useful QuestionsShow preparation, isolate the uncertainty and make the next response easier.Practical guide

QUESTION STRUCTURE

Checked, unclear, impact, request

I checked [drawing, register, instruction or source].
I understand [the part that is clear].
I am unclear about [the specific gap].
It may affect [scope, time, safety, quality, cost or another party].
Should I [proposed next step], or is there another process I should follow?

Before asking

  • Check the obvious controlled sources
  • Separate fact from assumption
  • Identify the exact point of uncertainty
  • Consider who owns the answer
  • State the timing or consequence where relevant
Do not hide uncertainty: a prepared question is useful. A vague question transfers all the thinking to somebody else. A silent assumption can transfer the consequence to the project.
05Take and Confirm InstructionsTurn a verbal request into a clear task with the right output and review path.Practical guide

TASK CONFIRMATION

Repeat the task before starting

Task: [what needs to be done]
Required output: [email, marked drawing, register update, analysis or other]
Source information: [controlled documents and people]
Deadline: [date and time]
Priority: [relative to current tasks]
Reviewer: [who checks it before use]
Constraints or authority: [what I must not assume or approve]

Confirm competing work

When several people give you tasks, do not quietly guess the priority. Show your current list, deadlines and estimated effort to your supervisor, then confirm the order and communicate any change to affected people.

Close the loop

Tell the requester when the task is complete, when it is blocked, what still needs review and where the output is stored.

06Record Actions and EvidenceCreate a simple record that helps the team see ownership, status and the facts behind a decision.Practical guide

ACTION RECORD

One action, one owner, one due date

Date and source: [meeting, call, inspection or email]
Issue or decision: [clear factual description]
Location or document reference: [grid, level, drawing, revision]
Action required: [specific output]
Owner: [one accountable person]
Due: [date and time]
Affected parties: [who needs the outcome]
Evidence or link: [controlled record]
Status: [open, blocked, ready for review or closed]

Record facts while they are current

  • Use dates, locations, quantities and revision references
  • Distinguish what you observed from what somebody said
  • Do not edit records to make later events appear obvious
  • Store records in the project system, not only in personal notes
  • Respect confidentiality and document control
07Read Drawings and RevisionsUse the title block, references and controlled source before relying on a detail.Practical guide

Read the title block first

  • Project, discipline, drawing title and number
  • Status, revision and issue date
  • Scale, orientation, levels, grids and legends
  • Referenced sections, details and schedules

Read across documents

A plan rarely contains the whole requirement. Follow detail bubbles, sections, notes, schedules, specifications and consultant documents. Check whether an apparent conflict has already been resolved in a later controlled source.

Do not manage revision control from memory

Confirm the current controlled issue in the document system. Remove superseded prints from circulation where the project process requires it and make sure affected people receive the resolved information.

Never approve what you are only learning to read: markups and observations should go to the authorised reviewer before they are used for construction.
08Meetings, Emails and CallsCommunicate the issue, decision, action and timing without burying the message.Practical guide

CONCISE PROJECT EMAIL

Context, issue, impact, action

Subject: [Project area] [specific issue] [action or decision required]

Context: [one or two factual sentences]
Issue: [what is unclear, changed or required]
Impact: [why it matters and by when]
Checked: [documents, people or facts already reviewed]
Action requested: [specific decision, review or response]
Owner and due date: [who and when]
Attachments or links: [controlled references]

In meetings

  • Prepare the facts and required outcome
  • Listen for decisions, assumptions and actions
  • Ask when ownership or due dates are unclear
  • Do not agree to commitments outside your authority

After important calls

Send a concise written record of what was discussed, agreed, still unresolved and who owns the next action.

09Boundaries, Safety and EscalationKnow the situations where speed must give way to authority, verification or immediate escalation.Practical guide

ESCALATION STRUCTURE

Facts, immediate control, consequence, decision

Observed fact: [what I directly saw or verified]
Immediate control: [what has been made safe or paused]
Uncertainty: [what still needs confirmation]
Potential consequence: [safety, quality, time, cost, compliance or stakeholder]
Affected parties: [who needs to know]
Decision required: [what authority or response is needed]
Timing: [when the decision is required]

Escalate immediately when

  • Work may be unsafe or outside an approved method
  • A proposed action could conceal a defect or nonconformance
  • Someone asks you to approve beyond your authority
  • Controlled information conflicts with the physical condition
  • A delay, change or instruction may have significant consequences
  • You are asked to alter, hide or backdate a record
Escalation is not failure: good escalation is timely, factual, proportionate and directed to the person with the authority to act.
10Your First 30, 60 and 90 DaysSet practical learning objectives that can be observed and reviewed.Practical guide
Plans save automatically in this browser.

TURN EXPOSURE INTO EVIDENCE

Record what you actually learned and contributed

After a placement activity, capture the context, what you did under supervision, the output, what the experience demonstrates and what you would do differently next time.

Open Evidence Portfolio →Keep evidence factual and do not upload confidential project material.