Students

Your campus, your tools, and your clear guidelines—all in one place.

Estudiantes

Virtual Classroom (GUTEC Campus).

Personal Dashboard: active modules, % complete, upcoming due dates (D+H), recent notes, and announcements from the coordinator.

Sprint Navigation: each week displays objectives, content, exercises, and deliverables with visible rubrics.

Shortcuts: forums, technical clinics, tutorials, library, messaging, repositories (CDE), and profile.

Completion Status: traffic light (green/yellow/red) per module, with automatic reminders.

  • Learning by doing: 60–80% practical with datasets, models (IFC/BC3/CSV/SCL), cases, and templates.
  • Session structure:
  1. Brief with objectives and acceptance criteria.

  2. Core material (videos, readings, guides).

  3. Guided practice + QA/QC checklist.

  4. Deliverable with rubric and required format.

  • Interoperability: submissions accepted in standard formats (IFC/BC3/CSV/JSON/tagged PDF).
  • Traceability: basic versioning and changelog of technical decisions within the CDE.
  • Forums per module with reproducibility rules (screenshots, versions, steps).

  •  

    Live technical clinics (BIM/MEP, 4D/5D, HEC/SUDS, FEM, ESG, OT/SCADA): complex problem solving.

  •  

    1:1 or group tutoring with slot booking; registration and summary on the campus.



  • GUTEC Rubrics: observable criteria (technical quality, traceability, interoperability, safety, ESG, presentation).

  •  

    Feedback: written comments + annotations; marking SLA ≤7–10 working days.

  •  

    Resubmissions: permitted when specified by the module; staggered penalties and visible deadlines.

  •  

    Capstone: defence before a panel (academia + industry) with technical Q&A; evidence recording.

  • Prohibited: plagiarism, impersonation, submission of others' work.
  • AI: only if the module allows; you must cite tools and prompts and explain how you validated results.
  • Detection: style matching, work evidence, and oral defence.
  • Due process: notification, hearing, resolution, and appeal according to regulations.
  • WCAG Materials: tagged PDF, proper contrast, subtitles/transcription where applicable, alt-text.
  • Adjustments: extra time, alternative formats, additional tutoring, practical assessment adaptation.
  • Deadline: response to requests within ≤10 days (see § 4.4).
  • Equipment: i7/Ryzen 7 CPU, 16–32 GB RAM, SSD, mid-range GPU for BIM/FEM; dual monitor recommended.
  • Connectivity: ≥20 Mbps symmetrical for sessions involving model sharing.
  • Licences: your own stack or GUTEC educational licences will be used where applicable.
  • Security: MFA where appropriate; role-based access to approved repositories.

Academic calendar.

Structure and calls for applications

Synchronization and reminders

Attendance and participation

Regulations and policies.

Assessment: weighting per module (published at the start). Passing: minimum overall grade ≥ 5.0/10 (or equivalent) and completion of critical deliverables. Resubmissions: specific window per module with potential penalties. Appeals: request for review ≤ 5 days after grading; response ≤ 7 days; subsequent appeal before a different panel.

  • Infractions: minor, serious, and very serious offences with proportional sanctions (ranging from mandatory resubmission to suspension from the module or sitting).
  • Due Process: written notification, hearing, reasoned resolution, and the right to appeal.
  • Legal Basis: Provision of educational services and consent (for communications).
  • Rights: Access, rectification, erasure, objection, portability, and restriction of processing (response within ≤ 30 days). Sensitive Project Data: Preference for anonymisation; use of approved repositories; sharing outside the campus without prior permission is strictly prohibited.
  • Requests: application form + minimal documentation (non-medical where possible; we prioritise trust).
  • Assessment: brief meeting; proposal of measures; mid-programme review.
  • Confidentiality: information managed with strict discretion.
  • Site Visits/Workshops: PPE (Personal Protective Equipment), safety briefing, required permits, and "no-photography" rules where applicable.
  • Insurance: Review your specific policy, programme conditions, and the regulations of the country where the activity takes place.
  • Digital Certificates with Verification: issued with secure verification, including milestone badges (Foundation/Specialist/Lead) and supplemental transcripts upon request.
  • Duplicates: requests must be submitted via administrative support.
student
student

Operativa y soporte.

  • Activate Account and MFA: Set up your credentials and multi-factor authentication (MFA).

  • Complete Profile: Update your time zone, language, sector, and tools.

  • Classroom Guide and Templates: Read the operational manual and download the base templates.

  • CDE/Repository Access: Test your access to the Common Data Environment and project repositories.

  • Calendar and Critical Sessions: Review the schedule and block out time for "critical" sessions.

  • Cohort Forum Introduction: Introduce yourself to your fellow students and tutors.

  • Submit Module 1 "Hello World": Send the initial warm-up task to verify the submission workflow.

  • Technical Support (access, CDE, files): ≤ 24–48 working hours.
  • Academic Support (content, rubrics): ≤ 48 working hours.
  • Administrative (payments, invoices, certificates): ≤ 72 hours.
  • Critical Incidents: campus banner and immediate email notification.
  • Internal module messaging for academic matters.

  • Announcements channel (read-only) from coordination.

  • Email for administrative affairs; avoid unofficial channels for technical queries.

  • Reasonable Adjustments
  • Grade Review / Appeal
  • Technical Support
  • Request Certificate / Transcript
  • Report Integrity Incident

Biblioteca y recursos (atajo para estudiantes)

Meta-search engine by standard/discipline/ software.

Reading lists per module.

Technical Repositories: example models, BC3, QA/QC checklists, dashboards, scripts.

How to Cite: Reference and Licensing Guide

Frequently Asked Questions (Student FAQ).

Verify the start date and enrolment status. If the issue persists, open a ticket (Technical SLA ≤ 24–48 working hours).

Yes, except for marked critical sessions. A recording will be available if privacy permits; you may request a rescheduling.

According to the rubric (relevance, evidence, reproducibility, respect). Up to 10–15% if the module specifies it.

IFC/BC3/CSV/JSON/Tagged PDF (and native files if required by the module). Check the deliverable factsheet.

Only if the module permits it and by citing tools/prompts; you must defend the process and validate the results.

If the module allows it, yes, with tiered penalties. The dates are in the calendar.

Complete the form; we will respond within≤ 10 working days with the agreed measures.

7–10 working days from the submission date, except for complex projects (the tutor will provide notice).

Request a review within ≤ 5 days; response within ≤ 7 days. Subsequently, an appeal before a different panel if applicable.

Do not share unauthorised data. Use anonymised datasets and approved repositories; any breach is a serious offence.

Recommended: i7/Ryzen 7 CPU, 16–32 GB RAM, SSD, mid-range GPU, dual monitors. Connection ≥ 20 Mbps.

Review the temporary interruption regulations and the re-engagement windows per intake.

It is automatically generated upon passing; duplicates or certificates can be requested through Support.

Yes: Career Services (CV Clinic, simulations, vacancies, internships). Access it from the Community menu.

Report via the integrity form; the report is confidential.

Microcopys y buenas prácticas

“Evidence > CV: document your process and versions.”

“If it is not on the calendar, it does not exist.”

“First reduce, then offset: also in your deliverables (weight, efficiency).”

“Ask before submission: timely questions earn points.”

“Respect IP and data: anonymise whenever you can.”

Scroll to Top