Skip to main content

How Data Timeframe Works in AI Check-Ins (This Week vs Last Week Explained)

Understand how AI Check-Ins pull data using “This Week,” “Last Week,” “This Month,” and “Last Month” timeframes.

Xenios Charalambous avatar
Written by Xenios Charalambous
Updated over a week ago

Many coaches get confused when testing AI Check-Ins because the data in placeholders doesn’t always match “today.”


This is normal — and it’s exactly how the Data Timeframe system is designed to work.

This article explains the logic behind:

  • This Week

  • Last Week

  • This Month

  • Last Month

So your check-ins always show accurate numbers.

You can change the "Data Timeframe" at by clicking on the side menu at AI → AI Check-Ins (Configure) → Select or create new template → "Data Timeframe"

1. Last Week = Always Monday → Sunday (Completed Week)

If today is Sunday, November 23, and your Data Timeframe is set to Last Week, then FitMetrics will pull data from:

Monday Nov 10 → Sunday Nov 16

This is because:

  • “Last Week” always refers to the previous full week

  • A full week is always Monday → Sunday

  • It does NOT include the current week at all

Example:

Today: Nov 23
Setting: Last Week
Data pulled: Nov 10–16

This is why testing on a Sunday shows data from the previous week — this is correct behavior.

2. This Week = Current Monday → Yesterday (NOT today)

If today is Friday, Nov 21, and your Data Timeframe is This Week, AI Check-Ins will pull:

Monday Nov 17 → Thursday Nov 20

It never includes today because the current day’s data is not complete yet.

Example:

Today: Friday, Nov 21
Setting: This Week
Data pulled: Nov 17–20

This ensures the averages and totals are accurate.

3. This Month = 1st of the Month → Yesterday

If today is Nov 21, then:

This Month pulls Nov 1 → Nov 20

The current date is excluded because the day is not finished yet.

4. Last Month = First → Last Day of Previous Month

If today is December 5, and you select Last Month, FitMetrics will pull:

November 1 → November 30

5. Why This Matters for Placeholder Accuracy

Any placeholder that relies on Trainerize data uses the Data Timeframe, including:

  • {{workouts_completed}}

  • {{avg_weight}}

  • {{avg_calories_eaten}}

  • {{workout_total_volume}}

  • {{nutrition_completed}}

  • {{avg_steps}}

So it’s critical that you choose the correct timeframe depending on:

  • What day you test the template

  • What data you expect to see

  • Whether the client has enough days in the timeframe

  • Whether they are in Week 1 of a program (no comparison yet)

6. Real Example from a Coach (Explained)

A coach asked:

“I'm testing training volume on Sunday, but it’s pulling last week’s volume. Should I test tomorrow?”

Yes — because Sunday still belongs to the ongoing week.

When you test “Last Week” on a Sunday:

  • FitMetrics uses the previous full week, not the current one

If the client is in Week 1, then:

  • There is no previous week to compare volume against

  • This is why placeholders like {{workout_total_volume_comparison}} show 0 or no data

7. Summary

Last Week

  • Always previous Monday → Sunday

  • Doesn’t include the current week

This Week

  • Current Monday → Yesterday

  • Never includes today

Last Month

  • Entire previous month

This Month

  • 1st of the month → Yesterday

Why your tests may look “wrong”

  • Because you are testing on a Sunday

  • Because the client is in Week 1

  • Because today’s data is never included

  • Because placeholders follow strict timeframe rules

Related Articles
What Are AI Check-Ins?
How to Create Your First AI Check-In Template
How to Share AI Forms Through AI Check-Ins
Why AI Form Check-Ins Are Grouped by Week (Even When Clients Submit Late)
AI Check-Ins: Complete Guide to All Placeholders
Did this answer your question?