How to keep permit deadlines and files under control

A renewal rarely gets missed because nobody cared. It gets missed because the date sits in a spreadsheet that one person updates, the supporting document sits in a shared folder, and the last exchange with the administration sits in somebody’s inbox. The director asks where a title stands, and three people give three slightly different answers.

The trouble grows faster than the portfolio. Each permit has its own type, its own administrative steps and its own dates. With a few titles, one careful person can hold all of that in their head. With more titles, crews in the field and that same person away on a mission, the whole calendar depends on someone who is out of reach.

Why the spreadsheet stops working

A spreadsheet stores dates well enough. It warns nobody, and it has no idea that a document needed for a filing is about to expire.

Copies do the rest of the damage. The same permit often exists in the ERP, in a spreadsheet, in a shared folder and in a chat thread, and the versions rarely agree, sometimes on the boundary itself. When a deadline is close, nobody wants to spend the morning working out which copy to believe.

Then there is the question of history. When a partner or an authority asks what happened on a title, you need the sequence of events, and a sequence rebuilt from old emails has holes in it.

One file for each permit

FlexiMining gives each permit its own complete file: boundaries, overlaps with neighbouring titles, assigned geologists, administrative steps, deadlines and history. Everybody works from that file, so the argument about which copy is right goes away.

The file starts before the grant. A licence application is followed against its document checklist, which shows exactly what is still missing. When the application is approved, the permit, the project and the administrative steps are created for you, and nobody types the same information a second time.

Overlaps sit in the same place. You see early where your permits touch neighbouring titles, while a boundary question is still easy to deal with. The permit map then shows all your titles and field points together, company by company if you run a group.

How the reminders work

Steps and due dates are set for each permit type, and you are warned before anything falls due. A step that runs late shows as overdue instead of sliding quietly into next month. Several things work together here:

• Reminders in the app ahead of each step.
• Permit expiry dates synced to Google Calendar, with the geologist, chief geologist and director as participants.
• A document library that warns you before a regulatory document expires. Each document is stored once and reused from one application to the next.
• A dashboard that shows permits, field work, spending and teams at a glance.

The limits are worth stating. Alerts live in the app and on the synced calendar. The platform does not send SMS, WhatsApp or email messages, and server push notifications are still on the roadmap, so somebody has to look at the app or the calendar. A reminder also files nothing. The responsible person still prepares the step and takes it to the administration.

Who holds the pen

Deadlines slip when responsibility is vague, so the screens follow the job. An administrative manager looks after permits, deadlines and spending for their companies, and can edit permit details and validate steps. A chief geologist sees all the permits of the company. A geologist sees the permits assigned to them, as lead or contributor. The general director sees every company.

The person who has to act finds the due date on their own screen, and the director can read the whole portfolio without asking anyone for a status report.