What I see is a simple layout with two portals. What parts of this layout design is proving difficult for you?
A key factor will be the tables, table occurrences, and relationships that form the foundation for this layout and its portals.
I agree with Phil, this looks pretty easy. A portal can be filtered by a date (right click on the portal, then choose filter). I suspect it's a larger problem.
I'll guess that @usmangadeer did what most new users would do, and has created one table (let's call it Appointments). Then he created a layout from the context of Appointments and then realized that he cannot create a portal to display appointments from this context.
This is a pretty big flaw in FMP's documentation and design. I suspect this stumps nearly all new users. The solutions are out there: use a global table (Selector-Connector), or a self-join, or a virtual list. Yet those topics are pretty complicated for a new user.
I'll suggest to @usmangadeer to look at a post I did last fall. I know this reads long but it's the workaround for FMP's basic design flaw:
Thanks mate you understood my problem really well......
Retrieving data ...