Shift Handover Log

The outgoing shift writes a handover for its own window. Every item still open is carried forward automatically into the next shift, with its age and the note each previous crew left against it, so nothing quietly falls off the end of a night shift. The incoming shift acknowledges the handover by name, with a timestamp. That acknowledgment is the difference between "we told them" and "they confirmed they read it" - and after an incident, only the second one holds up.

Describe your shift schedule once - two twelves, three eights, whatever you run - and the paid plan reports continuity against it: which shift windows went by with no handover filed, which handovers were never acknowledged, and which open items have been carried through so many crews that they are being passed on rather than dealt with. You also get a cross-team roll-up across all your logs and a dated CSV export for incident reviews and audits.

Built for network operations centers, security operations, service desks, data centers, control rooms, and laboratories - any team whose work never stops.

What this app deliberately does not do: it does not read your chats, files, mail, meetings, or calendar. It asks for one Microsoft Graph permission, User.Read - the ordinary sign-in permission - so in most organizations it installs without an administrator having to approve anything. Everything in the log is what your own people typed into it.

The starter plan covers one handover log, five people who can write, and the most recent five handovers - enough for one crew to run a real handover with real acknowledgments. Paid plans remove the limits and add continuity reporting, aging analysis, the cross-team roll-up, and CSV export.

Get started: add the app to the channel your operations team already lives in, describe your shift schedule, and the outgoing shift can file its first handover today. Support: support@maconapps.com or https://maconapps.com/saas-support.html