Skip to main content

Getting Started with BluSKY Log Books

1. Introduction​

BluSKY Log Books is a simple, intelligent way for buildings and facilities to capture daily activity, incidents, observations, service updates, and operational information in one place. It is designed to help teams log information quickly and consistently while allowing management to see what matters most without having to read through every individual entry.

At its core, Log Books does three things. First, it makes it easy for people to enter information as they work. Second, it uses AI to structure, enrich, and organize that information automatically. Third, it summarizes the activity over time so supervisors, property managers, and senior leadership can focus on the most important issues, trends, anomalies, and risks.

Log Books can be used by many different groups within a building. Security teams can use it for patrols, incidents, and shift notes. Engineering teams can use it for maintenance issues and building conditions. Property management can use it to track activity requiring attention. Vendors such as elevator companies, janitorial teams, pest control, and other service providers can use it to log work performed, issues encountered, and follow-up notes. The result is one shared operational record for the building.

The goal is not just to collect more data. The goal is to turn raw building activity into useful operational intelligence.

2. What Makes Log Books Different​

Many logging systems simply store entries. BluSKY Log Books goes much further. It is built to make logging fast for the person entering the information and valuable for the people reviewing it later.

The easiest and most natural way to use Log Books is through voice input. A user can speak naturally, and the system will interpret what was said and turn it into a structured entry. That lowers the barrier to adoption and makes it easier for users to record information while they are moving around the building.

Log Books also adds intelligence automatically. It does not just record what someone said or typed. It creates a proper title, determines the class, category, and subcategory, improves the grammar and wording, decides whether the item should be reviewed, and uses additional context such as weather and historical patterns to enrich the entry.

Another major difference is that Log Books is built around summaries, not just entries. The system automatically summarizes logs every hour, every 8 hours, every 24 hours, and over weekly, monthly, and longer periods. Those summaries highlight the most important information so management does not have to sift through large amounts of raw activity.

Finally, Log Books is part of a much larger operational vision. It can unify logs from people, vendors, and eventually building systems into one operational layer for the facility.

3. The Fastest Way to Get Started​

Getting started with BluSKY Log Books is simple. In most buildings, the initial rollout can begin very quickly.

The first step is deciding who should use Log Books. That may include security officers, supervisors, property managers, engineering staff, and selected vendors. Once you know who should participate, you assign permissions to those users or to the roles they already have in BluSKY.

Permissions are managed on a logbook-by-logbook basis. That means you can decide exactly which groups can see and use which logbooks. For example, a security role may have access to the Guard Logbook and Incident Logbook, while an engineering role may have access to Elevator, Lighting, and Maintenance logbooks.

After permissions are assigned, users can begin entering logs immediately. There is no need for a lengthy setup or complex onboarding process. Start with a small number of practical logbooks, give access to the right people, and begin capturing information. The system is intuitive enough that most users can learn the basics in just a few minutes.

A good first rollout focuses on speed and simplicity: choose the users, grant access, define the initial logbooks, and start logging.

4. Two Ways to Enter a Log​

4.1 Quick Entry​

Quick Entry is the fastest and easiest way to enter a log. It is designed for people who are actively moving through the building and need to capture information with minimal friction.

In Quick Entry, a user simply speaks naturally. The AI listens to what was said, interprets the content, and handles the structure automatically. It determines the best title, assigns the class, category, and subcategory, decides whether the item should be marked for review, and rewrites the content into a clear, organized entry.

This makes Quick Entry ideal for security personnel on patrol, engineers checking equipment, vendors performing service work, or anyone who needs to document something quickly while staying focused on the task at hand.

For most users, Quick Entry should be the default method of using Log Books.

4.2 Manual Entry​

Manual Entry gives the user more control over the creation process. It can still be used with typed input or spoken input, but it presents more of the entry structure on screen and allows the user to include additional supporting material.

Manual Entry is especially useful when the user wants to add attachments such as photos, video clips, scans, statements, or incident-related documents. It is also helpful when a user wants to review or refine the information before saving it.

Even in Manual Entry, AI still does the heavy lifting. The user does not have to manually define every field. The system still attempts to determine the title, category, subcategory, review status, and best wording based on what the user types or says.

Manual Entry should be used when more detail, control, or evidence is needed. Quick Entry should be used when speed is most important.

5. What AI Does Automatically​

One of the most important things to understand about BluSKY Log Books is that AI is not an optional extra layered on top of a manual process. It is central to how the system works.

When a user enters a log, the AI interprets the content and transforms it into a structured, usable record. It generates a meaningful title, places the entry into the most appropriate class and category, and improves the writing so that it is clearer and more consistent.

This is important because building logs are often entered by different people with different writing styles, different levels of detail, and different terminology. AI helps standardize the data so that it becomes easier to search, summarize, and review later.

AI also evaluates whether an item should be reviewed by management. It uses the wording of the entry, the context of the event, and the historical patterns it has seen over time to help determine whether something should be elevated.

Over time, AI adds increasing value because it can compare new information to prior building activity. It can tell the difference between what is routine and what is unusual. It can identify patterns, correlations, and anomalies that would be difficult for users to see by reading entries one at a time.

In short, AI takes raw human input and turns it into structured operational intelligence.

6. Weather and Context Awareness​

BluSKY Log Books is connected to the weather service, and weather information is incorporated into log entries automatically. This adds important context to what is happening in the building.

For example, a slippery floor issue, heavy lobby traffic, delayed building operations, or certain types of alarms may mean something different on a clear day than they do during rain, snow, ice, or wind. By capturing weather with the entry, the system can better understand the conditions surrounding the event.

Weather is also considered in summaries and in AI analysis. If the system sees that incidents are occurring under certain environmental conditions, it can account for that and surface it in trend analysis or risk evaluation.

The benefit is that the logs become more than a list of isolated events. They become part of a contextual operational picture. Users do not have to manually look up the weather or add it each time. The system does that automatically.

7. Automatic Risk Assessment​

Log Books automatically calculates risk. This is not something users have to score or manage themselves.

The system evaluates the information in each entry together with historical behavior, known trends, prior events, anomalies, and environmental context such as weather. It looks for what is normal, what is recurring, what is unusual, and what appears elevated relative to the baseline for that building or type of activity.

If something is anomalous or if it fits a pattern associated with increased concern, the system can elevate the perceived risk automatically. If something happens frequently and appears routine, the system can treat it differently than a rare or unexpected event.

This matters because most building teams do not have the time to manually assess risk for every issue they log. Log Books gives them a smarter operational layer that is constantly comparing current events to historical context and highlighting when something deserves greater attention.

As more information is collected over time, the risk model becomes more useful because it has more history to compare against.

8. Understanding the Main Screens​

8.1 Log Screen​

The Log screen is the main working area for individual entries. It shows the list of logs that have been entered, along with filters and search tools that make it easy to find what you need.

Users can filter by date, log type, status, and review conditions. This is where supervisors and managers can narrow the list to items needing attention, and where operational users can find past entries to review or update.

The Log screen also provides access to New Entry, Quick Entry, and status-related actions. In many buildings, this will be the primary working screen for frontline users.

8.2 Log Entry Detail Screen​

The Detail screen shows the full content of an individual entry. It includes the original entry, the AI-enhanced version, the associated metadata, attachments, and any amendments that were added after the original submission.

This screen is important because it preserves the operational record in a complete and reviewable form. It allows supervisors and managers to understand exactly what was captured, how it was interpreted, and what follow-up was added later.

8.3 Create Log Entry Screen​

The Create Log Entry screen is where a user can enter a new log manually. It includes the user description area, the AI description area, generation tools, and the ability to add attachments.

This screen is useful when a user wants to provide more detail or more supporting material than they would in a quick voice submission.

8.4 Quick Entry Modal​

The Quick Entry interface is designed for speed. It is the fastest path from observation to recorded entry. The user taps, speaks, and submits. The AI handles the organization.

This is the best place for most new users to start because it demonstrates how easy the system is to use.

8.5 Summaries Screen​

The Summaries screen is where management gets the greatest value from Log Books. It displays summaries by time period, such as hourly, 8-hour, daily, monthly, quarterly, and baseline summaries.

Rather than forcing a manager to read through large volumes of entries, the system condenses them into structured, readable summaries that highlight the key issues, trends, anomalies, and changes in risk.

8.6 Summary Review Screen​

The Summary Review screen provides the details behind a summary. It may include the summary narrative, aggregated statistics, risk information, environmental context such as weather, and other relevant correlations.

This is where a manager can review the intelligence that was produced from the underlying activity and decide whether to take action or drill deeper into the raw logs.

8.7 Dashboard (Forthcoming)​

A dashboard view is planned as a forthcoming addition. The dashboard will provide a higher-level operational overview across all logs, including counts, rollups, and building-wide activity summaries.

This will make it even easier for management to see the overall state of the building at a glance.

8.8 Reports and Analytics​

Reports and analytics will expand over time depending on the types of logbooks and systems involved. Some logs, such as reader logs, alarm logs, and other subsystem logs, may include additional reports and analytics as they are integrated.

As more operational areas roll into Log Books, the reports and analytics layer will become broader and more valuable.

9. Attachments and Supporting Evidence​

Log Books allows users to attach supporting material to entries. This can include images, photos, videos, live video references, scans, statements, incident-related files, and other relevant documents.

Attachments make the log more useful because they provide evidence and context beyond the text description. A photo of damage, a video clip of an incident, a scanned statement, or a supporting document can help clarify what happened and strengthen the operational record.

This is especially useful for incident review, maintenance issues, vendor documentation, and any situation where management may need more than a written note.

Attachments are typically best handled through Manual Entry, where the user has more control over what is added to the record.

10. The Review Workflow​

Log Books supports a review-driven workflow that makes it easier for management to focus on exceptions.

An entry may be marked for review automatically by AI if the content appears important, unusual, or higher risk. A user can also manually indicate that something should be reviewed. This gives the building a very simple way to elevate the items that matter most.

Once entries are marked for review, managers can filter specifically for those items. Instead of reading everything, they can focus on the subset of activity that needs attention.

This is one of the most practical features in the system. It creates a management-by-exception workflow. Frontline users keep logging as normal, AI helps identify what matters, and leadership can quickly review the most relevant items.

11. Where Different Users Should Spend Their Time​

11.1 Frontline Staff​

Frontline users should spend most of their time entering logs. Their job is to capture activity as it happens using Quick Entry or Manual Entry. They should focus on being accurate, timely, and consistent. Voice should generally be their first choice because it is the fastest and easiest.

11.2 Supervisors​

Supervisors should review flagged items, monitor shift-level activity, and ensure that important events are being followed up properly. They may use both the Log screen and the Summaries screen, depending on the situation.

Supervisors are often the bridge between entry-level activity and higher-level management review.

11.3 Property Management and Senior Management​

Property management and senior leadership should spend more time in Summaries than in raw logs. The summaries provide the best way to understand the building's operational picture without having to read every individual entry.

Managers should review daily, weekly, and monthly summaries regularly. Raw logs should be used when more detail is needed or when something in a summary needs to be investigated further.

12. Why Summaries Matter Most​

The real power of Log Books is not simply that it stores entries. The real power is that it summarizes them intelligently.

Summaries are generated automatically at regular intervals, including every 1 hour, every 8 hours, every 24 hours, and over longer periods such as weekly, monthly, quarterly, and beyond. Each summary reduces a large amount of raw activity into the most important information.

The summaries highlight what happened, what matters most, what may be trending, what appears anomalous, what risk may be changing, and what management should review. They also account for contextual information such as weather and historical patterns.

This means management can spend its time on the information that actually matters instead of reading through every note entered throughout the building.

For most buildings, summaries should become the primary management view of Log Books.

A successful first rollout should be simple and focused. Start with one building or one operational group. Identify the first users who should have access. Assign permissions by role and by logbook. Then choose a small number of useful logbooks to launch first.

A strong initial set might include Guard, Incident, General, Elevator, and Maintenance. That gives the building a meaningful operational baseline without making the rollout too broad.

Once the system is live, encourage users to use Quick Entry and voice as much as possible. Teach supervisors how to filter for review items. Teach managers to focus primarily on summaries.

Avoid overcomplicating the first phase. The fastest way to see value is to start using the system and let the building develop its logging habits naturally.

14. Permissions and Access Control​

Permissions are central to how Log Books is deployed. Access is controlled on a logbook-by-logbook basis, so buildings can decide exactly who can see and use each logbook.

This makes the system flexible. A security role can be allowed into one set of logbooks, engineering into another, and vendors into only the areas relevant to their work.

The easiest deployment method is usually to update existing roles. If a building already has security, engineering, and management roles defined in BluSKY, those roles can simply be given access to the appropriate logbooks.

The process is straightforward: identify the users or roles, assign allow or deny permissions per logbook, and begin logging.

When starting out, choose logbooks that solve immediate operational needs. A good initial set often includes:

  • Guard — for patrol and operational notes.
  • Incident — for important security or building issues.
  • General — for broad observations or activity that does not fit elsewhere.
  • Check-in — for recurring routine actions.
  • Lighting — for lights-out or lighting concerns.
  • Elevator — for elevator checks, complaints, and issues.
  • Maintenance — for repairs, service work, and building conditions.
  • Vendor or service logbooks — for external providers.

Buildings can always expand later. The best first phase is the one that gets people using the system right away.

16. Using Log Books Across Building Teams and Vendors​

Log Books is not limited to one department. It can be used across the full building ecosystem.

Security can record incidents and patrol activity. Engineering can record equipment conditions and maintenance issues. Property management can track follow-up items. Cleaning vendors can note completed work or concerns encountered. Elevator vendors can document service activity. Pest control and other third-party vendors can log their visits, work performed, and observations.

This creates a single operational record across many different sources. Instead of having separate notes, emails, spreadsheets, and verbal updates scattered across different teams, the building can capture activity in one system.

That unification is one of the biggest long-term benefits of Log Books.

17. The Bigger Vision​

Log Books begins by capturing information from people, but the larger vision is much broader. Over time, it becomes a unifying intelligence layer across the building.

In addition to human-entered logbooks, building systems will have their own logbooks and summaries. These may include systems such as video, snapshots, readers, alarms, elevators, visitors, vendors, occupancies, intercoms, maintenance, and system logs.

Examples include SeenIT for video cameras, ReadIT for card readers, RingIT for alarms, ElevateIT for elevators, SpeakIT for intercoms, MaintainIT for maintenance and work orders, and others.

These system-specific logbooks can roll up into broader subsystem views, security and life safety views, and ultimately into a unified building logbook.

That means Log Books is not just a place to store notes. It is the beginning of a building-wide operational intelligence platform.

18. Best Practices​

Use voice entry whenever possible. It is faster, easier, and more natural for most users. Let AI do the work of structuring the entry.

Use Manual Entry when attachments or additional control are needed. Add supporting evidence whenever it improves the value of the record.

Encourage users to log events close to when they happen. The more timely the entry, the more useful the record.

Use review flags deliberately. They are one of the simplest and most powerful ways to make sure the right items get management attention.

Train supervisors and managers to live in the Summaries screen rather than relying on raw logs for day-to-day awareness.

Start with a small number of logbooks and expand based on operational value. It is better to begin simply and build from actual use than to design too much upfront.

Treat Log Books as an operational system of record. The more consistently it is used, the more valuable its summaries, trends, and risk analysis become over time.

19. First 30 Days Checklist​

During the first 30 days, the building should focus on establishing basic usage and management habits.

Make sure the building or operational group has been selected. Confirm the initial users and roles. Assign permissions to the right logbooks. Define the first logbook types to use.

Test Quick Entry and Manual Entry. Make sure attachments are working properly. Confirm that review filtering works the way the building expects. Begin using daily summaries and establish at least a weekly management review process.

Collect initial feedback from users and supervisors. Find out what categories are working well, where more clarity may be needed, and whether additional logbooks should be added.

The first month is about adoption, consistency, and creating the habit of logging and reviewing.

20. Conclusion​

BluSKY Log Books makes it easy for buildings to capture operational activity, enrich it with AI, and surface what matters most. It is simple to deploy, easy to use, and powerful over time.

Frontline teams can log information quickly through voice or manual entry. AI handles the structure, categorization, weather context, review logic, anomaly detection, and risk evaluation. Supervisors can review flagged items and shift-level activity. Property managers and senior leadership can rely on summaries to understand the building without reading every entry.

As usage grows, Log Books becomes more valuable. It becomes the shared operational memory of the building and, over time, the unified intelligence layer across teams, vendors, and systems.

That is what makes BluSKY Log Books more than a logging tool. It is a smarter way to operate a building.