Oversight Isn't an Event

Say a plan's investment policy statement puts a fund on watch when it falls into the bottom quartile of its peer group over three years. In the second week of a quarter, the plan's mid-cap fund crosses that line. The committee's next meeting is ten weeks away. Under a quarterly process, nobody looks at the breach until the binder is printed, and by then the fund has spent most of a quarter outside the plan's own criteria with no documented response.

The claim of this post is that the committee meeting should review and ratify a monitoring process that runs between meetings, applying the criteria the committee already chose as the data changes. In the example above, the advisor would see the breach the week it happened, look at it, and record a decision: put the fund on watch, investigate the cause, or recommend a replacement. The meeting ten weeks later would confirm a call already on file.

Why oversight became quarterly

Quarterly review was a response to logistics. Someone had to gather the statements, pull the performance data, reconcile the lineup against the criteria, assemble it into something a committee could read, and get busy people into a room. That took weeks, so firms batched the work and did it as often as they reasonably could, which settled at four times a year.

The quarter reflects the pace of manual data collection. The fiduciary duty is to pay attention to whether the plan is being run prudently, and nothing in that duty ties attention to four fixed dates.

What changes between meetings

The events oversight is supposed to catch arrive on their own schedule. A fund can breach its watch criteria in any week. A recordkeeper can change a revenue-sharing arrangement or a service term without regard to your committee date. A cheaper share class can become available, and participants can sit in the more expensive one until someone notices. Participants face layoffs, hardships, rollover decisions, and deaths in the family in week six as often as on meeting day.

Under point-in-time review, most of these surface only when the committee convenes. Sometimes the delay is harmless. Sometimes it turns a small correction into a large one, and the committee cannot know in advance which kind of quarter it is in.

What continuous oversight looks like

Meeting monthly instead of quarterly shortens the gap without changing the model. The more useful change is to keep the plan's data current and evaluate it against the committee's criteria as conditions change.

In practice, that means the watch-list rules, fee thresholds, and lineup expectations the committee has already adopted get applied to current data, instead of being transcribed onto a slide once a quarter. When something crosses a line the committee cares about, the advisor sees it while there is still time to act.

The advisor and the committee still make every decision. Software does not decide whether a fund stays, whether a fee is reasonable, or whether a provider should be replaced. It keeps the data current, applies the criteria the committee set, and records what changed and when. Human attention goes to the few exceptions that warrant a decision, instead of to assembling the binder and re-reading three months of mostly uneventful history. A person decides. The system remembers.

The record it produces

Continuous oversight also produces a different kind of record. A stack of quarterly decks shows that on four days a year the committee reviewed a summary of past activity and signed off. A continuous record shows that the criteria were monitored throughout the year, that the mid-cap breach was noted the week it occurred, that someone reviewed it and documented a decision, and that the quarterly meeting confirmed it.

• A point-in-time file shows that you looked on a handful of dates. A continuous file shows that you were watching throughout.
• Learning about a breach the week it happens lets you make a choice. Learning about it ten weeks later leaves you writing an explanation.
• The committee meeting becomes the place where the committee reviews and ratifies a running process.
• Human judgment goes to exceptions that need a decision.

Software does not determine whether the committee met its obligations, and it does not make the call on any fund, fee, or provider. PlanSync is built to keep one current record per plan, so the committee can see what was reviewed, what was decided, and when.

Keep the meeting, change what it reviews

The quarterly meeting still has a purpose. A group of people sitting down together and taking ownership of the plan's decisions has real value. The change is in what they review: a process that has been running since the last meeting, with the decisions already documented, instead of three months of activity seen for the first time.

Go back to the mid-cap fund. Under a quarterly model, the committee learns about the breach ten weeks late and has to explain the gap. Under a continuous model, the breach was reviewed the week it happened, and the meeting confirms what the advisor already did. The duty to pay attention runs all year, and the tools to meet it that way now exist.