Skip to content
English
  • There are no suggestions because the search field is empty.

Module 4: Gate 1 Screening and Review

This module introduces the first formal screening point in the TCFG HubSpot process. It explains what Gate 1 is for, what information should be present, and how learners should think about readiness for progression.

Why This Module Matters
Gate 1 sets the quality standard for the rest of the workflow. If the project enters the process with weak information, the later stages become slower, less consistent, and harder for teams to manage.

Learning Objective
By the end of this module, learners will understand the purpose of Gate 1 screening, what information supports review, and how screening quality affects downstream progression.

Videos Included


 
Lesson 4.1
What Gate 1 Is Designed to Do

Lesson purpose
This lesson explains the role of Gate 1 in the wider workflow.

What learners should understand
Gate 1 is an early control point. It helps the business decide whether a project is suitable to progress, needs further discussion, or should stop.

Key points

  • Gate 1 is a decision-support stage
  • it should give enough clarity for review
  • it affects what happens next in the process

What good looks like

  • the learner understands why Gate 1 exists
  • the learner can explain what the business is trying to decide at this point

Common mistakes

  • seeing Gate 1 as only a data-entry step
  • assuming all projects should move forward
  • not appreciating how early-stage quality affects later teams

Quick check
Ask the learner to explain why Gate 1 matters before development begins.


 
Lesson 4.2
What Good Screening Information Looks Like

Lesson purpose
This lesson focuses on the information quality needed for a useful Gate 1 review.

What learners should understand
A good screening record should be clear enough that the next team can understand the brief, the context, and the likely next decision without needing to chase basic details.

Key points

  • screening information should be complete enough for review
  • relevant products and context should be visible
  • unclear information creates delay and weak decisions

What good looks like

  • the learner can recognise a review-ready record
  • the learner understands what makes a record useful versus incomplete

Common mistakes

  • accepting vague information
  • not checking whether the record makes sense from a reviewer’s perspective
  • progressing a record that still has obvious gaps

Quick check
Ask the learner to review a sample Gate 1 record and identify whether it is ready for review.


 
Lesson 4.3
Understanding Screening Outcomes

Lesson purpose
This lesson introduces the possible outcomes that can follow Gate 1.

What learners should understand
Not every project moves forward. Some will progress, some will require discussion, and some will stop. The important thing is that the outcome is clear and supported by the record.

Key points

  • screening supports a decision, not just a status change
  • discussion is different from approval
  • stopped projects still need clear handling

What good looks like

  • the learner understands that progression is conditional
  • the learner can describe the difference between progress, discussion, and stop

Common mistakes

  • assuming “not approved yet” means the same as “stopped”
  • leaving the outcome unclear
  • treating exceptions casually

 

Module 4 Key Takeaways

  • Gate 1 is a quality and suitability checkpoint
  • good screening supports good decisions
  • not every record should progress in the same way

 

Module 4 Suggested Assessment
Ask the learner to:

  • explain the purpose of Gate 1
  • review a sample record
  • identify whether the record is ready, unclear, or unsuitable for progression
  • explain the likely next outcome

 

Up Next: Module 5: Sample Tracker Working