When Your Dashboard Data Is Three Days Old and You Do Not Know It

Przemek Halvorsen runs a small property management company in Dublin. He set up an automated dashboard to track rent collection, maintenance spend, and monthly operating costs. It worked well until a contractor invoice did not appear for four days after submission. Przemek had already approved a second job from the same contractor, assuming the first had not been submitted yet. It had. He paid twice and spent a week recovering the overpayment.

Refresh schedules are not a technical detail

Most people configure a dashboard once and assume the data is current whenever they look at it. The refresh interval - how often the system pulls new data from connected sources - is usually set during setup and then forgotten. Accounting integrations often default to 24-hour syncs. Bank feeds can lag by 48 hours depending on the provider. If nobody checks the last-updated timestamp, the dashboard looks live but is not.

Refresh-related mistakes seen most often

• Assuming all connected sources refresh at the same interval when they do not
• No visible timestamp showing when data was last pulled
• Making same-day decisions using figures that reflect the previous business day
• Automated reports sent at 8am using data that last refreshed at midnight three days prior

Przemek added a last-refreshed indicator to the top of every panel. He also set critical feeds - bank balance and invoice status - to refresh every four hours during business hours. The fix took about 90 minutes. The duplicate payment cost him closer to six hours of admin time to resolve. Refresh frequency is not glamorous, but it is where trust in a dashboard is actually built or lost.