Begin with dates, not a new schedule
The simplest way to explore Metric Calendar is as a planning overlay: keep the Gregorian date and add its Metric equivalent. This lets you learn the structure while keeping appointments understandable to everyone else.
- Convert a few meaningful dates. Use the converter for today and a forthcoming milestone. Notice the metric month, day type, and position in the year.
- Use both labels. Write, for example, “Gregorian July 1, 2026 / Metric 2026-05-36.” Keep the normal Gregorian date in calendar software.
- Try a private planning view. Group notes or goals into metric months while leaving shared invitations and external deadlines on their existing dates.
- Reflect on the experience. Record confusion, useful patterns, and the effort needed to maintain two views before deciding whether to continue.
Birthdays, holidays, and recurring events
First decide what an event is anchored to: a Gregorian date, a weekday, another calendar, or a Metric date. Convert each occurrence from that original rule. A birthday kept on Gregorian July 1 maps to Metric month 05, day 36 in 2026, but month 06, day 01 in 2028.
Do not convert one birthday and repeat that Metric month/day forever unless you intend to change its Gregorian anniversary. Gregorian February 29 anniversaries also need an explicit non-leap-year convention; the converter does not choose one for you.
Bonus Rest Days interrupt the regular metric weeks. For events on a particular metric weekday, calculate each occurrence from the metric month/week structure rather than setting a six-day repeating event.
Separate a date overlay from a work-time pilot
Learning to label dates does not require altering hours, pay, leave, or staffing. A work-time experiment does. Treat these as separate decisions and communicate exactly which is being considered.
| Stage | Concrete output |
|---|---|
| Define the question | A written description of what is being tested: date comprehension, planning layout, or a work/rest schedule. |
| Map dependencies | An inventory of customers, payroll, leave, reporting, schools, observances, software, and partners affected. |
| Agree boundaries | Voluntary participation, duration, expected hours, pay arrangements, coverage, and an exit process. |
| Record a baseline | Comparable measures of hours, output, service quality, costs, and participant experience. |
| Run and review | A bounded trial with scheduled reviews and a published decision to stop, adapt, or continue. |
Use ordinary Gregorian dates as the authoritative dates for external appointments, contracts, and existing systems during an overlay trial. Where a Metric label is added, identify it explicitly and check its conversion.
Pay, coverage, and inclusion are design decisions
Compensation
The proposal’s stated intention is that salaried pay should not fall simply because time is organised differently. Calendar rules do not make that outcome automatic. A pilot needs explicit arrangements for salaries, hourly pay, overtime, leave, and reporting periods, reviewed against applicable obligations.
Continuous services
A label of “Rest Day” cannot by itself close a hospital, utility, or transit service. Model staffing, handovers, demand, and the cost of covering every elapsed day. A rotating schedule would need its own evaluation; the calendar does not supply a ready-made roster.
Different lives and commitments
Invite people to identify conflicts with care, education, transport, religious observance, second jobs, and other schedules. Metric Rest Days move relative to existing weekdays. Preserving choice and access may matter more than achieving one uniform pattern.
This guidance describes possible future practice. It does not document an existing Metric Calendar pilot or claim that any employer or government has adopted the framework.
Measure the experience, including the costs
Agree success criteria and thresholds for stopping before the trial begins. Measure actual behaviour, rather than assuming that a calendar label produces a benefit.
- Workload: paid and unpaid hours, intensity, overtime, and missed breaks.
- People: voluntary feedback on fatigue, recovery, satisfaction, conflicts, and preferences.
- Output and service: volume, quality, errors, waiting times, and staffing costs.
- Coordination: conversion errors, missed appointments, duplicated administration, and time spent explaining dates.
- Fairness: differences in outcomes by role and the distribution of extra coverage or care burdens.
A comparison group or staggered introduction may make results more informative where feasible. Record other changes, such as new tools or processes, that could explain outcomes. Set privacy and consent arrangements before collecting participant data, and use appropriate review for formal human-participant research.
Publish the intervention as implemented, participation and attrition, the observation period, and limitations. A successful date-overlay exercise would not establish that a six-day work/rest cycle is beneficial. See the research questions.
For researchers and policymakers
Broader civil calendar reform would require public deliberation and coordination across institutions. This site does not offer a validated transition model or evidence that such a transition is justified.
A useful early contribution is smaller: test date comprehension, identify compatibility requirements, examine who bears transition costs, and compare the proposal with simpler changes to working time inside the Gregorian system.