When the hangar does your maintenance
How a syndicate that outsources everything to an engineer records the work: FlyerOS holds the engineer's release to service, it never certifies airworthiness itself.
Last reviewed
Most syndicates do not do their own maintenance. The aeroplane goes to a hangar, an engineer works on it, and a certificate comes back. FlyerOS is built for exactly that: it records what the engineer certified and returns the aircraft to service against it. It never asserts that the aircraft is airworthy on its own, because that is the engineer's job, not the software's.
You record it, you do not certify it
When the work is done, you enter the engineer's release to service against the aircraft: what was done, who signed it, and the date. FlyerOS holds that record, dates it, and lifts the aircraft back into the diary. The release is the engineer's; the system carries it, and the trail shows plainly that a person, not the software, certified the aircraft fit to fly. See releasing an aircraft to service.
The dates the hangar watches, in your view too
Even though the hangar does the work, the group still needs to see what is coming. The ARC, the next check and any directives are held against the aircraft, so an owner booking three weeks out can see the annual approaching rather than finding out when the aeroplane is away. See continuing airworthiness and the ARC.
While the aircraft is away
The moment a defect is recorded or the aircraft is sent for work, its status changes and it drops out of the diary, so nobody books an aeroplane that is in the hangar. When the release comes back and you record it, the aircraft returns to service and the bookings can resume. See aircraft status.