History
In the portal: Nothing. History is on in every tenancy, the sixty days back and thirty forward are private constants in both apps, and the way in is an unconditional button in the home header.
What it is
History is where a participant goes back and answers something they missed.
They open it from the home screen, pick a day, and see what that day held. Anything on it that has no answer can still be answered.
That matters to you because it changes what a missed day means. Somebody who was away for a week is not locked out of that week.
What it looks like
A strip of days runs across the top. Pick a day and its items appear underneath.
The strip runs Monday to Sunday and scrolls, covering sixty days back and thirty days forward. Each day carries a small ring, and the ring says one of three things:
| The ring | What it means |
|---|---|
| No ring at all | A day in the future. Nothing on it has been done or missed yet. |
| A dotted ring | That day asked nothing of them. It is not a day of misses. |
| A ring filled in part or in whole | How much of that day they have answered |
Underneath, the day's items sit under their surface headings, exactly as they do on the home screen, with the same pictures and the same descriptions. An answered item carries a tick. One with no answer carries an empty circle.
When you would think about it
You think about History when you are deciding how much a missed day should matter to your programme.
A worked example. A six week course delivers a check-in every weekday. A participant travels and answers nothing for nine days. On the home screen those days are gone. In History they are all still there, and they can work back through them.
What you can set
Nothing. History is on in every tenancy, the sixty days back and thirty forward are compiled into both apps, and there is no setting that stops a participant catching up.
So it is not a feature you switch on for a programme. It is a fact about the app that your programme has to be designed around, which is what the rest of this page is for.
How it behaves
Anything without an answer can be answered. That holds for a day that has passed, the day they are on, and a day that has not arrived yet.
An item they have already submitted does not reopen in History. Whether a submitted
answer can be changed at all is set by revisable on the delivery.
The answer is filed against the day it belongs to, and the moment it was given is kept separately. So a Tuesday check-in answered on Friday sits on Tuesday in the record, and the platform still knows it arrived on Friday.
A journey waiting on that answer moves when the answer is given. Not on the day it was due. So somebody catching up on a week can move several steps through a journey in one sitting.
A lifetime cap counts answers, not days. A delivery that ends after a fixed number of answers can reach that number early if somebody works forward through History. Where the spread of answers matters as much as the count, end the delivery on a date instead.
What you can now do
Decide whether catching up is something your programme wants, and write the content to match.
Where catching up is welcome, say so, because a participant who has missed a week will not assume it.
What takes an item away is the other half: the four reasons an item leaves the home screen in the first place.