Cycles

A cycle is a window, not a reset

Nothing is reset or moved when a cycle starts. Leads, clients, stock and money stay where they are; a cycle is a pair of dates laid over them.

• What happened is counted in the cycle it happened in: leads gained, deals won and lost, revenue won, business booked, new clients, cash collected, units sold, projects and tasks finished, issues raised, recognition given. A new cycle reads zero on its first morning.
• Where things stood is read as of the cycle's last day: the open pipeline, what is owed and overdue, clients on the books, recurring revenue, headcount.

Revenue is contracts — client accounts opened in the cycle — and realtor sales no contract covers. It is never a lead's estimate.

The figures are grouped the way the work runs: winning work, clients and accounts, delivering work, money, inventory and stock, people, and goals and KPIs. A figure your workspace has no records for is left out rather than shown as zero. Hover a figure to see what it was read from; press it to go there.

What reads the cycles

The running cycle is the period the rest of Rople counts in.

• Home, Business position, Finance and the hubs. Headline figures that count something happening — revenue closed, collected, deals won — count the running cycle and name it, for example "Collected · Q4 2026".
• Goals. Goals › Cycles groups objectives by the workspace's cycles, and a new objective with no date is due when the running cycle ends. See Goals and KPIs.
• Reviews. Performance reviews can run on the cycles, so a review is the review of one cycle. See Reviews.
• Account targets. A new target on an account starts with the running cycle's dates. See Relationships.
• KPIs and branch targets. These do not reset. A cycle keeps where each stood on its last day, and closing freezes that.

The tabs

• This cycle. The running cycle so far — "Day 20 of 92", with how many days are left — against the previous cycle at the same day, so a three-week-old quarter is compared with the first three weeks of the last one. Each figure that adds up over time also says where it is heading at this pace.
• Trends. Each figure across the last eight cycles, with the change on the cycle before and on the same cycle a year earlier, which takes the season out.
• KPIs & targets. Where every KPI and branch target stood on each cycle's last day, and the percentage change from one cycle to the next. View it by Company, Department, Team, Person or Branch, and press a row for its KPIs.
• Compare. Any two cycles side by side.
• History. Every cycle's record: its figures, its projects and milestones, where the leads came from, what sold, who paid the most, how its goals ended, what was carried over, and its review.

Each cycle carries a state: Planned, Running, Ended · to close or Closed.

What a cycle inherited, and what it delivered

This cycle and every cycle's record in History show four more cards.

• Projects. Carried in (running on the first day), started, completed and stopped (cancelled). These always add up to what is carried out, and what one cycle carries out the next carries in. A project starts on the day it was created; on hold is not stopped. Below them are the projects whose last milestone was due in the cycle, and whether each finished on plan.
• Milestones due. Every milestone whose _original_ due date fell in the cycle. Moving a date later does not take a milestone out of the quarter it was promised in; the move is counted instead. Each is on time, late (with how many days), slipped (due and not done — the next cycle inherits it), not yet due, or dropped (its project was stopped). Something due today is not late until the day is out. The rate is on time by weight, counted strictly, and split between carried-in projects and new ones. The list is worst first; press one to open it.
• Milestones by owner. The same, per person — what their review reads.
• Leads. Carried in against new, what each became, what is still open, and how old the carried-in leads are. A lead's value is its estimate: the pipeline, never revenue. A win is worth what its contract was signed for.

Closing a cycle keeps these with its figures. The Carried over note on a closed cycle names the projects still running and the milestones the next cycle inherits.

KPIs and branch targets

A KPI's standing for a cycle is the KPI's own figure on the cycle's last day — the latest reading for a rate, the running total for something cumulative — against its target, the right way up when lower is better.

A branch's standing is its sales in the cycle against the monthly targets set for the months inside it.

A group's standing is the average attainment of its KPIs, and its change is how that average moved on the cycle before. A KPI belongs to its own department and team, or its owner's, and to the branch its owner was in on the cycle's last day.

Closing a cycle

When a cycle ends, the workspace admins are told the next morning, and Cycles shows a banner: the cycle has ended and its figures are ready to review. See figures opens it in History; Close followed by the cycle's name (for example Close Q3 2026) opens the close sheet. The same button is on the cycle in History.

Closing keeps the cycle's figures as they stand that day, so a receipt reversed or a lead deleted later does not quietly rewrite the period. KPI and branch standings are frozen with them.

The close sheet offers two more things:

• Move unfinished goals into the next cycle, due when it ends. They still count as unfinished in the cycle being closed.
• Retrospective — what went well, what did not, and what changes next cycle.

If nobody closes a cycle, Rople closes it after the grace period set in the calendar (14 days unless changed), so the record is kept either way. An automatic close moves no goals, and says on the record that Rople closed it.

A workspace admin can Reopen a closed cycle. It then reads live from the records until it is closed again.

A manager can write or change a cycle's retrospective from History with Save retrospective.

Cycle settings

Cycle settings, at the top of the screen for workspace admins, opens Organisation › Structure › Cycles & reviews. It has three sections.

The calendar.

• A cycle is — Monthly, Quarterly, Half-yearly, Yearly or Custom dates.
• The year starts in — the month your year begins.
• Close a cycle for us after (days) — the grace before Rople keeps the record if nobody has closed it.

A change takes effect from the next cycle. The one running now, and every one before it, stays as it is. The calendar can be set before the cycles are switched on.

Reviews. Whether performance reviews run on the cycles, when the owner is asked to start one (by the cycle's length, or a set number of days before the end), and whether the self-review comes before other work from the day before a cycle ends. See Reviews.

Coming up. The running cycle and the next, each with Edit dates.

Editing dates

Edit dates — in Coming up, or on the running cycle's card on This cycle — sets a cycle's name, start and end.

• A cycle that has not started can move both its start and its end.
• A cycle that has started can move only its end, and not into the past.
• A cycle that has ended keeps the dates it ran on, because they are its record.

The cycles after it are fitted round the new dates, with a short bridging cycle filling any gap up to the next boundary. A cycle somebody else set by hand is never moved to make room; Rople says which one is in the way.

Custom dates. With the calendar on Custom dates, you draw each cycle with Edit dates. Past the last one drawn, Rople carries on at the same length until you draw the next.

Where the history comes from

Cycles for the last two years (or the last twelve months, on a monthly calendar) are filled in from your records the first time the screen is opened, so trends are there from the start.

Who sees what

Everybody who can open Intelligence sees Cycles, read from the records they can see. A closed cycle's frozen, company-wide figures are shown to the workspace admins; anybody whose view is narrower reads the cycle live from their own records, and the screen says so. The same goes for KPI and branch standings.

How it connects

• Business position shows the running cycle in its band at the top. See Intelligence.
• Home and Finance count revenue and cash in the running cycle.
• Ask Rople does not read cycle figures yet.

Common questions

Why does last quarter's figure differ from what the records say now? Because it was closed, and its figures were kept as they stood at the close. A workspace admin can reopen it to read the records again.

Why does this cycle read zero? Because it has just started. Counts of things happening start from zero each cycle; leads, clients and stock carry on.

Can I change the length of the cycle we are in? You can move the running cycle's end with Edit dates. Changing the calendar itself takes effect from the next cycle.