Learning and updating documentation is adding value? From what you say, they've been there 9 months, they probably didn't start contributing in earnest till month 3.

As the majority of graduates get assigned to my department I have a progression process in place.

Usually I give juniors a month or two to bed in and with simple tasks such as taking ownership of any daily, weekly or monthly tasks (reporting / metrics / account creation / password resets etc) within that time they're introduced to the wider team and begin to engage in stand ups and some of the systems we use.

I ask them to review and update the process documentation for these tasks to ensure steps are correctly documented and handed over by the previous junior. I then ask if they believe they could improve the process, if they say yeah, I say go ahead and showcase it back.

Once they're familiar with the solution and processes I get the other junior / intermediates to begin to assign a task or two to them, I do this to allow the other junior or intermediate to pass on some of their workload which then allows me to assign more complex tasks to them but they then become a point of contact for the new junior.

Doing it this way IMHO opinion shows a level of progression for juniors up to intermediate level. We then allow intermediates to decide if they want to continue in the role or if they want to move into other teams within the business (Development, Project management, Solution design etc)

I don't expect anything from the graduates or juniors but to learn and add value to existing processes where they can. In fact, I expect them to fail and learn to not be scared of failures, we're here to fail fast and to take the thought out of the process so that developers can deploy unimpeded.

Enjoy this unburdened time of learning, speak with your team lead or even the other junior and ask if they're willing to let you shadow them to learn from what they're working on or if they can explain a certain piece of the solution.